How should you structure comp when your GTM model requires both a founder and a sales leader involved in closing — who owns quota, who owns variable pay, and how do you prevent overlap in 2027?

The two structures on the table — and the third that fails

Most companies land on one of two real structures once a founder and a hired sales leader are both closing. The third — the one people reach for first — is the failure case, and it's worth naming before comparing the survivors.

The failure case: put the founder on a comp plan. The instinct from a new VP of Sales or a RevOps leader trying to make the model "consistent" is one quota framework, one commission schedule, one source of truth, founder included. It is a mistake for a specific reason. A rep comp plan exists to buy a behavior the company would not otherwise get — that is the entire purpose of OTE, base/variable splits, accelerators, and draws. A founder holding a meaningful ownership stake is already maximally motivated to close the strategic logo; the equity movement on a single lighthouse deal dwarfs any commission you could plausibly write. So a founder commission buys nothing. It moves cash from a company to a person who partly owns that company, and it drains the variable budget that should be aimed at the people whose behavior actually is for sale. Worse, it corrupts the capacity model: a "quota-carrying" founder isn't ramping, isn't taking cold accounts, isn't doing pipeline hygiene, and may go dark for six weeks on a fundraise. Your capacity math is now lying to you, and every rep in the building has learned that the founder is a competitor for credit.

Structure A — founder off the system (house accounts). The founder's strategic deals book as house accounts. They do not retire team quota, they do not pay commission to anyone, and the team's number is set as though those deals do not exist. Zero credit ambiguity, because there is nothing to allocate. Team attainment means exactly what it says: revenue the team produced. Forecast accuracy stays clean. The cost is that Structure A only works when founder selling is genuinely a minor, separable slice — a handful of logos a year. Deploy it too early, when the founder is producing most of the revenue, and the team quota becomes a rounding error while the org looks either wildly over- or under-staffed depending on how you squint.

Structure B — founder as overlay. The founder functions as a strategic executive sponsor layered on top of deals the team owns. The rep on the account keeps full quota credit and full commission regardless of how deep the founder gets. The founder amplifies; the founder never extracts. This is the structure for a company where the founder is still load-bearing in the sales motion but is not trying to run a parallel book. The trade-off is that team attainment can flatter the underlying engine — the founder is propping up win rates — so Structure B requires a parallel measurement of founder-independent performance to stay honest.

Structure C — originate and hand off. The founder sources from their network and runs the first meeting or two, then transfers the deal to a rep at a defined, documented stage. The rep owns and is comped from that point. This is the bridge structure: it is how a founder-heavy pipeline deliberately becomes a team-carried pipeline. It lives or dies on the crispness of the handoff stage, and it naturally decays into Structure A as the team's self-sourced pipeline grows.

The three are not mutually exclusive across a company. A realistic mid-stage arrangement runs B for the founder's sponsorship activity and C for the founder's origination activity at the same time, drifting toward A over two to three years. But for any given *type* of founder involvement, you pick one and commit — the ambiguity is what causes the damage, not the choice.

How to decide which structure fits

The choice is not a matter of taste. It is a function of three measurable variables: how founder-dependent the go-to-market still is, what *kind* of involvement the founder has, and the maturity of the team underneath the sales leader.

Start by measuring founder dependence, honestly. Pull the last four quarters of closed-won and open pipeline and tag every deal: founder-sourced, founder-sponsored, or team-sourced. The output is a single percentage — the share of bookings that required founder involvement to happen. That number drives everything downstream. Companies routinely guess this wrong by 20 or 30 points in the flattering direction, which is exactly why you measure it instead of debating it.

Then classify the involvement. If the founder is mostly dropping into deals the team already owns — the CEO-to-CEO call, the late-stage trust builder, the security-review escalation — that is sponsorship, and Structure B fits. If the founder is mostly producing net-new opportunities from their network that the team could not have reached, that is origination, and Structure C fits. If the founder runs a small, named set of deals end to end and touches nothing else, that is Structure A.

Then check team maturity. Structure A requires a sales leader with a functioning pipeline-generation engine underneath them. Without that, house accounts leave the team with a quota so small it teaches the reps nothing and gives the sales leader no real book to manage.

