Stages of a sales cycle, and what to send at each one

You can send a proposal that looks tidy on your screen and still hear nothing back. That silence usually isn't the buyer vanishing. It's the deal moving into a stage you never made easy for them to complete. I've sent enough decks, proposals and one-pagers to know the feeling: the document gets opened, then legal, procurement or an internal champion takes over, and you're no longer in the room.

The fix isn't chasing harder at random. It's treating the stages of a sales cycle as a chain of handoffs, then giving each stage the right document, the right explanation and one obvious next step.

A sales cycle is a chain of handoffs, not one conversation

Most deals feel messy because they aren't one conversation. They're several small decisions happening in different heads at different times. You think the buyer is evaluating your proposal. They might be comparing notes internally, waiting on finance, or working out whether the person who booked the demo is allowed to sign anything.

That gap is where good deals go to die, and it's rarely because the pitch was weak. It's because nobody owned the next step.

So I think about document jobs rather than documents. A prospecting one-pager has one job. A proposal has a different one. If you've ever sent a lovely proposal and then spent three days explaining the same three pages over email, you've seen what happens when the document doesn't do enough of the talking on its own.

If a buyer has to book another meeting just to understand the proposal, the proposal is doing part of your job, badly.

The seven stages of a sales cycle

Every framework carves this up slightly differently. Seven is what I use, because it's enough to see where things break without turning the pipeline into a spreadsheet nobody updates.

A diagram illustrating the seven stages of a sales cycle process from prospecting to post-sale support.

Prospecting and qualification

Prospecting is the search for fit: building a list of accounts that might have the right pain, the right shape and a reason to talk now. Qualification is the filter that decides whether the conversation keeps going, and most of it should happen before you send anything rather than on the call. I've written the whole motion up in the sales prospecting process, so I won't repeat it here. Where several reps share a market, territory planning decides who owns which accounts before any of this starts.

The success metric at this stage isn't applause. It's whether the right accounts stay in motion and the wrong ones fall away quickly.

Discovery and proposal

Discovery is where you stop guessing. You're trying to understand the buyer's workflow, their constraints, who else is involved, and the reason they'd change anything this quarter. A good discovery call doesn't feel impressive. It feels precise.

The proposal is where people overtalk. The strongest ones I've sent weren't the longest. They were the ones that made the buyer say "yes, this is what we discussed". Scope, pricing and the value case need to be plain enough that the buyer can forward the thing internally without rewriting it. This sample sales proposal is roughly the shape.

Negotiation, close and post-sale

Negotiation is where assumptions get tested. Redlines, security questions, commercial tweaks. They all belong here, and they need explaining in plain language rather than legal fog. Close is the point where commitment becomes formal, and your job shifts from persuasion to coordination: who signs, in what order, and who owns implementation.

Post-sale matters because the cycle doesn't end at signature. It proves whether the promise survived contact with reality. If the buyer's first week is confusing, the expansion conversation is harder before it starts.

A sales cycle works when each stage has one owner, one purpose and one visible exit condition.

Where deals actually leak

Not at the top, or at least not in the way people assume. Almost nobody's pipeline fails because they couldn't build a list. Benchmarks compiled from First Page Sage and Ruler Analytics data, summarised in this roundup of sales funnel statistics, put lead-to-MQL at around 31% and MQL-to-SQL at around 13%, which says the early leak is qualification quality rather than volume.

Past qualification, it leaks in the transitions. The deal that's "proposal sent" in the CRM but hasn't been reviewed by anyone who can decide. The negotiation that stalls because a security questionnaire landed with someone who's never heard of you. The close that slips because nobody confirmed who signs.

Exit criteria fix more of this than any pipeline review. A stage shouldn't be "proposal sent" if the buyer still hasn't confirmed their process, the decision owner and the objection that could kill it. It should be "proposal sent and reviewed by the decision group". That sounds strict because it is, and it's the difference between a forecast and a wish list.

When I was running growth at DataBees, my pipeline reviews were mostly me reading tone into two-word replies. The deals I'd have called late stage were often nothing of the sort. They'd gone quiet after the proposal, and I'd promoted them in my head because the call had gone well.

What to send and say at each stage

The easiest way to keep a cycle moving is to stop sending generic material. A prospecting note shouldn't read like a proposal, and a proposal shouldn't read like a blog post.

Early stages need brevity

