How do you architect revenue operations for an aerospace company in 2027?

The supplier that won the design slot and lost the program

Picture a Tier-2 structural components supplier doing roughly $180M a year, split about 70/30 between commercial airframe work and a small defense book. They have twelve AEs, one shared Salesforce org that was configured for a distribution business six years ago, and a VP of Sales who came up selling to airlines. In Q1 they win a design-slot position on a new narrowbody wing subassembly — the kind of award that shows up in the board deck as a headline and prints revenue for fifteen years.

Eighteen months later the program slips, the OEM re-competes a portion of the work package, and the supplier loses it. The post-mortem finds nothing wrong with the engineering. What went wrong was operational. The design-slot award had been logged in the CRM as a single closed-won opportunity worth the first year of shipset revenue, so nobody was tracking the follow-on qualification milestones. Nobody owned the first-article inspection schedule as a revenue-affecting event. The customer's program office changed procurement leads twice and neither transition was captured, because contacts were owned by the AE personally rather than by an account team. And the NADCAP special-process accreditation for one of the heat-treat lines came up for renewal during the same quarter the OEM was re-scoring suppliers — the accreditation was restored, but not before the supplier got flagged on a quality scorecard that fed directly into the re-compete decision.

That is the shape of the aerospace revenue operations problem. It is not a lead-generation problem. Design-slot positions on major platforms are not won by top-of-funnel volume; the buyer universe is small enough that most suppliers could name every account that matters on a whiteboard. The problem is that aerospace revenue events span 24 to 60 months, run through engineering and quality functions that report nowhere near sales, and are gated by certifications and export-control conditions that a standard CRM has no concept of. Architecting revenue operations here means building a system that can hold a five-year commitment as a live, instrumented object rather than a closed record — and that can tell you, on any given Monday, which of your programs are at risk from something other than a competitor's price.

The rest of this page walks the architecture: how the four-buyer routing mechanism works, what the real numbers and coverage ratios look like, where the trade-offs sit between building versus buying each layer, and the specific failure modes that take suppliers down.

How the four-buyer routing mechanism actually works

The core mechanism is that a single opportunity object with a single stage model cannot serve aerospace. You need four parallel pipeline definitions sharing one data spine, with routing that happens at lead creation and never gets manually overridden.

Start with buyer-type classification as a required field at record creation, derived from the account rather than entered by the rep. Commercial OEM accounts — the airframers and their major structures partners — get the OEM pipeline. Defense primes and direct government customers get the defense pipeline. MRO providers and aftermarket distributors get the MRO pipeline. Airlines, lessors, and fleet operators get the operator pipeline. An account can carry more than one classification (GE Aerospace is an OEM buyer for engine components and an MRO buyer for shop-visit parts), so classification belongs on the opportunity, seeded from the account's default.

Each pipeline gets its own stage set and its own exit criteria. The OEM pipeline runs on program milestones, not sales stages: technology readiness engagement, design-in / spec-position, RFQ response, source selection, qualification, first article, rate production. The defense pipeline runs on capture phases: opportunity identification, pre-RFP capture, bid/no-bid gate, proposal, evaluation, award, contract negotiation. The MRO pipeline runs closer to conventional B2B — qualification, technical evaluation, pricing, contract — because the cycles are genuinely shorter. The operator pipeline runs shortest of all and is often the only one where a conventional sales-stage model applies cleanly.

The second half of the mechanism is what happens to a program after award. This is where most suppliers break. A design-in win is not a closed opportunity; it is the beginning of a revenue stream with its own milestone schedule, its own risk of loss, and its own follow-on expansion opportunities. Model it as a program record — a parent object holding the platform, the shipset content, the rate assumptions, the qualification milestones, the applicable certifications, and the export-control classification. Opportunities hang off the program. Backlog rolls up from it. When the OEM changes a production rate, you update one field and the forecast impact propagates across every opportunity attached.

