pipeline

Cash Machine 10-step B2B sales pipeline with 3 presets, verifiable checkpoints per step, trajectory logging, bottleneck detection with utilization formula, lead qualification gate (BANT 6-criteria), pipeline velocity and stall detection (2x threshold), two-tier probability scoring, BBS tracking, end-of-quarter syndrome detection. Use when managing sales pipeline, detecting bottlenecks, or forecasting revenue.

Sales Pipeline (Cash Machine)

When to Apply

  • Managing deal flow through the sales pipeline
  • Detecting and resolving pipeline bottlenecks
  • Revenue forecasting
  • When deals stall or pipeline health degrades
  • Onboarding pipeline configuration

Core Framework

10-Step B2B Pipeline (Default)

StepNameCompletion Criteria
1Prospect IdentifiedProspect entered into system
2QualifiedConfirmed: problem, budget, authority, timeline, fit, margin
3Needs AssessedGathered information to understand specific needs
4Needs ConfirmedProspect agrees with our understanding
5Overview PresentedProduct overview delivered (no detailed pricing)
6Proposal SubmittedSolution proposal + technical feasibility demonstrated
7Demo/TrialCustomized demo or trial for specific conditions
8Quote SubmittedFormal pricing presented upon request
9NegotiationActive negotiation on price/terms/timeline
10Closed WonPurchase order or contract signed

3 Pipeline Presets

  • B2B SaaS (default): Full 10-step pipeline above
  • B2C / PLG: Simplified funnel: Visitor -> Signup -> Activation -> Conversion -> Retention
  • Enterprise / Complex Sales: Extended with relationship mapping, multi-stakeholder tracking

Verifiable Checkpoints

Each step has an objective verification criterion — no advancement on belief alone:

StepVerificationMethod
1Prospect exists in systemCRM record created (automated)
2All BANT fields populatedData completeness check (automated)
3Needs document existsFile/note attached (automated)
4Prospect confirmation receivedEmail/message logged (semi-automated)
5Presentation deliveredCalendar event + follow-up sent (automated)
6Proposal document sentEmail delivery confirmed (automated)
7Demo/trial completedCalendar event or trial account activated (automated)
8Quote deliveredEmail delivery + open tracking (automated)
9Negotiation activeReply/counter-proposal within 14 days (automated)
10Contract signedSigned document in system (automated)

Trajectory logging: Full decision trajectory logged per deal — not just outcome, but WHY each approach was chosen. Correct outcomes from terrible processes are flagged.

Bottleneck Detection

Formula: utilization = actual_throughput / theoretical_capacity x 100%

Step 2 (Qualification):    capacity 200/mo  actual 150  util: 75%
Step 7 (Demo/Trial):       capacity  30/mo  actual  27  util: 90% <- BOTTLENECK
Step 9 (Negotiation):      capacity  50/mo  actual  18  util: 36%

When any step exceeds 80% utilization: flag as emerging bottleneck.

At 90%+, apply TOC 5 Focusing Steps:

  1. IDENTIFY: Demo is the constraint
  2. EXPLOIT: Optimize scheduling, pre-qualify, batch similar demos, recorded demos for screening
  3. SUBORDINATE: Reduce upstream lead gen to match demo capacity
  4. ELEVATE: Increase capacity (hire, self-service trial)
  5. REPEAT: Re-analyze for next bottleneck

Lead Qualification Gate (BANT 6-Criteria)

Quality gate at marketing-sales handoff:

CriteriaCheck
ProblemProspect has a problem our product solves
BudgetBudget allocated or likely
AuthorityDecision-maker engaged or accessible
TimelineReasonable purchase timeframe
FitProduct capability matches need
MarginAchievable margin above threshold
  • Qualified -> Pipeline Step 2
  • Unqualified -> Nurture sequence (NOT pipeline)
  • When bottleneck is downstream: pumping more unqualified leads only lengthens queues

Pipeline Velocity & Stall Detection

Track average days per step. Stall threshold: 2x average at current step.

Stalled deals (>2x average):
  Acme Corp: stuck at Step 5 for 38 days (avg 8) <- STALLED
  BetaCo: stuck at Step 7 for 42 days (avg 19)   <- STALLED

Investigate stall cause, propose unblock Actions.

Two-Tier Probability Scoring

ComponentSourceExample
Stage probabilityHistorical conversion at that stepStep 7: 65%
Deal-specific probabilityAgent assessment of deal signals80% (high engagement)
Weighted forecastvalue x stage% x deal%$24K x 65% x 80% = $12.5K

BBS (Backlog-Bookings-Shipments) Tracking

Opening Pipeline:    $450K
+ New Qualified:     $120K
- Closed Won:        $85K
- Closed Lost:       $45K
- Disqualified:      $15K
= Closing Pipeline:  $425K

Pipeline-to-quota ratio: 3.2x (healthy > 3x)

End-of-Quarter Syndrome Detection

Monitor monthly closing pattern within quarters:

Month 1: $45K (23%)  Month 2: $52K (27%)  Month 3: $98K (50%)
-> 50% concentrated in final month = END-OF-QUARTER SYNDROME

Risks: discount escalation, operations overload, backlog rollover.

Proposals: monthly targets, level pipeline flow, eliminate quarter-end discount authority.

Decision Rules

  1. Verification before advancement — no step completion without objective evidence
  2. Bottleneck at 80%+ utilization — flag emerging constraints early
  3. Subordinate to constraint — don't generate more leads than downstream can handle
  4. Stall at 2x average — investigate immediately
  5. Pipeline-to-quota > 3x — healthy pipeline coverage
  6. Monthly, not quarterly — even flow prevents syndrome

Anti-Patterns to Detect

Anti-PatternSignalResponse
Advancement without verificationSteps marked complete on belief"Verification checkpoint required. What's the objective evidence?"
Upstream floodingLead gen outpacing demo capacity"Generating more leads than downstream can handle is waste."
Stalled deal ignoredDeal at 2x+ average dwell time"This deal is stalled. Investigate and propose unblock action."
Quarter-end concentration>40% of closes in final month"End-of-quarter syndrome. Set monthly targets instead."
Low pipeline coveragePipeline-to-quota < 2x"Pipeline drying up. Accelerate lead gen Driver."

Anticipative Execution Reminder

When applying this framework, produce the FULL output immediately. Do not ask the founder which parts to analyze or which options to consider. Infer from business context, present the complete deliverable, and let the founder react to concrete work — not abstract choices.