I’m Charles.

I follow marketing problems past the edge of the channel, to wherever they actually break.

You've probably shipped a campaign the report called a win, but in the next meeting nobody could point to a dollar it moved. I've sat in that meeting.

The Handoff Split

Early in my career, I thought marketing's job ended once demand was generated, so we handed lead batches to sales, sure the campaign numbers looked strong.

But in pipeline reviews, sales looked at the same records and saw noise, while marketing saw qualified pipeline. Nobody had touched the leads. The two teams meant different things by them.

Neither team could see past its own dashboard, so no slide deck could explain why numbers that looked strong weren't turning into sales. That's why I started reading the CRM audit logs and writing SQL against the raw tables, to see for myself what happened to a lead after we handed it over.

Where Marketing Usually Stops

Most of the marketing I've worked around runs in the same closed loop. The agency writes the brief, buys the media, and hands over a traffic report without asking what happened after the click. When revenue stalls, the usual answer is more: a bigger budget, new creative, or a complaint that sales mishandled the leads.

But your customer doesn't know where marketing ends and operations begins. If a lead sits in a queue for days, the click you paid for mostly helped your competitor. If you rank first for people who can't afford the service, the traffic doesn't pay for anything.

I call this Market-Side Building: taking responsibility for what happens when the work meets the market, and following the problem past the channel that produced it.

What I Do

When the report and the sales team disagree, somebody has to go and look. I do that three ways.

1. Operator. I trace where demand breaks down between marketing, sales, and operations.
2. Builder. I write the SQL, the Python, and the site code myself, so I can check what happened without waiting for someone's summary of it.
3. Record-keeper. I log my own confident calls and check them later. The manifesto shows what that record found.

What I Tell Clients Anyway

The first time looking past the channel cost me something, my job was SEO at an agency. For some clients, the rankings turned into leads. For others, the same work brought nothing, so I looked, and the reason usually sat outside my job: bad reviews, or calls nobody answered.

We'd been hired to fix the channel, but the problem was in how the business ran, and at first I was distraught about it.

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.

Where to Go Next

If this sounds like your work too:

• The Manifesto: the six months I spent checking my own confident calls, and what the record showed.
• The Values: the six things I hold my own work to, and what each one cost me.