A useful heuristic by stage: at roughly $1M–$5M ARR with the founder in most deals, you are in C (or B if the founder is co-selling rather than originating). Somewhere in the $10M–$25M range, with a real VP of Sales and reps generating a meaningful share of their own pipeline, B and C start converting to A deal-type by deal-type. Past that, A is the resting state, and the founder's three strategic logos a year sit cleanly outside the machine.

Re-run this assessment every annual planning cycle. The correct answer *moves* as the company matures, and a structure that does not anticipate the movement produces a painful renegotiation about eighteen months in.

The concrete numbers behind each seat

Structure is half the answer; the actual dollar mechanics are the other half. Here is what each seat should look like, with the ranges practitioners typically work within — treat them as starting points to calibrate against your own market data, not as universal law.

The founder's seat: zero quota, zero variable. No number, no commission line, no accelerators, no draw. The founder takes a market-reasonable base salary appropriate to a CEO at that stage and company size, and their upside comes entirely from ownership. If the founder holds a meaningful double-digit percentage of a company whose valuation moves as a multiple of revenue, the equity delta on a large strategic deal is an order of magnitude past any commission you would write for it. Adding variable pay to that does not increase motivation — it just introduces a comp event where none is needed and gives the founder a claim on credit that will eventually collide with a rep's number.

The sales leader's seat. A VP of Sales or CRO typically runs a 50/50 or 60/40 base-to-variable split, with the variable driven by team attainment against the aggregate team number. The two failure modes are symmetric and both fatal. Inflating the number — loading founder-sourced strategic revenue into the team quota so the leader "hits" on the founder's back — feels generous and is corrosive: the leader knows it is not real, the board eventually decomposes it, and when the founder steps back the apparent performance collapses and the leader eats the blame for a decline that was really just a network being withdrawn. Making it un-hittable — setting a number that implicitly assumed founder help, then carving founder deals out without adjusting the quota down — leaves the leader chasing a target never calibrated for a founder-free team. The clean design is to build the team number bottom-up from team capacity and hold the leader accountable to that alone. If you want the leader to carry *any* accountability for founder-sourced revenue, do it as a separate, explicitly labeled line with a softer target and its own language: "founder/strategic revenue: $X — leader owns handoff hygiene and operational support, not origination." Never blend it into the core number.

The rep seat. Standard territory: a 50/50 OTE split for full-cycle AEs (sometimes 60/40 for more consultative enterprise motions), quota set at a multiple of OTE that your unit economics support, accelerators above 100% attainment. Nothing about founder involvement changes any of it. A rep's plan should be readable end to end without the word "founder" appearing anywhere except in the swoop clause that guarantees them full credit.

The quota-build arithmetic. Team quota is a capacity model: ramped rep count × expected productivity per ramped rep × a stretch factor, adjusted for partially ramped seats at their expected fraction. The founder is not a ramped rep with a productivity number, so the founder does not appear in that calculation at all. Total company target then reconciles as: team quota (bottom-up from capacity) + founder/strategic target (a separate line the founder owns) = company revenue goal. The two sum; they never blend. If the company target minus a capacity-honest team quota leaves a gap, that gap is the founder's strategic line — or it is a hiring plan — but it is never quietly assigned to reps who have no way to produce it.

The support-work exception. Under Structure A, reps sometimes do real work on a founder house account — running the technical evaluation, managing procurement, scoping implementation. Paying them literally nothing creates a disincentive to help the founder, which is its own problem. Two clean options: a flat support spiff (a fixed dollar amount for defined support work, not quota credit), or a small, explicitly capped partial quota credit sized so it cannot move their attainment materially. What you do not do is let it become a full-credit deal — that converts a house account back into a contested deal and reintroduces exactly the problem Structure A existed to solve.

Structure C's comp boundary. Two options once the rep owns the handed-off deal. *Option A — full commission on the whole deal*, treating founder origination as a free gift to the rep's pipeline. Simplest, maximally motivating, minimal accounting; usually correct at early-to-mid stage. *Option B — commission from the handoff stage forward*, with the origination portion uncomped. This makes sense only when founder-originated deals are a large fraction of pipeline and full credit would inflate rep attainment past what their own selling justifies. Pick one, write it into the plan document, and stop negotiating it per deal.

