Score C · 6.40/10Free to read$100K Hackathon · November 16, 2026 → December 16, 2026Nov 16, 2026

DoseDeck Protocol Cards

DoseDeck turns a practitioner's supplement protocol into a branded, tap-to-confirm dose card for each client and emails the practitioner a Monday list of who is slipping, so 8-week protocols actually get finished.

One product, one founder, thirty days. Everything below is built to be executed inside the contest window — the official rules still decide what counts.

Decide in 20 seconds

The facts that decide whether this is worth thirty days of yours.

Speculative6.40/10
MVP build (solo)
4 days
Launch price
$79
Sales to $1,000 revenue
13 customers
First paying customer
Hand-built direct Instagram/X DM and email outreach to 60 named practitioners whose public profiles advertise 1:1 multi-week supplement protocols.
Who pays

Owner-practitioner at a 1-3 person functional-medicine, nutrition, or health-coaching practice in the US, UK or Canada who sells 6-12 week supplement protocols at roughly $150-$600 per client and carries 10-60 active clients.

Biggest execution risk

Market demand 4.4/10

Narrow the buyer to a segment with an urgent, already-budgeted problem and reference the specific trigger event that creates willingness to pay.

Why this could work in 30 days: one founder can ship the MVP in 4 days; the plan targets a first sale on day 9; 13 sales at $79 clears $1,000 of collected revenue; strongest signal is speed to first revenue at 8.1/10.

Score and projections come from the generated report and are not guarantees. The $100K Hackathon is run by Ship or Die — read the official rules before you build.

Your first 24 hours

15 concrete actions. Tick them off as you go — nothing is saved or sent.

0/15
Entry price
$79
Solo build
4 days
30d base revenue
$1,422
30d hackathon profit
$1,236
Section 1 of 8

Product opportunity and positioning

Target customer

Owner-practitioner at a 1-3 person functional-medicine, nutrition, or health-coaching practice in the US, UK or Canada who sells 6-12 week supplement protocols at roughly $150-$600 per client and carries 10-60 active clients.

Why now

This buyer already sells multi-week paid programs, already takes card payments, and already owns the protocol content, so the only missing piece is a feedback loop they can adopt in one sitting for $79.

Problem

Protocol clients silently stop taking supplements around week 3, the practitioner has zero visibility between consultations, and the renewal call turns into a refund argument instead of an upsell.

Solution

The practitioner pastes their protocol, DoseDeck parses it into a structured schedule, issues a branded mobile dose card at a unique link per client, records tap-to-confirm events, and emails a Monday Slipping List with adherence percentages, missed slots and a pre-written nudge per at-risk client.

Differentiation · A PDF goes invisible after day one and a generic habit app gives the practitioner no data and no branding; DoseDeck is the only version that hands the practitioner a branded client artifact plus a weekly list of exactly who to contact.

1. Product opportunity and positioning

DoseDeck Protocol Cards sells to one person: the owner-practitioner at a 1-3 person functional-medicine, nutrition or health-coaching practice who sells 6-12 week supplement protocols at $150-$600 per client and runs 10-60 active clients. Their protocol ends as a PDF and a promise. Around week three clients go quiet, the practitioner has no signal until the renewal call, and the renewal becomes a refund conversation. Manual "how's it going?" texts eat hours and still miss exactly the clients about to quit.

The wedge is deliberately non-clinical. DoseDeck does not interpret interactions, adjust doses or make recommendations. It does the two things a practitioner cannot do cheaply by hand: it renders the protocol as a branded, tap-to-confirm card at a unique link per client (no app install, no client login), and it mails a Monday Slipping List of who is behind, which slots they missed, and a pre-written nudge to copy and send.

Against the alternatives: a PDF is invisible after day one; a generic habit app is unbranded and returns no data to the practitioner; a practice-management suite costs more and solves scheduling, not adherence. DoseDeck is $79/month, self-serve, cancel-anytime, and produces a client-facing artifact the practitioner can show in the same session they buy it. No payer, pharmacy, employer or regulator sits between the founder and the card. The buyer's trigger event is concrete and recent: a client who quit a protocol mid-way and did not renew.

Why now: this buyer already sells a multi-week paid program, already charges cards, and already owns the protocol text. DoseDeck only adds the missing feedback loop, which means adoption is an edit to an existing workflow rather than a new behaviour.

The scored concept carries a JEV score of 64/100 (band C), with market demand the weakest criterion at 4.43 normalized. The plan below compensates by narrowing outreach to practitioners whose public profiles visibly advertise 1:1 multi-week supplement protocols, i.e. people already selling the exact artifact DoseDeck wraps. Monetization potential (6.14), speed to first revenue (8.09) and solo build feasibility (7.57) are the strengths this 30-day plan leans on: one buyer, one card, one weekly email, card payment on day one.

