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

DoseNote Coach

DoseNote Coach turns a 12-question client intake into a white-labeled, citation-footnoted supplement plan PDF in under two minutes, so independent health coaches stop hand-writing plans in Google Docs.

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.07/10
MVP build (solo)
4 days
Launch price
$199
Sales to $1,000 revenue
6 customers
First paying customer
Direct Instagram DM to 300 solo health, nutrition and wellness coaches found by hashtag and certification-graduate directories, each offered one free branded plan from a real client intake before paying.
Who pays

Solo health, nutrition and wellness coaches and personal trainers running 1:1 or small-group programs (one-person businesses in the US, UK, Canada, Australia), triggered when a new client signs and a supplement plan is owed within about a week.

Biggest execution risk

Operational simplicity 3.8/10

Remove regulated data, human review steps and custom infrastructure; keep the product self-serve and stateless on managed services.

Why this could work in 30 days: one founder can ship the MVP in 4 days; the plan targets a first sale on day 10; 6 sales at $199 clears $1,000 of collected revenue; strongest signal is speed to first revenue at 8.2/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

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

0/18
Entry price
$199
Solo build
4 days
30d base revenue
$2,388
30d hackathon profit
$2,105
Section 1 of 8

Product opportunity and positioning

Target customer

Solo health, nutrition and wellness coaches and personal trainers running 1:1 or small-group programs (one-person businesses in the US, UK, Canada, Australia), triggered when a new client signs and a supplement plan is owed within about a week.

Why now

The coach already produces this exact document by hand, buys software alone with a card, and can be reached by a direct message this week, so no integration, procurement, inventory or marketplace cold-start stands between the pitch and the first $199.

Problem

One client plan takes 45-90 minutes of scattered searching, remembered dosing and manual formatting, so coaches either skip a paid upsell or recycle a generic template that ignores medications, pregnancy and stacking conflicts.

Solution

A hosted 12-question intake feeds a versioned deterministic rules engine (nutrient-gap mappings, stacking conflicts, upper-limit ceilings, referral-out triage) that emits templated sentences each bound to a numbered reference row, rendered as a branded 2-page PDF plus a shareable client page with an acknowledge button.

Differentiation · ChatGPT plus Canva returns an unversioned chat log with no dose ceilings, no do-not-stack block, no numbered citations, no referral-out flag and no audit trail; DoseNote Coach returns a fixed, versioned practitioner artifact under the coach's own logo and credentials.

Opportunity

A solo health, nutrition or wellness coach who sells 1:1 programs owes every new client a supplement plan inside the first week. That document is written by hand: searches, remembered dosing, a Google Doc with the coach's logo pasted at the top. Forty-five to ninety minutes per client, repeated on every signup, and the result is only as safe as the coach's memory of stacking conflicts and upper limits.

DoseNote Coach sells that afternoon back. The coach sends a hosted 12-question intake link. Two minutes later they have a 2-page plan under their own logo and credentials, with a numbered reference behind every sentence, explicit dose ceilings, a do-not-stack block, and a referral-out notice the moment the intake mentions medication, pregnancy or a diagnosed condition.

Who pays

The buyer is one person running a one-person practice, already charging for 1:1 coaching, already producing this exact artifact manually. They buy software alone with a card, they have no procurement cycle, and they are identifiable today by hashtag and by certification-graduate directories. The buying trigger is concrete and recurring: a new client signs and a plan is owed.

Positioning

The product is a document workflow, not a chat assistant. The output is a fixed, versioned artifact: every plan records the rules version used, so the coach can defend the document weeks later. The generic alternative, ChatGPT plus Canva, produces a chat log with no binding, no ceiling logic, no citation rows and no practitioner framing, and the coach still has to assemble and re-check it by hand.

Two design choices carry the positioning. First, sentences are templated and each must bind to a numbered reference row, with generation hard-blocked when binding is missing, so the plan cannot invent claims. Second, the referral-out path is deliberately conservative: medication, pregnancy or a diagnosed condition stops the nutrient advice and produces a refer-out notice instead of a guess.

Why it is believable in 30 days

JEV scored this exact concept 60.7/100 (band C, confidence 0.71). Speed to first revenue is the strongest criterion at 8.18 normalized; operational simplicity is the weakest at 3.82. The plan answers that weakness directly: serverless hosting, a rules table in Postgres, no human review step, no lab or wearable parsing, no supplement inventory, no client-facing accounts. Delivery cost per plan is fractions of a cent of API spend plus hosting.

