Most jobs start the same way. Someone has a business that works and they've lost track of how. It still makes money, the emails still go out, but they can't tell you which parts are pulling their weight and which are just still switched on.
Nobody can see their own business from the inside. The hard questions you can answer. It's the simple ones that go quiet: what happens after someone signs up, which channel actually makes money, what breaks first if your list doubles next month.
I know what happens when nobody looks. I watched it for ten years at fluentin3months.com, at the time the biggest language learning blog in the world, where I ended up CTO. The trouble was sitting in the data years before it landed. I could see it for the same reason I can see yours: it wasn't my business. But a warning from inside the org chart is easy to file under later, and fixing a business that still worked was nobody's job. It worked right up until it didn't, and everyone got let go. Everything about how I work now comes from that. The look has to be invited, and the fix has to be owned.
Getting you clear answers to those questions is the whole job. This is how I do it, start to finish.
What I'm actually looking for
Most systems show you a clean picture. Underneath, the real one is usually a bit different. Flip the switch.
All green. Revenue's holding. Nothing looks wrong from here.
None of this shows up on a dashboard. It only shows up when someone maps what's actually there. That someone is me.
The method
Five steps, same order every time. The first four are the audit, where I find out what's really going on. The fifth is the build, where I fix it. Click through.
1. Audit
I go through the whole system. Email platform, automations, ad accounts, analytics, the raw revenue data. Not a glance, a proper read of every moving part.
You walk away with: a complete list of what's running, what's broken, and what's quietly costing you.
One business had automations firing on rules nobody remembered writing, sending the wrong people the wrong thing for two years.
2. Map
The audit told me what's running. Now I follow a real person through it: they sign up, the welcome email lands, they click through, they hit the sales page, they buy or they don't. I draw every one of those routes the way it runs today, which is rarely how anyone remembers building it.
You walk away with: the first honest picture of your own machine, on one page.
A founder looked at the map and said "I didn't know we did that" about her own welcome sequence.
3. Work backwards
I start from what you're actually trying to achieve and trace back to where the system stops serving it. The gap between the goal and the setup is where the work is.
You walk away with: a short list of what to fix, in the order that pays back fastest.
The goal was more launch sales. The fix turned out to be a tagging problem three steps upstream that nobody had connected to it.
4. Verify
Every number I hand you traces to a source you can check. I don't guess, and I don't take a dashboard's word for it, because the dashboard is often the thing that's been lying.
You walk away with: findings you can trust, because you can follow each one back to where it came from.
A revenue rollup looked healthy until I rebuilt it from the raw rows. It had been double-counting the same sales for months.
5. Own
This is the build. A roadmap nobody owns just describes your problem in nicer formatting. If someone on your team can truly own the fix, take the roadmap and run, the audit has already paid for itself. Most teams don't have that person, it's the same hole in the middle the x-ray up top keeps finding. So I stay and put the fixes in: the strategy, the system itself, and the hands doing the work. Then we check the numbers at intervals so it keeps working after I've stepped back.
You walk away with: a business you can see, that keeps running the way you can see it.
Six months on, the owner reads her own numbers every morning and actually knows what they mean.
What working together looks like
No surprises. Here's the shape of it, from the first call to finished.
First call
I ask questions, I don't pitch. If I'm not the right person for what you need, I'll tell you on this call and save us both the time.
The audit
A fixed fee, two to three weeks. I agree the number up front. Either your tracking is solid and I show you what actually makes you money, or there are gaps and I show you what you're blind to. Either way you learn something you didn't know.
Findings
A written report and a roadmap, ranked by what pays back first. This is yours to keep whether or not we do anything else. If your team has someone who can own the build, it might be all you need.
The build
If it makes sense, I build what we agreed. The audit fee comes off the price of the build.
Review
We check the numbers at set points, so the system keeps doing its job instead of drifting back out of view.
A few things that are always true
- I don't guess. Every number I give you traces to a source you can check.
- I build for the subscriber first. Get the experience of the person moving through the system right, and the owner's numbers follow.
- I tell you both outcomes before you pay, so saying yes isn't a risk.
- If I'm not the right fit, I say so early. That's cheaper for you than a polite maybe.
- I design and write the structure; you add your voice on top. Faster than me trying to sound like you, and it stays yours.
If your business works and you can't quite see how, that's the conversation I like having. Email me directly and tell me what feels off. If nothing does, you probably don't need me yet.
A framework designer pushed me to write this down explicitly. She was right.