2. Smallest sellable MVP

The sellable unit is one branded client dose card plus the Monday Slipping List. Minimum: paste a protocol into a text box, get an editable parsed table of supplement, dose, time slots and duration, save it, generate a tokenized client card URL that renders today's slots as large tap targets, store tap events, and email the practitioner one weekly list. Plus Stripe Checkout so money can arrive on day five, and a cap of 25 active clients on the $79 tier. Anything that does not appear in that sentence waits.

3. Technical implementation plan

Next.js on Vercel serves both surfaces: the authenticated practitioner dashboard and the public client card at /c/[token]. Supabase Postgres holds practitioners, protocols, protocol_rows, clients, doses (slot, date, tapped_at) and plans, with magic-link auth for practitioners only — clients never authenticate, the token is the credential. One LLM call converts pasted protocol text into JSON rows that populate an editable table; a second call drafts the nudge message from missed-slot data. Resend sends the Monday email; a Vercel Cron job at 07:00 local per practitioner computes rolling adherence and renders the list. Stripe Checkout plus the Customer Portal handle subscription, tier gating and self-serve cancel. Build order: schema, auth, protocol intake plus edit table, card renderer, tap endpoint, adherence rollup, cron email, Stripe gating, branding, subdomain. The hardest risk is parsing messy real-world protocol text into correct slots; the manual edit table is the release valve and must ship in the same build as the parser.

4. Pricing and monetization

Three prices, all card-collectable without approval: $49 one-time First Card Setup (founder builds the card from their existing document, credited toward month one if they subscribe within 14 days), $79/month Solo Protocol up to 25 active cards, $149/month Practice up to 100 cards with a custom subdomain and per-slot missed-dose breakdown. Expected first-month ACV is $79. The $49 setup fee is the de-risked front door for practitioners who will not commit to a subscription from a cold DM; the $149 tier is the expansion path once a practice adds a second practitioner or passes 25 clients. No trials longer than the free first card, no annual plans, no discounts in the 30-day window.

5. First-customer acquisition

One channel: hand-built direct outreach to named practitioners. Build a list of 60 by hand over days one and two from public practitioner directories that publish practice contact details, practitioner Instagram and X accounts that post their own multi-week protocol programs, and podcast guest pages for functional-medicine shows. Message angle: their clients go quiet around week three and they find out at renewal; offer one free branded card built by the founder within 24 hours. Convert on the second client — card one free, card two onward at $79/month with a Stripe link in the same thread. Day-three follow-up to non-openers with a 20-second screen recording. Every client card carries a one-line "Built with DoseDeck" footer so practitioners' peers can request their own.

6. 30-day execution roadmap

Days 1-5 are build only, ending with a working end-to-end flow and Stripe live. Days 6-9 ship the demo assets and send the first 20 messages, with first sale targeted day 9. Days 10-14 are outreach wave two plus branding controls and the first real onboarding. Days 15-21 add the Practice tier, the referral footer and the nudge-quality pass, with a live cron test on day 19. Days 22-30 are conversion and retention: peer intros, the paid $49 front door, a public screen-recording post, and a day-30 reconciliation of Stripe against TrustMRR. Outreach volume target: 60 messages by day 7 and 150 conversations by day 24.

7. Revenue and profit scenarios

All three scenarios are projections built from the stated assumptions, not observed revenue. Conservative assumes 6 paying practitioners at $79 (about 8% of 60 first-wave conversations converting), no paid spend, $16 in Stripe fees and $40 of hosting, domain, email and LLM usage. Base assumes 18 paying accounts at $79, one refund, $60 of optional paid boosts. Upside assumes 35 accounts at a blended $85 (a mix of $79 and $149 tiers), one refund, $150 of paid boosts. The contest ranks hackathon profit, which deducts refunds, chargebacks, processing fees and ad spend but not hosting or inference; business profit then subtracts operating cost. Every scenario keeps a per-account delivery cost well under the $79 price.

8. Main risks and validation experiments

First, cold DMs may produce near-zero replies. Test: send 20 on day 7 and require 2 replies within 72 hours, otherwise rewrite the opening line to lead with the free card rather than the problem. Second, the Slipping List may read as noise. Test: call the first five paying practitioners on day 25 and ask whether they sent a nudge; if none did, the email is the wrong artifact. Third, clients may not tap, leaving empty adherence data. Test: watch five real clients for seven days and count taps per day; if under 40% completion, reduce the card to a single daily check-in. Fourth, LLM parsing may fail on messy documents. Test: run ten real protocols through the parser and count how many need more than two manual edits. Fifth, messaging may drift into clinical advice. Rule: any drafted copy that implies an interaction, dose change or safety claim is removed before release; the product is a reminder and engagement tool.

9. First 24-hour action plan