Scope discipline

The narrow wedge is the whole product for 30 days: self-reported intake in, branded cited PDF and share link out. No blood tests, no DNA, no wearables, no biomarker ranges, no supplement sales, no affiliate links, no mobile app, no EHR or booking integrations, no team seats. Every one of those would add regulated data or custom infrastructure and would slow the only thing that matters in the window: 300 direct conversations and 20 paid licenses.

Section 2 of 8

Smallest sellable MVP

A coach uploads a logo, sends a hosted 12-question intake link, and gets a branded, citation-footnoted 2-page PDF plus a shareable client page in under two minutes, gated by a $199 Stripe license.

Must-have features

  • Hosted 12-question per-client intake link with answer editing and last-updated timestamp
  • Deterministic JSON rules engine: 60 nutrient-gap mappings, 40 stacking conflicts, upper-limit ceilings, referral-out triage
  • Rules version stamped on every generated plan
  • Templated narrative generator with a hard block on sentences lacking a numbered reference binding
  • White-label kit: logo upload, two brand colors, coach name, credentials, editable disclaimer footer
  • 2-page PDF render plus shareable web plan with an acknowledge button
  • Coach dashboard: client list, item add/remove with audit log, one-click regenerate
  • Stripe Checkout license gate with per-account plan counter

Explicitly out of scope

  • Blood test, DNA or wearable file parsing and biomarker range interpretation
  • Supplement sales, affiliate links, cart hand-off or inventory
  • Mobile app, client-facing accounts, chat assistant
  • EHR, practice-management or booking-tool integrations
  • Team seats, multi-practitioner clinics, enterprise procurement
  • Advice on prescription medications or dosing for diagnosed conditions
  • Custom rules authoring UI for coaches
  • Multi-language output

Demo flow (what the buyer sees)

  1. Coach signs in and uploads a logo plus two brand colors.
  2. Coach creates a client and copies the generated intake link.
  3. Client answers 12 questions, including medication, pregnancy and condition flags.
  4. Rules engine scores answers and stamps the rules version.
  5. Templated narrative binds each rule hit to a numbered reference row.
  6. Referral-out block is injected if any red flag was answered.
  7. 2-page PDF renders with logo, credentials and disclaimer; shareable page is created.
  8. Coach edits one item, regenerates, sends the PDF and share link to the client.
Build plan

Technical implementation plan

Stack

Next.js on VercelSupabase Postgres, auth and storage for logosRules JSON served from Postgres with explicit rules_version rowsOpenAI or Anthropic API used only to select among fixed sentence templatesReact-PDF for the 2-page renderResend for intake and delivery emailStripe Checkout with Stripe Tax offTrustMRR-connected payment account from day one

Architecture

A Next.js app on Vercel talks to Supabase for auth, client records, intake answers, generated plans and logo storage. The rules engine is pure TypeScript reading a versioned JSON table from Postgres: it takes intake answers and returns an array of rule hits plus a referral_out boolean. A narrative layer maps each hit to exactly one pre-written sentence template bound to a reference row ID; if a hit has no binding the render aborts rather than emitting free text. The LLM is only allowed to pick among registered template variants, never to author claims. React-PDF renders the fixed 2-page layout, and the same plan data renders as a shareable HTML page with an acknowledge button. Stripe Checkout gates plan generation behind a validated license; every plan row stores rules_version, engine output JSON and a version history so regeneration is auditable.

Build steps

  1. Scaffold Next.js, Supabase auth and schema (clients, intakes, plans, rules_versions, licenses).
  2. Author rules_v1.json: 60 nutrient-gap mappings, 40 conflicts, ceilings, red-flag triage.
  3. Build the 12-question intake with conditional red-flag branching and per-client slug.
  4. Implement the scoring function and unit-test it against 10 canned intakes.
  5. Write the sentence template library with mandatory reference bindings and a bind-check assertion.
  6. Render the 2-page React-PDF layout including ceilings, do-not-stack block and referral-out notice.
  7. Add the branding kit: logo upload to Supabase storage, colors, credentials, disclaimer footer.
  8. Build the shareable client page with acknowledge button and version history list.
  9. Wire Stripe Checkout license gating and the per-account plan counter.
  10. Add Resend delivery emails and run end-to-end timing under two minutes.

