{ "schema": "aiblocks-page/1", "id": "agency-sales-engineer", "type": "agent", "name": "Sales engineer", "summary": "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.", "headline": "Sales engineer", "subhead": "Paste your discovery notes on a deal, what your product does and any rivals. It plans the technical questions to ask, builds a demo that starts with the buyer's problem, scopes a proof of concept with pass marks agreed in advance, and decodes the technical doubts you will hear.", "job": { "id": "sell-and-negotiate", "name": "Sell and negotiate" }, "level": "intermediate", "thinking": "high", "tested": true, "updated": "2026-11-03", "first_published": "2026-10-26", "inputs": [ { "type": "question", "required": true, "label": "Question", "what": "the problem, decision or piece of work you want help with, and what a good outcome looks like" }, { "type": "source_text", "required": false, "label": "Source text", "what": "a long source in full: an article, a video or talk transcript, or notes from a book, with its title, author and link" } ], "outputs": [ { "type": "plan", "required": true, "label": "Plan", "what": "a dated plan: what to do, in what order, with a decision rule for each step" } ], "you_give": [ "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)" ], "you_get": [ "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" ], "use_when": [ "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." ], "skip_when": [ "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." ], "output_sample": { "input": [ "Your discovery notes on the buyer's problem, systems and technical team", "What your product does, and its known limits", "The rivals in the evaluation (optional)", "A customer story and figures you may share (optional)" ], "prerequisites": [ "An AI chat such as Claude, ChatGPT or Gemini", "Access to your product, so you can check that every demo step works" ], "output": [ { "name": "Technical discovery", "contains": "Questions for the gaps in what you know about the buyer's stack, security and scale." }, { "name": "Demo plan", "contains": "A story that opens with the buyer's problem, shows the result first and ends with proof." }, { "name": "Proof of concept plan", "contains": "One problem statement, pass marks, scope in and out, a short timeline and a decision gate." }, { "name": "Competitive notes", "contains": "Fact, Impact, Act for each rival, with where you win, fight or lose and honest questions." }, { "name": "Doubt decoder", "contains": "Each technical question matched to what the buyer probably means and how to answer it." }, { "name": "Known limits", "contains": "What your product does not do natively, and what customers do instead." }, { "name": "Still to check", "contains": "Facts and claims to confirm before you use them with the buyer." } ] }, "output_shape": "BRIEF AND ASSUMPTIONS\n | buyer's problem | technical team | ASSUMED: | MISSING: \n\nTECHNICAL DISCOVERY\n | known | questions to ask | why it matters\n\nDEMO PLAN\n audience | problem restated | outcome to show first | how it works | proof | aha moment target | backup deep-dive path\n\nPROOF OF CONCEPT PLAN\n problem statement | pass marks | in scope | out of scope | timeline | decision gate \n\nCOMPETITIVE NOTES\n | Fact | Impact | Act | zone | landmine question \n\nDOUBT DECODER\n | | \n\nKNOWN LIMITS\n | what customers do instead | on the roadmap \n\nSTILL TO CHECK\n | who confirms it", "how_to_use": [ "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." ], "checks": [ "The result addresses your actual task and cites the evidence used.", "Examples, role-play experience and targets are kept separate from verified results.", "Claims of tests, memory, tool access or completed actions match what actually happened." ], "next": [ { "name": "Negotiation prep planner for the weaker side", "url": "https://useaiblocks.com/skills/weak-position-negotiation", "why": "Sell it" } ], "source": { "by": "Michael Sitarzewski and Agency Agents contributors", "repo": "msitarzewski/agency-agents", "url": "https://github.com/msitarzewski/agency-agents/blob/b37b5bb33b78f2c1d6567d98e25ca818e3259219/sales/sales-engineer.md", "licence": "MIT", "original_name": "Sales Engineer", "commit": "b37b5bb33b78f2c1d6567d98e25ca818e3259219" }, "credits": [ { "title": "Sales Engineer", "by": "Michael Sitarzewski and Agency Agents contributors", "url": "https://github.com/msitarzewski/agency-agents/blob/b37b5bb33b78f2c1d6567d98e25ca818e3259219/sales/sales-engineer.md", "used": "Original agent profile, preserved in references/source-agent.md; AI Blocks adds setup and review instructions." } ], "files": [ "LICENSE", "references/source-agent.md", "SETUP.md", "source.json" ], "links": { "page": "https://useaiblocks.com/agents/agency-sales-engineer", "markdown": "https://useaiblocks.com/agents/agency-sales-engineer.md", "json": "https://useaiblocks.com/agents/agency-sales-engineer.json", "instructions": "https://useaiblocks.com/skills/agency-sales-engineer/SKILL.md", "download": "https://useaiblocks.com/skills/agency-sales-engineer.zip", "api_item": "https://useaiblocks.com/api/v1/items/agency-sales-engineer", "api_document": "https://useaiblocks.com/api/v1/documents/agent/agency-sales-engineer", "mcp": "https://useaiblocks.com/mcp" } }