Hours 1-2: create the Stripe account, connect it to TrustMRR, and confirm no payments can arrive before launch. Hours 3-5: scaffold the Next.js repo on Vercel with Supabase schema for practitioners, protocols, clients and doses. Hours 6-9: build the protocol paste box and the LLM parser to a JSON row table. Hours 10-14: build the tokenized client card page with tap endpoints. Hours 15-18: build the practitioner roster view and start the 60-name list with the first 30 entries. Hours 19-24: deploy, run one fake protocol end to end, and log what breaks for day two.

Section 2 of 8

Smallest sellable MVP

A practitioner pastes a supplement protocol, gets an editable parsed schedule, and one client gets a branded tap-to-confirm card at a unique link; the practitioner receives one Monday email listing who is behind with a copy-ready nudge, and pays $79/month through Stripe.

Must-have features

  • Protocol paste box with LLM parsing into editable rows (supplement, dose, time slot, duration in weeks)
  • Tokenized public client card page per client with large tap targets and a done state
  • Tap event storage and rolling per-client, per-slot adherence calculation
  • Weekly Monday Slipping List email with client name, week, adherence %, missed slots and a drafted nudge
  • Practitioner dashboard roster with add/archive client and per-client adherence chart
  • Branding controls: practice name, logo and accent colour on every client card
  • Stripe Checkout subscription with tier client caps and a self-serve cancel link

Explicitly out of scope

  • Drug-drug interaction checking or any safety/clinical recommendation
  • Native iOS or Android app
  • Photo or OCR scanning of pill bottles
  • EHR, lab or practice-management integrations
  • Supplement recommendations, affiliate storefront or marketplace
  • SMS reminders to clients and SMS-based dose confirmation
  • Insurance, HSA/FSA or claims handling
  • Multi-practitioner team accounts beyond the Practice tier cap

Demo flow (what the buyer sees)

  1. Founder opens the dashboard and pastes a sample 8-week supplement protocol into the intake box.
  2. LLM parser returns structured rows; founder corrects one row in the edit table and saves.
  3. Founder adds a client and clicks generate card.
  4. A unique URL renders the branded mobile card with today's slots as tap targets.
  5. Founder taps two slots on a phone to simulate a client; dashboard adherence updates.
  6. Cron job renders the Monday email preview showing that client at 62% with two missed slots and a drafted nudge.
  7. Founder clicks the Stripe link and completes a $79 checkout.
Build plan

Technical implementation plan

Stack

Next.js on Vercel (dashboard + public client cards)Supabase Postgres with magic-link auth for practitionersStripe Checkout + Customer PortalResend for transactional and Monday emailsVercel Cron for the weekly Slipping List jobOne hosted LLM API for protocol parsing and nudge draftingTailwind CSS for the card UI

Architecture

A single Next.js app on Vercel serves two surfaces. The authenticated dashboard at /app reads and writes Supabase tables (practitioners, protocols, protocol_rows, clients, doses, plans) guarded by row-level security on practitioner_id. The public card at /c/[token] reads a client row by opaque token, renders today's slots from protocol_rows, and posts tap events to a serverless endpoint that writes a dose row with tapped_at; no client auth exists. A nightly Vercel Cron job groups practitioners by timezone, computes rolling adherence and missed slots, calls the LLM to draft one nudge per at-risk client, and sends the Monday email through Resend. Stripe webhooks update the plans table that controls the active-client cap.

Build steps

  1. Create Supabase project and schema: practitioners, protocols, protocol_rows, clients, doses, plans with RLS on practitioner_id.
  2. Wire Supabase magic-link auth and a protected /app route.
  3. Build the protocol paste box and an LLM parser that returns JSON rows, then an editable table with save.
  4. Build the client card page at /c/[token] rendering today's slots as tap targets with a done state.
  5. Add the tap endpoint, dedupe by (client_id, slot, date), and compute rolling adherence.
  6. Build the practitioner roster: add/archive client, generate card link, adherence chart.
  7. Add the Vercel Cron job that renders and sends the Monday Slipping List per practitioner timezone.
  8. Add the LLM nudge drafting call with a strict prompt and a copy button in the email and dashboard.
  9. Integrate Stripe Checkout, webhook, tier caps and the Customer Portal cancel link.
  10. Add branding controls, the "Built with DoseDeck" footer, and custom subdomain mapping for the Practice tier.

AI components

  • LLM structured extraction of pasted protocol text into supplement, dose, slot and duration rows
  • LLM drafting of a short, non-clinical nudge message per at-risk client from missed-slot data
  • No clinical reasoning, interaction checking or dosing advice is performed by any model
Hardest technical risk: LLM parsing of messy, unstructured protocol documents producing wrong or missing schedule rows, which would force founder time into manual setup and make the card untrustworthy on the first client.
Section 3 of 8

Pricing and monetization

First Card Setup

