Forecasting playbook · Operator diary · 2026

Pipeline review pre-revenue with no CRM

Standard B2B SaaS pipeline review advice assumes you have Salesforce, a 7-stage pipeline, and an SDR feeding leads. At 5-15 deals in flight, all of that is overhead. A Notion database, a weekly 30-minute Friday review, and a 5-question audit per deal is the entire system you need until you have 30+ closed deals or hire your first AE. This is the format I ran for the first year of StackSwap — and the trigger that tells you when to graduate.

Why standard pipeline review breaks at pre-revenue

Standard pipeline review is built for sales teams running 50-200 deals through a 7-stage Salesforce pipeline with default stage probabilities (10% Discovery, 25% Demo, 50% Proposal, etc.). Those probabilities come from someone else's historical data. At pre-revenue with 5-15 deals in flight, you have no historical data — and the stage probabilities collapse into optimism dressed as forecasting.

The 7-stage pipeline also produces stage-mismatch. You misstage half your deals because there is not enough volume to develop intuition for which stage a deal is actually in. Did the prospect just engage, or are they evaluating? Did they ask for pricing because they are buying, or because their procurement team asked for a quote? At 5 deals, you guess. At 50 deals, you know. The fix at 5 deals is to use fewer stages, not better intuition.

The 5-step framework

Step 1 — Build a 4-stage pipeline in Notion (or Airtable)

Forget Salesforce stages. At pre-revenue with 5-15 deals in flight, you need 4 stages, not 7. The cadence that works: Aware (replied to outbound or inbound, no meeting yet), Engaged (discovery call scheduled or completed, real pain identified), Discussion (proposal/pricing shared, multi-thread starting), Decision (in procurement, target close date set, paper or e-sig in motion). One Notion database with these 4 statuses, a "next step" field, a "next step date" field, and a deal-amount field. That is the entire CRM you need for the first 15 deals.

Operator tip: Do not customize until you have to. The Notion template should fit on one screen. Every field you add is a field you will not fill consistently — and the un-filled fields are how pipeline data goes stale. Add fields only when you have run 5 reviews without them and felt the gap.

Step 2 — Run pipeline review weekly — same day, same time, 30 minutes max

Friday at 3 PM works because the week is mostly closed and the next week is unscheduled. Block the slot on your calendar for 90 days minimum. The review structure: 10 minutes on each deal in Discussion or Decision (8-10 deals max — if you have more than 10 in late stage, your motion is broken upstream, not your review). For each: read the "next step" field aloud, ask yourself "is that still the next step?", update the date if it slipped, write a one-line "what I learned this week" note. 30 minutes total. Skip the meeting if you have fewer than 3 deals in flight — there is nothing to review.

Operator tip: The single discipline that separates working pipeline review from theater: write the "what I learned" note even when nothing happened. "Nothing happened" is data. Three weeks of nothing-happened on the same deal means the deal is dead and you have not admitted it.

Step 3 — Use the 5 questions per deal — not stage probabilities

Standard CRMs assign a probability per stage (10% Discovery, 50% Demo, etc.). Those numbers are guesses from someone else's data. At your scale, run 5 questions instead: (1) What is the next dated action and is it on the calendar? (2) Have I spoken to the economic buyer or named them? (3) Do I know the decision process? (4) If they did nothing for 6 months, what would happen? (5) What would have to be true for them to choose us vs. status quo? If you cannot answer 3+ of these confidently, the deal is not in Decision stage — it is in Aware or Engaged, regardless of what you have called it.

Operator tip: The questions are an audit, not a script. If you find yourself making up answers ("I think the EB is the CRO?"), you have not done the discovery. Either run the next call or de-stage the deal. Both are real moves; the wrong move is pretending you know.

Step 4 — Forecast in 2 buckets, not 3 (until you have 30+ closed deals)

Standard B2B SaaS uses commit / best case / pipeline. At pre-revenue, that math collapses — you do not have enough deals for "best case" to mean anything statistically. Run 2 buckets: This Month (deals you are confident close before month-end, paper in motion, EB committed) and Not This Month (everything else). The forecast is the sum of This Month dollars. Track it weekly — if This Month was $40K on Friday and $25K next Friday, something slipped and the review surfaced it. When you have 30+ closed deals and real conversion data, graduate to commit/best/pipeline. Until then, the 2-bucket version is more honest.

Operator tip: The 2-bucket forecast is also a forcing function. Putting a deal in "This Month" is a commitment to yourself. Reps and founders both get stretched if they routinely call deals This Month that slip out — your honesty calibration improves quarter over quarter once you start tracking the misses.

Step 5 — Graduate to a real CRM at deal 15 or first sales hire

Notion / Airtable break around deal 15 because: (a) the data structures stop scaling — you want to slice by source, persona, ACV, and the spreadsheet view gets cluttered; (b) the first sales hire needs CRM access, automation, and integrations Notion does not provide; (c) the historical data starts having strategic value (cycle length, source quality, win rate by segment) that requires querying. Pick HubSpot Sales Hub Starter ($20/user/mo), Pipedrive ($20-50/user/mo), or Close ($59-$329/user/mo) depending on motion. Migrate the existing 15 deals manually — it is a 2-hour job and the cleanup forces good hygiene on the new system.

