Sales Workflow Checklist: Lead to Close

What a sales workflow checklist must control

A sales workflow checklist should control execution, not merely describe pipeline stages. For every active account, it should show the action that must happen, the evidence that proves it happened, the person who owns it, and the dated next action. That structure turns a static process document into a working control for reps and managers.

Direct answer. Use the checklist across seven stages: account selection, research, outreach, qualification, call execution, follow-up, and deal control. Do not mark a stage complete because an activity occurred. Mark it complete only when the required evidence exists and a named owner has committed to the next action.

This distinction matters because a pipeline and a workflow answer different questions. Salesforce defines a pipeline as a view of where each prospect sits in the sales process, helping teams identify roadblocks and next steps. A workflow goes one level deeper: it defines what the seller must do inside and between those stages. Read the Salesforce pipeline guide for the stage model, then use this checklist to control the work that moves an account forward.

If you still need to design the underlying sequence, start with how to build a sales workflow. If the sequence already exists but feels inconsistent, use this page as the operating checklist and the separate sales workflow audit as the diagnostic.

Set up the checklist with the AEON model

Set up each checklist row with four fields: Action, Evidence, Owner, and Next action. The initials form AEON, a simple operating model for making completion auditable. It is a Gangly recommendation, not an industry standard, and you should change the fields when your governance requires more detail.

1. Action: write the smallest meaningful task in verb form. “Research account” is vague. “Confirm ICP fit and identify one current trigger” is usable.
2. Evidence: name the artifact that proves the task is complete. Use a CRM field, linked source, call note, buyer email, mutual plan, or recorded decision.
3. Owner: assign one person who is accountable for moving the item. Contributors can be listed separately, but shared ownership usually hides delay.
4. Next: record a dated action or a clear exit. “Follow up” is not enough. “Send security answers to Maya by 14 August” is.

Salesforce notes that the number and shape of sales-process steps vary by industry, product, and prospect. Its training model includes research, lead generation, the sales call and close, and relationship building, while its pipeline guidance uses seven more granular stages. Both are valid because stage labels are a design choice. The useful constant is that each stage needs a clear purpose and a way to know when it is complete. See the Salesforce Trailhead sales-process module for that adaptable foundation.

Stage 1: select and prioritize the right accounts

Account selection is complete when you can explain both fit and timing. Fit tells you whether the account resembles a customer you can serve. Timing gives you a defensible reason to work the account now instead of six months from now.

Account-selection checklist

• Confirm the company matches your ICP criteria for industry, size, geography, use case, and technical constraints.
• Identify the likely team or function that owns the problem.
• Record one observable timing signal, such as a leadership change, funding event, active evaluation, hiring pattern, contract date, or direct engagement.
• Write why the signal connects to the problem you solve. A news event without a relevance bridge is not a sales reason.
• Assign a priority and a review date. Remove the account when neither fit nor timing survives inspection.

The completion evidence is a one-sentence account thesis: “This account fits because ___, and it is worth attention now because ___.” Keep the source link beside it. If you cannot finish that sentence without guessing, return the account to nurture or research rather than pushing it into outreach.

This stage connects naturally to sales workflow mapping, where you define how signals enter the system and who decides what becomes rep work.

Stage 2: research the account and buying context

Research is complete when the seller has enough context to make a relevant first move, not when every public detail has been collected. The checklist should stop research from becoming either a two-minute guess or a forty-minute biography.

Research checklist

• Verify the contact's current role, remit, tenure, and likely relationship to the problem.
• Review the CRM for prior conversations, open opportunities, support history, opt-outs, and ownership conflicts.
• Open the source behind the trigger event and note its date.
• Write one pain hypothesis and label it as a hypothesis until the buyer confirms it.
• Choose one proof point or customer example that matches the account context. Do not force an unrelated logo into the message.
• Record what you still do not know and convert it into a discovery question.

The required artifact is a short account brief with source links, a relevance hypothesis, and two or three questions. Salesforce's process guidance explicitly starts with product and prospect research, but it also says to adapt the steps to the business. That is the right constraint: research must support a decision, not become the decision.

Stage 3: run outreach with a specific reason now

Outreach is complete only when the message has a specific reason now, one useful idea, a proportionate ask, and a scheduled next action. Sending a generic touch may satisfy an activity dashboard, but it does not satisfy this checklist.

Outreach checklist

• Open with the account-specific reason for contact.
• Connect that reason to a credible problem hypothesis without pretending you know the buyer's private situation.
• Offer one useful observation, question, or relevant proof point.
• Use a single call to action sized to the relationship.
• Check channel rules, consent, opt-out status, and local requirements before sending.
• Log the message and schedule the next touch or exit condition.

A good evidence row links to the exact message and the next scheduled action. This also makes a later workflow optimization review possible because you can compare what was sent, why it was sent, and what happened next.

Stage 4: qualify and discover before proposing

Qualification is complete when the seller and buyer have established a real problem, a plausible fit, the buying process, and a mutually understood next step. A filled framework is not enough if the answers are inferred or copied from another contact.

Qualification and discovery checklist

• Confirm the current situation and the consequence of leaving it unchanged.
• Identify the desired outcome in the buyer's own language.
• Separate confirmed facts from rep assumptions in the notes.
• Map the people involved in using, evaluating, approving, securing, and paying for the change.
• Understand the decision steps, timing constraints, and competing priorities.
• Test whether your solution can meet the material requirements. Disqualify when it cannot.
• Agree on a next action that both sides can see and date.