Entry offer
$49 one-time

For Practitioner who wants their first card built before committing to a subscription

  • Founder builds the first branded card from their existing protocol document
  • One revision pass
  • Credited toward month one if they subscribe within 14 days

Solo Protocol

$79 / month

For Owner-practitioner with up to 25 active protocol clients

  • Up to 25 active branded client cards
  • Tap-to-confirm adherence tracking
  • Weekly Monday Slipping List email
  • Logo and accent-colour branding
  • Self-serve cancel

Practice

$149 / month

For Practitioner or 2-3 person practice with up to 100 active clients

  • Up to 100 active branded client cards
  • Custom subdomain
  • Per-slot missed-dose breakdown
  • Archive and re-issue protocols for returning clients

Model: Monthly subscription per practitioner with a one-time setup fee as a de-risked front door; all charges by card, self-serve cancel.

First revenue offer: I'll build your next client's branded dose card from your existing protocol document by tomorrow, free — if your clients like it, card two onward is $79/month with a Stripe link in this thread.

Expected ACV: $79

Upsell path: Move Solo accounts to Practice at $149 when they pass 25 active clients or add a second practitioner; re-activate archived protocols for returning clients; add paid $49 setup builds as a standing front door for practitioners who will not self-serve.

Target customers
24
Revenue model
$1,896
Costs
$185
Profit model
$1,711
Section 4 of 8

First-customer acquisition

Primary channel

Hand-built direct Instagram/X DM and email outreach to 60 named practitioners whose public profiles advertise 1:1 multi-week supplement protocols.

Where to find them

  • Practitioner directories that publish practice name, website and contact email
  • Instagram accounts posting their own 6-12 week supplement protocol programs
  • X accounts of functional-medicine and nutrition practitioners linking to a booking page
  • Podcast guest pages for functional-medicine and nutrition shows
  • Local "aging in place" and nutrition-practice association member listings
  • Practitioners' own sites with a services page priced at $150-$600 per program

Exact outreach motions

  • Day 7: send 20 DMs leading with the free card, not the problem, and asking for their protocol document.
  • Day 8: build and deliver free cards within 24 hours of any reply, with their logo already applied.
  • Day 9: send the $79 Stripe link to the three warmest free-card practitioners in the same thread.
  • Day 10-11: day-three follow-up to non-openers with a 20-second screen recording of a tap plus the Monday email arriving.
  • Day 17-24: outreach waves three and four to reach 150 conversations, plus a peer intro request to every paying account.

Message template

Hi {first_name} — I noticed you run a {weeks}-week supplement protocol for clients. Most practitioners tell me clients go quiet around week three and they only find out at the renewal call. I built DoseDeck: a branded tap-to-confirm dose card at one link per client, plus a Monday email listing who's slipping and the nudge to send. I'll build your next client's card free, with your logo, by tomorrow — want it? Just send the protocol doc.
Week-one goal: 60 practitioners contacted, 8-12 replies, 5 free cards delivered, 2 paid subscriptions by day 9 and 4 by day 14.
Section 5 of 8

30-day execution roadmap

MVP deadline: day 5First sale target: day 930 days planned
Week 1 · Build & validate · 7 days
Day 1Foundation

Accounts and schema

  • Create Stripe account and connect it to TrustMRR before any payment can arrive.
  • Scaffold Next.js on Vercel with the Supabase schema.
  • Start the 60-practitioner list with the first 30 names.

Deliverable: Live repo, Stripe ready, 30 named prospects.

Day 2Protocol intake

Paste box plus parser

  • Build the protocol paste box with LLM parsing to JSON rows.
  • Add the editable row table with save.
  • Add 15 more names to the list.

Deliverable: A protocol saved as structured rows.

Day 3Client card

Public card and taps

  • Build the tokenized client card page with large tap targets.
  • Add the tap endpoint with dedupe.
  • Finish the list to 60 names.

Deliverable: A working branded card URL that records taps.

Day 4Practitioner view

Roster and adherence

  • Build the practitioner roster with add and archive client.
  • Add per-client adherence chart.
  • Wire Supabase magic-link auth.

Deliverable: Dashboard showing one client's adherence.

Day 5Revenue pathMVP shipped

Monday email plus Stripe

  • Build the Monday Slipping List email renderer and LLM nudge draft.
  • Integrate Stripe Checkout, webhook and 25-client cap.
  • Run one fake protocol end to end.

Deliverable: MVP live and chargeable.

Day 6Demo assets

Proof artifact

  • Build three demo cards from sample protocols.
  • Record a 20-second screen capture of a tap and the Monday email.
  • Write the DM and email templates.

Deliverable: Screen recording plus copy bank.

Day 7Outreach wave 1

First 20 messages

  • Send 20 DMs and emails with the free-card offer.
  • Log every send and reply in a sheet.
  • Fix any card-rendering bug found on mobile.

