Case study · Dan Meyer · Bucket List of Thromes

Thromes

Turning a sword swallower's TEDx audience into a movement people actually live.

Building nowMobile + webAudience-led productOwned community

Building now. Marketing site live at thromes.com; native apps + member dashboard in development. Book pre-order coming.

Chapter 01

Client

Dan Meyer — world-class sword swallower, three-time TEDx speaker, multiple Guinness World Record holder. Dan has dedicated his life to doing the impossible — and to helping others do the same. Through his adventures, his performances, and his framework of Thromes, he inspires people to turn their biggest dreams into real-world experiences.

The product is Thromes — a mobile + web platform that takes Dan's forty-year practice of capturing major life goals and turns it into something his audience can live, track, and share.

Website: thromes.com · TEDx talks: Cutting through fear (Maastricht, Yerevan)

Chapter 02

What it is

ThromesThriving on Hopes and dreaMS — is a mobile + web home for the goals that feel too big. Capture a Throme. Track the journey. Share the dopamine when the quest is done.

Throme (noun) \ˈthrōm\

A meaningful, often challenging quest, life pursuit, or experience that expands what one believes is possible. A goal distinguished by its emphasis on growth through effort, risk, and discovery, where the journey becomes more rewarding than the achievement itself.

*T.H.R.O.M.E. — Transformation through High-Risk, Outcome-Driven Meaningful Experience.*

The word isn't new — Dan learned it from his mentor Greg Ormson in Tamil Nadu, India, in 1978, the night before his 21st birthday. It comes from Patricia A. McKillip's 1973 fantasy novel The Throme of the Erril of Sherill. A week after Dan first heard it, he was on his deathbed with malaria. He wrote his first list of ten Thromes that night. He's been adding to it and checking things off for over four decades.

The product carries that history. The framework is Dan's. The app is where it scales.

Chapter 03

Existing Success

Dan isn't building an audience from scratch. The TEDx talks alone reach hundreds of thousands of people — Cutting through fear (TEDxMaastricht) and Doing the Impossible: Cutting Through Fear (TEDxYerevan) are still actively shared in leadership and resilience programs. Decades of keynote work have put him in front of corporate audiences, university stages, and prime-time television. Performance feats — sword-swallowing under MRI, world records, Guinness Book entries — keep the visibility compounding.

The reach exists. The trust exists. The framework exists. What's been missing is a place for any of it to land between events.

Chapter 04

The Challenge

Dan's problem was a business problem, not an audience problem.

  • The TEDx audience converts emotionally on stage and evaporates after. A standing ovation doesn't capture an email. The people most moved by Dan's work have nowhere to go when the talk ends.
  • The framework lives in keynote slides and a personal notebook. Thromes is a forty-year practice with no surface other people can use. Every conversation that's ever ended with "I want to do that too" hits a dead end.
  • Speaking revenue caps at events booked. Even at Dan's tier, there are only so many keynotes in a year. The model can't scale further without a product that compounds attention into something repeatable.
  • The book and the app need each other and there's no team to build either. Dan is one person. Building a publishing arm, a software product, and a community platform from scratch is months of solo work, or a hand-off to an agency that doesn't speak his voice.
  • Generic motivational-app speak would kill the whole thing. Dan's voice is specific — "the impossible is not impossible", "it's not about the destination, it's about the journey" — and a templated bucket-list app would betray the framework on day one.

Chapter 05

The Solution

theAppChicks is building Thromes as a set of business capabilities Dan now has, not a list of app features. Each is an outcome first, plumbing second.

An audience he owns

The TEDx viewer who downloads the app or signs up at thromes.com becomes a known member in Dan's database — name, email, the Thromes they've started, the quests they've finished. The audience that used to scroll past his talks now lives on his domain, in his Stripe account, in his email list. If YouTube or any platform shifts tomorrow, the relationship is intact.

A framework people live, not just hear

The app turns Thromes from a keynote concept into a daily practice. Capture a Throme. Break it into milestones. Track the dopamine of progress. See other people's Thromes — what they're attempting, what they've finished — to feel the universality of the quest. The framework doesn't compete with Dan's stage work; the stage drives people to the framework, and the framework holds them between performances.

A revenue ladder beyond keynote fees

Free on-ramp for the curious — capture your Thromes, see Dan's, follow the journey. Paid tiers layer in the deeper material as it ships: contributor quotes, the dopamine-loop guides, members-only Throme circles, the book launch. Speaking fees stay where they are; the recurring tier is what compounds.

