The 8:53 Conversation
What Seven Years of Doing It Right Taught Me About Why It's So Hard
This is not a post about a bad client. It is a post about the gap between knowing what needs to be done and having the organizational conditions to do it — and the one thing that closes that gap before it opens.
The meeting started at the top of the hour. The other person had already begun recording before I joined. His first words were, verbatim: "This meeting is being recorded."
Eight minutes and fifty-three seconds later, a seven-year professional relationship was over. He was professional, measured, and kind about it. He said there were no negatives. He offered a reference. He mentioned they might be in touch when the budget got real. He said they'd found someone in Europe who "charges by the hour" and "does more basic stuff." He said — and this is the sentence I keep returning to — "We don't have the pressure with that person to do stuff."
I thanked him, mentioned my equity stake, offered a transition document, wished him a happy birthday. Clean exit. No argument. No defense. The decision had been made before I joined the call. My job in those eight minutes was to keep the door open and my reputation intact. I did both.
But I want to talk about what actually happened over the seven years that preceded those eight minutes. Not because I'm bitter about the outcome — I'm not. Because the story of how a founding-era advisor becomes, in someone's words, "too advanced," is a story I've watched play out at dozens of companies, and the lesson inside it is more useful than anything in the six posts I've published before this one.
What It Means to Be Founding-Era
I didn't come in as a vendor. I came in as a believer.
The company was in a space that genuinely needed what it was building. The founders — a CEO and a co-founder — had the drive and the vision that made early-stage companies worth betting on. I believed that good marketing principles apply across industries. I believed I could build the infrastructure that would help them grow. I believed in them as people.
For a period of time, I worked without pay. Not because I was naive, but because I was invested — in the mission, in the founders, in the thing we were building together. The equity came later. The cash came in fits and starts. What remained consistent was the work.
Every advisor who has ever done founding-era work knows the feeling. You are not serving a client. You are building something together. The relationship has a different texture than any retainer that follows it.
That texture creates something real. Direct lines of communication. Decisions made fast because everyone involved is small enough to be in the same room, or the same Slack channel. Problems surfaced and solved because the people who spot them and the people who can fix them are the same people, or one step removed.
It also creates a vulnerability that takes years to name. When you are that invested, you stay longer than you should. You absorb more than is reasonable. You give the benefit of the doubt past the point where the doubt has been answered. And you become, slowly, the person who knows where all the bodies are buried — which is enormously valuable right up until it makes you expensive to keep.
The Dinner Where I Understood What Was Coming
There was a dinner, years before the eight-minute meeting. The founding CEO said something that I didn't fully absorb at the time but haven't forgotten since. He told me, in so many words, that the major decisions — the people decisions, the strategic pivots, the marketing hires — were no longer entirely his to make. The investors were involved. The board had its own networks, its own preferences, its own people it wanted to bring in. He could advocate, but he couldn't always win.
I heard this as context. I should have heard it as a forecast.
The founding CEO hadn't lost the company. He had lost the ability to act on his own instincts inside it. That is a different and more insidious kind of loss.
The people who came after him — the marketing hires, the CMOs, the consultants the board trusted — were not wrong to do their jobs. They were doing exactly what institutional investors expect: bringing their own frameworks, their own networks, their own ways of operating. The problem was not the people. The problem was structural. The company had taken institutional money and, in doing so, had invited a different set of priorities into the room. Those priorities were not always aligned with the founding vision. And the founding vision was what I had signed up to serve.
The moment I understood that even the CEO had lost the thread, I should have recalibrated what my role was. I didn't. I kept operating as if I had a direct line to the decision that mattered. I had the line. The decision had moved.
The Layers That Form Without Anyone Deciding to Form Them
Nobody at this company sat down and said: let's build walls between the people who know things and the people who can act on them. It happened gradually, the way all organizational entropy happens: through growth, through headcount, through the natural formalization that follows institutional investment.
In the early days, I could surface a problem in a shared Slack channel and have a response within the hour. The founders were there. They read it. They cared. We moved.
At some point, I stopped feeling safe using that channel. I created a separate one, called "Digital Marketing," because the original had become political enough that raising a problem there meant navigating whose territory it touched, whether it looked bad for someone, whether it would be received as criticism. The separate channel was quieter, smaller, and far less connected to anyone who could actually change things.
That is the corporatization tell. Not the press release about Series B. Not the new office. The moment a person who knows something critical starts routing around the channels that would get it addressed, because those channels have become more about appearance than information.
What the Layers Actually Broke
The six posts in the Foundation Series are a technical and strategic manual for building marketing infrastructure that compounds. Fix the pipes. Close the circuit. Build keyword intelligence as a living system. Read all six quality scores. Audit the tech stack before you hire. Each post describes something specific and actionable.
What none of them says directly, because I didn't understand it fully until this week, is this: every recommendation in every post assumes that the people with the expertise have a reasonably direct line to the decisions.
The moment organizational layers form between knowledge and authority, the Foundation Series becomes theoretically correct and practically impossible. Not because the advice is wrong. Because the company cannot act on it anymore.
The Foundation Series — What the Layers Actually Broke
Each post describes a feedback loop. Each feedback loop failed for the same organizational reason.
Six posts. Six different surface problems. One root cause running through all of them: the direct feedback channels had been filtered, layered, or closed.
The One Line a Founder Should Never Let the Layers Cross
If I could go back to that dinner with the founding CEO — the one where he told me the decisions were no longer entirely his — I would say one thing.
Whatever else you give up as you grow, whatever titles and reporting structures and layers you add to satisfy the board: protect the direct feedback channels.
From customers. Unfiltered. Not through a customer success summary. From the customers themselves.
From employees and contractors. Not through HR. Not through a manager's interpretation. From the people doing the work.
From vendors and agency partners. Not softened through a marketing director's pre-meeting briefing. From the people building your campaigns and your content and your infrastructure.
The moment you filter the raw feedback through hierarchy, you lose the ability to course-correct. The pipes start leaking. The circuit breaks. The algorithms drift. And the advisor who built the foundation gets replaced by someone who doesn't create pressure to do stuff.
This is not a romantic argument for flat organizations or founder-mode heroics. Companies need structure. Layers are sometimes the right answer. The question is not whether to have layers. It is which channels you protect from them.
The direct feedback loop from the people closest to the problem to the people with the authority to fix it — that is the one thing that must survive the transition from startup to corporation. Everything in the Foundation Series depends on it. And it is the first thing the layers take.
Feedback Loop Integrity Check
Eight questions about your direct feedback channels. Answer honestly.
What Seven Years Taught Me About Myself
The strategic lessons are the easier ones to write. The personal ones take longer.
I spent years getting better at something that most advisors never learn: the difference between holding the line and needing to win. Holding the rate when pressure was applied. Refusing to absorb accountability for infrastructure problems I didn't own. Documenting every blocker with the owner's name and a date. These are the places where I held the line, and holding them mattered.
But I also spent years learning to let go of things that felt like concessions but were actually just tactics. The client wanted a flat two-campaign structure instead of a tiered funnel. I thought the tiered approach would produce better data. I made the case, he made the decision, I executed his approach with full effort. If I was right, the data would show it at the end of the quarter. If he was right, we'd found a simpler structure that worked. Either way, the relationship was more durable than my being right about every detail.
The relationship is more durable than being right about every detail. It took me several years to actually believe that sentence, not just to say it.
The equity complicates all of it in ways I'm still processing. I am not just an advisor who got let go. I am a stakeholder in what comes next. If the new contractor and the new CMO can execute what I couldn't get executed — if they fix the HubSpot sync and build the landing pages and get the keywords onto the website — then my shares appreciate and I was wrong about some things. That outcome is genuinely fine with me. If the pattern continues, it won't.
The seven years were worth the education. The eight minutes were worth the clean exit. And the equity remains.
Three Questions Worth Sitting With
The Framework Is the Easy Part.
The Conditions Are Everything.
Every post in the Foundation Series describes something you can build. This post describes the one thing you must protect before you build any of it. The direct line between the people who know what's broken and the people who can fix it. Without that line, the best frameworks in the world stay theoretical. With it, even imperfect execution compounds over time.
Keep the line open.
Seven posts. One argument.
The infrastructure posts that teach you what to build, and the essay that teaches you why it's so hard. Subscribe to get the thinking that follows.