Build a founder sales pipeline that records rejection

A founder CRM often becomes a museum of conversations. Every friendly call is an opportunity, every opportunity is 'still alive,' and the pipeline expands while cash does not. The cure is not a more elaborate tool. It is a small number of stages with buyer-verified exits and an honest closed-lost state.

The broader founder-led sales discussion is at go-to-market chapter. Its useful output is a repeatable motion, not a pile of contacts.

Define qualified before defining stages

A qualified opportunity has a specific problem, a plausible fit, a responsible person, a reason to act in a bounded period, and an agreed next step. GitLab's public handbook describes qualification through authority, initiative, fit, and timing (GitLab effective discovery). That is one company's operating method, designed for its own sales organization. A founder can use a lighter test, but should not remove the underlying buyer facts.

Use five stages with exit evidence

1. Target: account fits the current segment; no pipeline value yet.
2. Qualified problem: buyer confirms the workflow, consequence, and timing.
3. Evaluation: buyer agrees to a demo, trial, or pilot with criteria and stakeholders.
4. Commercial decision: scope, buyer, price basis, approval path, and decision date are known.
5. Closed: won, lost, or no decision, with reason.

GitLab's opportunity-stage documentation requires an agreed next step and records a reason when an opportunity is unqualified (GitLab opportunity stages). Editorially, the founder version should be even stricter: a sent email is activity, not progression.

Make stalls visible

Every open opportunity needs a next buyer action, owner, and date. If the date passes without buyer action, mark it stalled. After a chosen period—perhaps two normal buying cycles for the stage—close it as no decision unless the buyer supplies a new dated step. The period is a company rule, not a universal benchmark.

Track losses with a controlled list: no urgent problem, no budget, wrong buyer, missing requirement, security or procurement block, competitor, internal build, timing, or no decision. Preserve a short note in the buyer's language. Rejections are product and segment evidence, not sales shame.

Hypothetical CRM examples

Hypothetical records:

• North Mill Logistics — Qualified problem. Ops lead confirmed 11 hours a week spent reconciling exceptions. CFO owns budget. Next step: finance joins workflow review on 24 September.
• Blue Kite Labs — Stalled evaluation. Demo completed, but no agreed criteria and champion missed two dates. Close as no decision on 30 September unless a buyer-owned test plan arrives.
• Harbor Clinic Group — Closed lost: missing requirement. Security requires regional data hosting that is outside current scope. Reopen only if the product decision changes.
• Oak & Finch — Disqualified. Interested user has no budget path and the problem occurs twice a year. Keep as research contact, not pipeline.

These are invented records, not reported company outcomes.

Weekly pipeline artifact

For each opportunity record:

• segment and triggering event;
• problem and consequence in buyer language;
• user, champion, economic buyer, and blocker;
• current stage and evidence for entry;
• next buyer action and date;
• estimated amount as a range until commercial scope exists;
• days in stage;
• stall or loss reason;
• product learning and follow-up owner.

Review new qualifications, stalled deals, and losses before totals. Do not forecast from unqualified targets.

Limits

A strict pipeline can still create false precision when deal counts are small. Stage probabilities borrowed from mature teams are especially misleading. Founder relationships may also move nonlinearly. Use the system to expose missing facts and repeated failure modes, not to manufacture predictable revenue before the motion is repeatable.