AI components

  • LLM used only to choose among registered sentence-template variants for a rule hit, never to author free text
  • Optional LLM pass that rewrites nothing but flags ambiguous intake answers for coach review
  • No OCR, no biomarker interpretation, no model trained on client data
Hardest technical risk: Keeping the templated narrative from drifting into unbound or overconfident phrasing, which is enforced by a bind-check assertion that blocks the render and a regression suite over 10 canned intakes.
Section 3 of 8

Pricing and monetization

Founding Coach License

Entry offer
$199 one-time

For Solo coaches who want to lock in the launch price during the hackathon window

  • 12 months of access, unlimited client plans
  • White-label branding kit
  • Branded 2-page PDF plus shareable client page
  • Editable item list with audit log and regeneration
  • Rules-version stamp on every exported plan

Coach Monthly

$39 / month

For Coaches who want to try it without a year commitment after the launch window

  • Up to 15 client plans per month
  • White-label branding kit
  • Shareable client page with acknowledge button

Model: A $199 one-time Founding Coach License during the 30-day window, moving to a $39/month plan after the first 30 licenses.

First revenue offer: I built a tool that turns your 12-question client intake into a branded, cited 2-page supplement plan in about two minutes. Send me one real client intake and I will build the plan free under your logo today. If it saves you the afternoon, the Founding Coach License is $199 for 12 months, unlimited plans, and the price goes to $39/mo after the first 30 licenses.

Expected ACV: $199

Upsell path: After the window, convert founding buyers to the $39/mo plan at renewal, sell the monthly tier to fence-sitters who will not prepay a year, and layer later paid add-ons (extra practitioner seats, custom rule packs) only after validated demand.

Target customers
20
Revenue model
$3,980
Costs
$210
Profit model
$3,770
Section 4 of 8

First-customer acquisition

Primary channel

Direct Instagram DM to 300 solo health, nutrition and wellness coaches found by hashtag and certification-graduate directories, each offered one free branded plan from a real client intake before paying.

Where to find them

  • Instagram hashtags #healthcoach, #nutritioncoach and #onlinenutritioncoach
  • Coaches whose link-in-bio sells a 1:1 program with an apply or work-with-me page
  • Certification-graduate directories that publish practitioner names and sites
  • Personal trainers advertising online 1:1 programs rather than in-person only
  • Build-in-public founders posting coaching-client onboarding content

Exact outreach motions

  • DM 20 coaches day 7 offering to build one free branded plan from a real client intake.
  • Deliver each free plan within 24 hours with the coach's own logo on page 1.
  • Send the $199 Stripe link only after a finished sample is in their hands.
  • Follow up day 2 with the finished sample and day 6 with the price-deadline note.
  • Publish one build-in-public post per day with a redacted plan page so inbound DMs have something to click.
  • Log every send, variant and reply; cut the weaker variant at day 14.

Message template

You sell 1:1 coaching, so you probably hand-write the supplement plan for every new client. I built a tool that turns a 12-question intake into a branded, cited 2-page PDF in about two minutes. Want me to build one free for a real client of yours, under your own logo?
Week-one goal: 120 qualified coaches on the list, 20 DMs sent, at least 3 replies and 2 free plans delivered.
Section 5 of 8

30-day execution roadmap

MVP deadline: day 5First sale target: day 1030 days planned
Week 1 · Build & validate · 7 days
Day 1Scaffold and rules table

Running skeleton plus curated rules JSON.

  • Create the Next.js and Supabase repo with auth and a plans table.
  • Transcribe 60 nutrient-gap mappings, 40 stacking conflicts and ceilings into rules_v1.json.
  • Add a rules_version column so every plan records what it used.
  • Open Stripe in test mode and draft the $199 product.

Deliverable: rules_v1.json committed and the app running locally.

Day 2Intake link

A hosted 12-question link that saves and edits answers.

  • Build the 12 questions with conditional red-flag branching.
  • Generate a per-client slug with edit and last-updated timestamp.
  • Send the link by email through Resend.
  • Write 10 canned test intakes covering normal, pregnant, medicated and blank cases.

Deliverable: Live shareable intake link with saved answers.

Day 3Rules engine

Deterministic, versioned rule hits.

  • Implement scoring that maps answers to rule hits.
  • Implement conservative referral-out triage for medication, pregnancy and diagnosed conditions.
  • Run the 10 canned intakes and diff outputs against expected hits.
  • Store engine output JSON and rules_version per plan.

Deliverable: Engine producing reproducible rule hits on 10 intakes.

