WRKZY
Start free trialStart trial

Customer operations

Build a sales pipeline around evidence, not optimism

Define every deal stage with customer evidence, a responsible owner, an exit decision and a dated next action.

WRKZY EditorialProduct learning and Help editorial team
guide7 min readPublished August 1, 2026

Proposal. ₹1,85,000. From the other side of a Friday pipeline review, that deal looks healthy.

Then the sales lead asks: What customer evidence put it there? Who owns the next decision? What must be true before it leaves? What happens next, and by when?

The stage label cannot answer. Probability is missing, the customer state says Awaiting customer and there is no accountable next action. The team knows where the card is; it does not know whether the commercial work is healthy.

A useful pipeline needs fewer hopeful columns and more explainable states—clear enough for an operator to use and a manager to inspect.

A revenue leader and sales operator inspect pipeline evidence and the next commercial action together.
A stage becomes useful when another teammate can see why the deal is there and what happens next.

Make every stage earn its name

A useful stage describes a meaningful change in the customer’s commercial decision. Calls, meetings, and record updates belong in conversations, tasks, comments, or history; they do not by themselves prove that the buying decision changed.

Define every stage with four parts:

  1. Required evidence: the customer, commercial, or operational facts that make the stage true.
  2. Responsible owner: the one person accountable for progressing the current decision.
  3. Exit decision: the new evidence or confirmed outcome that allows the deal to leave.
  4. Next action: the specific owned step and due time that keeps the decision moving.
WRKZY operating modelFour parts make a pipeline stage operational
  1. Stage 1QualifiedNeed and fit are evidencedNext: Confirm scope
  2. Stage 2Scope sharedBuyer received reviewed scopeNext: Resolve open points
  3. Stage 3DecisionQuote and stakeholders are currentNext: Record the response
  4. Outcome branchWon / LostDistinct evidence and reasonsNext: Start the right follow-through
A meaningful stage explains why the deal is there, who carries the decision, what evidence allows it to leave, and which dated action keeps the customer outcome moving.

The names will differ by selling motion, but a compact example could look like this:

StageRequired evidenceResponsible ownerExit decisionNext action
NewVerified contact or company with a legitimate commercial questionIntake or deal ownerQualify the need or keep it as an inbox enquiryConfirm need, scope, and decision path by a stated time
QualifiedNeed, likely scope, buying path, and timing are understoodDeal ownerInputs support preparing an offerConfirm commercial inputs or prepare reviewed scope
ProposalA reviewed quote or scope was shared with the buyerDeal ownerThe buyer accepts, requests change, declines, or gives a decision pathReview the response by its due time
WonBuyer acceptance and actual close date are confirmedClosing ownerThe accepted outcome and downstream responsibility are recordedHand off fulfilment, onboarding, billing, or the agreed next outcome
LostA declined, displaced, or stopped decision and its reviewed reason are confirmedClosing ownerThe loss reason and any legitimate return path are recordedClose current work and preserve only the agreed future follow-through

These are examples, not a universal schema. Different selling motions may need different labels; the four-part test should remain stable.

Do not make the stage carry every signal

Stage is only one signal in a deal. WRKZY also records owner, priority, probability, forecast category, expected close date, status, and next-action work. Each answers a different question:

  • Stage: where is the customer decision in the configured process?
  • Owner: who is accountable for progression now?
  • Priority: how urgently should the team attend to it?
  • Probability: what likelihood does the current evidence support?
  • Forecast category: how should the deal contribute to the selected period?
  • Expected close: when is the commercial decision currently expected?
  • Status: is the outcome open, won, or lost?

Do not use an advanced stage as proof of a close date, treat high priority as a forecast commitment, or assume a default probability is current customer evidence. See the WRKZY Pipelines product view for how these signals remain inspectable without collapsing them into one field.

Retire the stages that hide weak evidence

Ask whether two trained teammates would move the same deal from the same source evidence. These designs usually fail that test:

  • Activity stages: “Called twice” or “Demo booked” describe team activity, not a changed customer decision.
  • Mood stages: “Hot” or “Strong” conceal evidence. Use priority, probability, and forecast category independently.
  • Department stages: “With finance” names a queue without the dependency, owner, approval path, or exit decision.
  • Premature Proposal: a draft quote does not prove that a buyer received a reviewed offer.
  • Calendar movement: time should trigger inspection, not automatic advancement.
  • Terminal-stage cleanup: Won and Lost describe customer outcomes; archive describes record lifecycle.
WRKZY Retail Sales pipeline board showing New, Qualified, Proposal, and Won stages, three deals, portfolio value, forecast gaps, and cards without follow-ups or with an overdue close.
Look forStage · value · missing follow-upOpen larger ↗
  1. 1Selected pipeline and board view
  2. 2Portfolio health and forecast gaps
  3. 3Stage, value, and follow-up state
