How should I title the features of my demo?

How to title your demo features

Feature titles in a Standard Personalization Demo are what viewers see when they rate features as Very / Somewhat / Not Important. Bad titles kill the personalization step — viewers either misrate features they don't understand, or skip the rating entirely. Good titles make the rating intuitive and produce signal you can use.

The two-rule framework

Rule 1: write for the buyer, not the engineer

Use the language your buyers use when they describe their problems — not the language you use internally about your product. "Track customer health in one dashboard" beats "Customer Success Suite." "Catch errors before they ship" beats "Static Analysis Engine."

Rule 2: title by outcome, not feature

Outcome-framed titles ("Reduce manual reporting time," "Surface at-risk accounts faster") help the buyer self-identify with the value. Feature-framed titles ("Reporting Module," "Health Score Algorithm") force the buyer to translate features into outcomes — which they often skip.

Examples

• Feature-framed (avoid) → Outcome-framed (use)
• "Reporting Module" → "Get exec-ready reports without IT"
• "Multi-tenant Architecture" → "Scale to thousands of customers without rebuilding"
• "Real-time Sync API" → "Keep your data in lockstep with our platform"

Tips

• Aim for 4-7 word titles. Long titles get truncated; short titles lack context.
• Use parallel structure — if one title starts with a verb, they all should. Consistency makes the rating page scannable.
• Use the optional Description field to add specifics that don't fit in the title (it appears on hover).
• Test with two prospects before committing. If they hesitate on a title, the title needs work.

Where to set feature titles

Feature titles are configured on Step 3 (Demo Content) of the Demo Wizard. See "How do I rename the features titles?" for the editing flow.