CRAFT Content report
Sales Enablement Content: your result
This answer uses a made-up example company. Change the details above and press Run to see your own result.
Sales Enablement Content
For product marketing and sales enablement leads. The decision: what should sellers say at this stage of the deal?
Give it your product, the buyer your sellers pitch to and your proof points, and get value propositions, a pitch script for your sales stage, objection handlers and competitive responses.
This sample is a made up example, built from the inputs behind Fill in an example. It shows part of one section of the answer.
1. Resolve tickets end to end
2. Human approval for refunds
See the full example answer or run it with your own details.
CRAFT Content report
This answer uses a made-up example company. Change the details above and press Run to see your own result.
When a tool is not enough: if the decision needs more than one answer, talk it through in a call. Book 45 minutes with Shashwat.
What next? Work with Shashwat Try another tool See all 85 tools and skills
Generated on 2 November 2026 from this branch, with the inputs behind Fill in an example. Your own inputs give a different result.
CRAFT Content report
NOTE: You didn't provide objections and no sector could be read from your inputs, so no objection handlers are written (a generic list would be invented). Add common objections, or name the industry, to get them.
Sector: not clear from your inputs (name the industry for sector notes, or choose your sector). Business model: not stated. Tell us how you charge and the plan will adjust.
Billing dependent steps are conditional: trials, seats and recurring renewals require a subscription; a statement of work requires a services contract; site or link commitments require connectivity billing. Confirm the applicable choice before using those steps.
| Element | Detail |
|---|---|
| Product | our product |
| Persona | VPs of Customer Support at consumer apps |
| Price Position | Price position unknown |
| Sales Stage | discovery |
| Note | Objections suggested: replace them with the ones you hear |
1. Resolve tickets end to end
2. Human approval for refunds
Discovery Call Structure:
Opening (2 min):
"Thanks for taking the time. Before I tell you about our product, I'd love to understand your situation. Tell me how your team handles this today..."
Questions (15 min):
Focus on understanding their:
Bridge (3 min):
"Based on what you've shared, here's how our product could help: resolve tickets end to end and human approval for refunds."
Next Step:
"Would it be helpful to see a demo focused on the pain you described?"
No objection handlers: see the note at the top.
No competitor-specific objections provided. Add competitor objections parameter for battle cards.
Value Framework:
| Value | Proof you can cite |
|---|---|
| Resolve tickets end to end | 45% of tickets resolved without a human at a food delivery company |
| Human approval for refunds | 45% of tickets resolved without a human at a food delivery company |
Investment: Price position unknown. Supply the approved price position before using a pricing claim.
ROI Conversation:
"Let me share what customers have seen:
Based on what you've shared about your situation, here's what that could mean for you:" then work it out from the prospect's own figures, which this kit does not have.
If Price Pushback:
"I understand budget is a consideration. Let me ask: what does it cost you each month to leave this problem as it is?
Resolve tickets end to end: put it in the prospect's own numbers. For a company your size, work out the saving from their figures, not from ours."
Subject: our product next steps
Hi,
Thanks for sharing how your team handles this today.
Based on what you described, here's what stands out (fill these in from your call notes):
our product addresses this: resolve tickets end to end.
Relevant proof: 45% of tickets resolved without a human at a food delivery company
Next step: name the specific action and the date.
When works for you?
Subject: our product demo follow-up + next steps
Hi,
Great connecting today. Here's a quick recap:
What we covered:
What resonated: the moment they engaged (from your notes).
Your questions: the answers to the questions they raised.
Next step: the specific action and date.
Resources: the relevant case study and the one-pager.
Talk soon,
Before every discovery call:
Generated for VPs of Customer Support at consumer apps at discovery stage
Suggested timings, lengths and counts: adjust them to your own.
When a tool is not enough: if the decision needs more than one answer, talk it through in a call. Book 45 minutes with Shashwat.
The tool builds a Quick Reference Card, Value Propositions in pitch order paired with your proof points, a timed Pitch Script by Stage, Objection Handlers, Competitive Responses, Price Justification, Discovery Questions, and Follow-Up Templates. It only writes objection handlers when you supply objections or a sector, and it separates customer results from vendor claims under Quick Stats to Quote. Read Price Justification carefully: it does not invent ROI math and requires you to plug in the buyer's own baseline cost and expected saving during the call.
Re-run the tool whenever you target a new buyer persona, move into a different sales stage (Discovery, Demo, Proposal, or Negotiation), or collect a new customer proof point or objection from call reviews. The tool applies the same fixed rules every time. It does not call an AI model, and this site does not keep what you enter.
Add CRAFT Content once (see Use it in Claude, ChatGPT or Gemini), then ask in plain words. Here is a prompt built from the tested example:
My role is not stated. Ask me for my role first. Use CRAFT Content's Sales Enablement Content tool. product: our product; target persona: VPs of Customer Support at consumer apps; proof points: 45% of tickets resolved without a human at a food delivery company, Live in two weeks; value props: Resolve tickets end to end, Human approval for refunds; sales stage: Discovery. If this tool is unavailable, ask me to open its web page; do not invent its output. In Gemini CLI or Antigravity, use the Helix GTM Suite skills package for related guidance, without claiming to run this connector.
You do not need to sign in. A web browser is enough, and the answer comes back in a second or two.
It applies fixed rules in the CRAFT Content code to the inputs above and returns text. It does not call an AI model, does not look anything up, and does not store what you type. The web form and the AI assistant connector run the same tool code, so the same input gives the same answer in both.
MCP tool name: sales_enablement_content. REST: POST https://craft-content.gtmhelix.com/api/tools/sales_enablement_content with this JSON body (see How it works):
{
"input": {
"product": "our product",
"target_persona": "VPs of Customer Support at consumer apps",
"proof_points": "45% of tickets resolved without a human at a food delivery company, Live in two weeks",
"value_props": "Resolve tickets end to end, Human approval for refunds",
"sales_stage": "discovery"
}
}
Run a Helix tool in your browser, then take the result to ChatGPT, Claude or Gemini. Connectors work with supported plans in Claude, ChatGPT, Cursor, VS Code and Windsurf. The Helix GTM Suite skills package supports Claude Code, Gemini CLI, Antigravity, Cursor and VS Code, and is available through skills.sh. Each plugin has its own installation steps, below or on its own page.
Connector setup guides · Skills package setup guide · Find the skills on skills.sh