Salesforce describes qualification as checking fit and gathering needs, budget, timeline, and purchasing authority. That is a useful starting set, but your workflow should reflect the actual complexity of the deal. The evidence can be a structured call note, qualification record, stakeholder map, and buyer-confirmed next step.

Stage 5: prepare and run the sales call

Call execution starts before the meeting. The checklist should make the purpose, participants, evidence target, and next-step options explicit before anyone joins. It should then capture what changed because of the conversation.

Pre-call checklist

• State the meeting objective and the decision or evidence you need by the end.
• Confirm the right participants and their likely roles.
• Review the account brief, previous commitments, open questions, and known objections.
• Prepare an agenda and share it when appropriate.
• Choose the proof, demo path, or questions that match the confirmed problem.
• Prepare two sensible next steps: one for progress and one for a no-decision or disqualification outcome.

In-call checklist

• Confirm the purpose and adjust the agenda with the buyer.
• Ask before presenting. Do not treat the prep hypothesis as a diagnosis.
• Record decisions, concerns, owners, and dates as they emerge.
• Summarize what you heard and ask the buyer to correct it.
• Agree on the next action before ending the meeting.

The completion evidence is not “call held.” It is a confirmed summary plus the decision, new information, and next commitment created during the meeting.

Stage 6: close the loop after every conversation

Close the conversation loop while the context is still fresh. The follow-up should distinguish what was decided, what remains open, who owns each task, and when the parties will reconnect.

Post-call checklist

• Write the call summary using the buyer's language and correct any ambiguous notes.
• List decisions separately from discussion topics.
• Assign each task to one owner with a due date.
• Send the buyer recap and requested material through the agreed channel.
• Update the CRM fields supported by the conversation.
• Create the next meeting or task, or record why the opportunity is paused or closed.

The workflow should preserve the link between the source conversation and each field update. That trace is valuable when a manager reviews the deal and when another teammate takes over. It also prevents a recap email, CRM record, and forecast from telling three different stories.

Stage 7: keep the deal and CRM moving

Deal control means the CRM reflects buyer evidence rather than rep optimism. Salesforce explains that opportunities move when they meet stage exit criteria and that pipeline records need consistent updates. Your checklist should make those criteria visible and testable.

Deal-control checklist

• Move the stage only when its documented exit criteria are met.
• Keep amount, product scope, close date, contact roles, and next action current.
• Attach or link the evidence that supports material changes.
• Flag missing stakeholders, unanswered requirements, and buyer-side dependencies as risks.
• Review inactive opportunities and choose a next action, nurture state, or close reason.
• At closed won, transfer the problem, promised outcome, commitments, risks, and stakeholders to the implementation owner.
• At closed lost, record the actual reason when known and distinguish it from a guess.

Use the sales pipeline management guide for the management rhythm around these fields. The checklist here protects the evidence inside each record.

Adapt the checklist to your sales motion

Adapt the checklist by changing evidence depth and ownership, not by deleting the controls that make work visible. Salesforce's seven common pipeline stages are a helpful baseline, while other workflow templates add explicit objectives, activities, exit criteria, and blockers. The SiftHub workflow template is one example of that richer stage design, although its recommendations reflect its own product perspective.

If your goal is organizational diagnosis rather than daily execution, a process-audit checklist is the better tool. For example, the GSR Revenue process-audit checklist groups questions across lead management, nurture, discovery, presentation, closing, and pipeline hygiene. Use that kind of instrument to locate a system gap; use AEON to control the account work after you decide what to change.

Run a 15-minute weekly workflow review

A weekly workflow review should take a small sample of active accounts and inspect evidence quality. It is not another forecast meeting. The purpose is to find one execution rule that needs clarification or one recurring task that should be removed, automated, or reassigned.

1. 1. Which items are marked complete but have no evidence?
2. 2. Which active accounts have no dated next action?
3. 3. Which task has two owners or no owner?
4. 4. Which stage creates the most waiting or rework?
5. 5. What one rule should change before next week?

Sample across stages rather than reviewing only the largest opportunities. Pick one early account, one active evaluation, one late-stage deal, and one stale record. When the same problem appears across the sample, update the workflow rule. When it appears once, fix the account rather than redesigning the entire process.

Track only changes that help a decision. Useful workflow measures include the share of active accounts with a dated next action, the share of stage moves with evidence, overdue owner commitments, and time waiting between buyer and seller actions. These are operating measures, not universal benchmarks. Establish your baseline first, then judge whether a workflow change improves it.

How Gangly supports the connected workflow

Gangly supports the connected seller workflow by carrying context from one action to the next. It does not remove seller judgment, and the quality of several features depends on the CRM and data sources you connect.

• Signal Detection can surface and rank warm-account events so the rep can record a reason now.
• Outreach Writer uses the account signal and approved rep examples to draft a message for review rather than sending autonomously.
• Call Prep Engine assembles available account, contact, CRM, and conversation context into a structured brief.
• Post-Call Notes prepares a summary, tasks, CRM note, and follow-up draft for the rep to review.
• CRM Hygiene Engine suggests field and stage updates while keeping the rep in control of confirmation.
• Workflow Sequencer tracks where an account sits across the connected sequence.

Start with the checklist before adding software. If the team cannot define the action, evidence, owner, and next step, automation will only move ambiguity faster. Once those controls are clear, a connected system can reduce repeated entry and make missing evidence easier to see.