The third mechanism is the compliance gate. Export-control classification and certification status must be attributes of the opportunity, not documents in a shared drive. An opportunity involving a defense article carries an ITAR flag that changes who can see the record, what can be attached to it, and which foreign nationals can be added to the account team. An opportunity requiring a special process carries a pointer to the accreditation covering that process, with its expiry date. If the accreditation lapses, every attached opportunity turns red automatically. That single piece of wiring would have caught the heat-treat renewal in the scenario above.

Note what the diagram does not contain: a generic MQL-to-SQL handoff. In a market where the entire addressable buyer set fits on one page, lead scoring matters far less than account-team coverage and milestone discipline. Spend the RevOps engineering budget on the program object and the compliance gate, not on a scoring model.

Real numbers, ranges, and benchmarks worth planning against

Cycle length is the first number that reshapes everything else. Platform-program pursuits at commercial OEMs and defense primes routinely run 24 to 60 months from first substantive engagement to contract award, and longer if the platform itself slips. Aftermarket and OEM-approved parts positions run shorter, commonly 12 to 24 months. MRO contracts land in the 6 to 12 month range. Airline and operator purchases can close in 3 to 9 months. Those four ranges are why a single pipeline velocity metric is meaningless here — a blended average across all four tells you nothing actionable.

Pipeline coverage should be set per motion, not globally. Long-cycle defense and OEM pursuits need heavy coverage — in the range of 6x to 8x of the period target — because the loss rate on individual pursuits is high and the timing of awards is outside your control. MRO sits lower, around 4x to 5x. Operator business can run at 3x. If you apply a single 3x coverage rule across the whole business, you will systematically under-build the defense and OEM funnel and discover the gap two years too late to fix it.

Win rates differ by motion just as sharply. Defense pursuits entered late — after the RFP drops, with no prior positioning — win at a rate low enough that the honest planning assumption is near zero; the incumbent or the pre-positioned bidder has already shaped the requirements. Defense pursuits entered 12 to 24 months early with a funded capture plan win at a meaningfully higher rate, often in the 25% to 35% band for a supplier with relevant past performance. Commercial OEM re-competes where you are the incumbent win high — 60% or better is achievable when quality scorecards are clean. New-entrant OEM pursuits win far lower. Track these four win rates separately and never report a blended number to the board.

Capture investment is the number most suppliers get wrong in both directions. Underfunding capture means bidding blind; overfunding means burning engineering hours on pursuits you were never going to win. A workable frame is to size capture spend as a percentage of expected contract value and to gate it: opportunities below a defined threshold — many mid-size suppliers set this somewhere between $2M and $5M of lifetime value — get a lightweight response with no dedicated capture manager. Above the threshold, a capture plan is mandatory and includes competitor assessment, customer hot-button analysis, teaming strategy, and price-to-win work. The bid/no-bid gate should have real teeth: a documented target win probability below which you decline, and a discipline of actually declining. The single highest-leverage RevOps intervention in a defense-adjacent business is usually raising the no-bid rate.

Staffing ratios follow from the technical depth of the sale. Engineering-credentialed solution architects — people who can hold a design review, not demo software — typically support 3 to 5 AEs each. Capture managers on active defense pursuits support fewer, often 3 to 4 AEs, because capture is a full-time role per major pursuit during the intense phases. Program managers for post-award milestone execution are engineering program managers, not quota-carrying sellers, and they should report through operations with a dotted line to revenue.

Margin structure is the reason the MRO motion deserves its own leader and its own P&L. Aftermarket and MRO work carries substantially higher gross margin than original-equipment production — the spread is wide enough that a shift of ten points of revenue mix from OE to aftermarket can move blended gross margin by several points on its own. That makes MRO attach rate a first-class revenue metric: for every new OE program won, what percentage converts into a multi-year aftermarket agreement, and at what point in the program lifecycle is that agreement signed? Signing aftermarket terms at start-of-production, when your leverage is highest, is worth materially more than negotiating them years later when the fleet is already flying and third-party shops are competing for the work.

