← Back to the simulator

How to use the WIT Simulator

An operational guide for live demos, follow-up links, and team use


What this is

The WIT Simulator is the most concentrated form of Wellscend's pitch. In about ten minutes, with no audio, no clinical jargon, and no slide deck, it shows a sophisticated viewer what KNDRA becomes when WIT has had time to learn a person. The simulator is not a product preview — it is a narrative instrument. Used well, it does work no spoken pitch can do.

The artefact contains two case studies (Layla and Hamid) and three demonstration modes (Timeline, Side-by-Side, Cascade Map). The combinations adapt to different audiences without any backend changes.


The narrative spine

The thing every audience needs to absorb, in this order:

  1. The system speaks only when calibration warrants. Day 1 is intentionally quiet. WIT does not pretend to know a member it has not yet learned. This is the discipline pitch.
  2. The intelligence compounds visibly with time. From Day 90 to Day 365 to Day 1095, KNDRA's understanding deepens, the WIG fills in, and the WIT outputs activate. This is the moat pitch.
  3. Every prediction is falsifiable. The calibration scorecard logs every claim and scores it against actual outcomes. This is the AI-as-utility-not-hype pitch — Abu Dhabi's exact language.

If a viewer walks away with only those three points, the demo has done its job.


Three modes, three different stories

Timeline is the default. Use it for the first encounter with any audience. It tells the complete arc of one person over time and lets the viewer feel the system's discipline at Day 1 and its depth at Day 1095. Allow at least four minutes for this mode.

Side-by-Side is the contrast moment. Use it once a viewer has felt the timeline and is ready for the punchline. Day 1 silence on the left, Day 1095 depth on the right, and the three-number summary at the bottom (8 of 8 layers, 3 of 3 outputs, calibrated predictions logged) is the asset pitch. This is the mode for the "what compounds at Wellscend that can't be acquired" moment.

Cascade Map is the clinical reveal. Use it last, and only with audiences who will appreciate the longitudinal-causal modelling — government health officials, clinical advisors, longevity researchers, sophisticated investors. The personal cascade map is the moat made visible. Animate from Day 1 (empty) through Day 1095 (full architecture). Pause on Hamid's Day 1095 cascade specifically — the closed loop between Belief & Purpose, Vitality, Biology, and Hormonal Health is the single most clinically interesting image in the entire artefact.


Two case studies, two different audiences

Layla is the universal entry point. Her cascade is episodic (weekly and quarterly rhythm), her question is emotionally relatable, and her story works across every audience type — consumer, investor, government, partner. Start most demos here.

Hamid is the longevity audience. He is purpose-built for HELM cluster, IHLAD, NYUAD HealthX, and clinical advisors who care about chronic disease prevention and healthspan extension. His cascade is a closed multi-month loop. His Day 1095 KNDRA response references his father's cardiac history — this is the moment the longevity pitch crystallises. Always demo Hamid when the audience is anchored in chronic disease, midlife health, or longevity science.

The deepest move in any demo is switching case studies mid-pitch in the same mode. After showing Layla's Cascade Map at Day 1095, switch the case study selector to Hamid and stay in Cascade Map. The viewer sees instantly that the system models different causal architectures for different people. No flat algorithm. Sophisticated audiences catch this in two seconds.


The four ages — pacing and meaning

Each age in the timeline carries a specific narrative weight. The Play button auto-advances at about six seconds per stop, which is appropriate for an unattended demo. For live demos, advance manually so you can pace the talking points.

Day 1 is the discipline moment. The viewer sees KNDRA wondering rather than predicting, the WIG bars almost empty, every WIT output returning Insufficient. Linger here. The temptation will be to rush past Day 1 because nothing is "happening". The opposite is true: Day 1 is where the integrity of the system is established. Without this moment, every subsequent claim looks like marketing.

Day 90 is the early-recognition moment. KNDRA notices a pattern but holds it lightly. The Cascade Forecast emits a low-confidence noticing but stops short of a prediction. This is the credibility-building moment — the viewer sees that the system can already be useful without overreaching.

Day 365 is the prophetic moment. KNDRA references prior episodes and offers a window for intervention. The Cascade Forecast crosses the high-confidence threshold. The Intervention Simulation becomes available. This is the moment most viewers say something like "okay, this is real".

