The proposal-team staffing playbook (3, 15, 50 seats)

Proposal-team structure is not a matter of culture or maturity. It is a matter of volume. A company responding to six strategic bids a year has a different organizational problem than a company responding to 40 a year, and both of them have a different problem than a company responding to 300 a year. The same words — capture, compliance, color-team review — show up at every scale. The people behind the words are arranged completely differently.

This post is the canonical version of a staffing conversation I have repeatedly when proposal leads ask me how to build their team. There are, in my experience, three stable sizes: the three-seat shop, the fifteen-seat shop, and the fifty-seat enterprise proposal function. Anything in between is either growing into the next size or shrinking into the previous one. The three sizes are stable because they correspond to three different operational postures — not three steps on the same ladder.

This is not the only view of the question. APMP’s compensation survey publishes role-by-role salary data that implies its own sizing framework. The Shipley guide assumes a shape closer to the fifty-seat enterprise function as its default. I am not arguing against either; I am writing the playbook from the operator side, which is the view I have.

The three-seat shop

The team. One proposal lead. One or two writers. Capture and content work is shared across the team or outsourced. That is the shop.

The proposal lead — often called a proposal manager, sometimes a head of proposals if the title is generous — owns the intake, the bid/no-bid, the compliance matrix, the review scheduling, the submission, and at least some of the drafting. They are a player-coach. The writers, one or two of them depending on bid volume, draft sections, coordinate with SMEs, and cover capacity when the proposal lead is on a strategic bid. Sometimes one of the writers has secondary ownership of the knowledge base — in the three-seat shop, “owns the KB” means “occasionally cleans it up on a Friday,” and that is okay at this scale.

Capture is where the three-seat shop gets unstable. There is no dedicated capture lead; capture work lives with the sales function, with the account executives who sourced the opportunity, or with a founder. Often it does not happen at all, and the bid response starts from scratch every time. The honest version is that the three-seat shop does not systematically do capture; it does capture well for a small subset of strategic bids and skips it on the rest.

What the three-seat shop skips. Nothing, formally. Compressed, mostly. The compliance matrix gets built, but it is built as a working document during drafting rather than as an upfront artifact. Color-team reviews happen, but they usually collapse to a single pink-plus-red hybrid review and a very short gold check before submission. Post-mortems happen, but they are informal — a 20-minute debrief in the next team meeting rather than a scheduled retrospective with written output. SMEs are wrangled by the proposal lead directly, and the ticket-style discipline described in the SME collaboration piece is too heavy for the shop to maintain.

The things that actually disappear at this scale are the governance overheads of a larger function: not formal color-team cadences, not capture plans as standalone documents, not review-calendar discipline. The proposal lead is holding those disciplines in their head and compressing them into the bid-by-bid workflow. This is sustainable while the team is three people. It is not sustainable at five.

What the three-seat shop does well. Speed and flexibility. The team can turn a bid in a week because the coordination overhead is low — three people in one Slack channel can be in sync without a meeting. Decisions about structure, voice, and messaging happen in real time. The proposal lead can personally ensure every bid reflects the win themes they wanted.

The other thing the three-seat shop does well: the proposal lead knows every active bid intimately. There is no hand-off gap, no “whose bid is that” confusion, no context loss between capture and draft. The small-team coordination advantage is real and it is the reason the three-seat shop can produce high-quality responses despite not running the full ceremony.

Named failure modes. Three, in order of how often I see them.

The first: the proposal lead becomes the bottleneck. Every bid needs them. They are involved in intake, bid/no-bid, capture, compliance, drafting some sections, reviewing all sections, and submission. When they are on vacation, the function stops. When they are sick, bids slip. Three-seat shops are structurally fragile on this axis and the proposal lead has to actively delegate to avoid the function collapsing around them.

The second: capture does not happen. With no capture lead, capture is nobody’s named job, which means it gets done by whoever cares most that week. On bids the proposal lead thinks are strategic, it happens well. On bids the proposal lead thinks are transactional, it does not happen at all, and the response is generic. The three-seat shop wins fewer strategic bids than it should because the capture work that would have differentiated them did not happen.

The third: content debt accumulates. Because no one formally owns the KB, content rots. The reviewer model of SME engagement — which depends on a KB the writers can draft from — breaks when the KB is stale, and the shop slides back into the pattern of SMEs drafting from scratch. The bids take longer. The SMEs get frustrated. The KB rots further. Lohfeld Consulting has described this feedback loop as “processes holding you back,” and it is the specific pattern the three-seat shop has to actively interrupt.