Backlog and book-to-bill are the metrics the aerospace board actually reads, and they are not sales metrics in the SaaS sense. Backlog is contracted, unshipped revenue across multi-year programs. Book-to-bill is bookings divided by billings for the period; sustained below 1.0 means the backlog is draining faster than it is being replaced, which is the single clearest early warning of a revenue architecture that has stopped working. Report both monthly, with backlog decomposed by program and by year of expected recognition — a backlog number that does not show its recognition curve hides more than it reveals.

Trade-offs: what to build, what to buy, and what to leave alone

Every layer of this architecture has a build-versus-buy decision, and the right answer depends heavily on revenue scale and on which motion dominates the mix.

CRM platform. The realistic choice is between a manufacturing-oriented CRM configured for program and account-based revenue, or extending the ERP vendor's own sales module. The manufacturing CRM route gives you a better seller experience, a deeper integration ecosystem, and faster configuration; the ERP-native route gives you tighter write-back to production planning, costing, and contract accounting. The deciding question is usually where your hardest integration lives. If the painful daily reality is reconciling bookings against production schedules and cost-type contract accounting, the ERP-native path wins despite the worse UI. If the pain is that sellers do not use the system at all and program data lives in spreadsheets, the manufacturing CRM path wins. Either way, budget more for configuration than for licenses — the program object, the four pipelines, and the compliance gate are all custom work.

Market and program intelligence. Subscription intelligence on platform programs, production rates, and defense budget lines is expensive — the serious sources run well into five figures annually and a full stack can reach six. The trade-off is against the cost of being wrong about timing. If your business depends on knowing when a program moves to a new rate or when a budget line gets funded, the subscription pays for itself in one avoided misallocation of capture spend. If you are primarily an MRO or aftermarket business responding to fleet events, the intelligence value drops sharply and public sources plus customer relationships carry most of the load. Do not buy the full stack reflexively; buy the layer that maps to your dominant motion.

Government procurement data. Public procurement sources — solicitation notices, contract award databases, spending records — are free and genuinely useful. Paid aggregators add earlier signal, better alerting, and relationship mapping on top of the same underlying public data. For a supplier with a small defense book, the free sources plus a disciplined weekly review are adequate. Once defense passes roughly a quarter of revenue, the aggregator earns its cost through alert latency alone: knowing about a pre-solicitation notice within a day rather than a month is the difference between a capture plan and a scramble.

Conversation intelligence and forecast tooling. These are the layers most likely to be over-bought in aerospace. Call recording is far less valuable when the sale is a two-year technical engagement conducted substantially in design reviews, on-site audits, and program meetings that nobody is recording. Forecast automation is less valuable when the forecast is driven by customer program milestones rather than by rep judgment on close dates. Buy conversation intelligence if you have a high-velocity MRO or operator motion where call volume is real; skip it or buy minimal seats if you are purely program-driven. Put the money into the program object instead.

Export control and trade compliance tooling. This one is not really a trade-off. Restricted-party screening, license tracking, and technology control plan management should be systematized rather than run on spreadsheets, because the failure mode is not inefficiency — it is regulatory exposure with criminal dimensions. The real trade-off is scope: screen every counterparty and every foreign-national contact continuously, or screen at defined checkpoints. Continuous is better and costs more. Checkpoint screening is defensible for a business with a narrow, stable customer set, provided the checkpoints include every new contact, every teaming agreement, and every technical data transfer.

Capture management. Build, do not buy. Outsourced proposal shops can write compliant volumes, but capture is fundamentally about customer intimacy accumulated over years — knowing the program office, the incumbent's weaknesses, the evaluators' priorities. That knowledge does not survive an engagement boundary. Hire capture managers as employees, pay them like senior sellers, and give them the authority to say no to bids.

The pitfalls that actually take aerospace suppliers down

Treating a design-in as a closed deal. This is the scenario at the top of the page and it is the most common structural failure. The fix is the program object: award creates a program, the program carries milestones, and milestone slippage generates work for a named owner. If your CRM shows a win and then goes quiet for eighteen months, you have this problem.

Blended metrics that hide the failing motion. A blended win rate, a blended cycle time, or a blended coverage ratio across four buyer types will always look acceptable while one motion quietly dies. Report all four separately, every month, with no aggregate line. If the board wants one number, give them book-to-bill.

