Methods and Models for Founder-Led Sales and Pipeline Creation

Methods turn founder hustle into a teachable motion

Lesson 1 argued why Maya Chen and Jordan Park should still sell at RelayOps's $920K ARR (annual recurring revenue), 21 customers, and ~$44K ACV (average contract value). This lesson supplies methods and models: discovery call structure, pipeline stages, qualification frameworks adapted from enterprise sales, and outbound rhythm that fits a Series B U.S. SaaS (software-as-a-service) beachhead.

Methods are not bureaucracy. They are memory aids for tired founders who otherwise ask random questions and forget to request intros. Models are not scorecards for their own sake. They prevent unqualified demos from consuming 11-hour opp cycles.

Every method here connects to Unit 2 positioning: competitive alternative is PagerDuty-plus-Slack chaos; discovery must surface post-page pain metrics.

Discovery calls: the core founder-led method

A discovery call (first structured sales conversation to qualify pain, process, and fit) is not a demo. RelayOps founders target 25-35 minutes discovery before screenshare unless prospect demands earlier.

Discovery goals (in order):

1. Confirm beachhead ICP (ideal customer profile, best-fit account traits) fit or disqualify fast.
2. Name competitive alternative in customer words.
3. Quantify struggling moment metrics (Slack volume, MTTA, false pages).
4. Map buying committee (champion, economic buyer, blockers).
5. Secure next step with date (pilot scoping or technical workshop).

RelayOps discovery flow (minute-by-minute):

Question bank (sample):

• "How do incidents run after PagerDuty pages someone?"
• "How many Slack messages before ownership is clear?"
• "What is your MTTA (mean time to acknowledge, average minutes until someone owns the incident) on Sev-1 last quarter?"
• "If we cut false pages 35% in 30 days, who signs production use?"
• "What blocked similar tools before?"

Founders capture answers in CRM fields: alternative_named, slack_msgs_sev1, mtta_baseline, economic_buyer_role, blocker_notes.

Discovery disqualifiers (RelayOps):

• No Slack, no PagerDuty, no on-call rotation
• Wants rip-and-replace in 30 days with 6-month procurement
• Only buyer is junior engineer without exec path

Polite decline preserves hours. Unit 1 decline template applies.

Pipeline stages: definitions and exit criteria

RelayOps uses seven stages with exit criteria (requirements to advance). Stages without exit criteria become fiction.

Stage weighting for forecast:

RelayOps founder forecast uses conservative probabilities:

Expected ARR in pipeline = Σ (opp ACV × stage probability).

Example: 10 opps at Qualified ($44K, 15%) = 10 × 44,000 × 0.15 = $66,000 expected ARR.

Check: 10×44000×0.15 = 66,000 ✓

MEDDIC and BANT adapted for startups

Enterprise frameworks MEDDIC (Metrics, Economic buyer, Decision criteria, Decision process, Identify pain, Champion) and BANT (Budget, Authority, Need, Timeline) are often too heavy for early startups. RelayOps adapts them into MED-lite and BANT-lite for founder speed.

MED-lite (minimum for pilot approval):

Skip full MEDDIC paper process until ACV >$100K or procurement formal.

BANT-lite (disqualify early):

Adaptation principle: qualify to pilot, not to enterprise committee completeness. Pilot success creates budget.

Outbound and pipeline creation models

Founder outbound model (weekly):

• 12 tier-A accounts touched (email + LinkedIn)
• 4 warm intro requests from customers
• 2 follow-ups on stalled Qualified opps

Conversion assumptions (RelayOps rolling average):

Compound discovery → won: 0.45 × 0.60 × 0.65 = 0.1755 ≈ 17.6% (below 23% because many opps enter later stages from intros; use stage forecast for opps already qualified).

Intro model: Each happy customer → 2 intros/quarter. At 14 customers × 2 = 28 intros; 40% accept discovery → 11 discoveries. Protects pipeline when outbound fatigues.