Day 4Narrative and PDF

Templated sentences bound to numbered references.

  • Write one sentence template per rule hit, each bound to a reference row.
  • Hard-block generation when a sentence has no binding.
  • Render the 2-page React-PDF with ceilings and a do-not-stack block.
  • Hand-check 5 outputs for phrasing drift.

Deliverable: 2-page PDF generated from any intake.

Day 5Sellable MVPMVP shipped

Branding, share page and the Stripe gate.

  • Add logo upload, two colors, credentials and disclaimer footer.
  • Ship the shareable client page with an acknowledge button.
  • Gate plan generation behind a Stripe license check.
  • Run one end-to-end plan and time it under two minutes.

Deliverable: MVP ready to sell on day 5.

Day 6Coach list v1

120 qualified handles on a sheet.

  • Collect 120 solo coaches from the three hashtags.
  • Log handle, program price, link-in-bio type and 1:1 signal.
  • Write DM variants A and B.
  • Pick the first 20 to message.

Deliverable: Outreach sheet with 120 qualified handles.

Day 7First sends

20 DMs out with replies logged.

  • Send 20 DMs offering one free branded plan.
  • Log every send with date and variant.
  • Reply to every response within 2 hours.
  • Post build-in-public screenshot of a redacted plan page.

Deliverable: 20 DMs sent, at least 3 replies logged.

Week 2 · Launch & first sale · 7 days
Day 8Free sample delivery

Finished plans in coaches' hands.

  • Generate free plans for every coach who replied with an intake.
  • Return the PDF plus client share link within 24 hours.
  • Send 15 new DMs.
  • Write down the three most common objections.

Deliverable: 3-5 delivered sample plans with coach logos.

Day 9Objection handling

Pitch rewritten in the buyer's own words.

  • Rewrite the DM and sample email using real objection wording.
  • Add a one-screen how-the-citations-work page.
  • Send 15 DMs.
  • Send the day-2 follow-up on unanswered samples.

Deliverable: Revised pitch plus citations explainer page.

Day 10First revenueFirst sale target

Convert a finished sample into a paid license.

  • Send the $199 Stripe link to every coach holding a finished sample.
  • Send 15 DMs.
  • Confirm the charge lands in the TrustMRR-connected account.
  • Log the sale with date and source.

Deliverable: First paid Founding Coach License.

Day 11Self-serve check

A paying coach generates a plan alone.

  • Watch one paying coach generate their own plan.
  • Fix the first bug they hit.
  • Add a per-account plan counter to the dashboard.
  • Send 15 DMs and post build-in-public post 2.

Deliverable: Paying coach self-served one plan without help.

Day 12Referral-out hardening

Safety framing shipped to every plan.

  • Add an explicit referral-out block to the PDF template.
  • Add an editable not-medical-advice footer variant.
  • Send 15 DMs.
  • Send the day-6 price-deadline follow-up to all samples.

Deliverable: Hardened disclaimers live on all generated plans.

Day 13List expansion

180 handles and per-variant reply rates.

  • Add 60 more coaches to the sheet.
  • Send 15 DMs.
  • Reply to all open threads.
  • Record reply rate per variant.

Deliverable: List at 180 handles with variant reply rates.

Day 14Week 2 review

Funnel numbers and one decision.

  • Compute DMs sent, replies, samples, sales and cash collected.
  • Cut the weaker DM variant.
  • Fix the top friction point in plan generation.
  • Send 15 DMs.

Deliverable: Week-2 funnel note and a single decision.

Week 3 · Repeat & systematize · 7 days
Day 15Editing audit

Auditable item edits and version history.

  • Add an audit log on item add/remove.
  • Show version history per client.
  • Send 15 DMs.
  • Ask two paying coaches what would make them renew.

Deliverable: Audited editing plus renewal notes.

Day 16Onboarding polish

Remove every hesitation step.

  • Watch one paying coach generate a plan live.
  • Remove each step they hesitated on.
  • Send 15 DMs.
  • Reply within 2 hours to all threads.

Deliverable: Onboarding blockers trimmed to zero.

Day 17Proof surface

Public gallery of redacted plans.

  • Publish three redacted sample plans as a gallery page.
  • Link the gallery in the DM.
  • Send 15 DMs.
  • Post build-in-public post 3.

Deliverable: Public sample gallery live and linked.

Day 18Directory channel