Bidding without capture. Responding to RFPs you first learned about when they published is not a pipeline strategy; it is a way to donate engineering hours to a competitor's price validation. The fix is a bid/no-bid gate with enforced criteria and a leader willing to defend a low bid volume. Track the no-bid rate as a positive metric, and review declined pursuits quarterly to confirm you were declining the right ones.

Certification treated as a quality-department problem. Quality management system accreditation, special-process accreditation, and airborne software and hardware compliance are revenue gates. A lapse blocks shipments and can knock you off approved-supplier lists, and restoration is measured in quarters, not weeks. The fix is mechanical: every certification in a tracked register with an expiry date, renewal work starting a full year out, and certification status appearing on the same dashboard as pipeline coverage. Assign a named owner who reports the status in the monthly revenue reconciliation, not just to the VP of Quality.

Export-control exposure managed informally. The failure mode is rarely a deliberate violation. It is a foreign-national engineer added to a program email thread, a technical drawing attached to a CRM record visible to the wrong team, a teaming partner not re-screened after an ownership change. Consequences run to substantial settlements, loss of export privileges, and individual criminal liability. The fix is architectural rather than procedural: access controls on ITAR-flagged records enforced by the system, screening triggered automatically at defined events, a technology control plan that is actually maintained, and a voluntary-disclosure protocol agreed with counsel before you need it. Route ownership through legal, not sales.

Cost-type contract accounting bolted on late. If you take cost-reimbursable government work, the accounting system must support the associated audit requirements from the start. Retrofitting adequate timekeeping, indirect rate structures, and cost segregation after you already hold the contract is expensive and risky, and an adverse audit finding triggers renegotiation, cash recovery, and reputational damage that follows you into the next competition. Decide before the first cost-type bid whether you are willing to build the accounting infrastructure. If not, stay on firm-fixed-price work and say so as policy.

Account knowledge held personally by reps. In a market with 24-to-60-month cycles and customer program offices that reorganize every couple of years, an AE departure can vaporize the relationship history on a program worth a decade of revenue. The fix is account-team ownership, mandatory contact and interaction logging enforced at the opportunity level, and a program record that a successor can read and understand without the predecessor. This is unglamorous data hygiene work and it is worth more than any tool purchase in the stack.

Under-instrumenting the aftermarket. Suppliers optimize hard for the OE win and then let the higher-margin aftermarket revenue leak to third-party shops because nobody owned the attach motion. The fix is a separate MRO leader with a separate number, an aftermarket attach component in the OE seller's compensation, and a contractual push to sign multi-year aftermarket terms at start-of-production while your negotiating leverage is at its peak.

No cadence connecting revenue to engineering and quality. The architecture only holds together if the operating rhythm forces the functions into the same room. A weekly program-and-capture review covering top pursuits by motion and any milestone slippage. A monthly backlog reconciliation with finance, covering book-to-bill, backlog recognition curve, certification register, and any compliance incidents. A quarterly architecture review that revisits capture investment allocation, portfolio balance across the four motions, and the certification roadmap. Without those three meetings, everything above is documentation rather than operations.

Related questions

Does an aerospace supplier under $50M in revenue need all four buyer motions?

No. Most small suppliers serve one or two. Build the program object and the certification register regardless — those apply at any scale — but do not create four leadership roles and four pipelines for motions you do not actually run. Add a motion when it passes roughly 15% of revenue.

How should a defense-heavy supplier handle CRM access for foreign nationals?

Enforce it in the system, not by policy memo. Records carrying an export-control flag should be invisible to users without documented authorization, with attachments restricted separately. Reviewing access lists quarterly is a compliance requirement, not an IT chore, and belongs in the monthly reconciliation.

What is the right first hire when building this function from scratch?

A revenue operations lead who can build the program object and the reporting spine, hired before any additional sellers. Adding quota carriers to an uninstrumented pipeline just produces more untracked pursuits. The second hire is a capture manager if defense is meaningful, or an engineering solution architect if it is not.

