You can see the problem in the dashboard before anyone says it out loud. Marketing hit lead targets. Sales says the handoff is weak. Customer success is tracking onboarding in a separate system or spreadsheet. Finance has renewal data, but nobody can tie it back to the original acquisition source with confidence.
That setup creates a false sense of control. Teams optimise the front half of the journey because that's what the funnel shows clearly. Once a deal closes, reporting often gets fuzzy, ownership shifts, and the CRM stops telling the full revenue story.
The bow tie model fixes that. It treats Closed Won as the midpoint, not the finish line. That changes how you design lifecycle stages, how you structure Salesforce or HubSpot, and how you measure performance across acquisition, conversion, onboarding, retention, and expansion. For RevOps teams, that's the core value. Not another framework slide. A better operating model for the systems you already run.
Why Your Funnel Is Only Half the Picture
A traditional funnel is useful, but it's incomplete.
It shows how demand moves towards a sale. It doesn't naturally show what happens after the opportunity closes, who owns value delivery, or whether the customers you acquired were worth acquiring. In B2B, that gap matters because revenue doesn't stop at signature. It compounds, stalls, or erodes after the sale.
Where teams get stuck
The most common pattern looks like this:
- Marketing optimises volume: Campaigns drive form fills, MQLs, and meeting creation.
- Sales optimises pipeline: Reps focus on stage progression, forecast movement, and close plans.
- Customer teams optimise delivery: Onboarding, support, adoption, and renewal run in a separate rhythm.
- Leadership gets fragmented reporting: Each function has a dashboard, but nobody has one model that connects all of them.
The result is predictable. Marketing can't prove which channels produce durable customers. Sales can't see whether poor-fit deals turn into churn risk. Customer success inherits accounts without enough context on promise, source, or buying motion.
The funnel ends exactly where your revenue risk starts becoming more visible.
What the bow tie model changes
The bow tie model gives you a cleaner way to organise the full lifecycle. The left side captures how prospects move towards purchase. The centre marks the commitment point. The right side tracks what happens after the customer is live.
That simple shift changes the operating questions your CRM should answer:
- Which acquisition paths create customers that adopt well?
- Which sales motions produce cleaner handoffs and fewer post-sale issues?
- Which customer segments renew, expand, or advocate most reliably?
A normal funnel struggles with those questions because it treats the close as the endpoint. The bow tie model doesn't.
Why this matters in RevOps
RevOps sits in the middle of process, data, and accountability. That means you need a model that supports handoffs, not just lead flow.
If your lifecycle design only covers lead to opportunity, you'll end up with blind spots in account ownership, attribution, health tracking, and expansion planning. A bow tie design forces a better CRM architecture. It makes teams define the handoff event clearly, decide what post-sale stages matter, and build reporting that follows the customer past the contract.
That's the difference between managing a funnel and running a revenue engine.
Deconstructing the Bow Tie Model
The bow tie model didn't start in marketing. It comes from risk management and safety planning, where teams needed a structured way to map causes, critical events, and downstream consequences in one view. The model was first suggested in 1979, and later safety literature describes it as a fusion of a fault tree and an event tree, with the Top Event as the central knot linking causes on the left to consequences on the right, as described in this bow-tie history and review in safety literature.
That matters because it makes the framework more than a clever GTM metaphor. It's a mature model that has been in formal use for about 45+ years since 1979, and it's still used because it helps people see one critical event, the paths leading into it, and the outcomes that follow.
The original structure
The bow tie model has five parts:
- Hazard: The thing that carries risk or potential value.
- Threats: The conditions or actions that lead towards loss of control.
- Top event: The precise point where control is lost.
- Consequences: What happens after that event.
- Barriers or controls: The measures that prevent the event or reduce the damage after it.
In technical use, bow tie analysis works best when the top event is defined as the exact point of loss of control over a hazard, because the diagram separates prevention barriers on the left from mitigation barriers on the right, as outlined in the NHS bow tie safety model toolkit.
What that means in business terms
For RevOps, you can borrow that same discipline.
On the left, you map the things that increase the chance of a good-fit customer reaching a deal. Those are your acquisition motions, qualification rules, sales stages, and conversion controls. On the right, you map the things that protect revenue after the sale. Those are onboarding, adoption, support response, renewal planning, and expansion plays.
Practical rule: If your centre point is vague, the rest of the model gets messy fast.
A lot of teams make the knot too broad. They call it “customer lifecycle” or “conversion” and move on. That weakens the model. In RevOps, the middle has to be a specific event with clear system meaning. Usually that's a Closed Won opportunity or signed commercial commitment.
Prevention and mitigation in a CRM context
The left side is about reducing failure before the sale. In CRM terms, that includes:
- Lead qualification controls: Scoring, routing, enrichment, and duplicate management.
- Pipeline discipline: Exit criteria for each stage, mandatory fields, and validation rules.
- Sales readiness: Playbooks, opportunity hygiene, and handoff requirements.
The right side is about reducing revenue loss after the sale:
- Onboarding controls: Implementation milestones, owner assignment, and time-to-live tracking.
- Adoption controls: Usage flags, training completion, and product engagement signals.
- Commercial controls: Renewal dates, risk reviews, and expansion triggers.
The value of the bow tie model is that it makes both sides visible at once. That's why it works so well in RevOps. It forces one operating picture across marketing, sales, and customer teams.
Mapping the Bow Tie to the B2B Revenue Journey
Most B2B teams already have the pieces of the bow tie model. They just don't organise them as one connected system.
The left side usually lives in marketing automation and pipeline reports. The right side lives in account management, support workflows, renewal sheets, or customer success tools. The missing piece is a shared map of the full journey. A useful companion to that thinking is a structured B2B customer journey mapping approach, because it helps teams define actual stage transitions instead of copying generic funnel labels.
The left side of the bow tie
This is your acquisition and conversion engine. Typical stages look familiar:
- Awareness: Anonymous or known engagement from target accounts and prospects.
- Consideration: Leads are responding to campaigns, content, or outbound sequences.
- Qualification: MQL to SQL progression, with clearer fit and buying intent.
- Active evaluation: Discovery, demo, validation, and proposal work.
The key point isn't the naming. It's whether each stage has a real operational meaning. If “MQL” exists only because marketing automation needs a status, it won't help your model. If “SQL” means something different to SDRs and AEs, the left side becomes unreliable.
The knot in the middle
For B2B RevOps, the knot is usually Closed Won.
That's the commitment event. Money, contract, and ownership all change there. It's the cleanest point to mark the transition from pre-sale to post-sale. If you try to centre the model on “opportunity created” or “account engaged”, you'll blur the handoff between teams and weaken right-side reporting.
Closed Won should trigger more than celebration. It should trigger a controlled transfer of context, responsibility, and next actions.
The right side of the bow tie
This side is where many CRM models become shallow. It shouldn't.
A practical post-sale sequence often includes:
- Onboarding: Kick-off, implementation, provisioning, and training.
- Adoption: Users engage, teams change behaviour, workflows go live.
- Value realisation: The customer sees operational or commercial benefit.
- Renewal: Commercial continuation is assessed before the term ends.
- Expansion and advocacy: Cross-sell, upsell, referenceability, and referrals.
The bow tie model becomes commercially useful by letting you ask better questions than “how many leads did we get?” You can ask which segments onboard smoothly, which sources create customers that expand, and where poor-fit opportunities create post-sale drag.
A better way to define stage ownership
The strongest implementations tie each section of the model to a named operational owner:
| Revenue Journey Area | Primary Owner | Typical System Focus |
|---|---|---|
| Pre-sale acquisition | Marketing ops and SDR ops | lead routing, scoring, campaign attribution |
| Sales conversion | Sales ops and AEs | pipeline stages, forecast, close governance |
| Post-sale delivery | CS ops, service ops, account management | onboarding, health, renewal, expansion |
That ownership model matters. Without it, the bow tie becomes a diagram. With it, it becomes a management system.
Implementing the Bow Tie Model in Salesforce
Salesforce is well suited to the bow tie model because it already separates leads, contacts, accounts, opportunities, service activity, and custom objects. The challenge isn't platform capability. It's design discipline.
Too many orgs model only the left side cleanly. Lead statuses are detailed. Opportunity stages are maintained. Then everything after Closed Won gets pushed into notes, tasks, or disconnected processes. If you want a working bow tie, you need a deliberate post-sale data model.
Core design principles
Start with three decisions:
- Define the knot clearly: In most Salesforce environments, this is an Opportunity with Stage = Closed Won.
- Choose your post-sale source of truth: That may be Account fields, a custom object, Service Cloud records, renewal opportunities, or a mix.
- Separate lifecycle stage from operational task: “Customer lifecycle stage” should not be confused with “implementation task status”.
A good reporting foundation also depends on consistent field strategy. If you need help structuring dashboards after the model is built, this guide to Salesforce reports and dashboards is useful alongside the lifecycle work.
Salesforce Bow Tie Implementation Map
| Bow Tie Stage | Salesforce Object(s) | Key Field(s) | Example Values / Configuration |
|---|---|---|---|
| Awareness | Lead, Campaign Member | Lead Status, Lead Source, Campaign Status | New, Engaged, Source by channel, campaign response values |
| Consideration | Lead, Contact | Lead Score, Grade, Status, Persona fields | Marketing Qualified, Nurturing, ICP Fit, Product Interest |
| Qualification | Lead, Contact, Opportunity | MQL Date, SAL Date, SQL Date, Owner, Conversion fields | Accepted, Qualified, Converted, handoff timestamps |
| Active evaluation | Opportunity | Stage, Amount, Close Date, Primary Campaign Source, Next Step | Discovery, Demo, Proposal, Procurement |
| Closed Won knot | Opportunity, Account, Contact Roles | Stage, Closed Won Date, Primary Contact, Contract fields | Closed Won, term details, implementation owner |
| Onboarding | Account, Case, Custom Onboarding Object, Opportunity | Customer Lifecycle Stage, Onboarding Status, Go-Live Date | Kick-off, In Progress, Blocked, Live |
| Adoption | Account, Custom Usage Object, Case | Health Status, Product Adoption Flag, Training Complete | At Risk, Healthy, Power User, Training Done |
| Renewal | Opportunity, Contract, Account | Renewal Date, Renewal Owner, Renewal Stage | Upcoming, In Negotiation, Renewed |
| Expansion and advocacy | Opportunity, Account, Contact | Expansion Opportunity Type, Referenceable Status, Product Line | Upsell, Cross-sell, Reference Candidate |
What to configure first
A clean first version usually includes these components:
- Lifecycle fields on Account: Add fields such as Customer Lifecycle Stage, Customer Since, Renewal Date, Customer Segment, and Health Status.
- Stamped milestone dates: Capture MQL Date, SQL Date, Closed Won Date, Onboarding Start Date, Go-Live Date, and Renewal Decision Date.
- Opportunity discipline: Keep sales stages focused on pre-sale progression. Don't overload the main pipeline with onboarding steps.
- Post-sale process object: For complex implementations, a custom Onboarding object works better than cramming every milestone onto the Account.
Where MCAE fits
Marketing Cloud Account Engagement works well on the left side of the bow tie. Use it for scoring, grading, routing triggers, nurture logic, and campaign response capture.
It can also support the right side in lighter-touch motions. For example, customer nurture programmes can trigger training reminders, feature education, event invitations, and expansion signals. But don't force MCAE to become your customer success system. In Salesforce, post-sale operational truth usually belongs on the Account, Opportunity, Case, or a purpose-built custom object.
The trade-off is simple. If you keep the model too lightweight, reporting stays incomplete. If you overengineer every field before adoption exists, users stop maintaining it. The best Salesforce bow tie design is opinionated, staged, and built around handoffs people will follow.
Building the Bow Tie Funnel in HubSpot
HubSpot can support the bow tie model well, but the architecture is different. You don't have the same object depth as Salesforce in every deployment, so the design has to be simpler and more intentional.
That's not a drawback. In many mid-market teams, HubSpot's strength is speed. You can create a reliable full-revenue model quickly if you keep property definitions clean and resist the temptation to use one field for three different purposes.
Start with native lifecycle logic
For the left side, HubSpot already gives you a strong foundation through Lifecycle stage and associated contact and company properties. A practical setup often looks like this:
- Subscriber or Lead: Early engagement from forms, content, or outbound response.
- MQL: Marketing has enough fit and intent to pass the record forward.
- SQL: Sales has accepted and is working the opportunity.
- Opportunity: An active deal exists in the sales pipeline.
- Customer: The deal is won and the commercial relationship starts.
That lifecycle field should reflect revenue progression, not campaign status. Don't use it to track email nurture states, webinar attendance, or one-off operational flags.
Use the deal pipeline for the knot
The knot sits in the deal object. In HubSpot, that's usually straightforward. Your primary sales pipeline should carry the pre-sale stages up to Closed Won.
After that, you have two sensible options:
- Keep post-sale off the original deal and manage customer lifecycle on the company record.
- Create separate pipelines for onboarding, renewal, or expansion where your team needs stage-based operational control.
The right choice depends on operating model. If account managers and onboarding specialists need queue visibility and stage governance, separate pipelines usually work better. If the post-sale motion is light, company properties may be enough.
If every customer process becomes a deal stage, the sales pipeline stops being a sales pipeline.
Build the right side on companies and service workflows
In HubSpot, the company record is often the best anchor for the post-sale side of the bow tie. Add properties that make the customer lifecycle measurable, such as:
- Customer lifecycle stage
- Onboarding status
- Implementation owner
- Renewal month or renewal date
- Health status
- Primary product
- Expansion potential
- Referenceable status
Service Hub can carry more of the operational load when onboarding and support need structure. Tickets work well for implementation requests, issue management, and service milestones. If you want clearer accountability, create ticket pipelines for onboarding and support separately.
Automation that actually helps
HubSpot workflows are where the bow tie model becomes usable day to day.
A practical setup might include:
- Closed Won triggers: Set lifecycle stage to Customer, assign onboarding owner, create onboarding ticket, stamp customer start date.
- Adoption workflows: Trigger education emails or tasks when onboarding status changes to Live.
- Renewal preparation: Create tasks or records before the renewal period based on company properties.
- Expansion triggers: Notify account owners when product usage, support history, or firmographic changes suggest growth potential.
Marketing Hub can support customer marketing on the right side, but the same warning applies as in Salesforce. Don't confuse engagement automation with operational truth. The properties on the company, deal, and ticket records should remain the source of record for lifecycle reporting.
HubSpot implementations fail when teams treat lifecycle as cosmetic. They work when each property answers a real management question and each workflow supports a clear handoff.
Essential Dashboards and KPIs for Bow Tie Reporting
Once the bow tie model is built in the CRM, reporting gets more useful because it stops isolating functions. You're no longer asking only whether leads converted. You're asking whether acquisition quality holds up through onboarding, renewal, and expansion.
That's where a lot of attribution conversations become more mature. Instead of arguing over top-of-funnel credit alone, you can connect source, sales motion, and customer outcomes. This broader view complements a more complete approach to revenue attribution in B2B systems.
The dashboard categories that matter
A strong bow tie reporting layer usually has three dashboard groups.
Left-side dashboards focus on acquisition and conversion quality:
- Lead to MQL progression
- MQL to SQL conversion
- Opportunity creation by source, segment, or campaign
- Pipeline ageing and stage velocity
- Win rate by source, persona, or segment
Knot dashboards focus on the transition point:
- Closed Won by source and segment
- Average sales cycle by deal type
- Handoff completeness
- Time from Closed Won to onboarding start
- Deals won with missing implementation data or owner assignment
Right-side dashboards focus on customer revenue quality:
- Onboarding status by owner or segment
- Time to go-live
- Customer health distribution
- Renewal pipeline coverage
- Expansion pipeline by account cohort
- Referenceable customers and advocacy readiness
The most useful connected views
The primary benefit comes from cross-bow-tie reporting.
These are the reports I've seen create the best operational conversations:
| Connected Report | Why It Matters |
|---|---|
| Source to Closed Won to Renewal Outcome | shows which channels create durable customers, not just pipeline |
| Segment by Sales Motion by Health Status | surfaces poor-fit deals that looked good during selling |
| Campaign Family by Expansion Opportunity Creation | highlights acquisition programmes that lead to broader account growth |
| Onboarding Duration by Original Deal Type | shows where expectations sold pre-sale create delivery strain |
A healthy dashboard should expose tension between teams. That's often where the best process fixes are hiding.
Data enrichment on the right side
This is also where GTM engineering can add value. Tools such as Clay for account enrichment and signal building can help enrich company records with market, hiring, technology, or firmographic changes that support expansion planning or risk review.
The key is restraint. Don't flood the CRM with enrichment fields nobody uses. Add only the signals that support an action, such as routing an account review, prioritising a renewal conversation, or flagging an expansion candidate.
What doesn't work
A few reporting habits undermine the model fast:
- Vanity lifecycle reports: If every stage looks healthy because definitions are loose, the dashboard is lying.
- Separate post-sale reporting outside CRM: Renewal and expansion data held elsewhere break the bow tie.
- No date stamps: Without milestone dates, you can't analyse transition speed or handoff friction.
- Too many health metrics: One usable health model beats a cluttered scorecard no one trusts.
The best KPI set is compact, operational, and tied to action. If a metric doesn't change behaviour, it probably doesn't belong on the main dashboard.
Moving from a Funnel to a Full-Revenue Engine
The bow tie model works because it matches how B2B revenue behaves. Prospects become customers. Customers either realise value or drift. Revenue grows through retention and expansion, not just acquisition.
That sounds obvious, but most CRM setups still encode the older idea that marketing creates demand, sales closes it, and the rest happens somewhere else. That's why reporting fragments. That's why handoffs break. That's why teams optimise local metrics while leadership struggles to see the full picture.
What changes when you adopt the model
A bow tie design improves three things at once:
- Shared visibility: Marketing, sales, and customer teams work from one lifecycle model.
- Cleaner accountability: The transition from pre-sale to post-sale becomes explicit.
- Better decisions: You can connect acquisition activity to long-term customer quality.
It also forces a useful discipline. Teams have to decide what the critical event is, what fields prove stage progression, and which system owns each part of the journey. That's real RevOps work. Not just dashboard building. Operating model design.
The practical takeaway
If your CRM only describes how pipeline gets created, it's incomplete. If your dashboards stop at Closed Won, they're understating both risk and opportunity.
The bow tie model gives you a better structure for Salesforce, HubSpot, and the processes wrapped around them. It helps you build a lifecycle that sales can follow, customer teams can trust, and leadership can use to make clearer investment decisions.
You don't need a theoretical framework pinned to a workshop board. You need stage definitions, fields, automations, and dashboards that reflect the full revenue journey.
If you want help turning this into a working CRM design, MarTech Do can audit your current lifecycle model, identify the reporting and handoff gaps, and implement a bow tie structure in Salesforce or HubSpot that your team can run.
