Sales Process Flowchart Templates You Can Copy Today

I've rebuilt the sales process flowchart for more clients than any other single artifact in a RevOps engagement, and it's almost never because the previous one was drawn badly. It's because it was copied from a template and never adjusted to match how the team actually sells. A sales process flowchart template is a good starting point — it is not a finished process. Here are three templates you can copy today, plus what you need to change before they're actually useful.

Template 1: Outbound B2B sales process

This is the standard shape for teams doing cold outbound, SDR-led prospecting into an AE-run close motion.

Stages: Prospect identified → Outreach sent → Meeting booked → Discovery call → Qualified (or disqualified) → Demo → Proposal → Negotiation → Closed-Won / Closed-Lost.

Key decision points:

• After discovery: does the prospect meet your ideal customer profile and have budget authority in the room? If not, route to nurture, don't kill the deal outright.
• After demo: is there a clear internal champion pushing this forward? Deals without one stall disproportionately, in my experience across dozens of pipelines — worth tracking as its own qualifier.
• Before proposal: has pricing been pre-validated informally? Sending a formal proposal before this check wastes cycles on price objections that could have been surfaced earlier.

Comparison table: three sales process shapes

Template 2: Inbound-to-sales-assist process

For teams where marketing generates leads and a lighter-touch sales motion closes them.

Stages: Lead captured → Scored → Sales-qualified (threshold met) → Discovery call → Trial or pilot → Proposal → Closed-Won / Closed-Lost.

The critical decision gate here is the lead score threshold. Get this wrong — too low, and reps waste time on unqualified leads; too high, and good-fit leads never reach a human. HubSpot's own research on lead scoring is worth reading for calibration benchmarks, though your own conversion data over 90 days of actual deals should carry more weight than any generic threshold.

Template 3: Enterprise / committee-based sales process

For deals involving procurement, legal, and multiple internal stakeholders on the buyer's side.

Stages: Initial contact → Discovery → Technical evaluation → Business case review → Procurement/legal review → Contract negotiation → Closed-Won / Closed-Lost.

This process is longer and needs a branch for the evaluation committee stage, since multiple stakeholders can be reviewing in parallel rather than sequentially. A swimlane layout by stakeholder role (economic buyer, technical evaluator, legal) usually communicates this better than a single linear line.

What to customize before you use any of these

1. Exit criteria, not just stage names. Write one sentence per stage defining exactly what has to be true for a deal to move forward. "Discovery call happened" is not exit criteria. "Prospect has confirmed budget range and named a decision date" is.
2. Ownership at every handoff. Name the role responsible for moving the deal, especially at the marketing-to-sales boundary if those are separate functions.
3. Disqualification paths. Every template above needs a "this deal doesn't fit, route it out" branch at more than one point — most template libraries only show the happy path to closed-won.
4. Alignment with your actual CRM stages. If your flowchart has eight stages and your CRM pipeline has five, one of them is wrong. Reconcile them or reps will follow whichever one is easier, usually the CRM, and the flowchart becomes decoration.

Keeping the flowchart connected to real pipeline data

A flowchart is a static picture of a process that's constantly moving. The most durable setups I've built keep the flowchart as the reference document and the CRM pipeline as the live instance of it, reviewed together in weekly pipeline meetings — not as two disconnected artifacts maintained by different people. If your workspace lets you keep the process board and the pipeline view in the same place, that review takes ten minutes instead of thirty spent reconciling two out-of-sync documents.

Harvard Business Review's coverage of sales process design makes a similar point about B2B sales motions broadly: the process only creates value when the team actually follows it, and that only happens when it's visible in the tools they already use daily, not filed away in a separate diagramming app nobody opens after the kickoff meeting.

Copy one of these three templates as your starting skeleton, but budget a real 60- to 90-minute session with your sales team to rewrite the exit criteria and ownership before you call it done.