Foundry Academy · CRM Operations · Lesson 4 of 6

Pipeline stages and exit criteria

Define opportunity stages by buyer evidence and required next decisions so forecasts do not rest on seller optimism.

Start the lesson

Your learning work, on this device

No signup, cloud storage, cross-device sync or verified completion. Saving is optional. This browser profile is shared with anyone who can use it; private mode, browser cleanup or storage limits may remove work. Use only fictional or non-sensitive material. Export a copy before relying on this device.

Not saved. Worksheets, answers and practice notes currently last only in this tab.

Practice markers are self-reported, never credentials.

01 · Explanation

Pipeline stages and exit criteria

Objective: Define opportunity stages by buyer evidence and required next decisions so forecasts do not rest on seller optimism.

A pipeline stage describes the state of a specific buying process, not how busy the seller feels. Define entry evidence, required fields, owner, buyer commitment, next action, expected duration, and exit choices for each stage. Examples may include accepted discovery, verified problem and authority, solution fit, commercial review, decision, and closed outcome, but the model must fit the business. Do not advance an opportunity because a proposal was sent if the buyer has not agreed to evaluate it.

Require close date, amount, probability, and forecast category to have documented definitions and update triggers. Record lost, no-decision, disqualified, duplicate, and delayed outcomes honestly; do not leave dead opportunities open to protect the dashboard. Set aging thresholds based on observed cycle behavior, then review exceptions. Pipeline information can include confidential commercial and personal data, so access should reflect role and business need. Forecasts are management estimates, not guarantees. Contract probability, revenue recognition, credit, and regulated sales decisions require appropriate authorized or professional review.

Before you begin

  • Confirm missing dated next steps, missing decision-role contacts, former-employee owners, and conflicting qualified-stage definitions.
  • Distinguish buyer evidence from seller activity, confidence, or forecast preference.
  • No individual opportunity records were supplied or reviewed; RC rows are controlled training examples or gaps.

Original overview module anchor →

02 · Compare the artifacts

Supported work. Visible uncertainty.

This fictional training case uses fabricated company and contact records. It contains no real personal or confidential data and does not provide privacy, legal, employment, or technology-vendor advice.

OrbitWorks CRM repair

OrbitWorks is a fictional business-to-business maintenance software company with 14 sales and service users. Its CRM holds 8,420 company records, 11,780 contacts, and 1,360 open opportunities. An audit sample finds 23 percent of open opportunities have no dated next step, 18 percent lack a decision-role contact, and 11 percent are assigned to former employees. Two pipelines use different meanings for qualified, yet both feed one forecast. Sales moves opportunities forward when a meeting is scheduled; customer success uses the stage only after a written problem and buying process are recorded. A marketing import of 2,100 contacts is waiting. The source contains 430 probable duplicates, 280 records without a documented marketing basis, 17 personal notes copied into a free-text field, and country values in nine formats. The proposed automation sends four emails and creates a call task, but it has no stop rule after opt-out, reply, disqualification, or opportunity creation. A dashboard reports a 72 percent win rate because it excludes closed-lost records older than 30 days. A regional manager requests administrator rights for all representatives to fix records faster. The CRM also has three integrations whose owners left the company; one export token has not been rotated in 19 months. Leadership wants a clean forecast by Friday and suggests overwriting all records from the import. Learners must design a controlled repair that improves lifecycle clarity, data standards, follow-up, stage evidence, reporting, permissions, and change management. They must minimize unnecessary personal data, preserve auditability, and avoid claiming that a configuration alone establishes lawful processing or accurate forecasts.

Supported example — reference only

Term or field
Qualified opportunity
Definition
Shared buyer-evidence definition is not supplied because sales and customer-success use conflicting criteria.
Allowed values or rule
Learner proposal: require an authorized definition with observable buyer evidence and explicit exit criteria before reclassification.
Evidence source
M04-I03 (F04, conflicting)
Owner
CRM process owner and data steward
Change trigger
Authorized resolution of the cross-team definition conflict.
Status
Conflict open — stage use requires review

A well-handled evidence gap

Term or field
Record-level reclassification evidence
Definition
Original stage, dated buyer evidence, decision-role contact, owner, and proposed stage for one opportunity.
Allowed values or rule
Use Unknown and Pending when an individual record is not supplied; never infer from aggregate percentages.
Evidence source
M04-I01, M04-I02 (aggregate facts only)
Owner
CRM process owner and data steward
Change trigger
Individual source record and approved stage definition become available.
Status
Gap open — no production reclassification

Flawed approach — do not copy

Marking this pipeline stage dictionary “approved and complete” without the required evidence or reviewer is a flawed submission. Stop reclassification when the shared stage definition, original value, dated buyer evidence, decision-role contact, owner, or reviewer is missing.

Repair: Rework the pipeline stage dictionary as an evidence-backed draft, not an approved result. Define each pipeline stage using observable buyer evidence, entry rule, exit rule, exclusions, owner, and change trigger. Record the sales and customer-success definitions as conflicting and route a shared-definition decision to the process owner. Preserve original stage values before proposing any reclassification. Check the revision against this requirement: Stage definitions use observable buyer evidence and preserve the cross-team conflict until authorized resolution. If the required evidence is still absent, keep the decision blocked and identify the missing input or authorized reviewer.

Full case record, ambiguities and all assignments →

03 · Bounded practice

Build the pipeline stage dictionary.

Propose stage entry and exit evidence that both teams can apply consistently.

Deliverable: A stage dictionary, aggregate reclassification examples based on F02 through F04, and a blank twenty-row reclassification worksheet clearly marked for later record-level evidence.

