Skill 1
POC intake safety check
Use when raw opportunity notes, buyer goals, data needs, integration asks, or demo requests need screening before AI-assisted POC planning starts.
Back to Skill Library
Presales workflow library
Sales Engineer proof of concept readiness
Qualify POC requests, protect SE capacity, select the right demo environment, and define success criteria before work starts.
This is a complete workflow library with 6 individual skills. Download the full library or pick the specific skill folder your team needs first.
Individual skills in this library
Use one skill at a time, or keep the full workflow together.
Some AI tools expect one skill folder per upload. Download the full library when you want the whole workflow, or download an individual skill when you only need one job done.
Skill 2
Scoping the proof of concept
Use when POC scope, exclusions, participants, data boundaries, environments, and success criteria must be defined before work starts.
Skill 3
POC success criteria builder
Use when vague POC goals need to become measurable pass, partial-pass, fail, or blocked criteria with owners and evidence requirements.
Skill 4
POC pitch narrative and deck outline
Use when an SE or AE needs to explain the POC internally or to the buyer using a clear, accurate, on-brand story.
Skill 5
Technical risk and dependency register
Use when technical details, integrations, data requirements, environments, or blockers could affect POC feasibility or customer expectations.
Skill 6
POC closeout and CRM-safe recap
Use when POC outcomes, decision status, next steps, blockers, and CRM-safe notes must be summarized after execution.
Security fit check
Is the public Sales Engineer proof of concept readiness library enough, or does this need deeper review?
Use the public library when the workflow is low-risk, the inputs are already sanitized, and a team member can review the output before it reaches a buyer or customer.
Do deeper review when this workflow touches real tools, data sources, role ownership, approval paths, or customer-facing output.
Presales proofSales EngineerAccount ExecutiveSolutions Leader
Good deeper-review trigger signals
- The workflow touches customer, prospect, CRM, proposal, security, pricing, or campaign data.
- Different teams disagree on the approved source of truth.
- The AI output could become customer-facing, revenue-impacting, or compliance-sensitive.
- You need reusable eval checks before asking more people to use the workflow.