A book that's actually a product, not a press release

The Thromes book has Dan's full story arc — Indiana kid through Guinness-record sword swallower, Greg Ormson and Tamil Nadu, the deathbed list — paired with the framework's working materials. Pre-orders run through the same domain and the same Stripe account as the app. Buying the book makes you a member; being a member makes the book make sense. The two surfaces sell each other.

A voice that survives scale

A canonical persona doc and the canonical T.H.R.O.M.E. dictionary entry are the system prompt every content agent writes against. Push notifications, error states, email subjects, onboarding screens — all written in Dan-direct voice ("the impossible is not impossible"; "this isn't about the treasure, it's about the quest") automatically. The brand doesn't drift as the product grows.

A business that's portable

Stripe is in Dan's account. Resend is in Dan's account. The domain is in Dan's name. Apple Developer + Google Play accounts are Dan's. App Store listings, Play Store listings, and the bundle IDs are Dan's. If theAppChicks ever stepped away, Thromes would keep running — same product, same audience, same revenue.

Chapter 06

What Dan's Throme-keepers see

Dan's clear: the center of gravity is on the user, not on him. The app is theirs — a place to keep their own Thromes, see their own progress, live their own quests. Dan shows up as a steady contributor, not the headliner.

  • A calm dark/gold home that asks one question on first open: What are your Thromes?
  • A capture flow that's faster than the Notes app, with milestones, a journey log, and a dopamine-loop progress view that rewards the journey, not just the finish.
  • A library of contributor quotes — Dan's, Jen's, and (eventually) others — surfacing at the right moment without selling anything.
  • A book section, a story section, a one-line bio of Dan when they want it. None of it forced; all of it available.
  • Push notifications that feel like a friend nudging them, not a startup demanding engagement.

Chapter 07

What Dan sees

  • An admin where he writes a guide, drops a contributor quote, or publishes a journey, and members see it. No deploys, no tickets.
  • A member list showing who joined, what Thromes they're keeping, when they were last active.
  • A book pre-order dashboard tied to the same member identity, so a buyer is automatically a known member.
  • A single Stripe dashboard for revenue — recurring members, book pre-orders, speaking add-ons — all under his name.
  • An agent team running the platform under the hood (CEO, CTO, Mobile, Web, Backend, QA) — Dan never has to look at code.

Chapter 08

Why this matters

Thromes is the pattern for any speaker, performer, or thought-leader whose framework has outgrown the keynote stage:

The room you spoke to last night is gone by morning. The framework you walked them through deserves a home — a daily-use surface where the people you moved can live what you taught, tell each other about it, and bring the next person into the same quest. The app isn't a side project to the keynote. It's where the keynote goes to live the rest of its life.

It's also proof the theAppChicks model works for founder-led IP businesses — different from a trader's app, a creator's affiliate site, or an event-driven coaching platform, but the same ownership outcome. Dan owns his framework, his audience, his platform, and the relationship with every member who reaches through.

Chapter 09

The dopamine-loop philosophy

Dan's one-line thesis on the product, in his own words:

"It's not about the destination, it's about the journey. It's not about the treasure (the Throme), it's about the quest." — Dan Meyer

Every product decision routes through that. Streaks reward consistency, not finishes. Push notifications celebrate showing up, not winning. The contributor-quote system surfaces during a quest, when momentum needs a nudge — not after, when applause is cheap. The framework is the loop; the app is the loop made daily.

Appendix

Status

Building now. Marketing site live at thromes.com (also at thromes.app + www.thromes.com). In progress: auth flow, member dashboard, mobile shell, contributor-quote system. Next: universal-binary mobile app on App Store + Google Play, book pre-order.

Appendix

Technical appendix

Included for the curious. This is how the outcomes above are delivered; none of it is the story.

Layer Choice Why it serves the business
Mobile Expo + React Native One codebase, iOS + Android universal binary, Dan's brand on both stores
Web Next.js App Router + Tailwind Marketing + member dashboard on one domain; same voice, one deploy pipeline
Backend Supabase Identity, Thromes, milestones, and member state in one place
Hosting Cloudflare Workers Fast global edge, auto-deploy, preview URLs on every branch
Secrets Doppler (thromes project) Keys never sit in the repo or dashboard — injected at build and runtime

Voice-as-code: docs/product/persona-dan-meyer.md and docs/product/throme-definition.md are the canonical voice + definition documents. Every content surface in the product writes against them — no generic motivational-app prose can sneak in.