Hire an AI sales proposal narrative writer

Everything it can hand back

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

• 3 to 5 win themes, each with the buyer's need, your answer and the proof
• A one-page executive summary draft in five parts
• A section-by-section outline showing which theme each section carries
• A table of every buyer requirement, where it is answered and what to add
• A list of weak spots, such as generic lines, empty adjectives and claims with no proof
• A short note on how you stand out from likely rival bids, without naming them

How it does the job well

• Never invent proof: no case study, metric, customer name, award or reference. Write <proof needed> where the user gave none, and say what would count as proof.
• Every theme must name this buyer's own problem. If swapping in another client's name would not change it, rewrite it.
• No empty adjectives such as "robust" or "best-in-class". Replace each with a specific or cut it.
• Do not criticize rival bids by name. Show the contrast through your own strengths.
• Show value before price. Do not pick prices, discounts or terms. Pass those to the user.
• 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.

Mistakes it avoids

• A proposal where the buyer's name could be swapped for another and nothing breaks.
• Listing features instead of answering the buyer's problem.
• Copying the profile's sample metrics into the draft.
• Hiding a requirement the user cannot meet. Name it as a gap.
• Making claims about results, prices or terms that are not approved.
• Long first messages that ask for too much.

What a good result looks like

An example, not your task: An RFP has landed and you have a short deadline to respond.

• Win themes. Three to five themes, each with the buyer's need, your answer and the proof.
• Executive summary draft. A one-page argument in five parts, written in the buyer's own words.
• Proposal outline. The story in three parts, with a theme and a proof point for each section.
• Requirement map. Every buyer requirement, where you answer it and the point to add.
• Weak spots. Generic lines, empty adjectives and unproven claims, each with a fix.
• Assumptions and checks. What the AI assumed and what you must confirm before you submit.

How the work is checked

• Personal details are verifiable and correct.
• Each deal update cites the call, email or note behind it.
• Follow-ups have dates and owners.
• 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 April Dunford and Clayton Makepeace would. This is a way of reviewing the work. It does not mean they wrote or endorse it.

Capabilities

• Read the buyer. It pulls out what the buyer asked for, what they seem to prefer and how they will score answers.
• Draft win themes. It writes 3 to 5 candidate themes that link your strengths to the buyer's most urgent needs.
• Stress-test each theme. It asks whether the theme is specific to this buyer, provable, and hard for a rival to claim. Weak ones are cut.
• Plan the story. It splits the proposal into understanding, approach and outcome, and assigns each section a theme and a proof point.
• Draft the summary first. It writes the executive summary in five parts, so the argument is clear before the details pile up.
• Map the requirements. It lists every requirement with where it is answered and the extra point that answer should make.
• Flag weak spots. It marks generic lines, empty adjectives and claims with no proof, and says what to fix.

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 sales-proposal-strategist 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/sales-proposal-strategist/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

• The RFP, or your notes from calls with the buyer, pasted as text. A long RFP can go in as an uploaded file.
• What you offer and how you would do the work, in a few lines.
• Proof you can really show, such as past projects and results you can back with numbers or a named reference.
• Who else may bid and what you know about them (optional)
• The deadline, page limits and how the buyer will score answers (optional)
• Your price range or the buyer's budget (optional)

Helpful context (optional)

• A proposal of yours that won, so the new plan can reuse what worked.
• The buyer's own website or annual report text, so the summary uses their words.
• Written feedback from a lost bid, so the plan fixes what the buyer disliked.

Tools and access

• Claude, ChatGPT or Gemini with file upload: A long RFP goes in as a file, so the requirement map covers every line.

Functions and deliverables

• Sales proposal narrative writer: Turn an RFP or buyer brief into a sales proposal plan with win themes, a one-page summary draft and an outline you can write from.
  • 3 to 5 win themes, each with the buyer's need, your answer and the proof
  • A one-page executive summary draft in five parts
  • A section-by-section outline showing which theme each section carries
  • A table of every buyer requirement, where it is answered and what to add
  • A list of weak spots, such as generic lines, empty adjectives and claims with no proof
  • A short note on how you stand out from likely rival bids, without naming them
  Source: Michael Sitarzewski and Agency Agents contributors.
• Sales proposal writer: Turn an RFP or call notes into a sales proposal with a summary, price table, timeline and case studies, ready for you to polish and send.
  • An executive summary
  • Requirement-by-requirement answers
  • A pricing table
  • Case study sections
  Source: Burhan Sebin.
• Evidence-based sales copy writer: Write the body and close of your sales page, email or long ad, with proof beside every claim. Give it your opening, buyer notes and facts.
  • The body and close as finished text, within your length
  • A list of each claim and the proof placed beside it
  • What it assumed, any placeholders left for missing figures, and any check it couldn't meet
• Sales letter outline planner: Plan a sales letter outline before you write it. Give it your research and theme. You get ordered sections, headline ideas and the proof each claim needs.
  • A section-by-section outline, each section with the yes it must win
  • A pile of headline ideas sorted by how they lead
  • A table of claims with the proof for each
  • Three options for the headline, deck and lead-in
  • A brief another writer or AI can write from
• 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
• April Dunford: Work out why buyers should choose your product. Use April Dunford's positioning method to find real alternatives, buyer value and a clear sales pitch.
  • Your problem worked on the way April Dunford would: their questions, their method, their push-back
  • The answer or the work, in April Dunford's voice, using their ideas by name
  • Anything that goes beyond their public record, marked
  • One suggested next step
• Clayton Makepeace: Plan or review a sales page using Clayton Makepeace’s recorded approach. Understand the reader’s concern, outline the argument and find proof for claims.
  • Your problem worked on the way Clayton Makepeace would: their questions, their method, their push-back
  • The answer or the work, in Clayton Makepeace'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

• An RFP has landed and you have a short deadline to respond.
• A buyer asked for a proposal after a good call and you need to turn your notes into an argument.
• Your last proposals lost and the feedback said they felt generic.
• Several people will write the sections and need one set of themes to follow.

Limits to check before starting

• You need contract terms, a scope of work or NDA wording. Use the Contract and proposal drafter, and have a lawyer check it.
• You need the price set or your tiers worked out. Use the Pricing analyst.
• You want to judge whether a deal is worth chasing. Use the Sales deal reviewer.
• You want short outreach emails, not a proposal. Use the Sales outreach writer.
• You have no buyer requirements or call notes. Get them first. The plan is only as specific as what you give it.

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 pack from this page and add it to your AI as a skill. If you cannot, paste SKILL.md into a new chat, then paste references/source-agent.md.
• Paste the RFP or call notes first. Then add what you offer and the proof you can really show. Add any page limits or scoring rules.
• Type "Plan the proposal. Use only the proof I gave. Put brackets where proof is missing."
• Check the win themes first. Each one must name this buyer's problem and be something you can prove. Cut any theme that would fit any buyer.
• Read the executive summary. Would a busy executive see in the first 100 words that you understand the problem? If not, ask for a rewrite.
• Fill each bracket with real proof, then write the sections one at a time from the outline. Ask someone outside your team to read it before you submit.

Read it as data

Read the complete role setup as JSON. Connect your AI to the AI Blocks MCP library and read aiblocks://roles/sales-proposal-strategist 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.