# Enterprise SaaS Deal Teardown

> Every touch in a nine month committee purchase, who joined when, which assets moved it forward, and the four weeks that were pure procurement delay.

Source: https://saas-marketing.net/examples/enterprise-saas-deal-teardown/
Topic: B2B SaaS Marketing
Type: example
Published: 2026-09-11
Last updated: 2026-09-11
Publisher: SaaS Marketing (saas-marketing.net)
License: CC BY 4.0. Quote or republish with attribution and a link to https://saas-marketing.net/examples/enterprise-saas-deal-teardown/

## Short answer

A typical 180,000 dollar enterprise SaaS deal takes around nine months and 30 to 40 touches across seven stakeholders. It usually starts with a peer recommendation or an answer engine query rather than a demo request, runs through six weeks of security review and four weeks of procurement, and the assets that move it are a champion business case, a security page and an integration doc. Last touch attribution credits none of them.

## Key takeaways

- The deal opened with a peer recommendation and an AI search query, 71 days before any form was filled in.
- Seven stakeholders touched the deal, but only three ever appeared in the CRM as contacts.
- Security review consumed six weeks and procurement another four, so 23 percent of the cycle was pure process.
- The three assets that moved the deal forward were forwarded internally and generated zero tracked sessions.
- Under last touch attribution, a branded search would have taken full credit for a nine month committee purchase.
- This is a composite drawn from several anonymised deals, not a single named account.

---

This is a composite deal, assembled from several anonymised enterprise purchases in the 120,000 to 250,000 dollar band. Nothing here is a single named account, and nothing is presented as original research. What it gives you is the shape: nine months, 34 logged touches, seven stakeholders, and a set of assets that closed the deal while producing no measurable traffic at all.

The buyer is a 2,400 person logistics company. The product is a workflow platform replacing a mix of spreadsheets and an ageing incumbent. Contract value 180,000 dollars a year, three year term.

## When did this deal actually start?

Day zero was not the demo request. It was 71 days earlier, when the eventual champion, a director of operations, complained about the incumbent to a peer at a conference dinner and got a name back.

She did nothing for three weeks. Then she typed a question into an AI assistant, got four vendors named in the answer, and started reading. Two of those four had published comparison content. The vendor that eventually won was one of them.

**71 days** Between first exposure and the first tracked interaction

The CRM records this deal as starting on day 71. Everything before that is invisible, which is what people mean by [The Dark Funnel](/glossary/dark-funnel/). Research on [how B2B SaaS buyers find vendors](/research/how-b2b-saas-buyers-find-vendors/) keeps landing on the same finding: peers and AI answers now sit upstream of every measurable channel.

## The full timeline, stage by stage

Thirty four touches, seven people. Here's the compressed version.

| Week | Stage | Who joined | Notable touch |
| --- | --- | --- | --- |
| 0 | Problem aware | Champion | Peer recommendation at a conference |
| 3 | Research | Champion | AI assistant query, four vendors named |
| 5 to 9 | Research | Champion | Read two comparison pages, one pricing page, one G2 category |
| 10 | Shortlist | Champion, end user 1 | Demo request form, six fields |
| 10 | Contact | Champion | Instant scheduling, call booked for the next day |
| 11 to 14 | Evaluation | End users 1 and 2 | Two demos, then a sandbox |
| 15 | Business case | Economic buyer | Champion adapts a vendor business case template |
| 16 to 19 | Pilot | End users, platform engineer | 12 seat pilot, integration doc reviewed |
| 20 to 25 | Security | Security reviewer | Questionnaire, trust page, penetration test summary |
| 26 to 29 | Procurement | Procurement lead, legal | Redlines, DPA, insurance certificate |
| 30 to 36 | Negotiation | Economic buyer | Two pricing revisions, signature week 36 |

Nine months, near enough. The pattern matches what the [B2B SaaS Buying Committee Benchmarks](/research/b2b-saas-buying-committee-benchmarks/) show for this ACV band, where committee size and cycle length move together.

Weeks 20 to 29 contain no selling. Ten weeks, 23 percent of the cycle, spent in review and paperwork. Sales forecasts routinely assume four weeks for this and slip the quarter.

## Which assets were forwarded, and which were ignored

Three assets moved internally. The champion emailed a one page business case she had adapted from a vendor template. The security reviewer opened the public trust page and the subprocessor list without ever contacting sales. The platform engineer read the integration documentation twice and flagged one gap.

None of those three produced a tracked session attributable to the deal. They were opened from forwarded email, copied into an internal wiki, or read while logged into a corporate VPN that strips referrers.

What was ignored: the 34 page industry report the vendor gated, two nurture emails, one webinar invitation and an ebook about digital transformation. The champion later said she skimmed the report's summary and never opened the rest.

