The revenue-production unit.

TL;DR

• Complex B2B sales requires org-wide conviction across a buying group, not a single yes from a single buyer — selling effort is exerted across many individuals over multiple meetings, each advancing a different stakeholder's conviction.
• Kazanjy's construct for the next stage past founder-led selling: the unit of revenue production — the "revenue mitochondria" — the smallest cohesive team that can produce and retain revenue end-to-end.
• The common shape of the unit: one SDR, two AEs, one CSM — lead gen, selling and closing, and onboarding and retention, running as one machine. The founder is out of day-to-day selling.
• Within the unit, an IC-versus-management split starts to emerge. This is frequently where the first dedicated sales manager or leader gets hired — because the next move after this stage is to clone the unit.
• The goal of this phase is narrow: prove the complete unit works — lead gen, selling and closing, and onboarding — as one cohesive, repeatable machine.
• Exit criteria: predictable production rate, everyone hitting their KPIs, clean handoffs with backchecks that catch dropped balls, and founder confidence that the unit can be cloned.
• The anti-pattern is imbalance — five AEs fed by one SDR and zero CSMs is not a unit, it's a queue with a leak on both ends. Balance across functions is the discipline.

Why complex B2B sales needs a cohesive unit, not a hero

The founder-led motion works because one person can hold the entire deal in their head — the buyer's problem, the product's current state, the roadmap commitment, the champion's internal politics. That model has a ceiling, and the ceiling is set by the buyer's side of the table, not the seller's. Complex B2B deals are not won by convincing one person. They are won by producing conviction across an entire buying group — the economic buyer who owns budget, the technical evaluator who owns the security review, the day-to-day user who owns the workflow, the executive sponsor who owns political cover inside the account. Each of those stakeholders needs their own version of conviction, built on their own timeline, frequently in their own meeting.

Kazanjy's framing of this reality is a chain of meetings, not a single call: Meeting 1 advances one stakeholder's understanding of the problem; Meeting 2 advances a different stakeholder's evaluation of the solution; Meeting 3 surfaces the security or procurement stakeholder who hasn't been in the room yet; Meeting 4 closes the loop with the executive sponsor who needs the synthesis, not the detail. The selling effort is exerted across many individuals over multiple meetings, and no single meeting closes the deal — each one moves a different piece of the buying group's conviction forward.

The salesperson's job in this environment is connector work: find the need across the buying group, convince each stakeholder of that need in terms specific to their function, position the solution against each stakeholder's evaluation criteria, and then project-manage the procurement process that follows — the paperwork, the security questionnaire, the legal redline, the internal approval chain — because none of that happens on its own once the selling conversation ends. A single founder, or a single AE, can run this connector role for a handful of deals. Running it at volume, across a growing pipeline, is a different operational problem — and it is the problem Kazanjy's unit construct is built to solve.

The construct: the unit of revenue production — Kazanjy's "revenue mitochondria"

Kazanjy's term for the next organizational stage past founder-led selling is the unit of revenue production, and the name he gives it — the revenue mitochondria — is doing real conceptual work, not just being memorable. A mitochondrion is the smallest structure inside a cell that can independently generate the cell's usable energy; it is a complete, self-sufficient production system at a scale smaller than the organism. Kazanjy's claim is that revenue-producing organizations need an equivalent: the smallest cohesive team that can independently produce and retain revenue, end to end, without borrowing capacity from outside itself.

The common shape of that unit, per Kazanjy: one SDR generating and qualifying pipeline, two AEs selling and closing what the SDR feeds them, and one CSM onboarding and retaining what the AEs close. Three functions, four seats, one machine — lead gen, selling and closing, onboarding and retention, running as a cohesive whole rather than three disconnected activities that happen to sit in the same company.

The structural marker of this stage, and the reason it matters as a named milestone rather than just headcount growth: the founder is out of day-to-day selling. Not advising from the sidelines on the occasional strategic deal — out of the meetings, out of the pipeline, no longer the person whose calendar determines whether revenue gets produced this week. The unit produces revenue on its own. That is the entire point of naming it a unit in the first place.

The stages inside the unit, and where the IC-versus-management split appears

Inside the revenue-production unit, work flows through three stages in sequence: Lead Gen (the SDR), Selling (the two AEs), and Success (the CSM). Each stage hands off to the next — qualified pipeline from the SDR to the AEs, closed-won accounts from the AEs to the CSM — and the quality of each handoff determines whether the unit behaves like one machine or three uncoordinated functions billing against the same logo.

This is also where an IC-versus-management split begins to emerge for the first time. Up to this point, everyone in revenue — including the founder — has been an individual contributor: carrying their own pipeline, running their own meetings, closing their own deals. Once the unit is four seats deep across three functions, coordinating the handoffs, protecting the balance across functions, and coaching each seat against its own KPI set becomes a job in its own right — and it is frequently the point at which a company hires its first dedicated sales manager or sales leader. That hire is not premature at this stage; it is what the next move requires. The next move, once the unit is proven, is to clone it — run two or three of these units in parallel — and cloning a unit you cannot yet manage as a cohesive whole is how the second unit inherits the first unit's dysfunction instead of its performance.

The goal of this phase