When to jump. Two signals that it is time to move to the fifteen-seat shape. First, bid volume consistently exceeding what the proposal lead can personally oversee — practically, somewhere around 25–35 active bids a year, depending on bid complexity. Second, a strategic need to do capture systematically rather than opportunistically; typically this shows up when the company is targeting enterprise buyers with sales cycles long enough that capture work is a distinct, multi-week effort per bid.

The fifteen-seat shop

The team. One proposal director or head of proposals. Three to five proposal managers, each owning a portfolio of bids. A capture lead (sometimes shared with sales). An operations lead. A KB owner. A loosely-defined SME coordinator role, which is often a senior proposal manager wearing a second hat.

This is the shape most mid-sized B2B companies settle into when they take proposal work seriously. It is also the shape where the APMP-canonical practices — real color-team reviews, written capture plans, structured bid/no-bid scoring — become tractable rather than aspirational.

The proposal director sets overall strategy, owns the bid/no-bid decisions for the largest bids, represents the proposal function to the rest of the company, and manages the proposal managers. They are not on the bids day-to-day; they are overseeing the function. This is the role that does not exist in the three-seat shop — its absence is what defines the three-seat shop.

The proposal managers run bids. Each one carries a portfolio — three to six concurrent bids at any given time — and runs them through the eight-stage RFP pipeline. They do not draft; they coordinate drafting. They own the compliance matrix, the review calendar, the submission, and the post-mortem. They are the single point of accountability for each bid they carry.

The capture lead is where real capture discipline enters the function. They work with the sales team on upstream positioning — the months before an RFP posts — and produce written capture plans for every bid the shop intends to respond to. Qorus has written repeatedly about the SME-wrangling problem as the dominant theme in mid-sized proposal functions; the capture lead’s written plan is the artifact that lets the proposal manager pre-identify which SMEs will be needed on which sections, which in turn lets the SME coordinator set expectations upstream rather than scrambling.

The operations lead handles the infrastructure — the tool stack, the portal submissions, the templates, the version control. They are often a senior coordinator who grew into the role. Their presence is what lets the proposal managers spend time on bid strategy rather than on portal mechanics, which is where Quilt’s observation that sales engineers spend 100 to 300 hours per RFP response shows up most sharply: at the fifteen-seat scale, the ops lead’s job is specifically to reduce the non-strategic hours the rest of the team spends.

The KB owner is the role most often missing at this scale, which is why content debt shows up in fifteen-seat shops just like it shows up in three-seat shops, just more visibly. When the role is actually staffed — a person whose named job is content freshness, ownership clarity, and the structured review cadence described in the SME piece — the proposal function compounds. When it is not, every bid draws from a KB that is slightly more drifted than the last bid’s, and the compounding thesis breaks.

How color-team reviews actually work at this size. The fifteen-seat shop is where the full color-team structure becomes realistic. A pink team at roughly 30% draft, a red team at roughly 80%, a gold team at roughly 95%. Each review has named reviewers drawn from across the team — the proposal director, peer proposal managers, SMEs for the technical sections, sometimes customer-success leads for past-performance sections. The reviews are scheduled at kickoff and held to. The one qualification: on bids smaller than the shop’s threshold, the reviews often collapse to a single combined review — closer to what the color-team-review-modern-teams post described as the right-sized version.

The discipline is not that every bid gets the full ceremony. The discipline is that the review structure is appropriate to the bid size, and the decision about which ceremony a bid gets is made at kickoff, not improvised during drafting.

SME wrangling patterns. Three patterns work at this size. The first is the SME ticket queue — structured, SLA-bearing, visible to the SME’s manager. The second is the “SME reviewer, not author” pattern from the SME collaboration piece — writers draft from the KB, SMEs review. The third, which shows up at fifteen-seat shops and almost never at three-seat shops, is the SME liaison function: a person on the proposal team whose specific job is to maintain the relationship with the SME pool, track who is available when, and negotiate load across the proposal managers. The liaison role is small — often a fractional hat on a senior coordinator — but its presence meaningfully smooths the SME dynamic, and its absence means every proposal manager is running their own SME coordination in parallel, which scales badly.

Named failure modes. Three.

