Inbound reply and follow-up
Classify the message, draft from an approved answer bank, route the unusual cases to a named human.
Fixed price · one workflow
One process. One clear improvement.
A build starts by mapping one real workflow, finding where time or information is lost, and agreeing a measurable outcome. You work directly with the person designing and building it.
What gets built
How to chooseIntake through to quote
One field map between the form and the document, one template, one approval before anything is sent.
The weekly numbers pack
Collect and format across your existing exports. One factual summary sentence, no narrative.
Invoice and subscription matching
Read the invoice, match it to the purchase, flag the mismatch with the line that caused it.
48hFirst working version on scoped builds
2 roundsRevisions included, each one consolidated
1 priceWritten quote before any work begins
How an engagement runs
- Call, 20 minutes. One workflow, described end to end. No slides.
- Written scope. Trigger, steps, output, approval point, and the measure we will report. Fixed price on the same page.
- Build. First working version inside 48 hours of the scope being agreed, on a non-production copy of your data.
- Two revision rounds. Each consolidated into one list, then closed. Nothing reopens silently.
- Handover. You get the workflow, the prompts and a one-page runbook.
Not offered: full-stack product builds, ongoing retainers, or anything that promises a percentage saving before the process has been measured.
Questions
What counts as one build?
One trigger, one transformation and one output, with a human approval step. If a request needs four steps, it is two builds and we say so in the scope rather than quoting one price.
Do you take retainers?
No. Each build is quoted and paid once. If you want ongoing changes, they are new builds with their own fixed price.
Who owns the code?
You do, including the prompts and the workflow definition. It runs on accounts you control, and there is no runtime dependency on us to keep it working.
What if it does not save the time we expected?
The scope names the measure before work starts — cycle time, response time or rework rate. We instrument it in version one so the answer is a number you can read, not an opinion.
Start with the workflow that annoys you most.
Usually it is not the most expensive one. The spend check names the expensive one.