Test a second sourcing channel.

  • Pull 60 coaches from certification-graduate directories.
  • Add them to the sheet.
  • Send 15 DMs.
  • Compare reply rate with the hashtag list.

Deliverable: Two-channel reply-rate comparison.

Day 19Fix and refer

Layout fix plus organic referral asks.

  • Fix the top PDF layout complaint.
  • Send 12 DMs.
  • Ask each paying coach for one organic intro.
  • Log referrals separately from cold DMs.

Deliverable: Layout fix shipped and referral asks sent.

Day 20Midpoint check

Cash versus the base scenario.

  • Recompute collected revenue and hackathon profit to date.
  • Compare against the base projection.
  • Send 12 DMs.
  • Decide whether to open the $39 monthly link early.

Deliverable: Midpoint projection check and tier decision.

Day 21Refund policy

Payment hygiene.

  • Publish a plain refund and chargeback policy page.
  • Add it to checkout and the delivery email.
  • Send 12 DMs.
  • Send day-6 follow-ups to every warm thread.

Deliverable: Refund policy live, zero open payment disputes.

Week 4 · Scale what works · 7 days
Day 22Monthly tier

Offer a low-commitment entry.

  • Open the $39/mo Checkout for fence-sitters.
  • Send 12 DMs.
  • Answer try-one-plan objections with the monthly link.
  • Post build-in-public post 4.

Deliverable: Second checkout live and first monthly attempt made.

Day 23Honest scarcity

Real license count in public.

  • Post the real founding-license counter, no invented scarcity.
  • Send 12 DMs.
  • Follow up every sample delivered seven or more days ago.
  • Fix one bug from support threads.

Deliverable: Public counter post and follow-up wave complete.

Day 24Second segment

Test personal trainers with online 1:1 programs.

  • Message 12 trainers with training-load framing.
  • Adapt the DM wording.
  • Log replies as a new segment signal.
  • Reply to all open threads.

Deliverable: Segment test result recorded.

Day 25Content

A 60-second intake-to-PDF clip.

  • Record a screen capture from intake to finished PDF.
  • Send 12 DMs.
  • Put the clip in the landing page hero.
  • Fix any intake drop-off visible in logs.

Deliverable: Demo clip live on the landing page.

Day 26Reliability

Regression on the rules engine.

  • Add an error banner and retry for failed renders.
  • Regression-test 10 intakes against expected rule hits.
  • Send 12 DMs.
  • Document the rules_version bump process.

Deliverable: Regression suite green on 10 intakes.

Day 27Feedback loop

Ship the most requested in-scope fix.

  • Send a 4-question survey to every paying coach.
  • Send 12 DMs.
  • Implement the top requested fix that fits MVP scope.
  • Post build-in-public post 5.

Deliverable: Survey results and one shipped request.

Day 28Payment reconciliation

Clean ledger and finished list.

  • Reconcile every Stripe charge against the TrustMRR dashboard.
  • Refund anything that looks like a mistake immediately.
  • Send the final 7 DMs to reach 300.
  • Confirm no customer or payment existed before launch.

Deliverable: Reconciled ledger and all 300 coaches messaged.

Days 29-30 · Consolidate · 2 days
Day 29Final close

Close every warm thread.

  • Send a one-line deadline note to all warm threads.
  • Keep Checkout live through the window close.
  • Answer objections within one hour.
  • Post the closing-hours note.

Deliverable: Every warm thread closed or declined.

Day 30Wrap

Verified numbers, published.

  • Tally collected revenue, refunds, fees and verified hackathon profit.
  • Export a usage and rules-version report for buyers.
  • Publish the build-in-public recap with real numbers only.
  • Write the post-window plan for the $39/mo tier.

Deliverable: Verified profit tally and public recap.

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

  • All figures are projections from stated assumptions, not verified revenue or existing customers.
  • Base assumes roughly 300 DMs to solo coaches, about 70 replies, about 25 free sample plans delivered and 12 paid licenses inside the window.
  • Conservative assumes the DM channel underperforms badly: 3 paid licenses from the same outreach effort.
  • Upside assumes the reply rate holds and the day-2/day-6 follow-ups convert sample holders at the upper end: 20 paid licenses.
  • ARPU is the $199 Founding Coach License in all three scenarios; the $39/mo tier is treated as post-window upside and is not counted.
  • Payment processing assumed at about 3.5% blended (Stripe card pricing) on collected revenue.
  • Paid marketing is $0 in conservative and base; organic DM outreach and build-in-public posts cost nothing. Upside assumes $120 on boosting the best build-in-public post.
  • Operating costs cover Vercel, Supabase, a domain, Resend and API spend of roughly $0.30 per generated plan.
  • One refund is assumed in base and upside (a coach who never uses the license); chargebacks assumed at zero because buyers self-serve with a card and a plain refund policy is published on day 21.
  • Hackathon profit excludes hosting, tooling and API delivery costs per the contest rules; business profit deducts them.