Complete a bounded starter and gap analysis using only CB01, F02, F03, F04, and the assignment-scope record below. Populate supported fields, label every unavailable field “not supplied,” and cite the input ID for each material statement. You may design a proposed template, control, question, or decision rule, but must label it as a learner proposal rather than observed case evidence. Do not contact people, access live systems, run tests, sign records, claim approval, or invent names, dates, quotations, transactions, results, or source documents.

Exact supplied inputs for this assignment
  • M04-I01 · F02 — Twenty-three percent of sampled open opportunities lack a dated next step.
  • M04-I02 · F03 — Eighteen percent lack a decision-role contact and eleven percent have former-employee owners.
  • M04-I03 · F04 — Sales and customer-success teams use different evidence to define the same qualified stage.
  • M04-B01 · CB01 — Use CB01, the full versioned case brief printed once at the start of this packet, as a citable narrative source for details not normalized into F01–F12. Preserve its uncertainty language and do not treat narrative detail as approval, complete operational records, or professional judgment.
  • M04-S01 · F02, F03, F04 — Build a starter version of “A stage dictionary, aggregate reclassification examples based on F02 through F04, and a blank twenty-row reclassification worksheet clearly marked for later record-level evidence.” from the listed case facts. Treat requested structures, controls, questions, calculations, and templates as learner-designed proposals. Where an operational record or result is absent, add a gap entry naming the missing evidence and authorized owner instead of fabricating it.

Operating procedure

  1. Define each pipeline stage using observable buyer evidence, entry rule, exit rule, exclusions, owner, and change trigger.
  2. Record the sales and customer-success definitions as conflicting and route a shared-definition decision to the process owner.
  3. Preserve original stage values before proposing any reclassification.
  4. For every RC row, record observed buyer evidence and required exit criterion; use Unknown at record level when individual evidence is absent.
  5. Do not reclassify based only on seller activity, missing next-step cleanup, or a desire to improve the forecast.
  6. Route conflicting definitions and record-level exceptions to the CRM process owner and data steward before production change.
  7. Quality-check all 20 RC identifiers, exact columns, source IDs, confidence, original-value preservation, and pending status.
Field-by-field guidance
Term or field
Name one pipeline stage or stage-governance field.
Definition
Describe the buyer state in observable terms, not salesperson confidence.
Allowed values or rule
State entry, exit, prohibited proxy, and unknown handling as a learner proposal.
Evidence source
Cite M04-I03 for the definition conflict or the exact authorized source when later supplied.
Owner
Use CRM process owner and data steward.
Change trigger
State what buyer evidence, governance decision, or audit result requires definition review.
Status
Use Conflict open, Proposed definition, Record-level evidence missing, or Approval pending.
Pipeline stage dictionary · learning draft
Term or fieldDefinitionAllowed values or ruleEvidence sourceOwnerChange triggerStatus

Start with 2 rows; the complete workbook specifies 2 stable rows for this artifact. Add rows here or use the full download. No action is saved until you explicitly choose saving above.

Download complete six-module workbook (.md) · Structured case packet (.json)

Keep private client data, unpublished inventions, personal identifiers and credentials out of these public learning tools.

Module 4 · 2-item formative check

Pipeline stages and exit criteria

Choose an answer and request feedback. Read why each option does or does not fit the evidence. Answers stay in this tab unless you choose device-only saving; they are never submitted.

Question 1 of 2 · MODULE 4 · knowledgeWhat is the strongest basis for moving an opportunity into a new pipeline stage?
Question 2 of 2 · MODULE 4 · scenarioWhat may the learner responsibly do when OrbitWorks has only aggregate records and conflicting stage definitions?

Answer either question to review its reasoning.

Inspect the artifact, not just your quiz answers

  • Stage definitions use observable buyer evidence and preserve the cross-team conflict until authorized resolution.
  • All 20 RC rows retain original-value and evidence fields, with missing records marked not supplied.
  • No aggregate percentage is converted into an individual reclassification result.

Stop: Stop reclassification when the shared stage definition, original value, dated buyer evidence, decision-role contact, owner, or reviewer is missing.

Go: Go to bounded reviewer analysis when the complete record-level evidence and authorized stage rule are present.

Escalate: Escalate definition conflicts and production reclassification to the CRM process owner and data steward.

04 · Evidence to keep

Leave with usable work.

Stage dictionary, decision tree, reclassification log, stale-opportunity queue, exception approvals, and forecast-definition sheet.

Download your artifact CSV and, if wanted, export the learning-work JSON above. Neither export is a reviewed submission or certificate. Device-only saving is optional; you must press Save my work now after edits.

When all six artifacts are ready, compare the full packet against the track rubric. Qualified human review is still required before real-world decisions.

Customer operations team discussing data and lifecycle information in a meeting.
Learn the standard. Practice the work.
Revenue operations colleagues coordinating a shared customer workflow.
Leave with evidence you can inspect.

Sources, scope and review boundaries

Curriculum 2026.10.08-learning-paths-1. External source dates below are record checks, not continuing guarantees. Verify current requirements before consequential use.

ws-crm-operating-standard · Academy internal operating standard

Wealth Synergy CRM operations internal operating standard

Academy-selected lifecycle, field, queue, stage, dashboard, change, and review controls. This is an internal operating standard selected by Foundry Academy; it is not law, accreditation, licensure, or an external-standard requirement.

Version 1.0 · reviewed 2026-09-01 · owner: Foundry Academy curriculum owner

A future Wealth Synergy private professional-development certificate would be issued only after its assessment, capstone, identity, reviewer, retention, access, deletion, appeal, and issuance controls pass quality review. No credential is currently issued. Any future certificate would not be an accredited academic qualification, professional license, or government certification.