Demo pitch narrative

5-8 minute beta preview route for the digital layer behind a Texas innovation operating system.

Position this as an unofficial beta preview: source-cited graph data, Founder Router, source panel evidence, governed public improvement paths, and a controlled operator appendix only when the audience has approved access.

Opening line

"You announced an operating system for Texas innovation. I built a working beta preview of what the digital layer could look like: a public, source-cited graph that routes founders to next actions and shows what still needs verification."

This is not affiliated with any named partner. It is a narrow, source-cited digital layer for graph data, routing, governance, and maintainable public evidence.

Presentation route

Scripted demo path

Each beat has one proof point and one presenter note so the recording can stay inside the 5-8 minute window.

  1. 0:00-0:35

    Home

    Open route

    Frame the product as a public, source-cited Texas innovation graph that turns scattered records into routes, evidence, and visible gaps.

    Presenter note: Open with the unofficial beta preview boundary before describing any value proof.

  2. 0:35-1:25

    Search

    Open route

    Search for the Arlington WealthTech path and point to result cards, source freshness, confidence, filters, and correction paths.

    Presenter note: Search proves discoverability and lineage; do not imply exhaustive coverage.

  3. 1:25-2:20

    City page

    Open route

    Show Dallas category counts, source-backed featured records, data-quality signals, missing category signals, and suggested-source actions.

    Presenter note: Explain that stale and missing signals are review prompts, not city scores.

  4. 2:20-4:45

    Founder Router

    Open route

    Run Scenario A for an Allen or North Texas AI and HealthTech founder, then show ranked recommendations, matched factors, caveats, and a two-week action plan.

    Presenter note: Use source confidence, city, sector, stage, and need factors before describing any next action.

  5. 4:45-5:45

    Source panel

    Open route

    Open the TechFW opportunity record and show source URL, confidence, freshness, related graph records, caveats, Report correction, Request owner claim, Submit source update, and Review methodology actions.

    Presenter note: This is the trust moment: what is known, what is uncertain, and where the source owner should be checked.

  6. 5:45-6:35

    Public governance

    Open route

    Open suggested-source, correction, claim, and methodology paths to show that public improvements go through review before they affect the graph.

    Presenter note: Keep protected maintenance screens as an optional controlled operator appendix, not the public recording route.

  7. 6:35-7:30

    Close

    Open route

    Return to the demo route and make the three asks: validate data, pilot the North Texas/Arlington node, then discuss authorized feeds and branding.

    Presenter note: Close on a validation path, not an endorsement or completeness claim.

Scenario route map

Curated scenario paths

Each scenario has city, Opportunity Radar, entity, and methodology paths that can be opened directly during rehearsal.

Source evidence

Source evidence to cite

Name only source-backed examples on camera and keep caveats close to any claim about eligibility, freshness, affiliation, or coverage.

TechFW healthtech opportunity

Scenario A source-panel proof for North Texas AI/HealthTech routing.

https://www.techfw.org/

Caveat: Verify healthcare, eligibility, dates, and application status with the source owner.

The Founders Arena

Scenario B Arlington and WealthTech organization proof.

https://www.thefoundersarena.com/

Caveat: Describe public routing signals only; do not imply endorsement or introductions.

Dallas Economic Development Corporation

Scenario C city coverage and EDC governance proof.

https://dallasedc.com/about-edc/

Caveat: Missing categories mean missing reviewed evidence, not absent local resources.

Close

Three concrete asks

The asks stay concrete and reversible: validate data, run a focused pilot, then discuss authorized feeds and branding.

Ask 1

Data validation partnership

Run a short validation sprint where source owners or ecosystem partners review priority records, stale indicators, and correction paths.

Ask 2

Pilot with North Texas/Arlington node

Use Arlington and North Texas as a focused pilot for founder routing, city coverage, suggested sources, and data-quality operations.

Ask 3

Authorization for feeds and branding

After proof-of-work review, ask the relevant source owners for authorization before using official feeds, names, marks, or branding.

Objections

Likely objections and responses

Presenter notes should answer the hard questions before the audience asks them.

Unofficial status

This is intentionally labeled as an unofficial beta preview and does not claim affiliation, authorization, or source-owner approval.

Source rights

The source registry tracks public URL, crawl policy, trust tier, freshness policy, and owner contact paths; uncertain sources can be manual-only or removed.

Data freshness

Freshness is visible through stale labels, source panels, data-quality metrics, correction paths, and owner claims.

AI trust

Ranking stays deterministic and explanations are constrained to source-backed records, matched factors, confidence, and caveats.

Maintenance

Source submissions, correction review, owner claims, stale-source watchlists, metric snapshots, and a controlled operator appendix make the graph governable after the demo.