Preventing overlap: the four rules that do the work

Overlap is not prevented by a cleverer formula. It is prevented by four rules written down *before* the deals occur, because after the fact every credit question becomes a retroactive negotiation between a founder with structural power, a sales leader protecting their team, and a rep who did the work. That negotiation teaches the organization that credit is discretionary, which means effort is a gamble.

Rule 1 — the swoop policy. Founder involvement in a rep's deal, at any stage including the close, never reduces the rep's credit or commission. This is the single most important sentence in the entire structure, and it is counterintuitive to a lot of founders, so the reasoning has to be explicit. The alternative — splitting credit when the founder gets involved — creates an incentive that quietly destroys the model. If a rep loses money whenever the founder enters a deal, the rep will stop bringing the founder in. They will hide late-stage deals, decline to escalate, and keep the founder out of precisely the high-stakes moments where the founder is most valuable. You would be using your comp plan to disconnect your best closer from your most important deals. So the framing has to be relentless and public: founder involvement is a *gift* to the rep, never a *tax* on the rep. A rep should be thrilled when the founder joins, because it raises win probability and costs them nothing. A founder who insists on credit for swooping is revealing a delegation problem, not a comp problem, and no clause fixes that.

Rule 2 — the handoff definition. "The founder hands it off when it feels ready" is not a definition; it is a scheduled credit fight. A real definition names a stage: *the deal transfers to the assigned rep at the close of discovery, before the proposal/evaluation stage begins.* Whatever stage matches your process, you pick one, it is the same one every time, and it is documented. The handoff itself is a recorded event — the deal owner field changes, a handoff note captures what was discussed and committed during the founder-led portion, the stage change is timestamped. There is no informal handoff. If it is not in the CRM, it did not happen, and RevOps treats an undocumented transfer as a process violation. Crisp stage definitions protect both sides: the rep knows exactly what they are inheriting and from what point they own it, and the founder knows exactly when they are done. That is what lets a founder and a rep work the same accounts for years without the relationship eroding into suspicion.

Rule 3 — the deal-tagging taxonomy. Every deal carries a source tag: founder-sourced, rep-sourced, or handoff. Handoff deals additionally carry the transfer stage and the owner-of-record before and after. Founder-*involved* deals carry an involvement flag that feeds analytics and touches comp not at all. This tagging is the spine of the whole structure. It is what makes house accounts enforceable, what lets the overlay measure founder influence without taxing reps, what makes a handoff a recorded event rather than a memory, and what keeps the founder forecast category separate.

Rule 4 — the forecast separation. Founder strategic deals must be in the forecast — the CEO and the board need total-revenue visibility, and pretending the founder's pipeline does not exist makes the company forecast wrong. But they sit in their own clearly labeled "Founder / Strategic" category that rolls into total company forecast and is held entirely separate from the sales team's commit and best case. The separation is non-negotiable because team forecast accuracy is one of the best diagnostics you have on whether the engine is real. Founder deals are lumpy and idiosyncratic, timed to a partnership announcement or a travel schedule rather than a sales process; blending them into team commit either makes a well-forecasting team look erratic or masks a team that is forecasting badly. Under Structures B and C, founder-originated deals enter the team forecast *at the handoff point* under normal rules; before handoff they live in Founder / Strategic. That single boundary keeps the accuracy signal honest.

There is also a morale dimension these four rules exist to protect. Reps are not upset that a founder closes deals. They are upset when it is murky — when they cannot tell whether a logo was always going to be the founder's, whether they had a shot, whether the team number is real. Visible tags plus an explicit, consistent definition of what qualifies as a founder strategic deal solves that. Reps can live with "the founder takes the genuinely strategic logos, and here is what that means." They cannot live with "sometimes the founder takes deals and nobody knows the rule."

Implementation sequence and who owns what

Rolling this out is a six-step sequence, and the order matters — quota math before comp documents, comp documents before CRM configuration, CRM configuration before the first deal tests the rules.