The first: portfolio imbalance. One proposal manager ends up with the big strategic bids; the others carry the volume of transactional bids. The strategic proposal manager burns out. The transactional proposal managers feel under-invested in. A year of this and the function loses its senior talent. The fix is disciplined portfolio balancing by the proposal director — not purely by bid count, but by weighted complexity.

The second: KB debt compounds invisibly. The shop ships bids successfully for 18 months while the KB quality slowly degrades underneath. At some point the win rate starts to drop and nobody can point to a specific cause. The drop is the accumulated effect of drafting from a drifting KB. By the time it is visible, the fix is a multi-quarter content-cleanup project. Sparrow Genie has named this pattern in content-library contexts specifically.

The third: the capture-to-proposal handoff fails. This is the specific failure mode the handoff-checklist post walks through. In the three-seat shop, the handoff is informal because everyone was involved in the capture. In the fifteen-seat shop, the capture lead did the work and the proposal manager picks it up cold — and if the handoff artifact is thin, the proposal manager reinvents parts of the capture while drafting. The seven-field checklist is specifically a fifteen-seat intervention.

When to jump. Two signals for the next tier. First, bid volume regularly exceeding what five proposal managers can carry — roughly 75–100 active bids a year as a rough rule, though it varies widely by bid complexity. Second, a need for specialization that the generalist proposal-manager role cannot absorb: pricing specialists, past-performance specialists, technical-section specialists, compliance-and-legal specialists. When you find yourself wanting a proposal manager to be an expert in three unrelated domains, you are ready for the next tier.

The fifty-seat enterprise proposal function

The team. A proposal director or VP of proposals, sometimes with a “proposal operations” peer. Two to four regional proposal managers, each covering a geography or a vertical. Specialist writers organized by discipline — technical writers, pricing analysts, past-performance writers, executive-summary writers. A dedicated capture team with its own capture leads. A KB team with a KB manager and content analysts. An analytics function — someone whose job is win/loss intelligence, bid-ROI measurement, and pipeline dashboards. An SME liaison function, now a dedicated headcount rather than a hat. A legal/compliance embed. Often an in-house design team dedicated to proposal graphics.

This is the shape of the enterprise proposal function — the kind that lives inside a defense contractor, a large federal-services firm, a global management consultancy, or a very large healthcare vendor. The shop responds to bids whose individual ACV is eight or nine figures, and the investment in the proposal function is justified by the deal sizes it supports.

The enterprise proposal function runs differently from its smaller counterparts not because it works harder at the same things but because it runs different things entirely. Governance, for example, is a real layer here — there is a proposal-governance council that reviews bid/no-bid decisions above a certain threshold, a proposal-strategy forum that reviews win-themes for strategic pursuits, and a submission-approval path that goes through legal and finance before any response leaves the building. None of those exist in the fifteen-seat shop.

The specialization is the other defining characteristic. A pricing analyst on the proposal team is not a proposal writer who happens to be good at pricing — they are a pricing-operations professional who has been embedded in proposals and brings a different skill set. Past-performance writers specialize in writing exactly those narratives, and the specialization is what produces the past-tense, specific, humble voice described in the past-performance voice post reliably across every bid. Technical writers work closely with SMEs but are not SMEs themselves; their craft is translating SME content into evaluator-readable prose.

The capture function, at enterprise scale. The capture team is the size of the entire fifteen-seat proposal shop. Capture leads own relationships with buyers over multi-year timelines, not just on specific bids. The capture function influences RFP shape before the RFP posts — sometimes through formal advance-procurement engagement, sometimes through industry-day participation, sometimes through direct customer engagement months in advance. This is the kind of capture work Shipley’s guide treats as the default; it is tractable only at enterprise scale.

The KB team, at enterprise scale. A KB team with four to six people operates fundamentally differently from a single KB owner. There is a content-governance role that sets standards. There is a content-analyst role that runs the freshness reviews systematically across thousands of blocks. There is a content-strategy role that identifies gaps — questions that keep being asked on bids that the KB does not have good answers for — and drives content creation projects to close the gaps. The KB team’s output is measurable: blocks added, blocks verified, blocks retired, retrieval-quality metrics per segment.

Governance overhead. This is what people outside the enterprise proposal function underestimate about it. The fifteen-seat shop has three governance meetings a week at most. The fifty-seat shop may have fifteen. The cost of governance is real; the benefit is that decisions affecting eight-figure pursuits are made deliberately, with multiple informed stakeholders in the room, rather than improvised by a single proposal manager. At enterprise scale the cost is worth it. At smaller scales the same ceremony would consume the function.