How do you forecast revenue when customer program rates keep changing?

Forecast off the program object, not off opportunity close dates. Model shipset content times announced production rate times your share, then run scenarios at announced rate, announced minus a slippage haircut, and a downside case. Report the range, not a point estimate.

Should MRO sit under the same CRO as OEM sales?

Yes for reporting, no for operating model. Both should roll up to one revenue leader so portfolio decisions get made once, but MRO needs its own pipeline definition, its own coverage ratio, and its own P&L visibility because the margin profile and cycle length are entirely different.

FAQ

How long do aerospace sales cycles actually run?

It depends entirely on the motion. Platform-program pursuits at commercial OEMs and defense primes commonly run 24 to 60 months from first substantive engagement to award, and can stretch further if the platform schedule slips. Aftermarket and OEM-approved part positions run roughly 12 to 24 months. MRO contracts land in the 6 to 12 month range. Airline and operator purchases can close in 3 to 9 months. Any metric that averages across all four is misleading.

What pipeline coverage ratio should we run?

Set it per motion. Long-cycle defense and commercial-OEM pursuits warrant 6x to 8x coverage because individual pursuit loss rates are high and award timing is outside your control. MRO runs closer to 4x to 5x. Operator business can sustain 3x. A single global ratio systematically under-builds the long-cycle funnel, and because those cycles run years, you discover the shortfall far too late to correct it.

Do we need a dedicated capture manager?

If defense or government work is a meaningful part of the mix and you pursue opportunities above a few million dollars in lifetime value, yes. Capture is a distinct discipline from selling — pre-RFP positioning, competitor assessment, price-to-win analysis, teaming strategy — and it needs full-time attention during active pursuit phases. Below that threshold, a lightweight proposal response process run by the AE is adequate and a dedicated hire is not justified.

Which certifications gate aerospace revenue?

At minimum the aerospace quality management system standard, which is effectively table stakes for supplying the industry. Special-process accreditation applies if you perform heat treatment, welding, surface finishing, non-destructive testing, or similar operations. Airborne software and electronic hardware development assurance guidance applies to flight-critical software and complex electronics. Defense work handling controlled unclassified information carries its own cybersecurity maturity requirements. Track each with a named owner and an expiry date.

How do we keep export-control compliance from becoming a bottleneck?

Automate the screening and the access control so compliance happens as a side effect of normal system use rather than as a separate approval queue. Restricted-party screening should fire automatically on new contacts, new teaming partners, and ownership changes. Access to controlled records should be enforced by permission model. Reserve human review for genuine edge cases — new jurisdictions, novel technical data transfers, license applications — and keep ownership with legal.

What single metric best signals the architecture is working?

Book-to-bill sustained above 1.0, reported alongside a backlog recognition curve. It captures whether you are replacing consumed backlog faster than you burn it, which is the underlying health question in a program-driven business. Win rate and coverage are useful diagnostics when book-to-bill deteriorates, but they are inputs; book-to-bill is the outcome the board should be watching every month.

Sources

• https://www.aia-aerospace.org/
• https://www.sae.org/standards/
• https://www.faa.gov/aircraft/air_cert
• https://www.easa.europa.eu/en/domains/aircraft-products
• https://www.pmddtc.state.gov/ddtc_public
• https://www.bis.doc.gov/index.php/regulations/export-administration-regulations-ear
• https://sam.gov/
• https://www.usaspending.gov/
• https://dodcio.defense.gov/CMMC/
• https://www.dcaa.mil/

Related on PULSE

• [How to architect revenue operations for a vending machine operator in 2027](/knowledge/ra0644)
• [How to architect revenue operations for a courier and same-day delivery company in 2027](/knowledge/ra0643)
• [How to architect revenue operations for a credit union in 2027](/knowledge/ra0642)
• [How to architect revenue operations for an optometry and eye-care practice in 2027](/knowledge/ra0641)
• [How to architect revenue operations for a multi-location chiropractic clinic group in 2027](/knowledge/ra0640)