Sales Engineer
Structure a time-boxed product demo with checklist, attendee map, and agenda so a solo founder can run a credible technical evaluation call.
Overview
Sales Engineer is an agent skill most often used in Validate (also Grow lifecycle) that produces a structured demo script with checklist, attendee roles, and timed agenda for technical sales calls.
Install
npx skills add https://github.com/alirezarezvani/claude-skills --skill sales-engineerWhat is this skill?
- Pre-demo checklist covering environment, data, integrations, and backup slides
- Attendee table with roles (decision maker, champion, technical evaluator, end user)
- Timed agenda splitting AE welcome, SE core demo, integration segment, and admin
- Demo metadata block for customer, environment URL, duration, and presenters
- Use-case-led core demo segment placeholder (Use Cases 1–3)
- Pre-demo checklist with 10+ verification items
- Agenda segments for welcome, core demo, integration, and admin blocks
Adoption & trust: 668 installs on skills.sh; 17.5k GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You are about to demo your product to buyers and technical evaluators but lack a runbook, so one broken integration or missing stakeholder derails the call.
Who is it for?
Founder-led SaaS teams running their first repeatable enterprise-style demos with separate AE and technical voices.
Skip if: Pure self-serve products with no live demos, or teams that already maintain a full sales playbook in a CRM workflow.
When should I use this skill?
User needs a demo script, pre-demo checklist, attendee role table, or timed agenda for a customer technical evaluation.
What do I get? / Deliverables
You get a filled demo script with pre-demo checks, role-aware attendee notes, and a timed agenda so AE and technical presenter stay aligned through core and integration segments.
- Completed demo information and metadata table
- Checked pre-demo readiness list
- Minute-by-minute agenda with segment owners
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Early customer demos sit on Validate because they prove fit and scope before you scale GTM—this template is the shelf for planning that proof session. Scope subphase covers defining what you will show, to whom, and in what order when a prospect is still deciding whether to buy or build.
Where it fits
Define which three use cases and integrations you will show before committing to a pilot scope.
Align demo length and depth with economic buyer attendance before quoting tiers.
Reuse the script for expansion demos when new technical evaluators join an existing account.
How it compares
A demo-runbook template skill, not a CRM integration or automated outbound sequencer.
Common Questions / FAQ
Who is sales-engineer for?
Solo founders and small teams who play both seller and technical demonstrator and need a professional demo script without hiring a dedicated sales engineer.
When should I use sales-engineer?
During Validate when scoping a prospect demo, and in Grow lifecycle when onboarding champions—any time you need checklist, attendees, and a timed agenda before a live evaluation.
Is sales-engineer safe to install?
It is documentation and template content without mandatory external calls; review the Security Audits panel on this Prism page if the skill bundle is pulled from a third-party skills repo.
SKILL.md
READMESKILL.md - Sales Engineer
# Demo Script Template ## Demo Information | Field | Value | |-------|-------| | Customer | [Customer Name] | | Date/Time | [Date and Time] | | Duration | [XX minutes] | | Demo Environment | [Environment URL/Details] | | Presenter | [Sales Engineer Name] | | AE/Account Executive | [AE Name] | --- ## Pre-Demo Checklist - [ ] Demo environment tested and confirmed working - [ ] Sample data loaded and validated - [ ] Backup demo environment prepared - [ ] Screen sharing tested with correct resolution - [ ] Browser tabs pre-loaded with key screens - [ ] Recording setup confirmed (if applicable) - [ ] Customer-specific branding applied (if applicable) - [ ] Network and VPN connectivity verified - [ ] All integrations connected and tested - [ ] Backup slides prepared in case of technical issues --- ## Attendees and Roles | Name | Title | Role in Evaluation | Key Interest | |------|-------|-------------------|--------------| | [Name] | [CTO/VP Eng] | Decision Maker | ROI, strategic fit | | [Name] | [Director] | Champion | Solving [specific problem] | | [Name] | [Manager] | Technical Evaluator | Architecture, integrations | | [Name] | [Analyst] | End User | Day-to-day usability | --- ## Agenda | Time | Duration | Topic | Lead | |------|----------|-------|------| | 0:00 | 5 min | Welcome and introductions | AE | | 0:05 | 5 min | Agenda and objectives | SE | | 0:10 | 20 min | Core demo (Use Cases 1-3) | SE | | 0:30 | 10 min | Integration demo | SE | | 0:40 | 5 min | Admin and security overview | SE | | 0:45 | 10 min | Q&A | SE + AE | | 0:55 | 5 min | Next steps and wrap-up | AE | --- ## Demo Flow ### Opening (5 minutes) **Talking Points:** - Thank attendees for their time - Recap what we learned in discovery: "[Summarize 2-3 key challenges]" - Set expectations: "Today I'll show you how we address [Challenge 1], [Challenge 2], and [Challenge 3]" - Frame the demo: "I'll be using [data type] similar to what you described in our earlier conversations" **Transition:** "Let me start with the challenge you mentioned is most pressing: [Challenge 1]." --- ### Use Case 1: [Name] (7 minutes) **Business Context:** [1-2 sentences on why this matters to the customer] **Demo Steps:** 1. **Step 1:** [Navigate to / Click on / Show...] - **What to say:** "[Explain what they're seeing and why it matters]" - **Highlight:** [Specific feature or capability to emphasize] 2. **Step 2:** [Navigate to / Click on / Show...] - **What to say:** "[Connect this to their specific pain point]" - **Highlight:** [Differentiator from competitor] 3. **Step 3:** [Navigate to / Click on / Show...] - **What to say:** "[Quantify the value - time saved, errors reduced, etc.]" - **Highlight:** [Ease of use or power of the feature] **Key Message:** "[One sentence summarizing the value demonstrated]" **Transition:** "Now that you've seen how we handle [Use Case 1], let me show you [Use Case 2]." --- ### Use Case 2: [Name] (7 minutes) **Business Context:** [1-2 sentences on why this matters to the customer] **Demo Steps:** 1. **Step 1:** [Navigate to / Click on / Show...] - **What to say:** "[Explanation]" - **Highlight:** [Key capability] 2. **Step 2:** [Navigate to / Click on / Show...] - **What to say:** "[Explanation]" - **Highlight:** [Key capability] 3. **Step 3:** [Navigate to / Click on / Show...] - **What to say:** "[Explanation]" - **Highlight:** [Key capability] **Key Message:** "[One sentence summarizing the value demonstrated]" **Transition:** "[Transition statement to next section]" --- ### Use Case 3: [Name] (6 minutes) **Business Context:** [1-2 sentences on why this matters to the customer] **Demo Steps:** 1. **Step 1:** [Description] - **What to say:** "[Explanation]" - **Highlight:** [Key capability] 2. **Step 2:** [Description] - **What to say:** "[Explanation]" - **Highlight:** [Key capability] **Key Message:** "[One sentence summarizing the value demonstrated]" --- ### In