Day 1095 is the moat moment. KNDRA speaks with deep longitudinal knowing, surfaces shadow patterns gently, and (in Hamid's case) explicitly references the longevity trajectory against his father's history. All three WIT outputs are available at high confidence. Linger here at least as long as you linger on Day 1.


Demo flows by audience

Financial investor (five to seven minutes). Open in Timeline with Layla. Move quickly through Day 1 and Day 90. Pause at Day 365 to point out that the intelligence has earned the right to speak. Linger at Day 1095. Switch to Side-by-Side to deliver the "asset that cannot be acquired" line. End by switching the case study to Hamid and showing Day 1095 in Timeline. Total time: roughly six minutes.

Government / HELM cluster (ten to twelve minutes). Open with Hamid in Timeline. Anchor on his profile (45, executive, father of two, paternal cardiac history) before clicking Day 1. Walk the timeline more slowly than for investors. At Day 1095, read aloud the KNDRA response about his father's cardiac timeline — that paragraph is the entire healthspan pitch in one breath. Move to Cascade Map and animate through ages. Pause at Day 1095. Use the words "anticipatory health" and "AI as utility" explicitly. Close in Side-by-Side, summarising what was earned vs what was assumed.

Clinical advisor (eight to ten minutes). Skip the financial-investor preamble. Open directly in Cascade Map mode with Hamid at Day 1, then animate through ages. Stay technical: name the cascade edges (Belief & Purpose → Vitality, Vitality → Biology, Biology → Hormonal Health, Hormonal Health → Vitality — the closed loop). Discuss the mean-delay labels (30, 90, 120, 60 days) as longitudinal-causal observations, not predictions. Use the phrase "no twin model that ignores Belief & Purpose can see this engine of midlife chronic disease". Move to Timeline only briefly, to show how the cascade map informs KNDRA's surface conversation.

Practitioner partner (five to seven minutes). Open in Timeline with Layla. Spend most of the time on Day 365 and Day 1095 — these are the moments where a practitioner sees value walking into a session with KNDRA Context Notes. Skip Side-by-Side. Skip Cascade Map. Focus on the KNDRA conversation pane and the Intervention Simulation card. The relevant pitch line: "when Layla walks into your studio, you already know what she has been working on, what is happening for her, and what has previously worked."

Consumer / user (three to five minutes). Open in Timeline with Layla. Skip Side-by-Side and Cascade Map entirely. Move through the four ages at a steady pace and let the same-prompt-evolving-response do all the work. The thing a consumer needs to feel is "she will know me over time". They do not need to see the moat from a business perspective.


What to say while clicking — quick reference

At Day 1: "This is the most important moment in the demo. She is silent because she has no right to speak yet. Most AI products would pretend. We do not."

At Day 90: "Now she has noticed something — but notice the language. 'I am noticing' and 'I want to be honest with you'. Calibrated uncertainty surfaced as a relational discipline, not buried in a confidence score."

At Day 365: "Look at this. She references prior episodes by count and timing. She offers a window. Every prediction she has just made is logged and scored against what actually happens next."

At Day 1095: "Three years in. She knows the seventh time this has started. She has earned the right to ask a question that no system could ask earlier. The intelligence here cannot be acquired. It can only be patiently built."


Common mistakes to avoid

  • Do not skip Day 1. The discipline pitch lives there. Without it, every subsequent claim sounds like marketing.
  • Do not rush past the calibration scorecard. For Abu Dhabi audiences in particular, the calibration curve is the single most credible artefact in the entire simulator.
  • Do not claim Layla and Hamid are real members. The footer states they are representative; honour that in conversation. The behaviour shown is real production-emission logic; the personas are illustrative.
  • Do not over-promise on the timeline. WIT will not be fully operational on day one of deployment. The simulator shows what KNDRA becomes. Be clear about that arc, particularly with government and clinical audiences who will probe.
  • Do not switch modes too quickly in a live demo. Each mode needs at least 90 seconds to land. Quick mode-switching looks like you do not trust the content.
  • Do not narrate the visuals. Let the simulator do its own work. Talk around it, not over it.

After the demo

If the audience wants to go deeper, send three artefacts in this order:

  1. The WIT explainer (newcomer-friendly markdown) — for the curious reader.
  2. The WIT Module Specification — for any technical or engineering audience.
  3. The Abu Dhabi pilot proposal — for government, HELM cluster, or any audience considering a partnership.

For investors specifically, send a follow-up link to the simulator itself so they can revisit at their own pace. Most will. The Side-by-Side mode rewards a second viewing.


Practical notes

The simulator is a single React artefact (wellscend-wit-simulator-v3.jsx) that runs in a browser. To present in a meeting room, open it in a browser tab, set the window to its largest comfortable size, and dim distracting toolbars. The radial gradient background and Fraunces / Plus Jakarta Sans typography are intentional — they signal "this is built by people who care about every detail" before the viewer reads a single word.

For a sit-down demo on a phone, the simulator works but loses some of the impact (Side-by-Side stacks vertically). Default to a laptop or large display for stakes meetings.

For a link sent before or after a meeting, encourage the recipient to start in Timeline with Layla, then explore. Most will gravitate to the Play button on their second visit.


A closing principle

The simulator works because it shows discipline before it shows capability. Most AI pitches do the opposite — they show capability first, hoping the viewer will not probe the discipline. With WIT, the discipline is the capability. Trust this in the room. Day 1 sells the system more than Day 1095 does.


For questions, refinements, or new case studies, contact the Wellscend team.

← Back to the simulator