Somebody has to go and look.
Sure Is a Feeling
You've said "I'm pretty sure about this" in a planning meeting, and the room moved on.
So have I, for more than twenty years, in-house, at agencies, and as a consultant. I picked up code, data, and analytics along the way because the problems required it.
You've probably trusted someone because they had been doing the job for twenty years. I was that someone, and I trusted myself the same way.
I believed those years had turned my instincts into judgment. I trusted them on sight, and so did the room.
I never checked. In the rooms I've been in, almost nobody goes back later to check a call they were sure about. Then I did.
The record
From April to September 2025, I wrote my calls down. Each time, I noted what I decided, how confident I felt, and what I expected to happen. Then I went back and checked.
Sixty-five of those calls I'd marked ninety percent sure.
Thirty-eight were right.
Fifty-eight percent.
Nothing felt off while it was happening. I was just as sure on the calls that failed as on the ones that landed.
The feeling never changed. Only the record could tell them apart.
The record also showed what I couldn't see from inside. I was overconfident about people and underconfident about technical calls. I rushed the choices I could undo, and I agonized over the ones that barely mattered.
Twenty years hadn't fixed any of that. They had only made me more sure.
The same call, with more people agreeing
My journal caught me making unchecked calls. Then I saw the same call in the planning rooms I'd sat in.
The deck is clean, the logic holds, and everyone agrees. An approved plan makes the same call my journal caught, only with more people agreeing to it.
And now a model can write a plausible plan in seconds. The plans got cheap. Checking them didn't.
Most of the marketing I've worked around runs in a closed loop. The agency writes the brief, buys the media, and hands over a traffic report, and nobody asks what happened after the click.
When revenue stalls, the answer is more: a bigger budget, new creative, or a complaint that sales mishandled the leads.
The loop grades its own work. Its product is the report, and the report decides what the client gets to see.
I know that loop from the inside, because I handed over those reports myself.
A report records what the work did. The market records what happened.
I work on the market side, where the record is. I call it Market-Side Building. It means taking responsibility for what happens when the work meets the market, and following the problem past the channel that produced it.
Anyone who works this way is one of us.
What the report left out
What does that look like with a real client?
Early in my career, most of my work was SEO at an agency. I once ran the same SEO for two clients and got the same rankings for both.
One grew. The other never saw a return it could trace, and by the end they didn't believe the SEO had done anything.
The report was right both times. It measured the channel, and the problem sat outside it.
The client who grew was already doing the rest: outreach, email, brand advertising, their own reputation. The other was ranking for an audience that was never going to buy. Bad reviews sat between a good ranking and a real decision.
We'd been hired to fix the channel, but the problem was in how the business ran. At first I was distraught about it.
On a campaign of my own, the dashboard said the leads were qualified and sales said they were junk. I read the CRM audit logs and wrote SQL against the raw tables.
Both reports were true. The buyers were real, and they weren't ready to buy that quarter.
That's the Builder half of the name. I build the check myself, and when the market says I was wrong, I build again.
What I do now
So now I tell clients before they find it themselves. I'd rather say what they don't want to hear and lose the account than manage what they see.
You could call that bad business. Clients pay for confidence, and hard news costs accounts. Sometimes it does.
But I know what my confidence is worth without a record. Fifty-eight percent.
When a recommendation fails, my name is still on it. That's the fair exchange: owning the downside of what I told you to do, not just the credit when it works.
I trust a documented record over a confident veteran now, including when the veteran is me.
I still say "I'm pretty sure."
Now I write it down.
People like us work differently
We didn't get certified in this. We built a stance toward the work: care about the outcome more than the department, treat frameworks as maps, and expect the plan to change on contact with reality.
If that's familiar, the fuller version of what we stand for, and against, is written down.
Choose a trail
You've already been inside two or three of these. Here's the shape of the whole territory, named as five questions this site keeps returning to.
The Market. How do we get closer to reality? Customer understanding, demand, salience, the gap between the map and the ground.
Start with the Perception Engine →
The System. What is actually constraining the outcome? Handoffs, sales, operations, the information that gets lost between them.
Start with Proof of Transfer →
The Mind. How do people move from one belief to another? Decision-making, narrative, the customer's own journey.
Start with Confidently Wrong →
The Machine. What changes when intelligence becomes infrastructure? AI, agents, data, automation.
Start with Order Beats Presence →
The Craft. How do we turn thinking into things that survive contact with reality? Building, testing, learning, doing it again.
Start with Completion Isn't Contribution →
I write from the territory
Ideas I'm still working through. Patterns I'm noticing. Questions that won't leave me alone.
I send the ones worth sharing by email. If that sounds useful, you're welcome to join.
Or keep exploring. Everything here stays open either way.
A little about me
I've spent more than twenty years in marketing, in-house, agency, and consulting, and picked up code, data, and analytics along the way because the problems required it.
This site is where those interests meet: how a business actually touches its market, and what it takes to get close enough to that reality to build something that survives it.
The map helps. The market decides. I build accordingly.