Conservative

3 customers
$597
collected revenue · avg payment $199
Refunds
$0
Chargebacks
$0
Payment fees
$21
Paid marketing
$0
Hackathon profit
$576
Operating costs
$18
Business profit
$558

Base case

12 customers
$2,388
collected revenue · avg payment $199
Refunds
$199
Chargebacks
$0
Payment fees
$84
Paid marketing
$0
Hackathon profit
$2,105
Operating costs
$45
Business profit
$2,060

Optimistic

20 customers
$3,980
collected revenue · avg payment $199
Refunds
$199
Chargebacks
$0
Payment fees
$139
Paid marketing
$120
Hackathon profit
$3,522
Operating costs
$70
Business profit
$3,452

Model your own numbers

Runs in your browser · nothing is saved
Collected revenue
$2,388
Payment fees (3.9%)
$93
Paid marketing
$0
Hackathon profit
$2,295
Business profit
$2,250

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 built from the stated assumptions. They are projections, not verified revenue, existing customers or real traction. Reaching the $100K contest ceiling at $199 per license would require roughly 500 licenses in 30 days, which is not projected here.

Section 7 of 8

Main risks and validation experiments

Risk 1Scope-of-practice and liability exposure: a wrong ceiling or missed interaction could harm a client and the coach.

Mitigation

Conservative referral-out triage, an explicit do-not-stack block, a practitioner-use disclaimer footer, and no advice on prescription medications or diagnosed conditions.

Validation experiment

Show the referral-out plan and the disclaimer footer to 5 target coaches and ask whether it makes them more or less willing to send the document to a client.

Kill criteria

If 3 or more of 5 coaches say they would not send a rules-generated plan to a client even with citations and referral-outs, stop and rethink the artifact.

Risk 2Instagram DM outreach is rate-limited, lands in request folders, or reads as spam, collapsing the only channel.

Mitigation

Log every send, vary two message angles, cap volume near 15 per day, reply within 2 hours, and use the free-sample offer instead of a link in the first message.

Validation experiment

Send 20 DMs on day 7 and measure reply rate; if under 5 replies, rewrite the message and test 20 more before scaling.

Kill criteria

Fewer than 3 replies from the first 40 DMs means the channel is not viable at this volume; switch to directory and community outreach or stop.

Risk 3The templated narrative drifts into unbound or overconfident phrasing as templates are added.

Mitigation

A bind-check assertion that blocks the render when a sentence has no numbered reference, plus a 10-intake regression suite run on every rules change.

Validation experiment

Regenerate 10 canned intakes after every template edit and read every sentence for claims without a reference row.

Kill criteria

Any shipped plan containing an uncited claim is treated as a release blocker; two escapes in a week stops new template work until the suite covers them.

Risk 4Coaches decide free ChatGPT output is good enough once they see the artifact is a document, not a service.

Mitigation

Lead with the version stamp, dose ceilings and referral-out flag, which a chat log cannot provide, and let the coach compare a ChatGPT draft against a DoseNote plan side by side.

Validation experiment

Ask every sample recipient directly whether they would keep using ChatGPT for this and why; record the answer verbatim.

Kill criteria

If more than half of sample recipients say they will keep hand-writing or using ChatGPT and none pay by day 20, the artifact is not differentiated enough.

Risk 5Low willingness to pay because coaches enjoy plan writing as a sales ritual rather than treating it as overhead.

Mitigation

Price at one afternoon's value, offer 12 months for a one-time $199, and open the $39/mo tier by day 22 for commitment-averse buyers.

Validation experiment

Send the $199 link to every sample holder by day 10 and count how many ask for a lower-commitment monthly option instead.

Kill criteria

Zero paid licenses by day 14 with 10 or more samples delivered means the price or the buyer is wrong.

Risk 6A single visible accuracy error shared in a coach community ends the launch early.

Mitigation

Weekly manual read of every generated plan, a plain refund policy published on day 21, and immediate refunds on any disputed plan.

