Hire an AI stalled sales deal follow-up writer

Everything it can hand back

Your task sets the actual outputs. The specialist picks the methods that cover them.

• The cause of the stall, how deep it runs and whether to count the deal in a forecast
• A personal recommendation, a stop to extra exploring and a safety net for each fear
• Four to seven short questions, each with an honest yes, ending at your ask
• Short, true lines for each moment the talk could turn

How it does the job well

• Research the buyer and their company before writing. One specific, true detail beats ten generic lines.
• Lead with the buyer's problem and outcome, not your features.
• Give every message one clear, low-effort next step.
• Qualify honestly. Record budget, authority, need and timing as known, unknown or assumed.

Mistakes it avoids

• Making claims about results, prices or terms that are not approved.
• Long first messages that ask for too much.
• Updating pipeline numbers on hope rather than evidence.

What a good result looks like

An example, not your task: A buyer keeps asking for more information, another demo or more time.

• Step 1: Why it stalled. The signs, the cause, how deep it goes, a firm recommendation, what to stop offering and a safety net for each fear.
• Step 2: The questions. The decision you are heading to, shared ground, four to seven easy-yes questions with a move for each no.
• Step 3: The replies. Short true lines for pushback: a welcome, a listening line, an agree line, owning your part and holding your view.
• Hand-back summary. Each step's file, any step not run and why, and every MISSING line in one list.

How the work is checked

• Each step passed its own checks, or the run stopped at the step that failed and says why.
• The cause in step 1 is backed by quotes from the buyer's notes, with dates.
• Every safety net answers one named fear and is something the person said they can deliver.
• No line adds a fake deadline, a made-up discount or a hint of a threat.
• States which checks passed, failed or could not run, and names missing inputs.

These checks have not been run against a model yet. Your AI uses them to check its own work.

A second opinion

Before it hands back, your AI reviews the draft the way Dale Carnegie and Benjamin Franklin would. This is a way of reviewing the work. It does not mean they wrote or endorse it.

Capabilities

• Name the cause of the stall. Reads your notes for repeated requests, vague worries and delays, sorts the cause, rates how deep it goes and writes a firm recommendation with a safety net for each fear.
• Build the ladder of easy questions. Starts from what you and the buyer already agree on and writes short questions, each with an honest yes, that end at the decision. It plans a move for each no.
• Write calm lines for pushback. Writes a welcome, a listening line and a line that agrees where the buyer is right. It holds your view gently and buys time when needed.

How the role works

1. Checks your task, context and available tools.
2. Picks the methods needed and prepares a work plan.
3. Carries out supported tasks, with each method's limits and review gates.
4. Checks the real deliverables and corrects supported faults.
5. Hands back files, evidence and unresolved gaps.

Your specialist's working setup

Download the base specialist without a task form or account. README.md and SETUP.md explain how to use the folder. SOUL.md defines its scope. INTAKE.md asks missing questions inside your AI. PLAYBOOK.md, SKILLS.md, BEST_PRACTICES.md, CHECKS.md and HANDOFF.md guide the work and its checked deliverables.

Complete associated skills, supporting files and licences are included. Choose only the methods needed for the actual task. Keep context, working files and accepted feedback in your AI project.

Use this specialist through MCP or the API

Call prepare_specialist with role_id get-a-quiet-deal-moving-again-without-pressure only. No task is required to load it. Your AI asks what job you need done, what you want back and which relevant context it can use.

For task-led hiring, call find_specialist, explain the suggested specialists and let the user accept or change the team.

Complete ZIP: Download base specialist. API: GET /api/v1/specialists/get-a-quiet-deal-moving-again-without-pressure/pack. The host AI supplies its own model, tools and execution; a pack does not connect accounts or run a task.

Inputs and helpful context

The specialist starts from the task brief. Only active methods require their inputs.

For the primary method, when used

• Your notes on the deal, what was said, asked for and left unanswered
• What you offered and at what price (optional but helpful)
• What you want the buyer to decide, and by when it is real
• Doubts or objections the buyer has said out loud (optional)

Tools and access