Deliverable: 20 conversations opened.

Week 2 · Launch & first sale · 7 days
Day 8Free card builds

Deliver artifacts

  • Build free branded cards for every replier within 24 hours.
  • Send 20 more messages.
  • Ask each free-card practitioner for their protocol doc format.

Deliverable: 3-5 live client cards in practitioners' hands.

Day 9First saleFirst sale target

Convert the warmest three

  • Send the $79 Stripe link in the three warmest threads.
  • Remove any checkout friction reported in the first attempt.
  • Post one public screen recording on X.

Deliverable: First paying practitioner.

Day 10Onboarding

Real first client

  • Onboard the first paying practitioner and build their card live.
  • Log every parser error into a fix list.
  • Send 20 more messages.

Deliverable: One live client tapping daily.

Day 11Follow-up

Non-openers

  • Send the day-three follow-up with the screen recording to all non-openers.
  • Fix the top two parser errors.
  • Add a copy button to the dashboard nudge.

Deliverable: Second-wave replies logged.

Day 12Branding

Make the card look owned

  • Ship logo, accent colour and practice name controls.
  • Add the "Built with DoseDeck" footer.
  • Request a written quote from the first practitioner with permission.

Deliverable: Fully branded client cards.

Day 13Outreach wave 2

Volume

  • Send 25 messages to the second half of the list.
  • Build free cards for all new repliers.
  • Confirm Stripe payouts land correctly.

Deliverable: 80 total conversations opened.

Day 14Week two review

Fix the top friction

  • Review reply rate by message variant and keep the winner.
  • Fix the highest-friction onboarding step.
  • Write the refund policy in one line.

Deliverable: Updated message template plus a fix shipped.

Week 3 · Repeat & systematize · 7 days
Day 15Practice tier

Higher price point

  • Add custom subdomain support and tier gating at 100 clients.
  • Add per-slot missed-dose breakdown view.
  • Send the $149 upgrade to any practitioner near 25 clients.

Deliverable: Practice tier purchasable.

Day 16Referral loop

Peer distribution

  • Confirm the footer renders on every client card.
  • Ask each paying practitioner for one peer introduction.
  • Add a request-a-card link to the footer page.

Deliverable: Referral path live.

Day 17Outreach wave 3

Reach 120

  • Send 25 messages including warm intros.
  • Deliver all outstanding free cards.
  • Publish one before/after card screenshot.

Deliverable: 120 conversations opened.

Day 18Nudge quality

Make the email actionable

  • Tighten the nudge prompt to one short, non-clinical sentence.
  • Add a copy button directly in the email.
  • Test the email on three real practitioners' inboxes.

Deliverable: Copyable nudge in the Monday email.

Day 19Cron rehearsal

Prove the weekly job

  • Run the Monday cron against real accounts and check delivery.
  • Fix timezone handling per practitioner.
  • Confirm the list is empty-state safe when everyone is on track.

Deliverable: Verified weekly email job.

Day 20Proof assets

Credibility without claims

  • Write a one-page explainer with the product screenshots.
  • Collect one practitioner quote with written permission.
  • Update the landing page with both.

Deliverable: Landing page with real product proof.

Day 21Week three review

Conversion push

  • Email every free-card practitioner who has not subscribed.
  • Confirm all paying accounts have at least one live client.
  • Check refund exposure and reply to every open thread.

Deliverable: Conversion status per prospect.

Week 4 · Scale what works · 6 days
Day 22Archive and reissue

Returning clients

  • Ship archive and re-issue protocol for returning clients.
  • Ask every paying account for a peer intro again.
  • Send 15 new first-touch messages.

Deliverable: Re-issue feature live.

Day 23Outreach wave 4

Reach 150

  • Send 25 messages to a freshly built list of 30.
  • Deliver all free cards within 24 hours.
  • Log objections and cluster them.

Deliverable: 150 total conversations.

Day 24Objection handling

Remove the top blocker

  • Rewrite the offer to address the top objection.
  • Ship the smallest feature that removes it.
  • Send the rewritten offer to all cold threads.

Deliverable: Revised offer in market.

Day 25Retention check

Does the Monday email work

  • Call every paying practitioner and ask if they sent a nudge.
  • Record which clients were recovered.
  • Remove anything in the email nobody reads.

Deliverable: Verified Monday email usage data.

Day 26Paid front door

The $49 setup fee

  • Offer the $49 First Card Setup to everyone who stalled.
  • Wire the one-time Stripe price and 14-day credit note.
  • Track setup-to-subscription conversion.

Deliverable: Setup fee selling.

Day 27Public content

Organic only

  • Post a full card-plus-Monday-email walkthrough on X and Instagram.
  • Reply to every comment with the free-card offer.
  • Skip paid ads unless reply rate is proven.

