By Siddharth Gangal The 6-stage B2B sales workflow and how industry shapes it
Direct answer. The 6-stage B2B sales workflow — signal identification, prospecting, discovery, evaluation, negotiation, close and onboarding — applies across every industry. What changes is the duration of each stage, the number of stakeholders in the buying committee, the compliance requirements that extend legal review, and the signals that most reliably indicate active buying intent. This article shows how the workflow adapts for SaaS, fintech, healthcare, professional services, and cybersecurity — with worked examples and stage-level specifics for each.
The 6-stage workflow framework below is the lens through which each industry example is structured. Stage 1 is signal identification — finding accounts showing buying intent. Stage 2 is prospecting — making contact with the right people. Stage 3 is discovery — understanding the problem, the budget, the timeline, and the decision process. Stage 4 is evaluation — demo, proof of concept, or proposal review. Stage 5 is negotiation and legal — commercial terms and contract review. Stage 6 is close and onboarding — signature and the first 90 days of the customer relationship.
For a broader treatment of the sales workflow in SaaS specifically, see the SaaS sales guide. For the account executive role in this workflow, see the account executive playbook.
SaaS sales workflow example
SaaS sales is the reference point for B2B sales workflow design in 2026 — it is where most of the research, tooling, and benchmarks originate. The workflow below reflects a Mid-Market SaaS deal selling to another SaaS company, the most common ICP for early-stage B2B SaaS vendors.
Stage 1 — Signal identification (Days 0–2): The trigger events that most reliably indicate SaaS buying intent are: new VP of Sales or VP of Revenue hire (vendor review typically follows within 60 days), Series A or Series B funding announcement, rapid engineering headcount growth (signals scaling pain), and intent data showing research on solution category pages. The rep monitors these signals daily via LinkedIn Sales Navigator, Crunchbase, and intent data platforms.
Stage 2 — Prospecting (Days 1–7): Signal-triggered outreach to the VP-level champion. First touch references the specific signal. Sequence runs 8 to 10 touches over 14 days across email, LinkedIn, and phone. Reply rate benchmark for signal-triggered SaaS outreach: 4 to 7 percent (Gangly internal data, 2026).
Stage 3 — Discovery (Days 7–21): 45 to 60-minute discovery call. Questions focus on the current workflow, the specific friction point, the business cost of the friction, and the decision process. The ideal outcome: a defined problem, a quantified cost, a stated timeline, and at least two stakeholders identified. For the discovery question framework, see the sales discovery guide.
Stage 4 — Evaluation (Days 14–35): Product demo tailored to the use case identified in discovery. For Mid-Market, a 7 to 14-day trial or POC period is common. Success criteria for the POC should be defined in writing before the trial starts — this is the most common step that SaaS AEs skip and the one that most often causes evaluation to extend.
Stage 5 — Negotiation and legal (Days 30–60): Commercial and legal review run in parallel. SaaS contracts are typically simpler than enterprise contracts; legal review takes 5 to 10 business days for standard MSA terms. Negotiation focuses on price, contract length, and payment terms. See the sales negotiation tactics guide for the specific scripts.
Stage 6 — Close and onboarding (Day 60+): Signature, data migration or integration setup, and the first 30-day success metrics review. The rep introduces the CSM and transitions deal context to avoid the "I already told your sales team this" frustration that causes early churn.
Fintech sales workflow example
Fintech sales is characterized by two features that extend the standard SaaS workflow: elevated security and compliance requirements, and buying committees that include the CFO and sometimes the board. Deal cycles run 20 to 40 percent longer than equivalent SaaS deals outside fintech.
Stage 1 — Signal identification: The highest-converting fintech signals are: new CFO hire, Series A to Series C funding close (triggers infrastructure and tooling evaluation), regulatory examination or audit announcement, and rapid growth in the finance or compliance team headcount. A new CFO combined with a Series B close in the same 60-day window is the highest-value signal combination in Gangly's fintech customer data.
Stage 3 — Discovery additions: Fintech discovery must include two questions not standard in generic SaaS discovery: "What compliance frameworks do you operate under?" (SOC 2, PCI DSS, ISO 27001 are common) and "What is your data residency requirement?" The answers determine whether your product can be considered at all — asking late wastes both sides' time.
Stage 4 — Evaluation additions: Fintech evaluations often include a security questionnaire (100 to 300 questions) and a data handling review. Assign a solutions engineer to own this process. Deals where security review is handled by the AE alone take 34 percent longer to close.
Stage 5 — Legal additions: Expect a Data Processing Agreement, a BAA if financial data is involved, and often a vendor risk assessment. Legal review typically runs 3 to 6 weeks for a new vendor relationship. Parallel-track legal with commercial to avoid sequential delay.
Note. Fintech deals frequently stall in the security questionnaire stage. The fix: maintain a pre-filled security questionnaire document that can be sent within 24 hours of the request. Companies that provide a complete questionnaire response in under 48 hours reduce security-stage deal duration by an average of 12 days (Gangly internal data, 2026).
Healthcare and medtech sales workflow example
Healthcare and medtech sales has the longest average deal cycle, the largest buying committees, and the most stringent compliance requirements of any B2B vertical. The workflow below applies to software sold to hospital systems, health plans, and larger medical group practices. Small practice sales follow a pattern closer to SMB SaaS.
Stage 1 — Signal identification: The most reliable healthcare signals are: new CIO, CMIO, or COO hire (infrastructure and vendor reviews follow), Epic or Cerner implementation milestone (integration partners are evaluated concurrently), hospital system merger or acquisition (systems consolidation creates vendor evaluation), and regulatory change (ICD coding updates, CMS rule changes).
Stage 3 — Discovery complexity: Healthcare discovery typically spans 3 to 5 calls across clinical, IT, and administrative stakeholders. The champion is often the department head or clinical director; the economic buyer is often the CFO or CEO. Bridging those two perspectives — clinical outcome language and financial ROI language — is the core skill in healthcare sales.
Stage 5 — Legal additions: HIPAA Business Associate Agreement is mandatory for any product touching PHI. BAA review adds 2 to 4 weeks. For hospital systems with in-house legal teams, contract redlines are extensive. Providing a clean, pre-negotiated HIPAA-compliant contract template reduces legal cycle time by 3 to 5 weeks in first-time vendor relationships.
Average cycle: 9 to 14 months for enterprise health systems. 3 to 5 months for large physician group practices.
Professional services sales workflow example
Professional services sales — consulting, legal, accounting, advisory, staffing — is relationship-intensive and outcome-oriented. The buyer cannot evaluate the product before purchase the way they can in SaaS. Trust and evidence of past outcomes carry more weight than feature comparisons.
Stage 1 — Signal identification: Relationship-triggered signals dominate: an executive contact who moved to a new company, a referral from a current client, a LinkedIn post from a prospect describing a problem the firm solves, or a speaking engagement by a prospect leader at a conference. Cold outbound is less effective in professional services than in product sales; warm introductions convert at 4 to 6x the rate.
Stage 3 — Discovery depth: Professional services discovery is broader and qualitative. The rep is trying to understand the organizational context, the political dynamics, the history of attempts to solve the problem, and the measure of success. A discovery call that feels like a consultation — where the prospect gains insight from the conversation — advances the relationship more than a qualification checklist.
Stage 4 — Proposal co-creation: The most effective professional services proposals are written jointly with the champion. The AE drafts the scope and approach; the champion reviews and adds the language that will resonate with their organization's leadership. A co-created proposal has a 2.1x higher acceptance rate than a vendor-drafted document delivered cold (RAIN Group, 2025).
Cybersecurity sales workflow example
Cybersecurity sales is technically demanding, committee-intensive, and evaluation-heavy. The buyer's security team — who typically runs the evaluation — has a different risk calculus than a typical software buyer: they are evaluating the vendor as a potential attack surface, not just as a solution. This changes the entire dynamic of the evaluation stage.
Stage 1 — Signal identification: Top cybersecurity signals: CISO hire or departure (transitions trigger security stack review), data breach or incident at a peer company (creates urgency for similar organizations), regulatory mandate (GDPR, CCPA, SOC 2 audit deadline), and rapid cloud infrastructure expansion (increases attack surface and creates tool evaluation).
Stage 4 — POC rigor: Cybersecurity POCs are more technical and longer than typical SaaS evaluations. A well-structured POC has: defined success criteria agreed in writing before start, an SE dedicated to the POC relationship, a 14 to 30-day timeline (not open-ended), and weekly progress check-ins with the evaluation team. POCs without agreed success criteria run 2.3x longer than POCs with them.
Stage 5 — Security review of the vendor itself: In cybersecurity deals, the buyer's security team may conduct a security review of the vendor's own infrastructure. Prepare for this: maintain a current SOC 2 Type II report, a completed standard security questionnaire, and a data flow diagram. These three documents answer 80 percent of the questions in a standard vendor security assessment.
Industry workflow comparison: cycle, committee, close
| Industry | Avg cycle (Mid-Market) | Committee size | Win rate | Top signal |
|---|---|---|---|---|
| SaaS (selling to SaaS) | 60–80 days | 3–5 | 22–28% | VP Sales hire |
| Fintech | 90–150 days | 4–7 | 15–20% | CFO hire + funding |
| Healthcare | 9–14 months | 6–10 | 10–15% | CIO hire / merger |
| Professional services | 30–90 days | 2–4 | 28–40% | Warm intro / referral |
| Cybersecurity | 90–180 days | 4–8 | 12–18% | CISO hire / breach at peer |
Workflow design mistakes by industry
- Using a generic SaaS workflow for a regulated vertical. The most common workflow failure in healthcare and fintech is running the standard SaaS playbook without adding compliance discovery in Stage 3. Discovering a HIPAA BAA requirement or a PCI data residency constraint in Stage 5 restarts the deal. Fix: add two compliance questions to every discovery call with a regulated vertical prospect.
- Under-resourcing the technical evaluation stage. In cybersecurity and healthcare enterprise deals, the AE cannot manage the technical evaluation alone. Without a dedicated SE, POCs run over schedule and evaluation teams disengage. Fix: require SE assignment before any formal POC begins for deals over $50,000 ACV.
- Starting the proposal before all stakeholders are identified. In professional services and enterprise healthcare, delivering a proposal to the champion before the economic buyer is engaged results in the champion presenting a vendor-drafted document to a decision-maker who has no relationship with the vendor. Fix: before sending any proposal, confirm who the economic buyer is and request an introduction.
- Not adjusting pipeline coverage targets by vertical. Enterprise healthcare and cybersecurity deals have lower win rates than standard SaaS — 10 to 15 percent versus 22 percent. A pipeline coverage ratio of 3.5x that works for SaaS produces a 20 percent quota miss in these verticals. Fix: set vertical-specific coverage targets (5x to 6x for regulated enterprise deals).
How Gangly fits: one workflow system across all verticals
Verdict. Gangly runs the same signal-to-close workflow across all five industries described in this article. The signal detection engine is configurable by vertical — healthcare signals, fintech signals, and SaaS signals have different taxonomies but the same routing and response workflow. One system, five verticals, zero per-vertical configuration overhead.
The industry differences in sales workflow are real, but they do not require different tooling for each vertical. They require configurable tooling that adapts the signal definitions and stage timelines without rebuilding the underlying workflow infrastructure. Gangly is built for exactly this — the signal detection engine accepts custom signal definitions for each ICP, the call prep brief adapts to the deal stage and vertical context, and the CRM sync layer works with Salesforce and HubSpot regardless of how the pipeline stages are named.
Gangly customers selling into healthcare configure HIPAA compliance signals. Customers selling into fintech configure CFO hire and funding signals. Customers selling SaaS to SaaS configure VP Sales hire and product-led growth expansion signals. The workflow is the same; the signal grammar differs. See the full configuration options at the Gangly demo or explore pricing for your team size.
For the signal taxonomy that powers these workflows, read the B2B prospecting guide and the AI in sales overview.