I’m Done Performing
I'm done performing. Not done working. Not done caring. Done with the particular exhaustion of operating inside a game where everyone knows the rules are fake and nobody says it out loud.
Read →REVENUE ARCHITECTURE MANIFESTO
We don’t Believe in more tactics.
We believe in better systems.
They don’t. They never did. This is the manifesto that says so out loud — 64 sections, one honest argument, no performance. Read it in order or read it out of order. Either way, it’s the same company you already run.
The Prologue
and some content blurb here
PART ONE: THE PERFORMANCE
Chapter 1 — We Built Business for Robots
The foundational argument: organizations were designed for an idealized, frictionless, always-rational human who does not exist. Every system, every org chart, every SOP was built for that fictional person. The actual humans adapted. And then we blamed the humans.
The Two Companies
Every company is two companies. Not metaphorically — operationally. Two of them, running at the same time, in the same building, with the same people. Both are real.
Read →The Professional Mask
Somewhere between the parking lot and your desk, you put it on. The mask is not dramatic. That's what makes it invisible.
Read →What We Agreed Not to Say
There's a contract you signed on your first day of work. It wasn't in the onboarding packet. Nobody handed you a pen. But you signed it — by watching what happened to the last person who broke it.
Read →The Cost of the Performance
The performance is not free. Nothing that runs all day is. Everyone in your company has two jobs — the one in the job description, and performing it. The second job is unpaid, unlisted, and exhausting.
Read →The Two Companies
Every company is two companies. Not metaphorically — operationally. Two of them, running at the same time, in the same building, with the same people. Both are real.
Read →The Professional Mask
Somewhere between the parking lot and your desk, you put it on. The mask is not dramatic. That's what makes it invisible.
Read →What We Agreed Not to Say
There's a contract you signed on your first day of work. It wasn't in the onboarding packet. Nobody handed you a pen. But you signed it — by watching what happened to the last person who broke it.
Read →The Cost of the Performance
The performance is not free. Nothing that runs all day is. Everyone in your company has two jobs — the one in the job description, and performing it. The second job is unpaid, unlisted, and exhausting.
Read →Chapter 2 — The Masking Org
When the performance becomes the culture, the gap between the official story and the real one stops being an anomaly and starts being the operating model.
Revenue Is the Best Mask in Existence
If you want to hide something in a company, hide it under a good quarter. Nobody looks there. An organization's mask is made of numbers — and no number masks like revenue.
Read →The Official Story vs. The Real One
Ask leadership how the process works. Write it down. Now ask the team that runs the process. Write that down too. You are holding two documents that describe two different companies.
Read →When the Mask Fits Too Well
The most dangerous mask is the one that fits. A badly fitting mask gets noticed. It slips in a meeting. It chafes on a bad day. Eventually somebody asks if you’re okay, and the question — even awkward, even unwelcome — is a crack where the truth can get in. A perfect mask never triggers […]
Read →What Masking Costs at Scale
Three people gave three different revenue numbers in the same meeting. Everyone nodded. I’ve watched that nod in more companies than I can count, and I want to talk about what it costs — because that nod is masking at scale. It’s a room full of people agreeing, silently and in unison, not to ask […]
Read →PART TWO: THE HUMANS IN THE BUILDING
Chapter 3 — Mental Health Lives Here
ADHD, PTSD, trauma responses, panic attacks — they’re in your building right now. They have always been in your building. The only question is whether you’ve been reading them correctly.
I Have ADHD. I Have PTSD. I’m at Work.
I have ADHD. I have PTSD. I’m at work. All three of those sentences are true right now, as I write this. They were true yesterday. They will be true tomorrow. This is not a before picture. There is no after picture. There is just me, at work, managing both, the same way I manage […]
Read →I Still Built the Dashboards
During one of the worst stretches of my life, I was leading a HubSpot migration — a full transformation, systems moving, data mapping, and a set of dashboards to build so leadership could finally see their business clearly. Let me tell you what else was happening during those weeks. I cried in my office with […]
Read →ADHD in the Building
Somebody on your team has ADHD. Statistically, several somebodies. Most of them don’t know it. They weren’t diagnosed — they were described. Scattered. Intense. Too much. Inconsistent. A lot. They collected those words the way I did, for decades, and filed the compensations under personality, because nobody offered a better folder. ADHD is in your […]
Read →Trauma Responses Wear Business Casual
Trauma responses don’t look like trauma. They look like management styles. The responses people learned in unsafe places don’t stay in those places. They commute. They show up at nine, they take meetings, they get performance-reviewed — and they dress so well for the office that we stopped recognizing them entirely. We gave them professional […]
Read →The Employee Who Became the Process
Every company has a Susan. Yours might be named something else. You know who I mean, though, because when anything gets confusing, the answer is always the same three words: *ask Susan.* Why doesn’t the invoice match the contract? Ask Susan. What did we promise this client in 2021? Ask Susan. How does the handoff […]
Read →Chapter 4 — Founder Dependency Is a Nervous System Response
Nobody designs founder dependency. It accumulates — one innocent exception at a time — until the founder is the router, the translator, the institutional memory, and the reason nothing can scale.
How It Accumulates
Nobody designs founder dependency. There was no whiteboard session where anyone drew the founder as router, translator, historian, escalation path, emotional thermostat, institutional memory, and human CRM. No org chart has ever contained the box *person everything secretly runs through.* And yet I have never once walked into a founder-led company where that box wasn’t […]
Read →The Nervous System Remembered
Ask a founder why they can’t let go and you’ll get reasons. Quality. Standards. Client relationships. The team’s not ready yet. Ask their nervous system and you’ll get a memory. Every founder I’ve worked with has one. It’s specific. They can usually tell you the year, sometimes the date. The first real delegation that went […]
Read →The Difference Between Judgment and Load-Bearing
There are two standard prescriptions for founder dependency. They are opposites, and they are both wrong. The first one is *step back.* Delegate more. Get out of the weeds. This treats the founder’s involvement as the problem itself — so the founder pulls out of everything at once, judgment included. And then the thing that […]
Read →What Happens When the Founder Can’t Let Go
Nothing in this section is about the founder’s character. That’s not me being polite — it’s me being accurate. What follows is a physics problem. When every meaningful decision routes through one human being, certain outcomes stop being risks and become schedules. Here’s what’s on the schedule. — **The company caps at the founder’s bandwidth.** […]
Read →Chapter 5 — High Performers Are Not Superheroes. They’re Duct Tape.
Your highest performers are not a competitive advantage. They’re compensation — for systems that were never built, processes that were never documented, and gaps that nobody officially named.
The Absorption Economy
Right now, in your company, someone is manually doing what a system should be doing. Probably several someones. They’re reconciling two data sources that should agree and don’t. They’re translating between two departments that share a handoff but not a language. They’re updating the CRM after the fact because the integration broke months ago and […]
Read →What You’re Actually Paying For
The most expensive line on your P&L doesn’t appear on your P&L. Last section I said you have two economies and only manage one. Fine — but unmanaged is not unpaid. The absorption economy bills you constantly, in four installments, and I want to walk you through them in order, because they’re sequenced like a […]
Read →Scaling Headcount Without Fixing Systems
The company felt the strain and did the intuitive thing. It hired. Strain reads as *not enough hands* — that’s the intuition, and it’s clean, actionable, budgetable. Everyone’s slammed, so add people. It is also, in a company running on absorption, the most expensive mistake in the scaling playbook. Because the strain was never a […]
Read →Before You Restructure the Team, Look at What You Built Them Inside
Every reorg begins with the same sentence: *we have a people problem.* Sometimes it arrives as a performance plan. Sometimes as a culture conversation. Sometimes as a new org chart, drawn late at night, with certain boxes quietly missing. The diagnosis underneath is always the same — the people aren’t performing — and I have […]
Read →PART THREE: WHAT’S ACTUALLY HAPPENING
Chapter 6 — The Shadow Systems™
Shadow Systems™ aren’t problems. They’re evidence. Every workaround, every side spreadsheet, every informal process is a signal about where the official system failed the people who needed it.
The Spreadsheet Nobody Officially Owns
Turn on the flashlight. The first thing it lands on is a spreadsheet. It has no official owner. It appears in no process document, no tool inventory, no onboarding deck. IT doesn’t know it exists. Finance definitely doesn’t know it exists. And everyone — *everyone* — uses it. Ask who created it and you get […]
Read →Shadow Systems™ Are Evidence, Not Problems
When an organization discovers a Shadow System™, it reaches for the delete key. Consolidate the spreadsheets. Lock down the tools. Re-mandate the CRM. The discovery gets treated as a compliance failure, the response gets treated as enforcement, and six months later there’s a new spreadsheet — better hidden this time, because the team learned exactly […]
Read →The Most Dangerous Shadow System™
Watch your company closely in the forty-eight hours before a board meeting. Somewhere in the building, a person is “pulling the numbers.” Notice the verb. Not *reading* the numbers — pulling them. Exporting from three tools. Reconciling by hand what the systems can’t reconcile themselves. Massaging a CSV in Excel, applying judgment calls nobody documented, […]
Read →How to Read Them
By now you want to go find yours. Good. But there’s a right way to read Shadow Systems™, and it starts with the thing your instincts will resist most. Amnesty. Full, explicit, said-out-loud amnesty. Because here’s the physics: your people built these systems inside a contract that punishes honesty — we spent a whole chapter […]
Read →Chapter 7 — Visibility Debt™
Visibility Debt™ is the compounding gap between what your organization believes is happening and what it can actually prove. It accrues silently. It compounds. It is always more expensive than it looks.
The Gap Between What You Believe and What You Can Prove
Ask a founder their close rate and you’ll get a number. Instantly. Confidently. Ask them to prove it and watch the pause. That pause is the subject of this chapter. Not the number — the number might even be right. The pause. The half-second where the founder’s brain checks its sources and finds, instead of […]
Read →How It Compounds
Financial debt sends statements. Every month, a number, in writing: here’s what you owe, here’s the interest, here’s what happens if you ignore this. Visibility Debt™ sends nothing. That’s its defining feature and its whole strategy. It compounds in silence, and you find out the balance the way companies always find out — all at […]
Read →Data Trust Is Not a Tech Problem
At some point in the Visibility Debt™ story, somebody buys software. A new CRM. A BI platform. A data warehouse with a dashboard layer and a sales rep who said *single source of truth* out loud, twice, without laughing. The purchase feels like progress — we covered that feeling in the hiring chapter, and this […]
Read →Visibility Is Not Dashboards. It’s Reality.
You can dashboard a lie. Some of the most beautiful dashboards I have ever seen were sitting on top of the sickest data in the building — real-time visualizations of numbers nobody trusted, definitions nobody shared, and gaps nobody had looked into for years. Gorgeous. Responsive. Wrong. A dashboard is a screen. It will render […]
Read →Chapter 8 — Coordination Friction™
Revenue doesn’t move through departments. It moves through handoffs — and the friction lives between the boxes on the org chart, not inside them.
Revenue Moves Through Handoffs, Not Departments
Follow one dollar of revenue through your company. Actually follow it. It’s born in marketing, as attention. It gets handed to sales, as a lead. Handed again to onboarding, as a promise somebody now has to keep. Handed to delivery, as work. Handed to success, as a relationship. If everything goes well, it circles back […]
Read →The Handoff Nobody Designed
Ask who designed your sales-to-onboarding handoff. Enjoy the silence. Maybe someone eventually offers a name — a person who left in 2022, or “I think that’s just how Dana and Marcus started doing it.” That’s the answer, actually. That’s how nearly every handoff in your company came to exist: two people worked out a routine […]
Read →Local Optimization, Global Dysfunction
I have a rule about teams, and it sounds ridiculous when I say it out loud, which is exactly why it needs saying out loud: I don’t kick the ball into my own goal to prove I’m better than my goalie. We’re not competing, my goalie and I. We can’t be. We have different roles […]
Read →Chapter 9 — Oral Tradition Is Not a Revenue Strategy
When the only way to know how something works is to ask someone who’s been there long enough, that’s not institutional knowledge. That’s institutional risk.
The Knowledge That Walks Out the Door
If the only way to know what’s happening is to ask five people, you don’t have alignment. You have oral tradition. I mean that technically, not as an insult. Oral tradition is a real system — humanity ran on it for most of history. Knowledge held in specific heads, transmitted by proximity and conversation and […]
Read →Warm Systems vs. Scalable Ones
Before you race off to document everything, I need to defend oral tradition for a minute. Because here’s what’s true about asking Sarah instead of reading a wiki: it’s *warm.* The answer comes with context, with judgment, with the backstory of why. It comes with a relationship — a little deposit in the trust account […]
Read →Documentation Is Not the Answer
Every company that discovers its oral tradition problem responds the same way: a documentation initiative. A wiki gets stood up. A quarter gets dedicated. Everyone writes down their processes, there’s a spreadsheet tracking completion, and for one shining moment the company believes it has converted its folklore into infrastructure. Come back eighteen months later. The […]
Read →PART FOUR: THE MISDIAGNOSIS
Chapter 10 — The Problem Never Lives Where the Pain Appears
The symptom and the source are almost never in the same place. Revenue problems that look like sales problems are often ops problems. Ops problems that look like people problems are often visibility problems.
The Misdiagnosis Tax
By the time a company calls someone like me, they’ve already tried the obvious fixes. New CRM. New hire. New agency. A quarterly initiative with a name, a slide deck, and a kickoff meeting that genuinely energized people. Sometimes all four, in sequence, over three exhausting years. And the problem keeps coming back. Slightly disguised. […]
Read →Revenue Problems That Aren’t Revenue Problems
Let me walk you upstream. Every example in this section is a real pattern I’ve found more than once, anonymized into archetype. In each one, the pain surfaced in one department, the fix got aimed at that department, and the origin sat somewhere else entirely — untouched, patient, generating next year’s version of the same […]
Read →Why We Keep Misdiagnosing
If misdiagnosis is this predictable — and after two sections, you can see it coming — why do smart, experienced leadership teams keep doing it? Not stupidity. I want to be clear about that, because the answer matters for fixing it. Misdiagnosis is what intelligent people do inside structures that make the wrong answer cheap […]
Read →Chapter 11 — The CRM Is a Mirror
Your CRM doesn’t have a data problem. It has a reality problem. The mess in the pipeline reflects the mess in the process — and you cannot automate your way out of ambiguity.
Messy Pipeline Is Not a Software Problem
The CRM is the most reliable organizational mirror I know. Not because it’s always accurate. Because it’s always honest. Look at what yours is showing you right now. Pipeline stages applied inconsistently — each rep with a private theory of what stage three means. Deals parked for months at 60%, close dates rolling forward like […]
Read →You Cannot Automate What You Don’t Understand
The appetite for automation arrives at exactly the wrong moment. Companies don’t reach for automation when things are clear. Clear things are easy; nobody’s desperate to automate easy. Companies reach for automation when they’re drowning — when the volume has outrun the team, when the manual work is crushing, when everything feels chaotic. Which is […]
Read →Fix the Reality. Then Build the System.
Every failed CRM implementation I’ve ever autopsied died of the same cause: the company bought the sequence in reverse. The reverse sequence goes like this. Reality is messy — undefined stages, unagreed definitions, handoffs running on folklore. Rather than fix that (slow, unglamorous, requires admitting things), the company buys a system and assigns it the […]
Read →Chapter 12 — Communication Problems Are Visibility Problems
Meetings multiply when systems fail. Every standing sync, every status update, every “just checking in” is a human being compensating for infrastructure that doesn’t exist yet.
Why the Meetings Multiplied
Open your calendar and sort your meetings by their real purpose. Not their names — their purpose. Some exist to decide something. Keep those. Some exist to build something together. Keep those too. And some — be honest now — exist so that people can find out what’s going on. The status meeting. The weekly […]
Read →If the Only Way to Know Is to Ask Five People
Pick a simple question about your own business. Genuinely simple. *What’s the status of the Henderson deal?* Now watch what answering it actually costs. You ask the account executive, who gives you a fragment, a caveat, and a referral: *mostly closed, I think legal’s reviewing, but check with Dana.* Dana has a different fragment: *contract’s […]
Read →What Happens When You Build the Infrastructure
Most of what currently fills your calendar becomes unnecessary. That sentence makes some people uncomfortable. It should. Sit with the discomfort for a minute, because it’s diagnostic — and then let me show you what actually happens in a company that builds visibility infrastructure, because I’ve watched it, and it’s stranger and better than the […]
Read →PART FIVE: REVENUE ARCHITECTURE
Chapter 13 — What Revenue Architecture Actually Is
Revenue Architecture is the discipline of designing how revenue moves through an entire organization — not optimizing one department at a time, but seeing and fixing the whole system at once.
The Field I Found
I didn’t find Revenue Architecture in a book. I found it doing keyword research. That’s the least romantic version of a discovery story I can offer you, and it’s the true one. I was trying to figure out what to call the work I do — and, more practically, whether anyone would ever search for […]
Read →Why It’s Different
Every discipline that touches revenue looks at a piece of it. Sales strategy looks at the pipeline. Marketing looks at demand. RevOps looks at the tooling. A CRM implementation looks at the fields and the workflows. A department audit looks at the department. Each one is real work. Each one can be done brilliantly. And […]
Read →Designing for Humans
Every system in your company was designed for someone. The question is whether that someone exists. Most revenue systems are built for an idealized employee. She has perfect recall. She updates the CRM the moment the call ends, every call, forever. She reads every process doc, retains it, and never improvises. Her attention never fragments, […]
Read →Chapter 14 — The Revenue Health Matrix™
Five systems. Every company has all five, whether they built them intentionally or not. The question is whether they’re working together — or failing together.
The Positioning System™
Ask five people at the same company what the company does. If you get five different answers, you’ve just met the most expensive problem in the building — and it will never once appear on a report with the word “positioning” on it. — This chapter walks through the five systems of the Revenue Health […]
Read →The Authority System™
There are two kinds of sales calls. In one, you spend the first twenty minutes proving you deserve to be in the room. In the other, the prospect opens with “I’ve been reading your stuff for a year — here’s my situation.” Same company. Same offer. Same rep. Completely different economics. — The Authority System™ […]
Read →The Conversion System™
Somewhere in your company, right now, a lead is being followed up because somebody remembered. Not because anything surfaced it. Not because a system flagged that four days had passed. Because a human being, driving home or rinsing a coffee cup, thought: *oh — did anyone ever get back to that guy?* That lead is […]
Read →The Lifecycle System™
Watch where a company spends its design energy. The path to the signature is landscaped. Ad spend, sequences, retargeting, sales decks, proposal templates, a pipeline with named stages and a meeting devoted to staring at it. Every meter of the road from stranger to customer has been argued about by someone. Then the contract is […]
Read →The Visibility System™
Four systems in, you may have noticed a problem. I’ve described the Positioning System™, the Authority System™, the Conversion System™, the Lifecycle System™ — and every one of them fails quietly, in a location other than where the pain shows up. Which raises the obvious question: if the failures are quiet and the addresses are […]
Read →Why They’re Evaluated Together
You can audit each of the five systems on its own. People do it every day. It’s a whole industry. A positioning agency reviews your messaging. A sales consultant assesses your pipeline. A CS firm benchmarks your churn. Each audit is competent. Each produces findings. Each fix works, briefly. And eighteen months later you’re commissioning […]
Read →Chapter 15 — The PBJ Sessions™
What happens when you put leadership’s version of reality and the team’s version in the same room, at the same time, with a structured conversation and nowhere for either story to hide.
What Happens in the Room
The most important meeting I run has no dashboard, no deck, and no agenda item beyond one sentence: Describe the process. — A PBJ Session™ is a structured conversation with two descriptions in it. Leadership describes the process they believe exists — the one in the flowchart, the one the onboarding deck was built on, […]
Read →Why Psychological Safety Is Not a Soft Metric
Psychological safety has a branding problem, and the branding problem is the word “soft.” It got filed with the posters and the pizza parties. A culture initiative. A workshop with an icebreaker. The thing you invest in after the real systems are built, if there’s budget left, to make the numbers feel better about themselves. […]
Read →PART SIX: THE FUTURE
Chapter 16 — AI Cannot Replace This. It Can Help You See It.
AI is a powerful accelerant. What it cannot do is feel the room, read the pause, or understand why Linda’s spreadsheet exists. What it can do is handle what systems should already be handling.
AI Is a Wheelchair
Before anyone bristles at the comparison: I mean it as a compliment. To both. People who have never needed an assistive device tend to hear “wheelchair” as a diminishment. People who use one know better. A wheelchair is freedom. It’s the difference between a world you can move through and a world you can’t. It […]
Read →What AI Cannot Do
I ask a team lead how the handoff to delivery works. There’s a pause. Maybe half a second. Her eyes go to the operations manager — just a flick — and then she says, “It works pretty well, overall.” Everything I need to know about that handoff happened before the sentence started. — Feed the […]
Read →The Right Use of AI
Two posts ago I told you what AI is: range, memory, speed — a wheelchair. Last post I told you where it goes blind: the pause, the glance, the history, the gap between accurate and true. Which leaves the only question that matters operationally. What do you actually point it at? The answer is a […]
Read →Chapter 17 — Designing for Reality
Operational maturity isn’t perfection. It’s building systems for the humans who actually work in them — not the idealized, always-rational, perfectly consistent humans we wish we had hired.
Stop Designing for the Idealized Human
Back in Chapter 13, I made this argument as philosophy. This is the practice version, and the practice version is a habit you have to catch in the act. Because you don’t design for the idealized human once, in some grand architectural decision you could locate and reverse. You do it in small strokes, constantly, […]
Read →Operational Maturity Is Not Perfection
I’ve watched founders postpone fixing their operations the way people postpone going to the doctor. Not because they don’t care. Because they’re afraid of what the appointment will confirm, and somewhere along the way they absorbed the idea that the goal is a clean bill of health — so until they can present one, they’d […]
Read →Complexity Will Always Outpace Clarity If You Let It
Here’s the asymmetry that runs the whole game. Complexity is automatic. Clarity is manual. Nobody in your company is assigned to increasing complexity. There’s no headcount for it, no initiative, no OKR. It grows anyway — every hire adds relationships, every customer adds exceptions, every tool adds integrations, every quarter adds history that somebody now […]
Read →