Deliverable: Public post plus inbound replies.

Days 29-30 · Consolidate · 3 days
Day 28Last-call conversion

Close the window

  • Send a final-call email to every free-card builder.
  • Confirm every new subscription charge settles before December 16.
  • Fix any payment failure personally.

Deliverable: Maximum collected revenue inside the window.

Day 29Freeze

No new features

  • Freeze the codebase and stop shipping features.
  • Reconcile Stripe charges against TrustMRR records.
  • Log refunds and any chargebacks.

Deliverable: Reconciled revenue ledger.

Day 30Close-out

Report and next month

  • Submit the final hackathon report with verified figures.
  • Write the month-two plan from actual churn and usage.
  • Email every account with one concrete improvement request.

Deliverable: Submitted report and month-two plan.

Section 6 of 8

Revenue and profit scenarios

How the numbers are defined

Hackathon profit — Collected revenue − refunds − chargebacks − payment processing fees − paid marketing spend.

Business profit — Hackathon profit − operating costs (hosting, domains, tooling, AI/API delivery costs).

The contest ranks entrants on hackathon profit only. Hosting, tooling and AI/API delivery costs are not deducted by the organisers, but each sale still has to cover them — so we show both. Definitions verified on 2026-11-15 against the official rules.

Stated assumptions

  • Conservative: 6 paying practitioners from 60 first-wave conversations at $79/month, no paid spend.
  • Base: 18 paying practitioners at $79/month, roughly 12% conversion across 150 conversations.
  • Upside: 35 paying accounts at a blended $85, reflecting a mix of $79 Solo and $149 Practice tiers.
  • All scenarios: payments via Stripe at 2.9% + $0.30 per charge, the fee used for payment_fees_usd.
  • All scenarios: ad_spend_usd is paid marketing only; all outreach is organic and free.
  • Operating cost covers Vercel, Supabase, Resend, one domain and LLM API usage for parsing and nudge drafting.
  • Refunds are modelled at most one $79 refund per scenario; chargebacks modelled at zero.
  • Every scenario keeps delivery cost per account far below the $79 price, so no sale is below cost.
  • These are projections for a hackathon entry, not verified revenue, customers or traction.

Conservative

6 customers
$474
collected revenue · avg payment $79
Refunds
$0
Chargebacks
$0
Payment fees
$16
Paid marketing
$0
Hackathon profit
$458
Operating costs
$40
Business profit
$418

Base case

18 customers
$1,422
collected revenue · avg payment $79
Refunds
$79
Chargebacks
$0
Payment fees
$47
Paid marketing
$60
Hackathon profit
$1,236
Operating costs
$95
Business profit
$1,141

Optimistic

35 customers
$2,975
collected revenue · avg payment $85
Refunds
$79
Chargebacks
$0
Payment fees
$97
Paid marketing
$150
Hackathon profit
$2,649
Operating costs
$180
Business profit
$2,469

Model your own numbers

Runs in your browser · nothing is saved
Collected revenue
$1,422
Payment fees (3.9%)
$55
Paid marketing
$60
Hackathon profit
$1,307
Business profit
$1,212

Hypothetical arithmetic, not a forecast. The fee rate is a flat 3.9% assumption, refunds and chargebacks are left at zero here, and none of this is tracked data.

Scenario models from stated assumptions, not verified revenue. All figures are projections for a hackathon entry.

Section 7 of 8

Main risks and validation experiments

Risk 1Cold DM and email outreach produces near-zero replies, leaving no first paying practitioner inside the window.

Mitigation

Lead the opening message with the free branded card rather than the problem, and deliver that card within 24 hours of any reply.

Validation experiment

Send 20 messages on day 7 and require at least 2 replies within 72 hours.

Kill criteria

If 60 messages and the day-three follow-up produce zero free-card requests by day 14, replace the channel with warm intros through practitioner communities.

Risk 2Practitioners treat the Monday Slipping List as noise and cancel after month one.

Mitigation

Keep the email to one screen, put the copy-ready nudge first, and only include clients below the adherence threshold.

Validation experiment

On day 25, ask every paying practitioner whether they actually sent a nudge from the list.

Kill criteria

If fewer than 3 of 5 paying practitioners sent a nudge in week one, the weekly email must become an in-dashboard alert before further sales.

Risk 3Clients ignore the tap-to-confirm card, so adherence data is sparse and the Slipping List looks wrong.

Mitigation

Cap the card at one screen per day with large targets, and show a streak strip so the client sees progress.

Validation experiment

Watch 5 real clients for 7 days and measure daily completion rate.

Kill criteria

If completion stays under 40% for two weeks, reduce the card to a single daily check-in before selling further accounts.

Risk 4LLM parsing of messy protocol documents produces wrong schedules and forces manual founder setup per client.

Mitigation

