AI FOR YOUR WORK · SALESPEOPLE

Make AI your superpower: salespeople

Arrive prepared. Listen better. Follow up with purpose.

Your first project: A call brief and a relevant follow-up

A source-linked account brief, five discovery questions and a follow-up draft grounded in the call.

You bring the expertise: what matters to your audience, how your work is judged and what a useful result looks like. Give AI the organizing, drafting and exploration work that helps you move forward. Keep the decision in your hands.

Gather these inputs

The prospect’s public company page, a permitted CRM summary, your approved offer and notes from the actual conversation.

Choose one project that fits a focused working session. Save the original inputs and your final version together so you can see what changed. If you already pay for an assistant, begin there before adding another subscription.

1. Prepare around a reason to talk

Ask AI to extract the company’s stated priorities from public sources. Keep source links and dates. Frame a possible fit as a hypothesis, not a fact about the buyer’s budget or intent.

2. Write questions that reveal fit

Develop open questions about the current process, its consequences, the desired outcome and how a decision will be made. Avoid questions that merely steer the prospect toward your preferred answer.

3. Capture the commitments

After the call, separate buyer statements, your interpretation and agreed next steps. Record owners and dates only when they were actually discussed. Mark gaps for clarification.

4. Draft a useful follow-up

Summarize the problem in the buyer’s language. Connect the agreed next action to their goal and include the resource you promised. Review recipient, facts and links before sending. Keep follow-up timing tied to the conversation.

Try it with this practice brief

Practice inputCall notes: The team spends Friday compiling reports. Jordan wants to see a sample dashboard. You agreed to send a sample; no budget, implementation date or next meeting was agreed.

What a useful result preserves

The follow-up thanks Jordan, confirms the reporting problem and shares the sample. It does not claim a budget approval or say “see you Tuesday.”

Run the brief once, then deliberately remove an important detail. Check whether the assistant asks for it, leaves it unknown or invents an answer. Revise your instructions around the mistake you actually observe.

Copy your starting prompt

Create a concise follow-up using only these call notes and our approved offer. Include the buyer’s stated problem, commitments with owners, and one useful next action. List missing dates or details separately. Do not invent familiarity, budget, urgency, agreement or results. Produce a draft for my review; do not send it.

MY CONTEXT AND SOURCE MATERIAL:
[Paste permitted inputs]

OUTPUT REQUIREMENTS:
[Format, audience and constraints]

Keep the process that earns its place

Record preparation and review time, factual corrections, and whether the buyer takes the agreed next step. Separate reply volume from qualified progress.

Use the workflow on three representative examples. Keep a short correction log: what went wrong, what you changed and whether the next attempt improved. Save the best prompt with a good input/output example. That becomes a reusable working method for your next project.

When the steps become predictable, use the task automation guide. When the job needs an assistant to choose tools, follow the first-agent tutorial. Compare tools on the same brief in the Tool Trial Lab.

Common questions

Do I need a new subscription?

Start with an approved tool you already have. Add another only when the task exposes a specific missing capability. Check current plan limits and usage charges.

How do I know this is helping?

Count the time spent reviewing and correcting as well as drafting. Keep the workflow when it improves the finished result or makes the total process easier.

Explore the tools

Perplexity ↗Claude ↗

Sources and review notes

An original practice workflow from AI Superpower. The linked reference provides product or workflow background; the example is an exercise you can adapt.

Keep learning

← All journal articles