---
type: source-summary
title: 'Source: The 90-Second Pitch / Elevator Pitch (live demo /read/ track)'
modified: 2026-04-07
tags:
  - elevator-pitch
  - read-track
  - value-first
  - 4-beat
  - source
  - live-site
---

# Source: The 90-Second Pitch / Elevator Pitch (live demo /read/ track)

## What this source is

A **90-second, 4-beat delivery script** hosted in the `/read/` track of the Demo Hub at `demo.kstratmdconsulting.com`. Described in the source as *"A script anyone can deliver from memory"*. Companion to [[sources/read-talking-points|Leadership Talking Points]] — both are in the Demo Hub Read track, both are value-first by construction, and they share several canonical claims.

The structure is a timed 4-beat Problem → Solution → Proof → Ask script plus a short "Delivery Tips" coda with stage directions.

| Beat | Duration | Purpose |
|---|---|---|
| 1. The Problem | 20 seconds | Historical context + market pressure |
| 2. The Solution | 25 seconds | What SuiteCentral 2.0 is and why it's different |
| 3. The Proof | 25 seconds | Production evidence |
| 4. The Ask | 20 seconds | The 30-day evaluation request |

Unlike the Talking Points (which is a reference sheet an exec keeps in front of them), the Elevator Pitch is intended to be **memorized and delivered verbally**. The Delivery Tips reinforce this: *"Speak naturally, not from a script. Internalize the four beats, then use your own words."*

## Key claims

1. **Historical baseline (NEW)**: *"Three years ago our problem was manual mapping, with about 15 hours of labor per integration."* → [[pages/entities/squire]] — adds a concrete "before" state for Squire's integration work: ~15 labor-hours per integration circa 2023.
2. **Market pressure (NEW)**: *"Today the problem is survival. Oracle and Microsoft are shipping native AI + MCP capabilities, and last week's 'Something Big is Happening' narrative made this a board-level concern."* → [[pages/entities/squire]] and [[pages/concepts/suitecentral-2-overview]] — frames the market urgency as existential (survival) and mentions a recent board-level event ("Something Big is Happening").
3. **Commoditization risk (NEW)**: *"If we remain a services-heavy connector model, we get commoditized on both speed and value."* → [[pages/entities/squire]] — identifies the specific failure mode the adoption case is defending against: commoditization of Squire's services-heavy model.
4. **Product positioning (confirms Talking Points claim 2)**: *"SuiteCentral 2.0 is a governed AI integration layer."* → [[pages/concepts/suitecentral-2-overview]] — second-source confirmation of the "governance layer" framing.
5. **Four-capability specificity (NEW)**: *"It doesn't just map fields — it explains why, scores its confidence, detects hallucinations, and requires human approval before any change goes live."* → [[pages/concepts/suitecentral-2-overview]] — four concrete capability claims: (a) reasoning explanation, (b) confidence scoring, (c) hallucination detection, (d) human-approval gate. These are specific enough to verify against technical sources later.
6. **Dual-ERP support (confirms Talking Points)**: *"It works across NetSuite and Business Central."* → [[pages/concepts/suitecentral-2-overview]] — second-source.
7. **Production proof (confirms Talking Points vintage)**: *"9,207/9,237 tests passed with 34 intentionally skipped, and 404 of 404 suites passed. Six production connectors."* → [[pages/concepts/production-proof]] — second-source confirmation that the Talking Points vintage numbers are consistent across the two Read-track sources.
8. **Reasoning traces persisted (NEW)**: *"Reasoning traces persisted to database."* → [[pages/concepts/suitecentral-2-overview]] and (future) a dedicated reasoning-traces page — this is an ARCHITECTURAL claim, not just a feature claim. The AI's reasoning is written to durable storage.
9. **SOC 2 Trust Services Criteria (NEW specificity)**: *"A compliance dashboard mapped to SOC 2 Trust Services Criteria."* → this is a FRAMEWORK-specific claim, not a generic "SOC 2 mapping." TSC is the specific SOC 2 control framework (Security, Availability, Processing Integrity, Confidentiality, Privacy). → updates [[pages/role-briefs/cto]] and promotes the earlier CTO role brief's single-source SOC 2 claim to two-source.
10. **Oracle comparison page exists**: *"An Oracle comparison page showing where SuiteCentral emphasizes governance and auditability."* → [[pages/entities/demo-site]] — this is referenced in the demo site's Path C structure and is now known to exist. Future ingest candidate.
11. **"This isn't a pitch deck — it's production code"**: the delivery-stage direction calls this out as a key credibility-moment line. → quote-worthy for any value-forward page.
12. **30-day evaluation timeline (confirms Talking Points)**: Week 1 demo review → Week 2 technical deep-dive → Week 3 pilot client selection → Week 4 decision checkpoint. → [[pages/concepts/pilot-30-60-90]] — second-source confirmation.
13. **Squire production deployment status (NEW — important)**: *"SuiteCentral 2.0 is production-ready, but **not yet deployed in Squire production**, and ready for a controlled pilot."* → [[pages/entities/squire]] — explicit confirmation that Squire is NOT currently running SuiteCentral 2.0. They presumably still run SuiteCentral 1.0.
14. **SuiteCentral 1.0 is the existing baseline**: *"The goal is to decide whether Squire should sponsor that pilot built on **the credibility of SuiteCentral 1.0**."* → [[pages/entities/squire]] — SuiteCentral 1.0 is Squire's current state and is the credibility foundation the 2.0 pilot builds on. This is the first formally-ingested confirmation of SuiteCentral 1.0's existence and role.