Ship the editable row table in the same build as the parser, and log every failed parse to a fix list.

Validation experiment

Run 10 real practitioner protocols through the parser and count rows needing more than two manual edits.

Kill criteria

If more than half of real protocols need more than five manual edits by day 20, add a structured intake form as the default path.

Risk 5Messaging drifts into clinical territory (interaction warnings, dosing advice) and creates exposure the founder cannot absorb.

Mitigation

Constrain the LLM prompt to scheduling and encouragement only, and strip any safety or dosing language before release.

Validation experiment

Review every drafted nudge and the landing-page copy against a written no-clinical-claims rule before each send.

Kill criteria

If a practitioner asks for interaction checking twice, decline and document it rather than adding the feature in the window.

Risk 6Client card links get forwarded or reused across family members, corrupting adherence numbers.

Mitigation

Use one opaque token per client, label the card with the client's first name, and allow the practitioner to reissue a token.

Validation experiment

Check tap timestamps per token for duplicate-day anomalies across the first 10 live cards.

Kill criteria

If more than 20% of live cards show multi-device anomalies, add an optional four-digit client PIN.

Section 8 of 8

Hour-by-hour: the first 24 hours

Hours 1-2

  • Create the Stripe account and connect it to TrustMRR per the rules.
  • Confirm no checkout link is live before launch.

Output: Connected payment account with zero customers.

Hours 3-5

  • Scaffold Next.js on Vercel.
  • Create the Supabase schema for practitioners, protocols, protocol_rows, clients, doses, plans.

Output: Deployed empty app with schema.

Hours 6-9

  • Build the protocol paste box.
  • Wire the LLM parser to return structured JSON rows.
  • Render the editable row table.

Output: A protocol parsed into editable rows.

Hours 10-14

  • Build the public card page at /c/[token].
  • Add the tap endpoint with per-slot dedupe.
  • Test on a real phone.

Output: A working branded dose card URL.

Hours 15-18

  • Build the practitioner roster with add and archive client.
  • Start the 60-name prospect list with 30 entries.

Output: Dashboard roster and 30 named prospects.

Hours 19-24

  • Deploy the full flow end to end with one fake protocol.
  • Write down every breakage for day two.
  • Draft the free-card DM and email.

Output: End-to-end demo plus a prioritised fix list.

Complete report

Full 30-day launch report

Read the full generated report

1. Product opportunity and positioning

DoseDeck Protocol Cards sells to one person: the owner-practitioner at a 1-3 person functional-medicine, nutrition or health-coaching practice who sells 6-12 week supplement protocols at $150-$600 per client and runs 10-60 active clients. Their protocol ends as a PDF and a promise. Around week three clients go quiet, the practitioner has no signal until the renewal call, and the renewal becomes a refund conversation. Manual "how's it going?" texts eat hours and still miss exactly the clients about to quit.

The wedge is deliberately non-clinical. DoseDeck does not interpret interactions, adjust doses or make recommendations. It does the two things a practitioner cannot do cheaply by hand: it renders the protocol as a branded, tap-to-confirm card at a unique link per client (no app install, no client login), and it mails a Monday Slipping List of who is behind, which slots they missed, and a pre-written nudge to copy and send.

Against the alternatives: a PDF is invisible after day one; a generic habit app is unbranded and returns no data to the practitioner; a practice-management suite costs more and solves scheduling, not adherence. DoseDeck is $79/month, self-serve, cancel-anytime, and produces a client-facing artifact the practitioner can show in the same session they buy it. No payer, pharmacy, employer or regulator sits between the founder and the card. The buyer's trigger event is concrete and recent: a client who quit a protocol mid-way and did not renew.

Why now: this buyer already sells a multi-week paid program, already charges cards, and already owns the protocol text. DoseDeck only adds the missing feedback loop, which makes adoption an edit to an existing workflow rather than a new behaviour.

The scored concept carries a JEV score of 64/100 (band C), with market demand the weakest criterion at 4.43 normalized. This plan compensates by narrowing outreach to practitioners whose public profiles visibly advertise 1:1 multi-week supplement protocols, i.e. people already selling the exact artifact DoseDeck wraps. Monetization potential (6.14), speed to first revenue (8.09) and solo build feasibility (7.57) are the strengths the 30 days lean on: one buyer, one card, one weekly email, card payment on day five.

2. Smallest sellable MVP

The sellable unit is one branded client dose card plus the Monday Slipping List. Minimum: paste a protocol, get an editable parsed table of supplement, dose, time slots and duration, save it, generate a tokenized client card URL that renders today's slots as large tap targets, store tap events, and email the practitioner one weekly list. Plus Stripe Checkout so money can arrive on day five, and a 25-active-client cap on the $79 tier. Anything outside that sentence waits.

3. Technical implementation plan

