Kinetic UI Teardown Call Script: A 15‑Minute Demo That Doesn’t Pitch

This post is adapted from our internal demo script. We originally framed it around a paid pilot, but right now we’re using a simpler motion:

• diagnose the “UI tax”
• show the concept (tokens + foundation components)
• invite the person to shape the early access build

Goal

Get the buyer to say:

“Yes, this solves our UI consistency tax—and I want to be involved early.”

Setup (before the call)

• Pick one representative UI change to anchor the conversation (button styles across product, form consistency, spacing/typography drift).
• Have one simple visual ready (even a screenshot) that illustrates “token change cascades consistently.”

Agenda (15 minutes)

1. Problem + baseline (3 min)
2. Teardown + ‘aha’ demo (7 min)
3. How it works + next step (5 min)

1) Problem + baseline (3 min)

Prompts:

• “Where does UI inconsistency slow you down today?”
• “What’s a recent UI change that took longer than it should have?”

Listen for:

• PR churn
• re-building components
• drift between design and implementation
• onboarding pain

2) Teardown + ‘aha’ demo (7 min)

Show (conceptually):

• tokens defined once (color/type/spacing/radius)
• a spine component (Button/Input/Card) consuming tokens
• how a single token change cascades consistently
• how usage rules prevent drift

Narration:

• “The goal is that engineers stop making one‑off UI decisions in every PR.”
• “You get a small, standardized foundation you can expand later.”

3) How it works + next step (5 min)

Explain the early access motion:

• confirm target surfaces + the most expensive drift
• define minimal token set
• ship the first foundation components
• document usage rules + upgrade guidance

Close with a question:

• “If we built this baseline for your stack, would you want early access and founder pricing?”

If yes:

• confirm email (founder pricing cohort)
• capture one success metric they care about

If no:

• capture “why not” and classify:
  • timing, budget, buyer mismatch, unclear outcome, already solved, prefer DIY