At the top, send a short one-pager or a two-line intro. Its job isn't to explain everything. Its job is to earn a reply. For qualification, write down what the buyer said about fit, urgency, authority and blockers, then send a short recap so nobody has to remember the call from memory. If you share a document here, point it at one question: is this worth a deeper conversation?

Discovery and proposal need context

A discovery summary should read like a shared working brief. Name the pain, the current workflow, the people involved and the thing that would make them switch. That summary is the bridge into the proposal, because the buyer can see you understood the problem before you priced the fix.

LiveDocument

The proposal itself should carry the buyer's language back to them, and this is the one stage where I'd put your voice on the document rather than around it. A short recorded walkthrough of the scope and pricing pages answers the questions that usually trigger a second meeting. That's what LiveDocument is for: you attach a walkthrough to the PDF or image, share one link, and see which pages held attention. It's not a CRM and it won't run your sequence, so the stages above are still yours to manage.

Late stages need clarity

Negotiation notes should explain redlines like a human. If something changed, say what changed, why, and what stays the same. Buyers don't need theatre. They need certainty.

The close checklist is different again. It confirms decision owners, signature flow, implementation ownership and any open questions. Post-sale, the handover guide should remove confusion on day one. If the buyer has to hunt for the next step, you've lost momentum after the signature.

The more commercial the document, the more plain-language explanation it needs.

Buyers don't follow your stages

The tidy funnel breaks the moment a real buying committee gets involved. Buyers do most of their research before you ever hear from them: a Gartner figure of roughly 70% of the research done before first contact gets cited in The Starr Conspiracy's buyer journey Q&A, and it matches what I've seen. They'll jump backwards, sideways and occasionally into silence without telling you.

The other thing people miss is where the time goes. 42 Agency's analysis of CRM data from 87 of its own B2B SaaS clients puts the evaluation stage at 30 to 35% of the whole cycle, with the largest deals spending 30 to 60 days there on technical validation and security review. That's one agency's client base rather than the market, but it explains why a deal that stalls after a good demo isn't always a demo problem.

Consensus is the hidden stage. A lot of late-stage delay is really internal alignment: legal, procurement, finance and a stakeholder you didn't know existed until yesterday. The cycle lengthens because people need to agree, not because they forgot the pitch. Shorter cycles come from faster consensus, not louder pitching.

Reading a deal that has gone quiet

A prospect going quiet after a strong demo doesn't always mean no. It can mean they've moved to legal or procurement without telling you. If you're tracking the document, a reopen or a return to the same page may indicate a second read, or someone else looking over their shoulder. It doesn't tell you who or why, so treat it as a reason to ask a better question rather than a conclusion to act on.

Many objections show up late, disguised as process. Overcoming sales objections is a lot easier when you surface them early, in plain language, before they turn into a hidden stall.

Follow-up is what moves deals between stages

A proposal doesn't move itself. Neither does a redline. Someone has to create the next touchpoint, and the timing matters more than most reps want to admit.

Early in the cycle, speed matters because attention is fresh. After a proposal or during negotiation, the rhythm changes. You're no longer trying to create interest. You're trying to keep the buyer moving without making them feel chased. I've written up the full cadence for following up after a proposal, and the short version is three or four touches over two to three weeks, each with something new in it, then a clean way out.

The cleanest sequence I've found is boring in the best way. Send the document, watch for engagement, answer the likely question in the next note, then set the next contact date before the trail goes cold. Deal momentum usually dies where nobody owns the next nudge.

Frequently asked questions

Why do sales cycles get longer late in the deal?

Because consensus and procurement take time, not because the pitch was weak. Once the commercial decision gets real, more people need to agree, and each of them has a question nobody has answered yet. Write the exit criteria so "proposal sent" isn't a stage until the decision group has actually reviewed it.

What do I do when a prospect jumps back to legal or procurement?

Treat it as stage regression, not rejection. Find out who the new decision owner is, answer the process question in plain language, and make sure the document reflects what that person cares about, which is usually risk rather than value.

How many stages should a sales cycle have?

Enough to see where deals leak and no more. Seven works for most B2B teams. If you have twelve, nobody is updating them honestly, and if you have three, "proposal sent" is hiding half your pipeline problems.

What's the fastest way to improve stage visibility?

Give every stage an exit condition, then track whether the document at that stage was actually read rather than just sent. Page-level activity tells you more than a vague "interested" note in the CRM ever will.

I built LiveDocument because the stage I lost most deals in was the one right after I hit send. If that's a feeling you know, it's at livedocument.com.