Next.js on Vercel serves both surfaces: the authenticated dashboard at /app and the public card at /c/[token]. Supabase Postgres holds practitioners, protocols, protocol_rows, clients, doses and plans, with magic-link auth for practitioners only — clients never authenticate, the token is the credential. One LLM call converts pasted protocol text into JSON rows for the editable table; a second call drafts the nudge from missed-slot data. Resend sends the Monday email; a Vercel Cron job runs at 07:00 practitioner-local, computes adherence and renders the list. Stripe Checkout and the Customer Portal handle subscription, tier gating and self-serve cancel. Build order: schema, auth, intake plus edit table, card renderer, tap endpoint, adherence rollup, cron email, Stripe gating, branding, subdomain. The hardest risk is parsing messy real protocol text into correct slots; the manual edit table is the release valve and ships in the same build as the parser.

4. Pricing and monetization

Three prices, all card-collectable without approval: $49 one-time First Card Setup (founder builds the card from the practitioner's existing document, credited toward month one if they subscribe within 14 days), $79/month Solo Protocol up to 25 active cards, $149/month Practice up to 100 cards with custom subdomain and per-slot missed-dose breakdown. Expected first-month ACV is $79. The $49 setup fee is the de-risked front door for practitioners who will not subscribe on a cold first touch; the $149 tier is the expansion path once a practice adds a second practitioner or passes 25 clients. No trials beyond the free first card, no annual plans, no discounts in the window.

5. First-customer acquisition

One channel: hand-built direct outreach to named practitioners. Build a list of 60 over days one and two from public practitioner directories that publish practice contact details, practitioner Instagram and X accounts posting their own multi-week protocol programs, and podcast guest pages for functional-medicine shows. Message angle: their clients go quiet around week three and they find out at renewal; offer one free branded card built within 24 hours. Convert on the second client — card one free, card two onward at $79/month with a Stripe link in the same thread. Day-three follow-up to non-openers with a 20-second screen recording. Every client card carries a one-line "Built with DoseDeck" footer so peers can request their own.

6. 30-day execution roadmap

Days 1-5 are build only, ending with a working end-to-end flow and Stripe live. Days 6-9 ship the demo assets and send the first 20 messages, with the first sale targeted for day 9. Days 10-14 are outreach wave two plus branding controls and the first real onboarding. Days 15-21 add the Practice tier, the referral footer and the nudge-quality pass, with a live cron rehearsal on day 19. Days 22-30 are conversion and retention: peer intros, the paid $49 front door, a public screen-recording post, and a day-30 reconciliation of Stripe against TrustMRR. Volume targets: 60 messages by day 7 and 150 conversations by day 24.

7. Revenue and profit scenarios

All three scenarios are projections built from the stated assumptions, not observed revenue. Conservative assumes 6 paying practitioners at $79 (about 8% of the first 60 conversations converting), no paid spend, $16 of Stripe fees and $40 of hosting, domain, email and LLM usage. Base assumes 18 accounts at $79, one refund and $60 of optional paid boosts. Upside assumes 35 accounts at a blended $85 (a mix of $79 and $149 tiers), one refund and $150 of paid boosts. The contest ranks hackathon profit, which deducts refunds, chargebacks, processing fees and ad spend but not hosting or inference; business profit then subtracts operating cost. Every scenario keeps delivery cost per account far below $79.

8. Main risks and validation experiments

First, cold DMs may produce near-zero replies. Test: 20 messages on day 7 requiring 2 replies within 72 hours; otherwise lead with the free card rather than the problem. Second, the Slipping List may read as noise. Test: ask the first five paying practitioners on day 25 whether they actually sent a nudge. Third, clients may not tap. Test: watch five real clients for seven days; if completion stays under 40%, collapse the card to a single daily check-in. Fourth, LLM parsing may fail on messy documents. Test: run ten real protocols through and count those needing more than two manual edits. Fifth, messaging may drift into clinical advice. Rule: any copy implying an interaction, dose change or safety claim is cut before release; the product stays a reminder and engagement tool.

9. First 24-hour action plan

Hours 1-2: create Stripe, connect to TrustMRR, confirm no payment can arrive before launch. Hours 3-5: scaffold Next.js on Vercel and create the Supabase schema. Hours 6-9: build the paste box and LLM parser to an editable row table. Hours 10-14: build the tokenized card page and tap endpoint, tested on a real phone. Hours 15-18: build the practitioner roster and start the 60-name list with 30 entries. Hours 19-24: deploy, run one fake protocol end to end, and log every breakage for day two.

This brief was generated from public data about established startups, then narrowed and scored for a solo 30-day launch. Revenue and profit figures are scenario models, not verified results, guarantees or evidence of existing customers. Validate demand yourself before you spend a month on it — and check the contest rules for what counts toward your score.

Related ideas

All ideas →