Eight weeks. I build a custom AI system around the way your business already runs, on your accounts, permissioned for your team, with a log of everything it does. You own the whole thing at the end of week eight.
Six examples of the kind of thing that comes out of the eight weeks. Each one runs on a Tuesday without anybody thinking about it, which is the only test that matters.
A new enquiry lands
It reads the enquiry, pulls up the history if that name has been in before, and drafts the quote against your price list and your terms. It flags the two things the enquiry didn't tell it. The draft is sitting in your inbox with a one line summary. You check the number and hit send.
An invoice goes past due
Every unpaid invoice in your accounting system gets watched. A light nudge at seven days, a firmer one at fourteen, and it comes to you at thirty. Written in your voice, stopped the moment the payment clears, and it never chases the client you told it to leave alone.
06:00, every Monday
Built from live numbers instead of somebody's memory of the week. Won, lost, shipped, late, invoiced, owed. Who is over capacity, and the three things that need you to decide something. One page, in your inbox before you open the laptop.
A call ends
The notes get filed against the right client. The decisions land on the project. Everything anyone promised becomes a task with an owner and a date. The follow up email is drafted before you're out of the car park.
A client signs
Project opened, folders created, welcome pack out, kickoff booked against real availability, deposit invoice drafted. You get one message: Anika is live, kickoff Thursday 09:00, invoice ready for your sign off.
Someone on your team has a question
They ask the system instead of asking you. It answers out of your actual documents: your pricing, your process, what you decided in March, what you promised this client in the contract. When it doesn't know, it says it doesn't know.
Week one is where I trace how a job actually moves through your business, from first contact to paid, and we pick what gets built and in what order. Usually four to six systems, plus the layer they all stand on: your clients, projects and money in one place, wired into the tools your team already opens every morning.
The routine runs on its own. Anything that leaves your business, money or a message to a client, waits for a human yes. You choose where that line sits, system by system, and you can move it the day you decide to trust something more.
I don't vanish for two months and come back with a finished box. Each piece goes in one at a time and starts working the week it's built, so you can feel the thing growing rather than take my word for it.
Eight per four week cycle. After the week one session, that is the entire demand on your diary.
One thing being built at a time. Nothing sits half finished, and you always know exactly what is next.
From starting a development to it running in your business. That is the ceiling, not the average.
A working session with you and the people who actually do the work. I trace how a job moves from first contact to paid, and where the hours disappear. It ends with a list: what gets built, in what order, and what each one is worth to you.
The layer everything else stands on. Your clients, projects and money in one place, connected to the tools you already use, with roles and access set to match your team. Built inside your own accounts from day one, so even the work in progress is already yours.
One development at a time, in the order we agreed, each one in use within seven days of starting it. Your team learns each piece as it arrives, which beats a training day at the end that everybody forgets by Friday.
Keys, documentation, and a walkthrough of every piece with whoever is going to own it. Then I step back and it keeps running.
A seven day turnaround is only a promise worth making if I'm not spread across ten businesses at once, so I take three builds a quarter and no more. It also means the calendar is usually the thing that decides when you can start, not the paperwork.
Fixed and agreed in writing before week one starts. No hourly billing, no scope creep, no line items at the end that you never saw coming.
$5,500
USD, total
Two payments across the eight weeks. Half to start, half at the midpoint.
$4,950
USD, total
One payment up front, ten percent off. Same build, same scope, same eight weeks.
Nothing switches off when I walk out the door. The system is yours and it carries on. If you want me to stay involved there are two ways to do it, and you pick which one you're on at the start of every cycle.
| Fixes to what's built | New development | Price | |
|---|---|---|---|
| Upkeep | Inside 48 hours | Not included | $500per 4 week cycle |
| Extensions | Inside 48 hours | 7 to 10 days | $2,000per 4 week cycle |
Both tiers include a call a week, plus the ports and model upgrades for when something changes upstream. Move between them whenever you want, or stop, and everything you own keeps working.
Two calls a week covers the build for most people. If you want more, extra sessions are $200 for sixty minutes, or four of them for $600.
Billed straight to your account by the provider, at cost, because the system runs on your accounts. I take no margin on it and I'll show you the meter during the build.
There's no subscription here that you rent until the price goes up. I build the system into your business, hand it over, and if we stopped working together tomorrow it would run on Monday exactly the way it ran on Friday.
Because it's built inside your own accounts, your data never moves into mine. It stays exactly where it lives today.
I sign a confidentiality agreement before I look at anything. If your industry has rules about client information, I build to them.
My access is yours to revoke. Any day, with one click, during the eight weeks as much as after them.
Letting AI touch the business only works if it can't do damage while nobody's looking. Five things handle that, and they go in before any of the clever stuff.
| Clients | Projects | Invoices | Bank | |
|---|---|---|---|---|
| You | has access to Clients | has access to Projects | has access to Invoices | has access to Bank |
| Bookkeeper | has access to Clients | no access to Projects | has access to Invoices | has access to Bank |
| Account manager | has access to Clients | has access to Projects | has access to Invoices | no access to Bank |
| New hire | has access to Clients | has access to Projects | no access to Invoices | no access to Bank |
An example. Yours gets set to your roles in week two, and you can change it any day after that.
Access is set at the data itself, not by asking the AI nicely. Your bookkeeper sees the books. Your newest hire doesn't see the bank balance.
Who asked for what, what the system did, and when. You can read back any day of the last year, and so can your accountant.
Anything leaving your business needs a human to approve it, until you decide a particular system has earned the right to send on its own.
A single source of truth that belongs to you, backed up, and sitting well away from anything of mine.
You and your team see the work, the log and the approvals in one place. Everyone else carries on working where they already work.
The Build is done for you. Some people would rather have the skill than the system, and some aren't ready to put $5,500 into something they can't picture yet. Both of those are fair, so there's a second door.
The Workshop is hands on training in a group setting. Two sessions a week for eight weeks, at most eight businesses in an intake, and you build on your own real work while I'm in the room with you. Not a course, not a community, and nobody is going to coach you. You turn up and do the work with someone who has done it before.
Here's the ceiling, said now rather than in week seven. What you build there lives on your laptop, under your login. It won't hold state between runs, your team can't each have their own access to it, and there's no permission model or audit trail underneath it. That part is what the Build adds.
Start there and move to the Build within 30 days, and every dollar you paid, team seats included, comes off the Build price.
Nothing renews on its own. Another eight week block is $1,500 a seat if you want to keep going.
Three builds a quarter.
That's the whole capacity, and it's the reason the seven day turnaround is worth anything. So the next step is a call, and the call is genuinely a working session.
Bring the part of your week that irritates you most. By the end you'll know what the first three systems would be, roughly what each one is worth to you, and whether the eight weeks is the right move at all. If it isn't, I'll tell you on the call rather than sell you something.