• Any good chat AI: Reading notes and drafting a short message is text work a strong chat AI does well.
• Your CRM or notes tool: Keep dates and quotes for each deal in one place.
• Any good chat AI: Ordering claims and wording short questions is text work any strong chat AI does well.
• An index card: Put the ladder on one card so you can glance at it in the room.
• Any good chat AI: Rewriting a reply in a calm, honest tone is text work any strong chat AI does well.
• Your email drafts folder: Save the reply as a draft and read it again the next day.

Functions and deliverables

• Stalled sales deal follow-up writer: Review why a deal may have stalled. Draft a clear next-step proposal, questions and calm replies from the facts you have.
  • The cause of the stall, how deep it runs and whether to count the deal in a forecast
  • A personal recommendation, a stop to extra exploring and a safety net for each fear
  • Four to seven short questions, each with an honest yes, ending at your ask
  • Short, true lines for each moment the talk could turn
• Stalled deal indecision checker: Find out why a quiet deal stalled: doubt, endless research or fear of a mistake. Paste your deal notes, get a plan and a message to send.
  • The signs of a stall, quoted with dates
  • The cause, with the quotes that show it
  • How deep it runs and whether to count the deal in your forecast
  • A personal pick, what to stop offering and a safety net for each fear
  • A message under 150 words that you can send today
• Sales agreement question planner: Write a yes ladder of four to seven fair questions that leads from shared ground to your ask, with a plan for each no.
  • A ladder of four to seven questions in order, each with the yes it expects
  • The shared point it starts from, and why it is safe
  • A move for each no, and a stopping line
  • A fairness check on every rung
• Disagreement response writer: Share the point at issue and what each person wants. Get honest listening, response and pause lines that avoid fake agreement.
  • A line for each moment the talk could turn
  • A rewrite of any phrase that says they are wrong
  • A true admission, if you erred, in one sentence
  • A rule for when to pause, and a line to do it
• Brand profile builder: Share your website. Get a reusable profile covering your products, customers, voice and approved claims, with sources.
  • A folder of eight plain files, from a start file for your AI to a claims list and a change log
  • A tag on every fact, and every claim marked approved, pending or banned
  • A two-sentence diagnosis of your biggest gap, and a list of what's missing and who can answer it
  • A short slice for your next step, if you name one
• Dale Carnegie: Rewrite a tense message or prepare a people conversation using Dale Carnegie’s recorded approach. See the other side, give sincere credit and ask clearly.
  • Your problem worked on the way Dale Carnegie would: their questions, their method, their push-back
  • The answer or the work, in Dale Carnegie's voice, using their ideas by name
  • Anything that goes beyond their public record, marked
  • One suggested next step
• Benjamin Franklin: Weigh a choice, start a habit or rally a group using Benjamin Franklin’s recorded approach. Write it down, test small and share the credit.
  • Your problem worked on the way Benjamin Franklin would: their questions, their method, their push-back
  • The answer or the work, in Benjamin Franklin's voice, using their ideas by name
  • Anything that goes beyond their public record, marked
  • One suggested next step

Tasks you can use it for

• A buyer keeps asking for more information, another demo or more time.
• A deal went quiet after a good meeting and you do not know why.
• You want to follow up without pushing or inventing urgency.

Limits to check before starting

• The buyer has said no. Accept it and ask what would have changed their mind, or end the talk politely.
• The deadline is real and you only need to close. Send a direct, short ask yourself instead.
• You have no notes on the buyer's own words yet. Get a call or email first, then come back.

Best way to use this role

Give it one clear outcome, the actual files and a definition of done. Keep the work in one AI project so it can reuse checked context and earlier files.

• Download the handoff pack. It's a zip with HANDOFF.md plus one skill file for each step.
• Give the folder to Claude (in Claude Code, or as files in a Claude Project) and say "Follow HANDOFF.md".
• Paste the buyer's own words from emails and calls, not your summary of them.
• Say if a deadline is real. If it is not, the steps leave urgency out.

Read it as data

Read the complete role setup as JSON. Connect your AI to the AI Blocks MCP library and read aiblocks://roles/get-a-quiet-deal-moving-again-without-pressure for its role instructions and pinned sources.

This is a prepared AI role. No task has run. Your AI carries out authorized work using its available tools and reports the actual deliverables and checks.