Tell me what's eating your week. The plan is free.
You describe the task that keeps swallowing hours. I go away and research it properly, then come back with a written plan: what to build, what it costs, what it saves — and whether it's even worth doing.
No cost for the plan · No obligation to build · Usually back to you in about a week
Your assessment includes
- ✓A call about the problem — no prep needed
- ✓A walkthrough of how the work happens now
- ✓Proper research into what's actually solvable
- ✓A written build plan in plain English
- ✓Both prices up front — build fee and monthly
- ✓An honest "don't build it" if that's the answer
You know it should be automated. Nobody will give you a straight answer.
Most owners can name the job that's wasting their team's time. What they can't get is a clear answer on whether software can really take it over, what building it involves, and what it costs. So it stays on the someday list for another year.
- Someone re-types the same information into two systems every single day
- Enquiries sit unanswered overnight because nobody's watching the inbox
- Quotes take three days because one person assembles them by hand
- The same report gets rebuilt from scratch every month
- Notes and forms get written twice — once on paper, once in the system
Three steps, and you only pay at the third.
The order is the point: you see the whole plan and the whole price before any money or any code changes hands.
You describe the problem
An hour on a call, and sometimes a look at how the work gets done today. Describing it the way you'd describe it to a new hire is exactly right — no technical vocabulary needed.
FreeI research and write the plan
I work out what's genuinely solvable, what it takes, and what it's worth. You get a written document with both prices and a timeline — or a clear no, if that's the honest answer.
FreeYou decide if I build it
If it's a yes, we agree in writing what "working" means before I start — measurable, testable, no vague finish line. If it's a no, the plan is still yours to keep.
Build fee + monthlyWhat actually lands in your inbox
A document you could hand to your accountant, your partner or your board and have them understand it. Written in plain language, not model names.
- What the problem really is
Your process written back to you, with the hours it eats and where they go. Half the value is usually right here.
- What can and can't be automated
Split out explicitly. Some of it will be a poor fit for AI, and you'll be told which parts and why.
- The proposed system, in plain English
What it does, where it sits in your day, who touches it, and what happens when it gets something wrong.
- Both numbers, before you commit
The one-time build fee and the monthly fee to keep it running, plus a delivery date. No surprises after you say yes.
- The payback maths
Hours saved per week against the build fee and the monthly, so you can judge it as a business decision rather than a leap of faith.
What you're really buying is judgement.
Sometimes the answer is don't build it
AI is genuinely bad at some things and unreliable at others. If your problem is one of those, the plan says so and tells you what would work instead. That answer costs you nothing and saves you plenty.
Sometimes the fix isn't software at all
A fair share of "we need automation" turns out to be a form with too many fields, or two systems that were never connected. Cheaper fixes get named as cheaper fixes.
"Working" gets defined before I start
Not "you'll be happy with it" — an agreed, measurable standard written into the agreement, so neither of us ends up arguing about a feeling.
Why there's a monthly fee at all
The tools underneath these systems change constantly, and something built once and left alone quietly stops working. The monthly is what keeps it running and improving — month to month, 30 days' notice, no contract to sign your way out of.
The parts most people don't publish.
- The assessment
- Free, and yours whether or not you hire me. Usually about a week from our first call.
- Build fee
- A one-time fixed price to design, build and launch the system. Quoted in the plan, not hourly — so a slow week is my problem, not your invoice.
- Monthly fee
- Covers running the system, watching it, fixing it when it breaks, keeping it current as the underlying tools change, and small tweaks as your process shifts.
- Payment schedule
- A deposit to begin the build, the balance once the agreed standard is met and demonstrated. The monthly starts the day it goes live, not before.
- Revisions
- Two rounds included during the build. After launch, small adjustments are part of the monthly; genuinely new features get quoted separately.
- Cancelling
- Month to month with 30 days' notice. No annual contract, no lock-in period, no cancellation fee.
Describe the problem. Get the plan. Decide later.
Two sentences about the task that's eating your week is enough to start. Worst case, you come away with a free assessment of your own operation.
Email IRVNo cost · No obligation · Reply within one business day