Case study · Amy Bell

Bell Curve Health

Turning 28 years of trusted answers into a platform she owns.

Building nowTelehealthOwned platformRegulated industry

In active build: the core site, quiz, and education layer are coming together on Amy's final copy. Clinical backend integration and membership billing in active development; not yet publicly live.

Chapter 01

Client

Amy Bell - founder of Bell Curve Health, with 28+ years in the compounding pharmacy sector. She has spent nearly three decades answering the same questions from women in midlife who feel dismissed by their doctors and lost in conflicting health advice online. Bell Curve Health turns that experience into a company: an elevated telehealth and wellness platform for women ages 40–58 navigating the hormonal and metabolic changes of midlife.

Website (preview): bellcurvehealth.theappchicks.workers.dev (preview build until the site goes live)

Chapter 02

What it is

Bell Curve Health is Amy's own telehealth and membership platform - a site where a woman can take a symptom quiz, get a personalized profile, read the education library that matches her result, join a membership, and move into a clinical consultation and prescription pathway, all inside one brand she owns. The site's promise is simple: "I'm doing everything right - but still not feeling like myself." Bell Curve exists to say back to her: you are not crazy, you are not failing, there is a path forward.

The clinical piece - licensed prescribing and pharmacy fulfillment - runs through a licensed clinical backend, connected behind a single, swappable integration layer. Amy's patient data, her business logic, and her brand all live on her own platform; the clinical backend is one API call away, not the product itself.

Chapter 03

Existing Success

Amy isn't new to this audience. For 28+ years in compounding pharmacy, she has been the person women in midlife turn to when their doctor tells them their labs are "normal" and sends them home anyway. That trust, and the years of informal conversations behind it, are the real asset Bell Curve Health is built to capture - Amy already has the answers; she never had a platform of her own to deliver them at scale.

Chapter 04

The Challenge

Amy's problem was a business problem, not a content problem.

  • A rented white-label telehealth platform caps everything. The typical vendor model bundles a branded portal, a prescriber network, and pharmacy fulfillment behind a flat monthly platform fee plus per-consult and per-prescription charges - fees that apply whether Amy has 5 patients or 500, deducted before she sees a dollar of margin. Customization stops at whatever the vendor's roadmap allows.
  • Ownership was unclear everywhere it mattered. Who owns the patient relationship? Can she export her own patient data if she ever wants to leave? A rented platform's answers are vague at best and vendor-dependent at worst.
  • The clinical backend kept changing. Amy evaluated more than one licensed clinical vendor before settling on the right fit, and the relationship can still evolve. A platform wired directly to one vendor's quirks would have meant rebuilding the whole site every time the clinical relationship changed.
  • Compliance has real teeth here. LegitScript certification gates any paid marketing and constrains what the site can say about specific compounds before certification is granted. Genuine testimonials carry their own FTC framing requirements. None of this is optional, and getting it wrong is expensive.
  • Amy wanted a small, high-quality business, not a volume mill. In her own words: "I don't need to be like [a big competitor's] scale. If this could be a great small niche... I don't need volume. I want quality over quantity." The platform had to fit that goal, not push her toward one it wasn't built for.

Chapter 05

The Solution

theAppChicks is building Bell Curve Health as a set of business capabilities Amy now has, not a features checklist.

A platform Amy owns outright

The repo, the domain, and the data are Amy's. Supabase (her account, row-level security from day one), Stripe (her account), Resend (her account, sending from her domain) - every credential is hers. theAppChicks is the ongoing tech and operating partner, not a vendor renting her a black box. If Amy ever wanted to walk away from the partnership, she keeps everything she built.

A clinical backend that's swappable, not load-bearing

A single ClinicalBackendClient layer sits between Amy's platform and whichever licensed prescribing and pharmacy network she uses. More than one vendor was evaluated, and the platform survives a future vendor change because the clinical backend was never the product; it's a component behind one interface.

A quiz that turns a symptom list into a real conversation

A multi-question intake quiz scores across profile dimensions and routes each woman to the education content and next step that matches her actual symptoms - hormonal, metabolic, energy, or aging-focused - instead of a generic landing page. The scoring logic lives in its own tested module, separate from the UI, so profile logic can be verified independently of how the quiz is presented on screen.

A content engine built for how AI search actually works today

A structured article system (profile-tagged, schema-marked, built to answer the exact questions women are typing into Google and AI chat) means Bell Curve's education library is discoverable by both traditional search and the AI engines increasingly answering health questions directly. Content is gated through a compliance filter tied to LegitScript's certification rules before anything about a specific compound goes live.

Amy's own words, unedited

Every page is built from Amy's verbatim copy: her founder letter, her page-by-page content package, her design tokens. The rule on this build is explicit: her words don't get rewritten for SEO or house style; the platform adapts structure around her voice, never the other way around.

Chapter 06

What Amy's visitors see

  • A quiz that feels like being understood, not diagnosed - a few honest questions, then a profile that matches how she actually feels.
  • An education library organized by what she's actually experiencing, not a generic blog.
  • A membership that unlocks deeper content and a path to a real consultation, on Amy's own pricing.
  • A founder letter, in Amy's own words, that tells women this is not "just aging" - because Amy lived it first.

Chapter 07

What Amy sees

  • A single admin surface for the business as it grows: patient intake, care plans, membership status, and - as the clinical integration deepens - the prescribing and fulfillment pipeline behind one dashboard.
  • A milestone view of the build itself, so she always knows what shipped, what's in progress, and what's next, without a status meeting.
  • A platform priced and structured around her stated goal: a smaller, higher-quality practice, not a scale-at-all-costs funnel.

Chapter 08

Why this matters

Bell Curve Health is the pattern for any practitioner who has built real trust the slow way - one patient, one conversation, one relationship at a time - and is ready to turn it into a platform:

Twenty-eight years of answering the same questions one patient at a time is a real asset. The question is whether it stays locked inside your own head and calendar, or becomes a platform that can answer for you at scale, with your own words, on your own terms, in a regulated space where getting the details right matters.

It's also proof theAppChicks works in a regulated, clinically-backed industry - a genuinely different constraint set from a trading app, a membership hub, or a lifestyle brand, but the same ownership outcome: Amy's data, Amy's domain, Amy's brand, with theAppChicks as the ongoing technology and platform partner behind it.

Appendix

Status

Active build, Phase 0 in progress. The core site, the symptom quiz, and the education content layer are built on Amy's final copy and coming together now at bellcurvehealth.com. The clinical backend integration and full membership billing are in active development as the partnership moves into the next phase; the site is not yet publicly live.

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
Framework Next.js App Router + React + TypeScript One codebase for marketing site, quiz, education library, and member/admin dashboards
Styling Tailwind, design-tokens-as-source-of-truth Amy's exact brand palette and typography live in a single tokens file; a build-time guard fails the build on visual drift
Database Supabase (Amy's account, RLS from day one) Patient and content data in one place, owned by Amy, portable via full SQL export
Payments Stripe (Connect, Amy's account) Membership billing lands in Amy's account directly
Email Resend Transactional and welcome sequences sent from Amy's own domain
Clinical backend A licensed clinical vendor, behind a swappable client layer Licensed prescribing + pharmacy fulfillment as an API, not the platform itself
Hosting Cloudflare Workers Fast global edge delivery, auto-deploy from main, preview URLs for every branch
Secrets Doppler (bellcurvehealth project) Keys never sit in the repo; injected at build and runtime

Testing baseline: shipped with a mutation-tested suite from the start - every significant test proven to fail against a broken implementation before being trusted - plus a workerd smoke test that boots the app on the real production runtime and checks every route, not just that the code compiles.