Weblux builds the system.
Amber runs the daily work.
Every engagement opens the same way: the same call, the same diagnosis. Some of them end in a build. Some end somewhere else, because the build was never what was wrong.
Where Amber is right now
Amber is in closed beta and active development. A small group of owners are using it and shaping it, and we are widening what it covers with them rather than guessing from the outside. It is not generally available yet, so nothing on this page is something you can buy this week.
Better you read that here than discover it on a call. The rest of this page covers how the two companies fit together, which is true today, and what Amber is being built to do, which is the part still in progress.
A co-pilot for the businesses that run on jobs.
Amber is an AI co-pilot for service and blue-collar businesses — the trades, field service, and the operations that run on jobs rather than on documents. It is aimed at the daily running of the place: the follow-up nobody made, the call nobody picked up, the record nobody updated, the paperwork that lands three days after the work.
The line between the two companies is the line between a build and an operation. If the answer is a thing that has to exist, it is ours. If the answer is work that has to happen every day, it is Amber’s.
The work that happens away from a desk.
Catching the job while it is happening, instead of reconstructing it from memory that evening.
Turning what was said on site into the paperwork it implies, so the invoice does not trail the work by a week.
Giving the people doing the job somewhere to ask what the senior tech would have told them.
Making a business the sum of its jobs rather than the sum of what got typed up afterwards.
Written as direction, not as a feature list. The beta is where the specifics get decided, and the owners in it have more say over that than anyone arriving after launch.
One way in. One diagnosis.
Nobody picks a company off a menu and nobody picks a tier. The first three stages run the same way for every business we meet. The fourth happens to some of them.
- 01
One way in
Every engagement opens with the same call, whatever size the business is. There is no tier to pick and no form that sorts you.
Weblux
- 02
One diagnosis
We map how work moves and write down what it is costing you. The map is yours from that point on, whatever you decide.
Weblux
- 03
Two builds
The diagnosis says whether the answer is a custom build or a packaged one. We make that call, so you are not guessing about it on day one.
Weblux
- 04
The handoff to Amber
Some businesses turn out to have no build problem at all. What they have is a workflow problem, and that is what Amber is being built to take.
Amber
Signs that a build will not fix it.
The system is fine. Nobody uses it.
The portal works. The automations fire. And the follow-up still waits on somebody remembering to do it. No amount of building fixes that.
The calls are the bottleneck.
Every new job begins with a phone call, and it has to be answered by someone who is currently up a ladder, under a sink, or on a roof.
It is the same work every time.
The same sequence, the same questions, the same three messages. Run by hand, several hundred times a month.
When that is what we find, we say so. Building a portal for a company whose real problem is that nobody rings the customer back is the same error as automating a broken process. Both of them just make the wrong thing quicker.
We stay involved after the handoff.
The diagnosis travels with you. Nobody asks you to explain your business a second time.
You keep whatever Weblux has already built. Nothing gets switched off because the relationship moved house.
If Amber has not reached your trade yet, you hear that in a sentence — and you hear where it actually is.
One of us stays your point of contact. Two companies is our problem to manage, not yours.
One material, two solids. Weblux closes the seams in a business. Amber runs what moves through them afterwards.