The Alactic library
Sales pipeline design guides
From a better WhatsApp conversation to a clearer team handoff. Find a specific decision, a useful checklist or a workflow your business can put into practice.
20 articles in Sales pipeline design
Clear filtersClean an unreliable pipeline without replacing bad data with guesses
A practical way to separate proven corrections from open questions, review risky records first, and preserve context through a filled pipeline-cleanup worksheet.
10 min readMove open opportunities to revised stage definitions without guessing
Reassess existing deals against revised stage criteria, distinguish supported assignments from unresolved reviews, and use a filled worksheet to make each decision explainable.
9 min readCorrect stage history when administrative edits look like buyer progress
An accidental stage move is not buyer progress, and a correction is not a lost deal. Use an evidence-based correction log to preserve what happened, distinguish dates, and leave uncertain history explicitly unresolved.
10 min readRequire only the pipeline fields needed for the current stage
Use stage-specific requirements to prevent guessed CRM entries without letting advanced deals proceed on unsupported claims. Includes a filled matrix and a worked stage-change review.
9 min readPrevent duplicate opportunities from representing the same purchase
Use scope, buying decisions, budget and commitment evidence to separate duplicate opportunities from real parallel purchases—and keep one defensible record active for each purchase.
10 min readChoose the right pipeline correction for a stalled deal
Separate missing stage evidence, a blocked next step and a verified waiting period. Use a filled decision tree to make stalled-deal corrections traceable.
9 min readRepresent a genuine buyer pause without leaving a deal falsely active
A paused purchase is not an advancing deal. Use a separate pause status, preserve the last evidenced stage, and require buyer-backed restart evidence before returning it to active progression.
10 min readSeparate buyer inactivity from seller inactivity in stalled opportunities
A busy opportunity is not necessarily a moving purchase. Use a filled event-classification worksheet to separate CRM maintenance, seller effort, buyer engagement, and verified buyer progress.
10 min readDefine stalled deals using stage context rather than one universal timeout
Separate genuine stalls from legitimate waits and missing information using stage-specific milestones, evidence freshness, and a filled review worksheet.
10 min readRepresent conditional buyer commitments without overstating progress
A conditional yes is not always a reason to hold a deal back. Use stage exit criteria and a condition register to distinguish missing commitment evidence from parallel work and disclosed constraints.
10 min readDecide when parallel purchase paths should be separate opportunities
A department’s approval should not advance an entire account-wide deal. Use decision authority, commitment, timing, and purchase dependency to decide what belongs in one opportunity and what needs a linked record.
10 min readTrack parallel buyer approvals without turning them into a false sequence
Keep opportunity stages tied to buyer progress while tracking technical, security, procurement, and commercial reviews separately—with evidence, blockers, and explicit advancement conditions.
10 min readChoose between one pipeline and separate buying-motion pipelines
Compare buyer decisions and exit evidence to decide when separate pipelines are necessary—and when a label or conditional check will do.
9 min readDefine the exact event that makes an opportunity closed won
Choose a verifiable sales-completion event, distinguish blockers from later milestones, and test your rule with a filled decision table and calibration exercise.
9 min readMove a deal backward when buyer progress has genuinely reversed
Distinguish a temporary obstacle from lost buyer evidence, choose a supported destination stage, and preserve why the deal moved backward.
9 min readSet rules for opportunities that skip sales stages
Let returning buyers and fast-moving deals bypass unnecessary steps without bypassing evidence. Use a filled decision table to define permitted jumps, required checks, exception records, and recovery rules.
10 min readHandle missing evidence without pretending a deal has passed its stage gate
A seller’s confidence is not the same as confirmed evidence. Use explicit evidence statuses and bounded exceptions to keep opportunities moving without recording an unsupported stage-gate pass.
10 min readWrite stage exit criteria that two sellers can apply the same way
Turn vague pipeline labels into observable exit tests. Use a fictional filled matrix to define acceptable proof, distinguish fail from unresolved, and handle exceptions without creating a paperwork burden.
11 min readDecide whether a proposed pipeline stage deserves to exist
Keep a pipeline stage only when it distinguishes a buyer state, changes an operational decision, and has reliable evidence. Use a worked decision table to retain useful distinctions without turning every activity into a stage.
10 min readDefine sales stages around buyer progress instead of seller activity
A sent proposal is seller activity, not proof of buyer progress. Use this filled stage-definition worksheet to build evidence-based stages and test whether staff classify the same opportunity consistently.
10 min readTurn a guide into a working customer journey.
Explore the tools and services behind the operating process.