The SME liaison function, at enterprise scale. Named headcount, not a hat. The SME liaison runs a capacity model for the entire engineering, legal, finance, and customer-success SME pool. They know who is available on which weeks, who has expertise on which topics, and who has maxed out on proposal load this quarter. When a new bid is accepted, the SME liaison assigns the likely SME needs and negotiates load proactively. The proposal manager does not Slack random SMEs. They request SME support through the liaison, who orchestrates.

This is the shape that genuinely reduces the SME bottleneck at scale. The 48% number that has held steady for five years is an industry-wide average; the enterprise functions that have staffed a real SME liaison role do better than the average, and the ones that have not, even at fifty seats, are still inside the industry average.

Named failure modes. Three.

The first: governance becomes performance. The governance meetings happen, the review decks are produced, the approvals are recorded. And the actual strategic debates that should be happening inside those meetings do not happen, because the meetings are treated as checkpoints to clear rather than forums to wrestle with hard decisions. The enterprise proposal function that has lost its strategic voice looks, from the outside, indistinguishable from a healthy one; from the inside, the staff know the difference. This is the failure mode that degrades over years rather than quarters.

The second: specialization becomes silo-ization. A pricing analyst who does not talk to past-performance writers produces pricing narratives that do not reinforce past-performance evidence, and vice versa. At enterprise scale the specializations can become so deep that cross-pollination requires explicit coordination. When the coordination lapses, bids read like they were written by ten different people, because they were.

The third: the KB team outgrows its usefulness. A content-governance function that produces governance for its own sake — style guides, approval workflows, taxonomy projects — without a tight connection to what the bids need, ends up as a cost center the proposal function does not fully trust. The fix is disciplined outcome focus: every KB-team initiative has a measurable proposal-side benefit, or it gets deprioritized.

When to jump tiers

Two structural questions determine when a shop is actually ready to move, rather than just grow.

Is the current tier limiting win rate? If the function is losing bids it should be winning because the current structure cannot support them — capture that is not happening, review that is not thorough enough, content that is not fresh enough — that is a signal to jump. If the function is losing bids because of market conditions, bid-quality issues, or product fit, restructuring the proposal team will not change anything.

Can the next tier support itself economically? The fifteen-seat shop requires roughly $3–8M in annual proposal-attributable revenue to justify its cost, depending on industry and geography. The fifty-seat shop requires substantially more. A shop that jumps to the next tier before the revenue supports it ends up downsizing, which is worse than not jumping — the function loses talent during the contraction and rebuilds from a worse starting point.

Operational signals. A few specific signals that usually precede a successful tier jump:

• The proposal lead at the current tier is burning out specifically because they are doing work that should be delegated to a role that does not yet exist.
• The same category of bid is being lost repeatedly for the same structural reason — missing capture, missing specialist expertise, missing freshness.
• The company’s strategic plan is targeting a deal size or vertical that the current function cannot credibly pursue.
• Win rate on strategic bids is trending down while win rate on transactional bids stays flat.

A tier jump is a multi-quarter investment. New headcount takes time to become productive. The operational disruption during the transition is real. A shop that jumps tiers cleanly takes two to three quarters to reach steady state at the new size; a shop that jumps poorly can take a year or more.

Closing

Staffing is structural, not cultural. The three-seat shop, the fifteen-seat shop, and the fifty-seat enterprise function are different operating models, not different points on the same growth curve. Each has its own governance profile, its own specialization pattern, its own capture posture, and its own failure modes.

The compounding advantage in proposal work — the thesis the eight-stage pipeline post closed on, and that the SME collaboration piece developed — is available at every tier. The three-seat shop compounds through the proposal lead’s personal memory. The fifteen-seat shop compounds through the KB owner’s structured cadence. The fifty-seat shop compounds through the KB team’s analytics.

What the tiers share is the belief that every bid should make the next one easier. What differs is the mechanism by which that belief gets operationalized. Pick the mechanism that fits your scale. Staff for the shape you are actually running, not the shape you read about in the Shipley guide. When the shape starts to strain, jump — but jump deliberately, with the revenue to support it, and with a written plan for what the next tier actually looks like.

Three sizes. Three playbooks. Pick yours.