Hire an AI sales engineer

Everything it can hand back

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

• Technical discovery questions for what you still do not know
• A demo plan that opens with the buyer's problem and shows the result first
• A proof of concept plan with a problem statement, pass marks, scope in and out, a short timeline and a decision gate
• A Fact, Impact, Act note for each rival, plus where you win, fight or lose
• A table that decodes technical doubts into what the buyer means and how to respond
• A list of facts to confirm and an honest list of what your product cannot do yet

How it does the job well

• You cannot run the product, open the buyer's systems or test a rival. Say which things you could not check. Label every step "to rehearse before use".
• Do not claim a customer result, benchmark or roadmap date the user did not give you.
• Do not negotiate price or contract terms. Say that is outside this role.
• 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: You have finished a discovery call and need to turn it into a demo that fits the buyer.

• Technical discovery. Questions for the gaps in what you know about the buyer's stack, security and scale.
• Demo plan. A story that opens with the buyer's problem, shows the result first and ends with proof.
• Proof of concept plan. One problem statement, pass marks, scope in and out, a short timeline and a decision gate.
• Competitive notes. Fact, Impact, Act for each rival, with where you win, fight or lose and honest questions.
• Doubt decoder. Each technical question matched to what the buyer probably means and how to answer it.
• Known limits. What your product does not do natively, and what customers do instead.

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 Elmer Wheeler and Neil Rackham would. This is a way of reviewing the work. It does not mean they wrote or endorse it.

Capabilities

• Fill the technical picture. It lists what you know about the buyer's stack, links to other tools, security needs and scale, and what is missing.
• Plan the questions. It writes discovery questions for the gaps, including honest ones that bring out needs where you are strong.
• Build the demo story. It restates the problem, shows the end result, explains how it works and ends with proof from a similar customer.
• Scope the proof of concept. It writes one problem statement, pass marks, what is out of scope, a short timeline and a go or no-go gate.
• Position against rivals. It gives a Fact, Impact, Act note per rival and sorts each criterion into win, fight or lose.
• Decode the doubts. It turns each technical question into what the buyer probably means and how to answer the real worry.
• List what is unproven. It names the facts and limits to confirm before you use any of it.

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-engineer 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-engineer/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 discovery notes on the buyer's problem, their systems and their technical team
• What your product does and the limits you know of
• The buyer's security, integration and scale needs, as far as you know them
• The rivals in the evaluation and what the buyer has said about them (optional)
• Any demo or test date and the people who will attend (optional)
• A customer story you can use as proof, with the figures you may share (optional)

Helpful context (optional)

• The buyer's security questionnaire or architecture notes.
• Names, roles and priorities of each technical person on their side.
• Notes from your last call, with the exact words the buyer used.

Tools and access

• Claude, ChatGPT or Gemini: They turn raw discovery notes into a demo story and a proof plan. You paste your notes in and check each step against your product.
• Your own demo or test environment: The AI cannot run your product. Rehearse every step there before the buyer sees it.

Functions and deliverables

• Sales engineer: Plan the technical side of a B2B sale with discovery questions, a demo story, a proof-of-concept scope with pass marks and answers to technical doubts.
  • Technical discovery questions for what you still do not know
  • A demo plan that opens with the buyer's problem and shows the result first
  • A proof of concept plan with a problem statement, pass marks, scope in and out, a short timeline and a decision gate
  • A Fact, Impact, Act note for each rival, plus where you win, fight or lose
  • A table that decodes technical doubts into what the buyer means and how to respond
  • A list of facts to confirm and an honest list of what your product cannot do yet
  Source: Michael Sitarzewski and Agency Agents contributors.
• Pre-sales proof of concept planner: Share buyer requirements and product details. Get coverage gaps, a competitor feature table and a trial plan.
  • A fit score from 0 to 100 percent
  • The count of must-have gaps
  • A bid, bid with a plan, or no bid call, with the reason
  • A feature table against each rival
  • A phased trial plan with success checks and a scorecard
  Source: Alireza Rezvani.
• Sales discovery question writer: Paste what you sell and a buyer's situation. Get the questions that make the cost of their problem clear.
  • Situation, problem, knock-on and worth questions in order
  • The three telling traps and what to ask instead
  • One close question that asks for a commitment
• Objection answer sheet writer: Turn the doubts buyers raise into an objection answer sheet. Each doubt gets a yes-question, an honest reply and proof you can show.
  • Each doubt sorted by kind
  • A yes-question, an honest agreement and a fact for each doubt
  • Proof you can show, and where it comes from
  • A list of doubts that still lack proof
• 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
• Elmer Wheeler: Improve a short sales line using Elmer Wheeler’s recorded approach. Lead with a real benefit, show it in action and test the wording.
  • Your problem worked on the way Elmer Wheeler would: their questions, their method, their push-back
  • The answer or the work, in Elmer Wheeler's voice, using their ideas by name
  • Anything that goes beyond their public record, marked
  • One suggested next step
• Neil Rackham: Plan complex sales questions using Neil Rackham’s SPIN approach. Find the buyer’s problem, explore its costs and let them describe a useful fix.
  • Your problem worked on the way Neil Rackham would: their questions, their method, their push-back
  • The answer or the work, in Neil Rackham'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

• You have finished a discovery call and need to turn it into a demo that fits the buyer.
• A buyer asks for a proof of concept and you want to keep it small, with clear pass marks.
• A technical evaluator asks a hard question and you want to know what they are really asking.
• A rival is in the evaluation and you need an honest, fact-based plan for each technical point.

Limits to check before starting

• You are negotiating price, discounts or contract terms. Use the Deal desk reviewer.
• You are answering a formal questionnaire or tender. Use the RFP response builder.
• You want a deal scored for risk. Use the Sales deal reviewer.
• You need a short demo script for a simple product with no technical evaluation. Use the Product demonstration script writer.
• You want it to run the demo or the test. It cannot access your product or the buyer's systems.

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 and add it to your AI as a skill. Or paste SKILL.md into a new chat, then paste references/source-agent.md after it.
• Paste your discovery notes, what your product does and any known limits. Say which job you want first, such as a demo plan or a proof of concept plan.
• Answer any question once. Anything you skip is marked MISSING. It will not invent a feature, a customer or a figure.
• Read the demo plan and compare it with what your product can really show. Cut anything you cannot show live.
• Agree the proof of concept pass marks with the buyer in writing before any set-up starts.
• Paste what happened after each demo or test and ask for the next step and the next set of questions.

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-engineer 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.