Retail Sales shows three populated deals across Qualified, Proposal, and Won, with stage values, no-follow-up warnings, missing weighted inputs, and an overdue close. It does not prove linked records, history, or forecast accuracy.

Evidence boundaryThis proves the current board, stage placement, value, and visible operating gaps. It does not prove why a deal entered a stage, the configured movement rules, or the evidence in each deal's history.

This board is useful precisely because it does not present the pipeline as healthy. It makes missing follow-up, incomplete weighted inputs, and overdue timing visible reasons to inspect the underlying deals.

Configure the process in the order people use it

Start with a process the team already runs. Owners and Admins can then translate it into WRKZY without confusing configuration with proof.

  1. Choose one selling motion. Use sanitized representative patterns to identify where the customer decision changes.
  2. Define the beginning and outcomes. Decide what qualifies as a deal, which Open stage may accept new work, and what evidence confirms Won or Lost.
  3. Write the four-part contract. Agree on evidence, owner, exit decision, and next action before configuring controls.
  4. Configure stage behavior. Set name, color, Open/Won/Lost type, default probability, stale threshold, creation rule, and optional, recommended, or required fields.
  5. Protect meaning. Restrict skips or backward moves when intermediate evidence matters; add a value-based approval threshold where needed.
  6. Test with a non-customer record. Exercise allowed and blocked moves, missing fields, approval, and Won/Lost outcomes. Verify close evidence and history.
  7. Plan for existing deals. Review open records, choose how to assess or migrate them, and teach the evidence definitions before saving structural change.

The implementation guide provides the exact setup and test path for configuring sales pipelines and stages.

Treat the Deal Room as the stage receipt

Board position answers where the deal sits. The Deal Room should help an authorized teammate understand why it sits there and what must happen next.

Before every move, ask:

  1. What changed with the customer?
  2. Which destination-stage definition is now true?
  3. What work remains?
  4. Who owns that work, and by when?

If the only answer is “we want the deal to progress,” leave it where it is. Complete required fields from verified sources, obtain any triggered approval, create or update the deal-linked next-action task, and confirm the transition appears in durable history.

WRKZY Deal Room showing the buyer, deal stage, value, owner, customer state, missing forecast evidence, and no accountable next action.
Look forDeal state · evidence · next actionOpen larger ↗
  1. 1Buyer, stage, and value
  2. 2No accountable next action
  3. 3Evidence and risk signals
This Proposal-stage Deal Room shows Aarav Mehta, ₹1,85,000 value, customer state, missing probability, and no next action. It proves visible commercial gaps, not the source conversation or History contents.

Evidence boundaryThis proves a commercial decision surface and visible missing evidence. It does not show the source conversation or the contents of the History tab.

The deal records the team’s current commercial judgment; a linked quote records the exact buyer-facing offer and its response history. Keep that distinction intact when you move a deal through a pipeline.

No next action, no healthy deal

An active deal without a named owner and due action is not operational merely because it occupies the correct column. After movement, mark one deal-linked task as the next action, with a clear title, assignee, due time, priority, and reminder where needed. Use comments for progress or blockers and notes for durable context.

Use each Deals view for a distinct operating question:

  • Work for commitments such as Needs action, Awaiting customer, Overdue, Unassigned, Quote pending, Stalled, and Data gaps;
  • Board for stage flow and individual movement;
  • Table for dense comparison and reviewed bulk changes; and
  • Forecast for period, owner, probability, category, currency, target, and coverage inspection.

None replaces the Deal Room when a consequential change needs customer and commercial context. For the task-level practice, use Track deal follow-ups, tasks, and comments.

Measure whether the pipeline is getting more truthful

Pipeline health is not the number of deals that move forward. A fast-moving pipeline can still contain weak evidence, missing ownership, and repeatedly pushed close dates.

Review a sample weekly and track:

  • the share of active deals with one accountable owner;
  • the share with one marked next action and a usable due time;
  • deals beyond their stage’s stale-after threshold;
  • no-follow-up, missing-probability, and overdue-close signals;
  • close-date pushes and time in stage;
  • blocked moves caused by missing required fields or approvals; and
  • sampled stage transitions where the source evidence, exit decision, and history agree.

Read these as prompts, not verdicts. A blocked move can mean the control worked; a long stage can reflect a legitimate buying process. Open the deal before deciding whether to coach the owner, repair the definition, or close honestly.

Prove the design with one representative deal

Choose a recurring selling motion and run one representative opportunity from verified enquiry to a governed outcome. At every stage, require the team to explain the evidence, owner, exit decision, and next action. Then inspect whether Work, Board, Table, Forecast, the Deal Room, and history describe the same commercial reality.

Explore WRKZY Pipelines to evaluate the operating model, then use the configuration guide to turn one approved sales process into a testable pipeline.

Related Help Center guideConfigure sales pipelines and stages

Continue the workflow

The next field notes for this operating problem.