Step 1 — Measure and classify (week 1). Tag the trailing four quarters of bookings and current open pipeline by source. Produce two numbers: founder-dependent share of bookings, and founder-dependent share of open pipeline. Classify the founder's involvement as sponsorship, origination, or end-to-end strategic. These two outputs select the structure.

Step 2 — Build the quota bottom-up (weeks 1–2). Model team capacity from ramped and ramping headcount, hold the founder out entirely, and set the team quota from that. Set the founder/strategic target as a separate line. Confirm the two reconcile to the company revenue goal, and if they do not, resolve the gap through hiring plan or founder target — never by quietly loading it onto reps.

Step 3 — Write the plans (weeks 2–3). The sales leader's plan, referencing the team number exclusive of founder revenue and, if applicable, a separately labeled softer founder/strategic line. The rep plan, standard, with the swoop clause written in plainly. The founder's arrangement, documented as base-only with no quota and no variable — write it down even though it is a negative, because the absence needs to be explicit and shared, not assumed.

Step 4 — Configure the system (weeks 3–4). RevOps owns this and it is where the structure becomes real. Source tag required before a deal can advance past qualification. Handoff fields required before an owner change on a founder-sourced deal. House accounts flagged so they are excluded from quota retirement automatically rather than by someone remembering. Founder / Strategic maintained as a distinct forecast rollup. Founder-involvement flag available at any stage, wired to analytics and disconnected from comp calculation.

Step 5 — Communicate to the whole team (week 4). Every rep hears the swoop policy directly, from the founder if possible. Every rep hears how the team quota was built and that founder revenue is not in it. The definition of what qualifies as a founder strategic deal is shared, not held privately by the founder and the sales leader.

Step 6 — Instrument the transition (ongoing). Define the structure sequence as a sequence, not a menu: "we are in C now; when team self-sourced pipeline crosses [threshold], handoff volume drops and we move toward A." Tie each migration to a measurable trigger — founder-independent pipeline share, or team self-sourced bookings — so the change is a planned event rather than a political fight. Re-baseline quota deliberately at each transition, with everyone knowing in advance that this is how it works so it does not read as a moved goalpost.

RevOps owns the audit trail. When a credit question does arise — and one will — RevOps should be able to answer it as a five-second lookup with timestamps rather than a negotiation. That capability is what keeps every rule above from quietly degrading back into deal-by-deal litigation. RevOps also owns the founder-independence metric: the share of pipeline and bookings that is genuinely team-sourced, reported on a fixed cadence to the CEO, the sales leader, and the board. That number is the one investors care about, because a company whose revenue is mostly the founder's network carries a key-person dependency and an unproven engine. A company that can say "team self-sourced bookings were 40% two years ago and are 75% now, here is the tagging behind it" is telling a materially stronger story than one that can only report a total. It is also why the inflate-the-team-number version is a bad trade: sophisticated diligence decomposes revenue by source, and getting caught inflating costs credibility on everything else in the data room.

Two things this structure cannot fix. It cannot fix a founder who will not let go — you can carve them out of the comp system cleanly and the sales leader will still be unable to build, and the structure's only contribution is making the dependence visible so the board can have the real conversation. And at a company where the founder genuinely *is* the sales team, formalizing any of this is premature bureaucracy. Wait until there is a second seller whose behavior a plan is actually buying.

Related questions

Should the founder get a commission on deals they close?

No. The founder's ownership stake already captures far more value from a closed deal than any commission would pay. Adding variable pay does not increase motivation — it creates a credit claim that will eventually collide with a rep's number and drains budget from the people whose behavior is genuinely being purchased.

Who owns the forecast when both are selling?

The sales leader owns Team Commit and Team Best Case, graded for accuracy against the team's number alone. The founder — or RevOps on their behalf — owns a separate Founder / Strategic category. Both roll into the CEO's total board view; neither is ever blended into the other.

What if the founder sources a deal a rep then closes?

Under Structure C, the rep gets full commission once they own it — typically the whole deal, or from the documented handoff stage forward if founder-originated volume is large enough to inflate attainment. The founder receives no cash credit either way. The rule lives in the plan, not in a per-deal conversation.

