Describe the problem in writing
Everything starts with a written brief: the contact form or the assistant on this site. Plain words are enough — 'we miss half our calls after 6pm' or 'support spends all day on where-is-my-order'. No call, no calendar link, no discovery meeting.
A written proposal within one business day
You get scope, a fixed price, the delivery date and the expected monthly run cost on your own accounts — on paper, before you commit. The proposal is the contract; the brief does not drift.
Build, 2–6 days
Most single-role agents, assistants and automations ship in two to six days from an approved proposal. Progress arrives in writing; questions come batched, not as meetings. Approval gates are designed in from the first day.
Recorded demo, then the balance
You watch your system working on video before the balance is due. Rewatch it, forward it, decide slowly.
Handover — or the retainer
Code, accounts, keys and plain-language docs are handed over; you can run it without us. If you would rather we kept it running, the AI Operations Partner retainer takes over from there.
Questions
Do you ever need a call?
No. Calls are where scope gets vague and prices get invented. Everything we would say on a call survives better in writing — so that is where it lives.
What if my need is unclear?
Describe the symptom. The written reply tells you which service fits, what it costs, or — honestly — that you don't need us.