Three stages, in order. You can stop after any one.

AI Readiness Audit

One to two weeks · Flat fee · Start here

We sit down with how your business actually runs — not the org chart version, the real one. Where does time disappear? What gets done twice? What does someone do every single day that a system could do instead?

Then we work out which of those are genuinely worth automating, and which aren't. That second list matters as much as the first. Plenty of manual work is manual for a good reason, and you should know which of yours is before anyone spends money.

• A written map of the processes we reviewed, in plain language
• The two or three highest-return opportunities, ranked, with what each would take to build
• An honest list of what we'd recommend leaving alone, and why
• A roadmap you own outright — yours to keep, act on, or hand to someone else entirely

Custom Implementation

Fixed scope · Fixed price · Agreed before we start

We build the system and put it into production. Not a prototype, not a proof of concept — the actual thing, running against real work, wired into the software you already use.

Scope and price are agreed in writing before anything begins, so the number you approve is the number you pay. Changes go through a written change order rather than appearing on an invoice later.

What that usually looks like:

• Voice and phone systems — automated calls that place, capture, and route the routine conversations someone currently makes by hand
• Customer-facing assistants — trained on your own information, your pricing, your policies, not a generic model guessing
• Workflow automation — connecting tools that don't talk to each other, so the same data stops being keyed in twice
• Internal tools — the small piece of software your business needs and no vendor sells

Everything gets tested against real work before it touches production, and we're there alongside your team through launch, not handing over a login and leaving.

Ongoing Support

Monthly · Month to month · Cancel any time

Systems drift. Your business changes, a vendor changes an API, a seasonal pattern shifts and something that worked in March needs adjusting by October. Support covers keeping it working and keeping it useful.

• Monitoring, so problems surface before someone in your office finds them
• Tuning and iteration as the work changes
• A person who already knows your system when you need something changed

Month to month, with no minimum term. It should be easy to stop paying for this the moment it stops earning its keep — and if you'd rather have your own team run it, we'll document it and hand it over.