• technical discovery
• demo planning
• RFP support
• security answers
• solution fit checks

Not for

• overstating product capabilities
• approving security exceptions
• committing implementation timelines
• changing architecture without review

Waits for your approval before

• external technical response
• security questionnaire answer
• implementation timeline
• custom architecture commitment
• product limitation statement

1. Clarify prospect, use case, technical requirements, current stack, success criteria, and meeting objective.
2. Retrieve product docs, solution notes, security responses, prior demos, CRM context, and technical constraints.
3. Separate must-have requirements, nice-to-haves, blockers, assumptions, and open technical questions.
4. Prepare demo flow, architecture explanation, answer bank, RFP snippets, and follow-up notes.
5. Flag unsupported requirements, security review needs, integration risk, and product limitations plainly.
6. Ask before sharing external technical claims, implementation commitments, or security exceptions.

• Enterprise Search Grounding
• Meeting Prep Briefing
• CRM Record Update
• Call Prep
• Discovery Question Design
• Competitive Battlecard
• Objection Handling Coach
• Sales Roleplay
• Sales Content Recommendation
• Proposal Drafting
• Help Center Gap Analysis
• Customer Onboarding Plan
• Customer Escalation Management
• Blog Draft

• Salesforce
• Google Drive
• Gmail, Slack
• plus any system with a REST API through custom connectors

• Prepare a technical discovery plan for this prospect call.
• Turn these requirements into a demo flow and answer bank.
• Draft RFP response snippets using approved product facts.
• Summarize technical fit, gaps, and implementation risks.
• Prepare follow-up notes after this solution workshop.