Validation experiment

Manually audit 5 generated plans per week against the rules table, recording every mismatch.

Kill criteria

Two confirmed dose or conflict errors in shipped plans pauses sales until the rules table and the regression suite are fixed.

Section 8 of 8

Hour-by-hour: the first 24 hours

Hours 1-2

  • Create the Next.js and Supabase repo, auth and the clients/intakes/plans tables.
  • Open the Stripe account and confirm it is the account connected to TrustMRR from launch.
  • Register the domain and deploy an empty landing page.

Output: Deployed skeleton, live payment account, domain resolving.

Hours 3-6

  • Write rules_v1.json: 60 nutrient-gap mappings, 40 stacking conflicts, upper-limit ceilings.
  • Add the red-flag triage list for medication, pregnancy and diagnosed conditions.
  • Commit with a rules_version tag.

Output: rules_v1.json in the repo with a version stamp.

Hours 7-10

  • Build the 12-question intake with conditional branching and a per-client slug.
  • Wire save, edit and last-updated timestamp.
  • Write 10 canned test intakes.

Output: Working intake link plus a test corpus.

Hours 11-14

  • Build the coach list from #healthcoach, #nutritioncoach and #onlinenutritioncoach.
  • Log handle, program price and 1:1 signal for the first 60 coaches.
  • Draft DM variants A and B.

Output: 60-handle outreach sheet and two message variants.

Hours 15-20

  • Implement the scoring function and run it against the 10 canned intakes.
  • Write the first 20 sentence templates bound to numbered reference rows.
  • Add the bind-check assertion that blocks unbound sentences.

Output: Engine plus template library returning cited rule hits.

Hours 21-24

  • Render a first 2-page PDF with a placeholder logo and the disclaimer footer.
  • Time the intake-to-PDF path end to end.
  • Send DM variant A to the first 15 coaches.

Output: First rendered plan PDF, timing number, 15 DMs out.

Complete report

Full 30-day launch report

Read the full generated report

DoseNote Coach — 30-Day Public Report

1. Product opportunity and positioning

Solo health, nutrition and wellness coaches sell 1:1 programs and owe each new client a supplement plan inside the first week. Today they write it by hand: scattered searching, remembered dosing, a Google Doc with a logo pasted on top. Forty-five to ninety minutes per client, repeated on every signup, and the result is only as safe as the coach's memory of stacking conflicts and dose ceilings.

DoseNote Coach sells that afternoon back. The coach sends a hosted 12-question intake. Two minutes later they hold a 2-page plan under their own logo and credentials, with a numbered reference behind every sentence, explicit dose ceilings, a do-not-stack block and a referral-out notice whenever the intake mentions medication, pregnancy or a diagnosed condition.

The positioning is a document workflow, not a chatbot. The output is a fixed, versioned artifact that records the rules version it used, so the coach can defend it weeks later. The generic alternative, ChatGPT plus Canva, returns a chat log with no binding, no ceilings, no citation rows and no audit trail, and the coach still has to assemble and re-check it.

JEV scored this exact concept 60.7/100 (band C, confidence 0.71). Speed to first revenue is strongest at 8.18 normalized; operational simplicity is weakest at 3.82. The plan answers that directly: serverless hosting, a rules table in Postgres, no human review, no lab or wearable data, no supplement inventory, no client accounts.

2. Smallest sellable MVP

Logo upload, hosted intake link, rules engine, templated cited narrative, 2-page PDF, shareable client page with acknowledge button, dashboard with audited item edits, and a Stripe license gate. That is the whole product for 30 days. Explicitly excluded: blood tests, wearables, biomarker ranges, supplement sales, affiliate links, mobile app, EHR or booking integrations, team seats, and any advice on prescription medications.

3. Technical implementation plan

Next.js on Vercel with Supabase for auth, Postgres and logo storage. The rules engine is pure TypeScript reading a versioned JSON table: intake answers in, an array of rule hits plus a referral_out boolean out. Each hit maps to exactly one registered sentence template bound to a numbered reference row; if the binding is missing the render aborts instead of emitting prose. The LLM only selects among registered template variants and never authors claims. React-PDF renders the fixed 2-page layout; the same plan data renders as the shareable page. Stripe Checkout gates generation; every plan row stores rules_version, engine output JSON and version history.

The hardest technical risk is narrative drift into uncited or overconfident phrasing. It is controlled by a bind-check assertion plus a 10-intake regression suite run on every template or rules change.

