Sales role
AI Sales Engineer
An AI sales engineer that turns discovery notes into a tailored demo plan, a scoped proof of concept and battlecards that stick to facts.
Give it the discovery notes, the buyer’s requirements and your own product documentation, and it prepares the technical side of a deal: a demo plan that starts from the buyer’s problem, a proof of concept with written pass/fail criteria and a fixed scope, answers to the technical and security questions with sources from your docs, and competitive battlecards built from facts it can cite.
Things you could ask for
Written the way you would actually say them. The agent plans the steps itself.
- “Here are the discovery notes from the Contoso call. Map their three biggest pains to features in our docs and write a 30-minute demo plan that shows the outcome before the configuration.”
- “Scope a two-week proof of concept for Contoso: a one-sentence problem statement, success criteria with targets, what is in and out of scope, and a midpoint review.”
- “Answer the integration and security questions in this spreadsheet from our Confluence pages. Quote the page for every answer, and mark anything our docs do not cover as unanswered.”
- “Build a fact / impact / act battlecard against our two main competitors from their public docs and pricing pages, with a source for every fact.”
- “Their architect asked whether we support SSO. Read the thread and tell me what they are really worried about, then draft the reply.”
What you get back
Deal-ready technical material: evaluation notes on the buyer’s environment and decision makers, a demo storyline with the moment it should land, a POC plan with success criteria and a decision gate, sourced answers to technical questionnaires, and battlecards in Google Docs or Slides — each claim linked to your documentation or a public source.
Tools it works with
A role is a job description; connectors are what let it do the job on your real work instead of on whatever you paste into a chat.
Where it is the wrong tool
- It does not run demos or build environments. A remote agent has no shell and no access to your product’s admin console, so it prepares the plan, the script and the data story; a person drives the product.
- It answers from your documentation, never from memory. Security and compliance questions about certifications, data residency or encryption are answered only when a page you gave it says so; anything else is marked unanswered rather than guessed.
- Competitive facts are public facts. It reads competitors’ published docs, pricing and reviews through web search and cites them; it will not make a claim it cannot source, and it does not write FUD.
- It joins no calls and sends nothing. Replies to evaluators come back as drafts; transcripts can be pasted or uploaded, or read through the Fathom connector.
Starting an agent with this role
- 1Create a Burrak account — any plan works, and your first week is $1.
- 2In the Marketplace, open the Roles tab, find Sales Engineer and choose “Start an agent as Sales Engineer”. That creates a remote agent with the role’s instructions in its system prompt.
- 3Connect the tools it needs — Atlassian (Jira + Confluence), Notion, Google Docs, Google Slides, Tavily Web Search, Google Sheets — from Connectors.
- 4Give it a brief. It keeps working in the cloud after you close the tab, and you are only charged while it is actually working.
The Sales Engineer role, in practice
- Can it fill in a security questionnaire for us?
- It can draft one from your own documentation, with the source page quoted next to every answer and the gaps clearly marked. Someone who owns your security posture should still review it before it goes out, because a wrong “yes” on a questionnaire is a contractual problem, not a typo.
- Does it need access to our product?
- No. It works from what describes the product: your docs in Confluence, Notion or Google Docs, release notes and past proposals. That is also the right boundary, because those are what a buyer will hold you to.
- How is this different from the Proposal Strategist?
- The Proposal Strategist writes the response to an RFP: compliance matrix, win themes and the document itself. The Sales Engineer wins the technical evaluation around it: discovery, demo plan, proof of concept and the hard questions from the buyer’s engineers.
Capability reference
Summarised from the role’s instructions, which are adapted from the agency-agents collection (AgentLand Contributors), used under the MIT licence.
- Technical discovery that uncovers integration, security and scale requirements
- Demo plans that quantify the problem and show the outcome before the configuration
- Proof-of-concept scoping with written success criteria and a hard timeline
- Fact / impact / act competitive battlecards that win on substance
- Objection handling that answers the concern behind the question
Your AI assistant is waiting.
Put it to work today.
Put an agent on the work that never needed a human in the first place — the research, the reports, the follow-ups — and take the week back.
$1 for your first week · Cancel anytime · Works on Mac, Windows, iPhone, Android & Web