Demo build for a fictional foundation, sample data only. See how it is put together on the V1 Launch Blueprint page.
SSilverbark Health FoundationEducation in natural medicine

The working plan behind this site

The V1 Launch Blueprint

One small sprint, established platforms, manual routines wherever automation is not yet earned. The whole plan is three honest sentences: this must work now, this can stay manual, this should wait.

Sprint one

Build now

  • Public website + waiting list into Brevo
  • Grand Rounds loop: Zoom, registration, reminders
  • Skool: community, first course, Stripe billing
  • Secure consultation intake, sealed off from the site
  • Foundation-owned accounts, documentation, handoff

Deliberately human

Keep manual

  • Report delivery by personal expiring links
  • Consultation triage and scheduling
  • Posting the weekly recording to the classroom
  • Weekly exports: contacts, members, site backup

Earned later

Defer

  • Custom member portal and single sign-on
  • Automation platform (n8n, Zapier)
  • Custom CRM, LMS, or community software
  • Clinical-reasoning software, on principle

The platform map

Two lanes that never cross. Everyday data flows through everyday tools the foundation owns. Health information lives in its own sealed corridor.

Ordinary lane · public and members

Website

WordPress or static, foundation hosting

Brevo

CRM: contacts, waiting list, email

Zoom

Weekly Grand Rounds

Skool

Community, courses, membership

Stripe

Billing inside Skool, foundation account

Secure lane · health information only

Secure intake form

HIPAA-capable provider, encrypted in transit

Encrypted vault

Restricted storage, clinical team only

Expiring links

Personal, signed, logged delivery

The client

And no one else

Case information never enters the website database, the media library, the community, or ordinary email. Try it live on the consultation intake.

Who owns what

The foundation, in every case. The developer is a guest with keys that can be taken back.

  • Domain, hosting, Brevo, Zoom, Skool, and Stripe are all registered to the foundation, on foundation billing
  • Credentials live in the foundation's password vault; the developer holds a removable seat, never the root
  • Weekly exports: contacts, member list, full site backup
  • Documentation plus a recorded admin walkthrough

Where you log in, day to day

Site admin · pages and postsBrevo · contacts and emailSkool · members and coursesZoom · sessionsStripe · money

What the first sprint buys

One fixed price covers the Build now column, end to end: live, documented, and owned by the foundation. That is the initial functionality, not the full institution, and the exact list is confirmed together before the sprint starts.

The Keep manual column costs a routine, not software. The Defer column belongs to later sprints, each scoped and authorized on its own when the foundation is ready.

Expect about three weeks: foundations first, then the weekly loop and membership, then the secure lane and the handoff walkthrough.

The point

Everything in the first column is working on this demo site right now. Everything in the second column is a documented routine, not missing software. Everything in the third column is waiting its turn on purpose.

Start small, build clean, and hand the keys to the institution that owns them.