If an asset cannot be forwarded as a single link and understood without you in the room, it will not travel through a committee. That rules out most gated PDFs and every deck that needs narration.

The business case is the single most useful item on that list, because the champion is presenting to a finance approver she cannot control. Our [Champion Business Case Template](/templates/champion-business-case/) exists for exactly this moment, and the underlying dynamics are unpacked in [How to Market to a B2B SaaS Buying Committee](/guides/b2b-saas-buying-committee/).

## The security review, broken out

Six weeks, of which the actual review was four working days. Three weeks were queue time in an understaffed security function. One week was a back and forth about data residency that a published FAQ would have answered.

**What compressed this review**

Procurement then took four weeks and produced nothing marketing could influence, except one thing: an insurance certificate and a standard DPA available on request the same day rather than in five. That saved roughly nine days.

## The marketing scorecard under three attribution models

Here's the part that should change how your team reports. The same deal, credited three ways.

The comparison page from week five and the trust page from week 20 are credited by none of the automated models. A last touch dashboard would recommend cutting both. That is the strongest available argument for adding a self reported field to your demo form and reporting all three numbers side by side.

We killed our comparison pages because the dashboard said they sourced nothing. Two quarters later win rates dropped and we rebuilt them.

## The two moments the deal nearly died

Week 17, during the pilot. One of the two end users could not get a report to match what the old system produced, raised it in a group thread, and the champion spent four days defending a decision she had not yet made. What saved it was a public documentation page explaining the calculation difference. Not a support ticket, a page she found herself and pasted into the thread.

Week 32, in negotiation. The economic buyer asked for a three year commitment discount and got a number that arrived eleven days later. Eleven days of silence in a competitive negotiation is how deals get re-opened. A competitor was re-contacted during that window and sent a fresh proposal.

Both near-death moments were information delays, not objections. Nobody disliked the product. The buying group simply could not get an answer fast enough to keep the internal momentum going, and momentum in a committee purchase is a wasting asset. Every week of silence invites someone to reconsider.

That is the argument for publishing more than feels comfortable. Calculation methodology, migration limitations, integration gaps, standard commercial terms. Every one of those pages is a page your champion can use when you are not in the room, which is roughly 95 percent of a nine month cycle.

## What to change on Monday

Three things, in order of how quickly they pay back.

**Fixes ranked by payback**

The honest tradeoff: everything above lengthens your content backlog and none of it will show up in a sessions report. You are trading measurable vanity for unmeasurable velocity, and you will have to defend that trade to a CFO who wants a number.

Start with the trust page. It's the cheapest item, it removes the longest delay, and unlike content it never goes stale in a way that hurts you. Then look at what your own site does to a committee buyer in the first five seconds, which is what our [B2B SaaS Homepage Teardowns](/examples/b2b-saas-homepage-teardowns/) measure. The full structure sits in the [Enterprise SaaS Marketing Playbook](/playbooks/enterprise-saas-marketing/), and the term itself is defined in our [Buying Committee](/glossary/buying-committee/) entry. If you want the wider context, the [B2B SaaS Marketing](/b2b-saas-marketing/) hub ties the pieces together.

## Frequently asked questions

### How long does an enterprise SaaS deal actually take?

For an ACV around 180,000 dollars with a committee of six or more, nine months from first touch to signature is normal. Sales usually logs it as five months because the clock starts at the demo request. The missing four months are the research period, where buyers read, ask peers and shortlist without contacting anyone.

### Who is in a B2B SaaS buying committee?

In this deal: a champion who owned the problem, an economic buyer who owned the budget, a security reviewer, a procurement lead, two end users who ran the pilot and a platform engineer who checked the integration. Gartner puts the typical enterprise software committee at six to ten people, which matches what practitioners see.

### Which marketing assets actually close enterprise deals?

The ones that get forwarded inside the buyer's company. In this teardown that meant a one page business case the champion adapted, a public security and subprocessor page the reviewer read without talking to anyone, and an integration doc the platform engineer checked. None generated a form fill, so none appeared in the lead report.

### Why did the security review take six weeks?

Three weeks were the reviewer's queue, not the review. The actual review took four working days once it started. The vendor's public trust page removed a further two weeks of questionnaire exchange, which is the strongest argument for publishing security documentation rather than gating it behind a sales conversation.

### Should we use first touch or last touch attribution for deals like this?

Neither on its own. Last touch credits the branded search at month eight. First touch credits a podcast nobody can measure. Run both, add a self reported how did you hear about us field on the demo form, and report the three together. The gap between them is the information, not the noise.

### Is this a real deal?

It is a composite, clearly labelled as one. The timeline, stakeholder count, review durations and asset list are drawn from several anonymised enterprise purchases in the 120,000 to 250,000 dollar range. No single customer is identifiable and no figure is presented as original research from this site.