Level 3: Turn the rotor
Custom-built In-house AI Automation Solutions
Systems wired into the tools you already use, and owned by you
Custom automation built against your real data and your real processes, deployed into production, documented, and handed over as something you own rather than something you rent.
- Typical duration
- Six to ten weeks per system
- Investment
- Fixed fee per workflow
- Priced per system so you can stop after one. No retainer required to start.
- Tier
- 3 of 4
The problem
Off-the-shelf automation assumes your business looks like the average of every business that vendor has sold to. It never quite fits, so your team adapts around the tool (and you end up paying a subscription for the privilege of changing how you work).
What you walk away with
A working system running against live data, integrated with your existing tools, with the code, the prompts, the configuration and the documentation all belonging to you.
Included
What you actually get
Production system
Built and deployed into your environment, not a demo that needs six more weeks to become real.
Integrations that hold
Wired into the CRM, inbox, spreadsheets and internal tools your team already lives in.
Model choice with reasoning
Frontier models where capability matters, open-weight models on your own hardware where data sensitivity or unit cost does. The trade-off is documented, not hidden.
Evaluation before rollout
Tested against real historical cases so you can see how it behaves before it touches anything live.
Safeguards and fallbacks
Clear boundaries on what the system decides alone, what it escalates, and what happens when it is unsure.
Full handover
Code, prompts, configuration and written documentation, plus a session walking your team through how to run and change it.
Right for you if
- Businesses whose best process is the one no vendor supports properly
- Teams handling volume that is growing faster than headcount can
- Owners who want to own the system outright rather than rent it indefinitely
How it runs
The shape of the engagement
-
Scope one workflow
Week 1The highest-value item from the plan. One thing, finished, before anything else starts.
-
Build against real data
Weeks 2–5Working software early, reviewed with you as it goes, so surprises surface while they are still cheap.
-
Evaluate and harden
Weeks 5–7Run it against historical cases, measure where it is wrong, and fix that before anyone depends on it.
-
Deploy and hand over
Week 8Into production with monitoring, documentation and a team that knows how it works.
One-page PDF
Eight Questions Before You Buy Another Seat
One sheet, eight questions, no email address. The things worth asking out loud before adding another per-seat subscription — what it costs at twice your headcount, whether your data can actually leave, and what you would do if the price doubled tomorrow. Put it in front of whoever signs off on software.
- Eight questions that take ten minutes
- The overlap check that finds software you already pay for
- The exit test most businesses run a year too late
- No email address required
Questions about this tier
-
You work with me directly. There is no account manager relaying your questions to a delivery team you never meet, and no incentive to stretch a six week build into six months.
The trade-off is honest: I am one person, so I take fewer clients and I will tell you if your timeline does not fit. What you get in exchange is someone who remembers every decision made on your systems.
-
Not necessarily. For a lot of workflows a frontier model is the right call and the data involved is unremarkable. For others — anything involving customer records, health information, or contract terms you are not free to share — running an open-weight model on hardware you control is the better answer.
That decision gets made per workflow, and the reasoning gets written down so you can take it to a client, an auditor or an insurer.
-
A training session can happen within a couple of weeks. An audit runs two to three weeks. A first custom build is typically six to ten weeks from scope to production.
If someone promises you a production system in days, ask them what happens when it is wrong about something that matters.
The natural next step
Dedicated Ongoing AI & Automation Support
Software does not stay finished. Models change, APIs move, your business grows. Ongoing support is what keeps a system that works this month still working next year.