4. Pricing and monetization

Founding Coach License: $199 one-time for 12 months and unlimited plans, sold only during the window. Coach Monthly: $39/month, opened around day 22 for buyers who will not prepay a year. The offer logic is simple: one saved afternoon of client work pays for the license, so the price is defended against the artifact, not against software budgets. Renewal revenue after the window is the real business; the window exists to buy 20 references and a rules table that has survived real client intakes.

5. First-customer acquisition

One channel: direct Instagram DM to 300 solo coaches identified by three hashtags and by certification-graduate directories. The first message offers a free branded plan built from a real client intake, delivered within 24 hours with the coach's own logo on page 1. Only after a finished sample is in hand does the $199 link get sent. Follow-up runs on day 2 with the finished sample and day 6 with the price-deadline note. Every send is logged by variant; the weaker variant is cut at day 14.

6. 30-day execution roadmap

Days 1-5 build and ship the sellable MVP: rules table on day 1, intake link on day 2, engine on day 3, PDF on day 4, branding and Stripe gate on day 5. Days 6-7 build the 120-handle list and send the first 20 DMs.

Days 8-14 are delivery and conversion: free plans for every reply, objection-driven pitch rewrites, the first $199 sale targeted for day 10, referral-out hardening, and a week-2 funnel review that cuts the losing variant.

Days 15-21 are proof and polish: audited editing and version history, live observation of a paying coach, a public gallery of three redacted plans, a directory-sourced second list, a refund policy, and a midpoint check of cash against the base projection.

Days 22-28 open the $39 monthly tier, publish the real license counter, test personal trainers as a second segment, ship the demo clip, run the regression suite, close the survey loop and reconcile every charge against the payment dashboard while finishing all 300 DMs.

Days 29-30 close every warm thread and publish verified numbers only.

7. Revenue and profit scenarios (projections only)

Every figure below is a projection from stated assumptions, not verified revenue or existing customers. ARPU is $199 in all three cases.

ScenarioLicensesGross revenueRefundsFeesAd spendOperatingHackathon profitBusiness profit
Conservative3$597$0$21$0$18$576$558
Base12$2,388$199$84$0$45$2,105$2,060
Upside20$3,980$199$139$120$70$3,522$3,452

Hackathon profit is collected revenue minus refunds, chargebacks, payment fees and paid marketing. Business profit additionally subtracts hosting, tooling and API delivery cost. Reaching the $100K contest ceiling at $199 would need roughly 500 licenses in 30 days, which is not projected. The realistic target is 12 licenses and about $2.1K of hackathon profit, with the rules table and 12 paying coaches as the durable asset.

8. Main risks and validation experiments

Scope-of-practice exposure is the first risk: a wrong ceiling or a missed interaction harms a client and the coach. Mitigation is conservative referral-out triage, a visible do-not-stack block and a practitioner-use disclaimer. Test it by showing the referral-out plan to five coaches and asking whether it makes them more or less willing to send it.

The single acquisition channel is the second risk. Twenty DMs on day 7 measure whether the channel works at all; fewer than three replies from the first forty means rewrite or abandon the channel.

Narrative drift is the third: the bind-check assertion and the 10-intake regression suite are the control, and any shipped uncited claim is a release blocker.

The fourth is indifference: coaches may prefer free ChatGPT output. Every sample recipient is asked directly whether they would keep using ChatGPT and why, and the answer is recorded verbatim.

The fifth is price rejection. Sending the $199 link to every sample holder by day 10 and counting requests for a monthly option surfaces that early; zero licenses by day 14 with ten or more samples delivered means the price or the buyer is wrong.

9. First 24-hour action plan

Hours 1-2: repo, Supabase schema, Stripe account connected to TrustMRR, domain with a placeholder landing page. Hours 3-6: rules_v1.json with 60 mappings, 40 conflicts and ceilings, tagged with a version. Hours 7-10: the 12-question intake with branching, save and edit, plus 10 canned test intakes. Hours 11-14: the first 60 coaches on the outreach sheet and two DM variants. Hours 15-20: scoring function, first 20 bound sentence templates and the bind-check assertion. Hours 21-24: first rendered 2-page PDF, an end-to-end timing number, and 15 DMs sent.

Every number in this report is a hypothesis until a card is charged. The only verified metrics that matter are DMs sent, samples delivered, dollars collected and refunds issued.

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 →