The goal, stated plainly, is narrow and specific: prove successful performance of a complete unit of revenue production and retention — lead gen, selling and closing, and onboarding — running as one cohesive machine. Not prove that an SDR can generate pipeline in isolation. Not prove that an AE can close deals in isolation. Prove that the whole chain, end to end, produces and keeps revenue as a system. Any one function performing well in isolation is not the same evidence, and treating it as equivalent is the most common way this phase gets called "done" before it actually is.

Exit criteria: are you actually ready to clone this?

Kazanjy's exit criteria for this stage are specific enough to check against, not vibes:

• Predictable production rate. The unit produces revenue at a rate you can forecast, not a rate that surprises you each month in either direction.
• Everyone hitting their KPIs. The SDR hitting their qualified-pipeline number, both AEs hitting their closed-won number, the CSM hitting their retention and expansion number — all four seats, not two out of four with the other two carried by the rest of the team.
• Smooth handoffs with real backchecks. Pipeline moving from SDR to AE, and accounts moving from AE to CSM, with an explicit check step that catches a dropped ball before it becomes a lost deal or a churned account — not an informal hope that nothing falls through the crack between two people's inboxes.
• Founder confidence that the unit can be cloned. Not hope, not a plan to fix the unit's problems in the next version — actual confidence, grounded in the three criteria above, that standing up a second identical unit produces a second version of the same performance rather than a second version of the same problems.

All four hold together or none of them count. A unit hitting its revenue number on the back of one heroic AE while the SDR misses their pipeline target and the CSM is quietly losing accounts is not a unit that has passed this stage — it is a unit that looks like it has passed this stage until you clone it and the second copy doesn't produce the same number.

The anti-pattern: scaling one function out of line with the others

Because the one-SDR-two-AE-one-CSM shape is a pattern, not a rigid rule, the temptation is to treat it as infinitely flexible — to scale whichever function feels most urgent this quarter without checking whether the rest of the unit can absorb it. Kazanjy's warning is specific: the anti-pattern is imbalance. Five AEs fed by one SDR, with one CSM or zero, is the canonical failure shape. It looks like aggressive growth — headcount on the revenue-producing side of the business is up — and it produces the opposite of growth: AEs starved for qualified pipeline because one SDR cannot feed five sellers, and closed-won accounts churning quietly because one CSM (or nobody) is watching onboarding and retention for a customer base that just tripled.

Balance across the three functions is the actual discipline, not headcount growth in any single function. The ongoing work at this stage — continued orchestration refinement between the three stages, building out the sales tooling that makes the handoffs reliable rather than manual, and hiring a dedicated customer-success staffer once the CSM function is under the same strain the AE function was under a quarter earlier — is what keeps the unit a unit instead of letting it drift into three unrelated departments. This is also, not coincidentally, the point at which the founder's time allocation flips: nearly all of it now goes to hiring, onboarding, training, and managing the people who run the unit, rather than to running deals personally.

Common operator failures

• Scaling AE headcount without scaling lead gen. Two AEs become four or five while the SDR function stays at one; the AEs are well-staffed and pipeline-starved, and the fix everyone reaches for — hiring a third AE — makes the actual bottleneck worse.
• No CSM, or one CSM covering a customer base built for four.Onboarding and retention get treated as an afterthought to the "real" selling motion; churn shows up a full quarter after the accounts were closed, by which point the pattern is baked into the base.
• Declaring the unit "proven" on revenue alone. The headline number looks right while one seat is quietly missing their KPI and being covered for by teammates; cloning the unit at this point clones the cover-up along with the performance.
• Handoffs with no backcheck. SDR-to-AE and AE-to-CSM handoffs happen informally — a Slack message, a CRM field nobody's required to fill in — and dropped balls surface as lost deals and silent churn rather than as a caught mistake.
• Cloning before the exit criteria hold. The unit looks good enough after one strong month; a second unit gets stood up against a pattern that hasn't actually stabilized, and the second unit inherits the first unit's unresolved imbalance rather than its performance.
• No management layer once ICs can't coordinate their own handoffs. Four seats across three functions still being run as four independent ICs with no one accountable for the orchestration between them — the manager hire that this stage calls for keeps getting deferred in favor of one more IC seat.

Source and credit

This chapter is Allston Labs' distillation, for operators, of material taught by Pete Kazanjy in his Founder-Led Sales course through Founding Sales(foundingsales.com). The "unit of revenue production" construct, the "revenue mitochondria" term, the one-SDR-two-AE-one-CSM shape, the stage sequence, the goal and exit criteria, and the balance anti-pattern are Kazanjy's framework, not Allston's invention — we are elaborating the mechanism and the operator failure modes we've observed in the house voice, but the underlying construct and terminology are credited to him throughout. If you run a founder-led or early sales-led motion and haven't taken the course directly, it is the more complete and more rigorously taught version of what this chapter summarizes.

Related chapters

• The Ramp-Economics Parable — what it actually costs to bring a new seat in this unit up to full production.
• The Manager's Operating Rhythm — the cadence the new sales manager runs once the unit exists.
• SDR vs AE — the function split that becomes the unit's Lead Gen and Selling stages.
• The First AE Transition — the step immediately before this unit exists at all.