Start with a map, not a leap of faith.
The Opportunity Map is a fixed-fee day, $950, that finds where admin is eating your week and tells you what getting those hours back is worth. I spend the day alongside you and whoever else does the work, then you get a plain-English document ranked by impact, effort and payback. Commission a build afterwards and the full $950 comes off the price.
Your Opportunity Map
Worked exampleStart top-left. Every finding lands somewhere on this map, with a number beside it. Hover a finding to see what it gives back.
What it costs, and what comes back
$950 fixed fee, credited toward your first build
- Every finding sorted by impact and effort, so each call is obvious
- Ranked by payback: what to do first, what to skip, and why
- Yours to keep, and plain enough that another developer could work from it
Commission any build afterwards and the full $950 comes off the price, so the map ends up costing nothing.
Book your mapping dayWhat actually happens.
No workshop, no whiteboard exercises, no homework beforehand. I watch the work as it actually happens, because most of the findings come from seeing someone do something by hand for the fourth time before lunch.
-
8:30am
Start where the work starts
I'm there for whatever normally kicks off your day, and nobody changes their routine for me.
-
Morning
Follow the admin, not the org chart
I track what gets typed twice, chased by hand, or held in someone's head, because whoever does the work already knows where it hurts.
-
Midday
Count the hours honestly
Every piece of busywork gets a real number: how often, how long, and who does it.
-
Afternoon
Look at the tools you already pay for
Often the fix is a feature you're already licensed for and nobody switched on.
-
Before I go
Say the obvious ones out loud
Anything clear by the end of the day, you hear that day, with nothing held back to make the document look better.
-
Within a week
The map arrives
Written in plain English, ranked by payback, with the "leave it alone" list included.
Three things, all yours.
-
A ranked list, with numbers
Every finding placed by impact and effort, with the hours it gives back and what that is worth over a year. No vague "efficiency gains".
-
A fixed price against each one
You see what fixing each thing costs before you decide anything. Nothing gets quoted after the fact, and nothing gets quoted hourly.
-
An honest "leave it alone" list
The things not worth doing, and why. This is usually the most useful page, and it is the reason the map is worth paying for rather than getting free.
The things people ask first.
What actually happens on the day?
I spend the day with you, and your team if you have one, watching the work as it actually happens rather than as it is described in a meeting. Most of the findings come from seeing someone do something manually for the fourth time before lunch. You get the map within a week.
What if you find nothing worth doing?
Then the map says so, and that is a real result. Knowing your setup is already sound is worth more than being sold a project you did not need. It has not happened yet, but the map is written to allow for it.
Do I have to buy anything afterwards?
No. The map is yours, and it is written plainly enough that another developer could work from it. If you commission a build with me, the full $950 comes off the price.
How is this different from a free consultation?
A free consultation is a sales meeting, and it ends with a proposal for whatever the seller happens to sell. This is a paid day of work that ends with a document, including the parts that say do not bother. Charging for it is what makes it possible to tell you the truth.
What size business is this for?
Small businesses, from a solo operator to a small team. Trades, clinics and small service firms are the common shape, and the day fits the business: for a solo operator it can be a sit-down over the tools you actually use and how the work really flows, and for a team it is a day on site alongside everyone. If you are big enough to have an IT department, the honest answer is that you want a firm with a team behind it, and this is not that.
Do you need access to our systems?
Not to do the map. Watching the work and asking questions is enough to find where the hours go. If a finding needs a closer look at a specific system, I will ask before touching anything.
Twenty minutes first, if you'd rather.
Tell me what's eating your week, whether that's the website, the day-to-day behind it, or you're honestly not sure yet. If the map isn't the right next step, I'll say so.