How do you set the sales leader's quota so it's fair?

Build it bottom-up from ramped rep capacity with the founder excluded entirely, then reconcile against the company goal by adjusting the hiring plan or the founder's separate strategic target. Never close the gap by loading founder-sourced revenue into the team number.

When should you migrate from handoff to house accounts?

When team self-sourced pipeline becomes the majority and the founder's selling narrows to a handful of named strategic logos. Tie the migration to that measurable threshold rather than a judgment call, and re-baseline the team quota deliberately at the switch.

FAQ

Should a co-founder who runs sales day to day be treated as the sales leader or as a founder?

Both, split by function. Treat them as the sales leader for org design — they own the team quota, the forecast rollup, and the reps' plans. Treat them as a founder for compensation: no variable pay, incentive through equity. The reps underneath run standard plans. The genuine risk here is that a co-founder-as-sales-leader is never replaced and the company never builds true VP Sales muscle, so the founder-independence metric and a clear-eyed board matter more in this configuration than in any other.

What happens if the founder disagrees with the swoop policy and wants credit?

Hold the policy and treat the disagreement as diagnostic. The policy protects a mechanism the founder needs — reps voluntarily pulling them into high-stakes deals — and bending it destroys that mechanism within a quarter. A founder who wants credit for late-stage involvement is usually signaling something deeper about unwillingness to build a team that operates without them, which is worth surfacing to the board directly rather than solving with a comp clause.

Does the founder need any target at all, or nothing?

A target, yes; variable pay tied to it, no. The founder/strategic line is a forecast and planning number that reconciles with the team quota against the company goal, and the founder is accountable for it in the ordinary sense that any executive is accountable for a commitment. It simply is not a compensation trigger, and it never retires team quota.

How do you keep reps from resenting the founder's easy network deals?

Two mechanics and one framing. Mechanically: build team quota exclusive of founder revenue so the game reps are playing is fair and hittable, and tag every deal visibly so nobody has to guess what became a founder deal or why. In framing: leadership talks about founder involvement relentlessly as a free resource, not a threat, and the swoop policy backs that up in cash. Reps tolerate a clear rule about strategic logos; they will not tolerate an unstated one.

Can you run more than one structure at once?

Yes, and most mid-stage companies do. Overlay treatment for the founder's sponsorship activity and handoff treatment for their origination activity coexist without conflict, because they cover different kinds of involvement. What breaks is running two structures for the *same* kind of involvement, or leaving the boundary undefined so each deal picks its own rules retroactively.

What if the company target requires the founder's revenue to be hit?

Then say so explicitly in the plan, as two lines that sum to the goal rather than one blended number. The company can absolutely depend on founder revenue at an early stage — that is normal and often correct. The failure is hiding that dependence inside a team quota, because it makes the sales engine untestable and sets up a manufactured crisis the moment the founder's attention moves elsewhere.

Sources

• https://hbr.org/2012/07/how-to-really-motivate-salespeople
• https://www.saastr.com/how-to-hire-your-first-vp-of-sales/
• https://openviewpartners.com/blog/sales-compensation-plans/
• https://www.forentrepreneurs.com/sales-compensation/
• https://www.mckinsey.com/capabilities/growth-marketing-and-sales/our-insights/the-secret-to-making-sales-incentives-work
• https://www.bvp.com/atlas/scaling-to-100-million
• https://a16z.com/the-sales-learning-curve/
• https://firstround.com/review/the-sales-hiring-playbook-that-took-us-from-0-to-100-million/
• https://www.salesforce.com/resources/articles/sales-compensation-plans/
• https://www.gartner.com/en/sales/topics/sales-compensation

Related on PULSE

• How do you build a sales capacity model that produces a defensible team quota?
• When should a founder hire their first VP of Sales versus another rep?
• How should RevOps design deal-source tagging so credit questions are auditable?
• What forecast categories should a board-facing revenue rollup actually use?
• How do you measure founder-independent revenue and report it to investors?
• How do you set OTE and base/variable splits for a first enterprise AE hire?