## Pages updated by this ingest

**Created** (0 new pages): all claims land on pages that already exist after the Talking Points ingest.

**Updated** (5 existing pages):
- [[pages/concepts/suitecentral-2-overview]] — added four-capability specificity, "not just map fields" framing, reasoning-traces-persisted architectural claim
- [[pages/concepts/production-proof]] — second-source confirmation of Talking Points vintage
- [[pages/entities/squire]] — added historical baseline (~15 labor-hours per integration circa 2023), market pressure framing (survival, board-level concern, commoditization risk), explicit statement that Squire does NOT run SuiteCentral 2.0 yet, and recognition of SuiteCentral 1.0 as the current baseline
- [[pages/concepts/pilot-30-60-90]] — second-source confirmation of 30-day evaluation phase
- [[pages/role-briefs/cto]] — promoted the SOC 2 mapping claim from single-source to two-source, with "Trust Services Criteria" framework specificity

## Notable quotes

> "Three years ago our problem was manual mapping, with about 15 hours of labor per integration. Today the problem is survival."
> — Beat 1, The Problem

> "It doesn't just map fields — it explains why, scores its confidence, detects hallucinations, and requires human approval before any change goes live."
> — Beat 2, The Solution

> "This isn't a pitch deck — it's production code."
> — Beat 3, The Proof (stage direction: *"Make eye contact during this line. Credibility lives in delivery, not slides."*)

> "SuiteCentral 2.0 is production-ready, but not yet deployed in Squire production, and ready for a controlled pilot."
> — Beat 4, The Ask

## Cross-references / contradictions found

- **Two-source confirmation of Talking Points vintage test counts**: the 9,207/9,237 / 404/404 / 30-skipped numbers now appear in two independent sources in the Demo Hub Read track. Both sources are in the same vintage, so this is not a contradiction — it confirms that the Read track was updated as a set.
- **"Last week's 'Something Big is Happening' narrative"**: cryptic reference to an unnamed recent event that elevated AI integration to board-level concern at Squire. Not elaborated in this source. Possibly refers to a specific Oracle/Microsoft announcement, an analyst report, or a Squire internal event. Flagged as an open question — a deeper-ingest source may name it.
- **"Three years ago" = circa 2023**: the "three years ago our problem was manual mapping with 15 hours per integration" framing places the starting baseline at ~2023 (relative to the 2026-dated source). This gives the adoption case a concrete temporal arc: 2023 = manual mapping → 2026 = AI-assisted integration is common → SuiteCentral 2.0 must ship now.
- **Squire does NOT run SuiteCentral 2.0** (explicit confirmation): the earlier sources in the corpus were ambiguous about this. Elevator Pitch Beat 4 resolves it — SuiteCentral 2.0 is production-ready code but not deployed in Squire production. Squire runs SuiteCentral 1.0. The pilot is about moving Squire from 1.0 to 2.0. This is a significant clarification of the adoption case.
- **SuiteCentral 1.0 as credibility anchor**: the ask is framed as *"built on the credibility of SuiteCentral 1.0"* — meaning SC 1.0 is already in production at Squire and has proven itself enough that 2.0 can piggyback on its reputation. First formally-ingested mention of SC 1.0 as the current baseline.

## Notes

- The Elevator Pitch is structurally the **tightest value-first** source in the corpus: Problem → Solution → Proof → Ask in 90 seconds. When writing the synthesis page or refreshing the curated indexes, this 4-beat pattern is a good template.
- The Delivery Tips section is NOT content claims — it's stage direction for a speaker. I did not treat it as claims in this ingest.
- The phrase "Something Big is Happening" is capitalized and quoted in the source, suggesting it refers to a specific named event or analyst narrative. Worth tracking — may surface in a competitive-evidence source.
- The "three years ago / 15 hours per integration" data point is the first pre-2.0 baseline in the corpus. It gives the adoption case a "before" state to compare to.