One process at a time, wired into the WhatsApp, email and spreadsheets your business already runs on.
02:14
Is the white GT still available?
It is - I've got it in stock right now. Want me to put you in with someone in the morning?
None of it is hard. It is just constant, and it takes the hours you would rather spend on the part of the job you are actually good at.
A workflow does that job at 2am, in whatever language the message arrived in, and tells you when it needs you.
It is a real sequence, which is why it is numbered.
Week one
We pick the one process that costs most and breaks least. You keep the map whether or not you build anything.
One workflow
One workflow, end to end - your rules, your copy, your tone of voice. Not a platform nobody finishes rolling out.
Your accounts
Your number, your inbox, your sheet. Nothing gets migrated and nobody learns a new tool.
After launch
Real conversations break things no specification predicts. Fixing those is where most of the work is.
Each one is a bounded workflow with a fixed scope and a fixed price. Not a platform.
Built for
Plumbers, electricians, HVAC and field trades
A call goes unanswered on site, and within a minute the caller has a text that knows your hours, answers the obvious question and offers a slot.
Tier
Build
Built for
Restaurants, salons and auto repair
The job closes, the request goes out at the hour that person is most likely to reply, and the unhappy ones get flagged to you instead of to Google.
Tier
Build
Built for
Dentists, law firms and estate agents
A lead arrives from any channel, gets answered in under a minute, and gets chased three more times before it is left alone.
Tier
Run
Built for
Gyms, clinics and med spas
It finds the customers who quietly stopped coming, reads what they used to book, and reaches out at thirty, sixty and ninety days with a reason rather than a discount.
Tier
Run
Built for
Roofers, painters and landscapers
You send ten estimates a week and chase none of them; this one checks in on day two, five and ten, and answers the objection instead of repeating the price.
Tier
Build
Built for
Clinics, med spas and home services
Every call answered around the clock in a real voice, qualified, and put in your calendar before you have finished the job you were on.
Tier
Run
Built for
Contractors, agencies and multi-site businesses
Leads, scheduling, invoicing and reporting stop being six tools that do not talk, and start being one system that does.
Tier
Run
The question that comes up on every first call, answered before you ask it.
If it has an API, it connects. If it doesn't, there is usually another way in - a browser step, an export, a shared inbox. Which route yours takes is settled at mapping, not after you have paid for a build.
100%
of enquiries answered without a salesperson
Every enquiry landed on one WhatsApp number at any hour, in Arabic, Russian, Hindi or broken English, mixed in with people selling cars, people wanting jobs, and people wasting time. The sales team answered all of it by hand.
55 conversations and 534 messages in four weeks, each one labelled by type and on the record instead of living in somebody's phone.
Audit and Build are one-off. Run is monthly, with a three-month minimum term.
Quoted and invoiced in US dollars for clients outside the UAE. VAT is added only where it applies.
$275 one-off
Lead offer
$2,050 setup + $350/mo
$1,350/mo
No asterisks. If a row says a thing, it's in that tier.
| Included | Audit$275 one-off | Build$2,050 setup + $350/mo | Run$1,350/mo |
|---|---|---|---|
| Scope | |||
| Who it is for | A business that needs the right first use case | A business that knows the problem and wants one workflow live | A business that wants the lead process actively owned |
| Process-mapping session and priority report | Included | Included | Included |
| Build | |||
| One workflow built and live | —Not included | Included | Included |
| WhatsApp, Instagram, email or web-chat connection | —Not included | One channel included | One primary channel plus agreed integrations |
| Business answers, escalation and bilingual handling | —Not included | Included | Included |
| Additional workflow | —Not included | $525 setup each | Included only within the active-workflow cap below |
| Ongoing | |||
| Monthly tuning from real conversations | —Not included | First 30 days only | Included |
| Change requests | —Not included | Up to 2 inside the 30-day tuning window | Included within the monthly improvement cycle |
| Response-time / accuracy reporting | —Not included | —Not included | Included monthly |
| Sensible guardrail | —Not included | One live workflow; up to two integrations | Up to three active workflows, one agreed improvement cycle monthly |
| Delivery | |||
| Timeline | 3 business days after the session | 10 business days after approved copy/access | First workflow live in 10 business days; then ongoing |
Written as documentation, not marketing. The difference is what happens after the invoice.
Live on your own accounts by the end of the build. Not a demo, not a template you finish yourself.
One document per workflow: what it does, what triggers it, what it will never do, and what happens when it fails.
You do. Every API key, account and number is in your name and on your billing from day one. Stop working with me tomorrow and nothing switches off.
There is no published response-time guarantee - I will not publish a number I have no system behind. What is committed is the reporting:
Every tier states its cap in writing before anything is built, so scope is a table row rather than a conversation in month three:
The workflows keep running. The tuning, reporting and changes stop. You keep what was built and the accounts it runs on.
Answered flat, including the two that are easier to dodge.
A VA is a person, so they sleep, take holidays and eventually leave with everything they learned in their head. A workflow answers at 2am in whatever language the message arrived in, and what it knows is written down. The honest version: a person is better at judgement and a workflow is better at volume and hours, so most businesses end up wanting both. This one is the cheaper half to keep.
That is the part that gets the most work. The rules a bot can never break run as code after the model has spoken, not as instructions inside the prompt, so a reply that trips one never goes out and the conversation goes to a human instead. Price negotiation, complaints and anyone who asks for a person are handed over by default rather than answered.
No. It connects to the accounts you already have - your messaging number, your inbox, your spreadsheet - and nothing gets migrated. If a tool you depend on genuinely has no way in, you will hear that during the mapping session, before there is anything to pay for.
You do, all of it. Every API key and every connected account is created in your name and billed to you, and the conversation data lives in your systems rather than in a platform of mine. There is nothing to migrate away from later because there was never anything to migrate away from.
On Build, the workflow carries on running and the included tuning window closes; you can leave it alone or move onto the monthly tier later. On Run, the first 30 days is just the first month - tuning from real conversations, monthly reporting and one agreed improvement cycle continue for as long as it runs.
I am in the Gulf, so I overlap with Europe for most of the working day and with the US east coast through your morning. Calls happen in your window rather than mine. The workflows themselves do not care what time it is, which is most of the reason to have them.
Because the first thing that happens is not software, it is a session where your process gets mapped, and that is real work whether or not anything gets built afterwards. The Audit is the closest thing to a trial: it is the cheapest way in, you keep the map and the priority report, and if you go on to build, that step is already done.
Tell me the one job you would hand over first.