Demo and pilot methods

Demo rule: No feature tour before struggling moment recap. Slide 1 is customer's last incident story, slide 2 is metric baseline, slide 3 is pilot plan.

Pilot method (14 days): Baseline days 0-2; game day optional day 5; exec readout day 14. Success thresholds tied to Unit 2 message map.

Handoff fields to customer success: integrations, rotation map, executive viewer seats, success metrics agreed in discovery.

CRM hygiene as a sales method

Methods fail when notes live in founder heads. RelayOps treats CRM (customer relationship management) fields as part of the sales method, not admin punishment.

Required fields by stage:

RevOps runs weekly field completeness report. Opps with <100% required fields cannot appear in forecast slide.

Objection handling model (RelayOps)

Objections cluster. Methods include scripted acknowledge, isolate, proof, next step flow.

"We already have PagerDuty."

• Acknowledge: "Most beachhead customers do."
• Isolate: "Is the pain after the page, or paging itself?"
• Proof: Northwind case with coexistence architecture diagram.
• Next step: 20-minute incident timeline workshop.

"No budget."

• Acknowledge: "Budget is tight everywhere."
• Isolate: "Is there budget for engineering hours lost in Slack during Sev-1?"
• Proof: Pilot ROI (return on investment, economic gain vs cost) worksheet comparing subscription to 3 engineer-hours per incident.
• Next step: Pilot scoped to one rotation.

"Slack is fine."

• Acknowledge: "Slack is great for chat."
• Isolate: "How do you know who owns the incident at message 150?"
• Proof: Landmine qualifies low-volume prospects; offer executive timeline module story.
• Next step: Disqualify politely or escalate to VP if executive visibility pain exists.

Scripts are starting points. Founders must sound human. CRM tags which script path was used for learning loops.

Multi-channel discovery: inbound, outbound, intro

Same MED-lite applies; method changes by channel.

Outbound: Hypothesis-led. Open with pain guess and proof offer. Disqualify fast.

Inbound: Skeptical qualification. Ask "what made you reach out now?" before demo. Many inbounds want cheaper PagerDuty; landmine early.

Intro: Reference-led. Ask introducer what pain was mentioned. Skip generic company overview; confirm struggling moment in first five minutes.

RelayOps Q3 data: intro win rate 36% vs inbound 13%. Method implication: spend founder hours on intro prep calls with customers, not on unqualified inbound demos.

Negotiation and pricing guardrails for founders

At $44K ACV, RelayOps avoids enterprise negotiation theater. Methods:

• List price on website for standard package (transparency reduces haggling).
• Maximum discount 15% without CEO approval.
• Multi-year prepay discount capped at 10% additional.
• Pilots free for 14 days; paid pilot only if security requires size.

Founders document walk-away conditions: rip-and-replace scope, unlimited custom integrations, on-prem deployment. Walking away is a method that protects positioning and product focus.

Pipeline stage regression rules

Opps move backward, not only forward. RelayOps defines regression triggers:

• Economic buyer disengages after being active → Qualified back to Discovery.
• Pilot metrics miss by >25% without remediation plan → Pilot back to Qualified.
• Security review exceeds 30 days without executive sponsor → Commit back to Pilot.

Regression protects forecast honesty. Founders hate moving deals back; investors hate surprise slips more.

Post-call documentation template

Within 24 hours, founders complete a five-line note:

1. Alternative named in customer words.
2. Baseline metrics captured (Y/N).
3. Authority gap (who missing).
4. Next step with calendar date.
5. One product or positioning signal.

Template fits mobile CRM forms. Learning loops depend on field 5: "Third mention of Datadog dedupe pain this week" triggers product prioritization.

Role-play certification before live calls

