Kimmy's Skills

Atlas 2.0 — the field is the product — Presentation Requirements

Source: ../product-launch.html · Type: Product launch · Audience: Customers, partners, and press · Mode: Live demo + Q&A · Time: 8 min + 5 Q&A Fictional case. The deck is the current implementation; this file captures the brief, structure, and acceptance.

1. Audience and intent

Customers, partners, and press; 8 minutes plus Q&A.

Intent: Join the launch cohort or book a demo.

Decision or action: Sign up for the cohort or book a demo.

Success: The audience can state the offline-first value and the single CTA.

2. Narrative

Problem → insight → demo → value → evidence → availability → CTA → close.

Slide sequence

#	Slide	Budget	Purpose / speaker cue
1	Atlas 2.0 — the field is the product	1	Open with the promise: offline-first field service.
2	The problem	1	One number per stat.
3	The insight	1	The insight is the architecture: local-first, sync later.
4	Demo — three scenes	3	Golden path only.
5	Value	1	Pilot results, not promises.
6	Customer evidence	1	Let the quote do the work.
7	Availability	1	Price is a slide, not a secret.
8	CTA	1	One CTA.
9	Close	1	End on the line.

3. Evidence and fact-check

Pilot results: 3 customers, 240 techs, 8 weeks. Fictional; label the sample and replace before use.

Fact-check gate: confirm names, numbers, dates, and comparisons before layout. A precise number without a date and source is a liability.

4. Language and delivery

Spoken, energetic, concrete; no feature list; one CTA.

5. Visual and accessibility

Bright, coral/blue; product mockups; one demo path; captions for the demo. Cover uses a field technician with a tablet, not a laboratory photograph.

6. Time and structure

8 minutes plus 5 Q&A. Must-cut: pricing detail; protect the demo, value, and CTA. (total budget: 11 minutes)

Q&A: prepare the ten most likely questions and one honest answer for each. Do not improvise a fact.

7. Verification

• Titles-only read: read the slide titles in order. The argument must hold without the body.
• Timed run: rehearse to a hard stop, record it, and cut from the must-cut list.
• Evidence: every number and comparison has a source, date, and range where relevant.
• Visual: check at presentation size, in grayscale, and in the exported file.
• Accessibility: alt text, reading order, contrast, color-not-alone, reduced motion, captions/transcript.
• Print: one slide per page, notes hidden, no clipped content.
• Run the demo with the network off; time the demo; check the CTA appears once.

8. Non-goals and open questions

Risks: Demo failure; feature tour; multiple CTAs.

Open: Replace fictional pilot data; prepare a fallback recording; confirm pricing and legal review.

This site is open source. Improve this page.