Operator tip: Do not migrate to Salesforce as your first CRM. Salesforce is built for sales teams of 5+ with admin capacity. At pre-revenue you will spend more time configuring Salesforce than running pipeline. HubSpot or Close are the right shape for first CRM; Salesforce is for later.

The Notion template — the entire artifact

The 4-stage pipeline lives in one Notion database. Fields:

That is the whole CRM. Eight fields. No automations, no integrations, no view customization. Add fields only when you have run 5 reviews without them and felt the gap. The gap-driven addition keeps the schema honest.

Three approaches considered

ApproachStructurePro caseWhy it fails at pre-revenue
Notion / Airtable 4-stage pipeline
Chose this
4-stage Notion or Airtable DB with next-step + next-step-date + amount fields. Weekly Friday 30-min review with 5 questions per deal. 2-bucket forecast (This Month / Not This Month). Migrate to real CRM at deal 15.Zero CRM cost for the first 15 deals. Pipeline review is fast (30 min vs. 90 min Salesforce reviews at scale). Founder runs the system personally and can absorb every deal mentally. Migration to real CRM later is straightforward (15 deals is manual but trivial).Breaks at deal 15-20. Does not integrate with email tools, marketing automation, billing. The first sales hire needs to graduate the system before they start. Plan for the migration ahead of time.
HubSpot Free CRM from day oneHubSpot Free CRM (2 free users) with the default 7-stage pipeline and weekly review meeting.Free for 2 users. Built-in email tracking and meeting booking. Real CRM that the first sales hire can use without migration. Looks more professional in conversations with customers.The default 7-stage pipeline is too granular for 5-15 deals. You will stage-mismatch deals constantly because there is not enough volume to develop intuition. Free-tier feature gates push you to paid quickly ($20+/user/mo on Sales Hub Starter). And the HubSpot UI rewards over-customization, which eats founder time.
Memory + a single text fileFounder keeps deals in their head plus a "deals.md" markdown file with rough status. No structured review.Zero setup. Maximum flexibility. Some founders genuinely run this way until deal 10 and close fine.Falls apart at deal 5-8. Deals slip without anyone noticing because there is no review cadence. When you hire the first AE, you have nothing to hand them — no history, no patterns, no next steps. The "I keep it in my head" approach is a future-self tax.

Common mistakes

Related operator reading

FAQ

Around deal 15 in active pipeline. The signs: you start losing track of who you talked to last week, the "next step" field gets stale on multiple deals, you want to slice by source or persona and the spreadsheet view is unworkable, or you are about to hire your first AE who needs CRM access. Any one of those is the migration trigger. The migration itself is a 2-hour manual job for 15 deals.

At 5-15 deals, 7 stages produces stage-mismatch — you misstage half your deals because there is not enough volume to develop intuition for which stage a deal is actually in. 4 stages (Aware / Engaged / Discussion / Decision) are simple enough to apply consistently. You can add stages later when you have 50+ closed deals and the data tells you where the natural breaks are.

Two reasons: (1) the week is mostly closed — most of what was going to happen has happened, and you can see the real movement; (2) the next week is unscheduled — you can act on the review by scheduling next steps before the weekend. Monday morning reviews look forward but cannot act on the past week's data; mid-week reviews catch you in motion. Friday 3-4 PM is the sweet spot.

No, not in the pipeline review. Activity tracking is for SDR / AE management once you have a team. At pre-revenue with you running every deal, the activity is implicit — you already know whether you talked to a prospect this week. What matters is the next dated action, not the count of prior actions. Save activity tracking for after the first hire.

Use the 2-bucket method: This Month (deals you are confident close before month-end) and Not This Month (everything else). Forecast = sum of This Month dollars. Track week over week. When This Month drops, ask yourself which deal slipped and why. After 30+ closed deals, you have enough data to add a 3rd bucket (Best Case) and run the standard commit / best case / pipeline structure.

Skip the review meeting and update the Notion doc as deals move. 30 minutes spent reviewing 2 deals is theater. The review structure earns its time at 5-15 deals in flight; below 5, you are running every deal in your head anyway. Resume the review cadence when pipeline rebuilds.

Set a 21-day cap on Aware stage. If a deal has been in Aware for 21 days with no movement, close it lost with reason "no engagement after 21 days" and re-add to your outbound list at a future date if the trigger is still real. Pipeline that sits forever inflates your sense of momentum without producing revenue. Forcing the close-out keeps the data honest.

The full forecasting-and-pipeline-review skill in the Playbook covers the 9-component framework end-to-end: stage definitions with exit criteria, deal scoring rubrics, forecast categories, pipeline review cadence at scale, forecast roll-up, accuracy tracking, slip detection, pipeline health KPIs. The Notion / 4-stage version above is the pre-revenue cut. Graduate to the full framework when you have 30+ closed deals or hire your first AE.

Canonical URL: https://stackswap.ai/pipeline-review-pre-revenue-no-crm