Sales system action surface
Sales system work breaks when every lead gets a different next action.
Use this parent playbook to connect lead summaries, routing, enrichment, qualification, outreach, follow-up, and CRM hygiene into one stage-by-stage operating map.
The system leak
AI sales work creates motion, but the CRM still needs decisions.
Teams often add AI to research, summaries, routing, message drafts, and CRM notes as separate tasks. That creates more output without a reliable handoff. A lead can be summarized but not routed, enriched but not qualified, or contacted without a follow-up rule.
The playbook is not a list of tips. It is the sales system map that says what each stage needs as input, what decision it must make, what output it must leave behind, and which next action is allowed.
Summaries stop short
The brief describes the lead but does not create an owner, route, or action.
Routing lacks proof
The lead enters a queue without a reason code or confidence level.
Enrichment expands forever
The team fills fields that do not change routing, qualification, or reply quality.
CRM truth arrives late
The next operator cannot see stage, last action, next action, owner, and date.
Central action object
Sales system map builder
Paste one live sales batch and your current rules. The output should show which stage each lead is in, what decision is blocked, and what next action should happen.
Copy-ready prompt
You are a sales operations playbook assistant.
Input:
SALES_BATCH:
[PASTE 5 TO 25 LEADS WITH SOURCE, SUMMARY, COMPANY, ROLE, NEED, ROUTE, ENRICHMENT STATUS, QUALIFICATION STATUS, OUTREACH STATUS, FOLLOW-UP DATE, CRM STAGE, OWNER, AND NOTES]
CURRENT_RULES:
[PASTE RULES FOR SUMMARY, ROUTING, ENRICHMENT, QUALIFICATION, OUTREACH, FOLLOW-UP, STOP CONDITIONS, AND CRM UPDATE REQUIREMENTS]
Task:
Create a sales system map for this batch. Identify each lead's current stage, blocked decision, required output, and next action.
Return this exact output format:
- system health summary
- stage map
- blocked decisions
- next-action selector
- CRM updates required
- risks or review flags
- first three actions to take today
Decision criteria:
Prioritize leads by evidence strength, current intent, route clarity, missing fields that block action, reply status, SLA risk, and revenue impact.
Rules:
- do not invent missing facts, budget, authority, urgency, or account ownership;
- separate Explicit, Inferred, and Unknown information;
- if a lead lacks a usable summary, send it to lead summary before routing;
- if a lead has a summary but no defensible route, send it to routing;
- if a route is blocked by missing fields, send it to enrichment;
- if qualification or outreach is not ready, state the exact missing output;
- every recommendation must convert to a CRM update or owner action.
QA check:
Before finalizing, remove any recommendation that sounds useful but does not produce a next action, CRM update, owner decision, or review flag.
Sales system map
Each stage must leave a decision behind for the next stage.
1. Lead summary
Convert raw form fields or notes into explicit facts, inferred context, unknown gaps, routing lane, and recommended next action.
2. Routing
Choose pursue, nurture, enrich, or skip with a rule, evidence, confidence, owner, and exception flag.
3. Enrichment
Fill only the minimum fields that change route, owner, qualification, first reply, suppression, duplicate handling, or skip decision.
4. Qualification
Decide whether the lead deserves active sales attention now, later nurture, review, or no action.
5. Outreach and follow-up
Turn the qualified reason into a useful message, then apply reply, pause, stop, and next-touch rules.
6. CRM truth
Store stage, owner, last action, next action, date, evidence note, and open risk so the next person can act.
Stage decisions
Use a stage-by-stage decision table before adding more automation.
| Stage | Input needed | Decision | Output required | Next action |
|---|---|---|---|---|
| Lead summary | Form fields, message, source, company, role. | What did the lead ask for, and what is unknown? | Brief with explicit facts, inferred intent, gaps, and recommended action. | Send to routing. |
| Routing | Lead brief, routing policy, account status, source priority. | pursue, nurture, enrich, or skip? | Route, reason code, owner, confidence, exception flag. | Assign, enrich, nurture, review, or close. |
| Enrichment | CRM record, blocked decision, minimum field policy. | enrich or do not enrich? | Only fields that change route, qualification, reply, or skip decision. | Rerun routing or move to qualification. |
| Qualification | Route, company context, role, need, urgency, missing gaps. | Is active selling justified now? | Fit decision, evidence line, risk, and next qualification question. | Send outreach, nurture, review, or skip. |
| Outreach | Qualified reason, relevance signal, channel, guardrails. | What useful promise and CTA should be sent? | Message angle, send date, CTA, and stop conditions. | Send and schedule follow-up. |
| Follow-up | Sent message, reply status, objection, next-touch date. | Continue, pause, stop, or book? | Reply summary, next touch, stop reason, meeting path. | Update CRM truth. |
| CRM truth | All previous stage outputs. | What must the next operator see? | Stage, owner, last action, next action, date, short evidence note. | Review stalled or risky records weekly. |
Next-action selector
Pick the next action from the first broken handoff.
raw lead, no brief
Build an inbound lead summary before routing. The route should not be guessed from a form notification alone.
brief exists, route unclear
Run the lead routing rule builder and choose pursue, nurture, enrich, or skip with evidence.
route blocked by missing data
Run the enrichment checklist and fill only the minimum fields that change the decision.
pursue route is clear
Assign an owner, qualify the remaining gaps, and create the first reply or meeting path.
nurture route is clear
Add a context note, review date, and reason why active selling is premature.
skip route is clear
Close, merge, suppress, or mark no action with the reason code visible.
Example output
One lead should move through the system without losing the decision trail.
lead summary
VP Operations says inbound demo handoffs are inconsistent and urgent requests need faster routing. Budget and current CRM platform are Unknown.
routing stage
pursue with enrichment attached. Rule fired from inbound source, stated workflow pain, senior operations role, and planning deadline.
enrichment stage
Verify website and account status. Keep budget, authority, inbound volume, and CRM platform as Unknown until supplied or evidenced.
qualification stage
Ask one clarifying question about inbound volume and whether the planning meeting is a decision deadline or an internal checkpoint.
CRM truth
Stage: routed. Owner: inbound sales operations queue. Last action: lead brief created. Next action: reply today and enrich account status. Risk: budget Unknown.
Quality boundary
The playbook is working only when every stage converts to action.
Good AI role
Summarize, classify, draft, compare, flag gaps, and convert messy notes into stage output.
Human-owned decision
Approve route policy, decide pursuit, send claims, handle replies, and move real pipeline stages.
Evidence rule
Any claim about fit, urgency, owner, account status, or next action must cite a field, message, CRM value, or policy rule.
CRM rule
No stage is done until the CRM contains owner, last action, next action, date, and uncertainty.
A sales playbook is not finished when it explains the funnel. It is finished when the next owner can act from the record.