RelayOps requires founders to pass quarterly discovery role-play with PMM scoring rubric: ICP disqualification (20 pts), alternative clarity (20 pts), metrics capture (30 pts), next step date (20 pts), message map compliance (10 pts). Score ≥80 before running outbound campaigns solo. Hires must pass same rubric before unsupervised discovery in Phase 2.

Part A: Prospect fact pattern

Part B: Discovery scoring (MED-lite)

Stage after call: Discovery → Qualified only if VP intro scheduled within 7 days. Otherwise remain Discovery at 5% forecast.

Action: Maya emails champion: "Pilot readout requires VP sign-off; book 20 minutes with VP before pilot day 1."

Part C: Pilot scope draft

Targets: Slack msgs ≤ 85; MTTA ≤ 10 min; false pages ≤ 4/engineer/week.

Check: targets align with Unit 2 proof story (35-45% improvements) ✓

Part D: Managerial read

Do not advance to Pilot without VP on commit call. BANT-lite authority gap is top churn reason for pilots that "succeed" technically but never convert.

RelayOps pipeline snapshot:

Total expected ARR: 26,400 + 52,800 + 88,000 + 61,600 = $228,800

Target new ARR: $440,000
Gap: $211,200

Required additional expected ARR via new Qualified opps or stage advancement.

If founders add 6 Qualified opps: 6 × 44,000 × 0.15 = $39,600. Still short unless Pilot count rises.

Check: sum expected = 228,800 ✓; gap = 440,000 - 228,800 = 211,200 ✓

Managerial read: Q4 plan needs either 10+ new Qualified opps in 60 days or higher Pilot conversion. Outbound model must run weekly.

RelayOps runs discovery on Northwind SaaS. Notes: 8 Sev-1/quarter, 190 Slack msgs/incident, MTTA 22 min, champion is Eng Manager, VP Eng available in 3 weeks, budget "depends on pilot," PagerDuty renewal in 10 months.

Tasks:

1. Apply BANT-lite: list pass/fail per letter with one sentence each.
2. Assign pipeline stage and forecast probability.
3. Write three discovery follow-up actions with owners.
4. Draft MED-lite pilot metrics targets (justify % improvement).

Solution

1. BANT-lite

• B Budget: Pass conditional. Pain costs engineering opex; pilot can reframe budget if metrics hit.
• A Authority: Fail for Pilot today. Eng Manager is not economic buyer; VP Eng not yet engaged.
• N Need: Pass. 8 Sev-1/quarter exceeds threshold; Slack volume extreme.
• T Timeline: Pass conditional. 3-week VP delay acceptable if pilot starts after VP alignment call.

2. Stage and forecast

Remain Discovery at 5% until VP Eng call completes. Do not open Pilot without VP. If VP confirms within 3 weeks, advance Qualified at 15%.

3. Follow-up actions

1. Maya: schedule 25-minute VP call within 10 business days (not 3 weeks idle).
2. Jordan: send coexistence architecture one-pager for security pre-read.
3. Champion: export last incident Slack analytics for baseline file.

4. Pilot metrics

• Slack msgs: 190 → ≤105 (45% reduction, matches case studies)
• MTTA: 22 → ≤13 min (~41% reduction)
• False pages: baseline week 1 → ≤60% of baseline by day 14

Check: 190×0.55=104.5≈105 ✓; aligns with Unit 2 proof bands ✓

Key takeaways

• Discovery calls qualify pain and metrics before demos; use RelayOps question bank tied to alternatives.
• Pipeline stages require exit criteria and stage-weighted forecast math.
• MED-lite and BANT-lite adapt enterprise frameworks to startup pilot-led selling.
• Outbound plus intro models feed pipeline; weekly rhythm beats quarterly bursts.
• Pilots must mirror message map metrics with baselines captured day 0.

1. Write a discovery script with eight questions for your venture or RelayOps beachhead.
2. Define five pipeline stages with exit criteria for your CRM.
3. Continue to Lesson 3: Evidence, Metrics and Assumptions in Founder-Led Sales and Pipeline Creation.