Buyer Signal to Rep Action

Purpose

Turn a current signal into a clear rep action. The skill is not a generic account-research exercise and it is not a reason to send more outreach. It helps a team decide whether the signal is commercially meaningful, what it implies, who should engage, and what the next move should be.

This is designed as a repeatable RevOps-deployed workflow. Every rep should receive the same decision logic, output structure, and quality bar while applying it to their own accounts.

Inputs

Start with the account name, domain, CRM record, contact, or signal. Ask one focused question only if the account or intended motion cannot be resolved.

Useful signal inputs include:

• New inbound lead, active conversation, or high-intent website activity.
• A prospect reply, renewed email activity, or a dormant deal re-engaging.
• Hiring, leadership, product, market, funding, competitor, or organizational change.
• A CRM event, call insight, customer win, or rep observation.

Workflow

1. Resolve the account and collect only evidence relevant to the signal. Use available connected sources such as CRM, inbox, LinkedIn, and approved account context. Never invent a signal, stakeholder, activity, or contact detail.

2. Classify the signal as High, Medium, Weak, or No action. Explain the classification in one sentence using the evidence. A signal is High only when it plausibly changes buying timing, business pain, stakeholder urgency, or the team’s ability to act now.

3. Build an account-specific sales play:

• What happened and why it matters now.
• The most likely business implication or hypothesis.
• The best person or role to engage next.
• The single best next action for the rep.
• A concise call opener and one diagnostic question.
• A review-ready email or LinkedIn outreach draft when outreach is appropriate.

4. Prefer judgment over activity. If the signal is weak, recommend monitoring, waiting, or a different action instead of manufacturing urgency or outreach.

5. Keep the play aligned to the team’s approved motion. Reuse the company’s product positioning, target personas, proof points, and messaging only when supported by the available context. Do not make unsupported outcome claims.

Output

Return a concise, rep-ready play using these reader-facing sections:

Signal State the evidence and confidence level.

Why It Matters Explain the commercial implication, or why it does not yet justify action.

Recommended Play Name the best next action, target role, and timing.

Talk Track Give a call opener plus one diagnostic question.

Draft Outreach Provide a short, personalized draft only when outreach is warranted.

What To Log State the material CRM note or learning the rep should capture after acting.

Demo Mode

For an end-to-end demo, use one real or sanitized signal and show the full loop:

1. A rep starts with a signal rather than a blank prompt.
2. The skill separates a real commercial reason to act from noise.
3. The rep receives an account-specific play, not generic research.
4. The rep reviews a ready-to-use call opener and outreach draft.
5. RevOps can deploy this same workflow to every rep, so the team acts on signals with the same standard.

Use a competitor play, new-segment motion, re-engaged opportunity, or high-intent inbound signal as the default demonstration scenario. The strongest demo is one where the skill recommends a specific action and explains why.

Guardrails

• Do not send messages, update records, or take external action unless the user asks for that action.
• Do not treat generic website visits, weak social engagement, or vague company news as proof of buying intent.
• Do not use a generic meeting request when a signal-specific question would be stronger.
• Do not output a long company brief. The output must help a rep decide what to do next.
• When evidence is insufficient, say so plainly and recommend the smallest useful follow-up action.