Chasing what you are owed
Invoices past their date, chased on a schedule in your tone, with the awkward ones handed to a person before they sour.
Built round the job you name
Whatever takes up your week, we can build a team around it. Tell us what needs doing: we build the seats, give them the tools, connect them to the systems you already run on, and set the rules they work inside.
Written for you, and yours to change. Every line is a sentence, not a setting.4 seats
Real asks, not a menu
None of these started as a product. Each one started as somebody saying what was eating their week.
Invoices past their date, chased on a schedule in your tone, with the awkward ones handed to a person before they sour.
The back and forth to find a time that suits, done over text and email, your diary updated the moment it lands.
A customer sends a picture. It reads the job, prices it off your own rate card, and puts the quote in front of you.
A shift drops out. It works down the people who could cover it until one says yes, then updates the rota.
Reading the post, answering the routine, and passing on what genuinely needs a person, with the thread attached.
If one job is quietly costing you a day every week, it is probably the one worth building first.
From a sentence to a working team
The same four steps every team goes through, whether it is one we have built fifty times or one nobody has asked for before.
Not a flowchart, not a spec. The job in the words you would use with a new starter on their first morning. One or two sentences is enough to start the conversation.
The sentence at the top of this page is a real one.
The seats, what each one does, the tools it gets, and the systems it reads and writes. What it handles on its own, and what always comes to you. You change any of it on the call, before a line of it is built.
An orchestrator and agents, shaped around your job rather than a template.
Your website, your policies, the work you have already done, all of it read inside your own account. None of it trains anyone else's model and none of it is shared with another customer. Then it is rehearsed on real situations from your own history, with nothing connected to the outside world, and you watch it play through them.
Nothing reaches a real customer during a rehearsal, and nothing it learns leaves your business.
Day one nothing goes out until you say so, and every draft comes with the reason it chose that answer and where it got its facts. You let go of one kind of job at a time, once you have seen it get that kind right enough times.
Starting supervised is the default, not an option you have to go and find.
Before the first call
You do not need a brief, a process map or a shortlist of tools. You need to be able to describe the job and say where the line is.
What needs doing, how often, and what going wrong looks like. Two sentences beats two pages.
The systems it would need to read and write: your diary, your inbox, your job sheets, whatever you run on.
What it can do on its own, and what always waits for a person. Money and promises usually sit on your side of it.
An hour or two of the person who does it now, while it learns. They are the ones who spot what it has got wrong.
You stay in charge
It runs on its own. These four things stay yours, and every one of them is a switch or a screen in the product.
Start with everything past you. When the "is my phone ready" replies are always right, let those go out on their own and keep checking the rest. Refunds never stop waiting for you.
Typical approval rate, illustrative: about 70% of replies approved unedited in week 1, about 90% by month 3. The spending limit shown is an example. Our name for the queue is approvals; the limit is a spending cap.
Every team is built round the way you already work: your systems, your tone, your rules. Tell us what needs doing and we will show you what it would look like.