Deliver sales enablement for product

Before you start

This use case works best when you've already set up some foundational elements in Quotient:

• Knowledge Store populated: Add your product overview, key value props, and competitive positioning so the Campaign Agent can align enablement with how you actually sell.
• Feature or product in scope: Have the feature name, key benefits, who it's for, and how it fits into the broader product. Screenshots or a short demo flow help.
• Audience for sales: Know who sales is selling to (e.g. CMO vs. developer, SMB vs. enterprise) so the one-pager and script match the conversation.

How to do it in Quotient

1. Start a conversation with the Campaign Agent

Open a new chat and describe the sales enablement you need. Include the product or feature, the buyer persona, and which assets you want. For example:

"We're rolling out our new analytics feature to the sales team. I need a one-pager they can leave with prospects, a short demo script that hits the 3 main benefits in 5 minutes, and 3–4 objection handlers for 'we already use X' and 'we don't have budget for this.' Include a quick competitive comparison so they know how we stack up."

2. The agent creates the deliverables

The Campaign Agent creates a campaign with tasks for each asset — one-pager, demo script, objection handlers, and optionally a battle card or competitive cheat sheet. It pulls from your Knowledge Store so messaging and positioning stay consistent with the rest of your go-to-market content.

3. Provide the details

Share specifics so the enablement is accurate and usable:

• "The demo should start with [key workflow] — that's what resonates most"
• "Our main competitor here is [X] — sales hears 'we're evaluating them' a lot. Give them a clear differentiator."
• "One-pager should be one side only, scannable. They use it in live meetings."
• "Include a link to the help doc and a short 'how to get a trial' CTA for the one-pager"

4. Review and distribute

Review the one-pager, script, and objection handlers. Share with product or sales leadership for a quick sign-off, then add to your enablement hub or sales playbook. Schedule a short training or office hours so reps know where to find the assets and how to use them.

What you'll get

A typical product sales enablement set includes:

• One-pager — one side, benefit-led summary with key points, differentiator, and a clear next step (demo, trial, doc)
• Demo script — short narrative and talking points for a 5–10 minute demo, with suggested flow and key messages
• Objection handlers — 3–5 common objections (competitor, budget, timing, "we're good") with concise responses and proof points
• Competitive talking points or battle card — how you compare on the features that matter for this product, and how to position when the prospect is evaluating others

Tips for better results

• Keep the one-pager to one page. Sales won't use two-pagers in meetings. Ask the agent to prioritize the 3–5 points that close deals.
• Script = talking points, not a script. Reps don't read word-for-word. Ask for bullets and transitions, not a paragraph script.
• Use real objections. Share the top 3–5 objections your sales team actually hears. Generic ones are less useful.
• Update when the product changes. When you ship a related feature or change positioning, come back and ask the agent to refresh the one-pager and script.
• Tie to the deal. If you have a specific segment (e.g. enterprise vs. mid-market), ask for slightly different one-pagers or script variants so sales can match the room.