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

Practice Ticket Studio

Generates a printable one-page weekly 'practice ticket' — measure ranges, tempo ladder, and a QR-linked student page — for private instrument teachers, so every student leaves the lesson knowing exactly what to practice.

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.17/10
MVP build (solo)
5 days
Launch price
$79
Sales to $1,000 revenue
13 customers
First paying customer
Direct outreach to named private instrument teachers in Facebook groups and public state/provincial association member directories, led by a finished sample ticket.
Who pays

Solo private instrument teachers and 2-3 teacher studios (piano, guitar, voice, strings, winds) with 15-60 weekly students, selling lessons direct-to-parent, mostly US/UK/CA/AU.

Biggest execution risk

Market demand 4.5/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 5 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.3/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

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

0/10
Entry price
$79
Solo build
5 days
30d base revenue
$996
30d hackathon profit
$963
Section 1 of 8

Product opportunity and positioning

Target customer

Solo private instrument teachers and 2-3 teacher studios (piano, guitar, voice, strings, winds) with 15-60 weekly students, selling lessons direct-to-parent, mostly US/UK/CA/AU.

Why now

The artifact already exists and is already made by hand weekly, so the teacher only swaps pen for generator; a one-time $79 license needs no procurement, and December recital prep makes assignment instructions high-stakes.

Problem

Teachers hand-write per-student assignment notes every week in 10-20 minutes per student; parents cannot read the shorthand, students lose the page, and the next lesson is spent re-teaching the assignment instead of technique.

Solution

Teacher enters a piece plus student level and daily minutes; the app produces a five-day practice ladder (segmented bars, tempo ramp, hands-separate to hands-together), renders a branded one-page PDF with checkboxes and a signature line, and links a tokenized QR student page with day check-offs and a tap metronome.

Differentiation · Notation, worksheet and studio-management tools store repertoire, invoices or generic exercises; none emits the per-student, per-week assignment handover that gets printed and signed.

Practice Ticket Studio — 30-Day Launch Report

1. Product opportunity and positioning

Practice Ticket Studio sells a back-office artifact to a professional buyer. Private instrument teachers already spend 10-20 minutes per student per week writing assignment shorthand into a notebook ('bars 12-24, hands separate, 72 bpm, then join'). Parents cannot read it, students lose the page, and the next lesson is spent re-teaching the assignment instead of teaching technique. No notation tool or worksheet pack produces that per-student, per-week handover, because the artifact comes from the teacher's judgment, not from the score.

The JEV score of 61.7/100 (band C) is carried by speed to first revenue (8.3 normalized) and dragged by market-demand evidence (4.46). The plan therefore treats demand as an open question and front-loads proof: the first ten days are a demand test disguised as fulfilment, not a launch party.

Positioning is narrow on purpose. The buyer is a solo piano, guitar, voice, strings or winds teacher with 15-60 weekly students who sells lessons direct to parents in the US, UK, CA or AU, and who is findable by name in public association member listings and in private-music-teacher Facebook groups. The pitch is not 'learn music better'. It is 'stop hand-writing the same assignment sheet forty times a month'. The finished ticket is the entire sales asset: a redacted before/after converts a stranger in one message, with no brand, no audience, no ad budget and no catalog license.

2. Smallest sellable MVP

The smallest sellable thing: a teacher types a piece title and measure count, picks a student level and a daily minute budget, and receives a branded one-page PDF with five days of segmented measure ranges, a tempo ramp (60 to 72 to 84 bpm), a hands-separate then hands-together progression, checkboxes, a parent signature line and a QR code — plus a tokenized student page that needs no login and carries a tap metronome. A Stripe Checkout link issues a 12-month license key and unlocks the studio.

Everything else waits. No native app, no microphone pitch detection, no score catalog, no notation editor, no student billing, no marketplace. Score upload accepts PDF or a phone photo but stores nothing beyond the render; a manual measure-count box is the fallback and is the path most teachers will actually use in week one.

3. Technical implementation plan

Next.js on Vercel, Supabase for Postgres, storage and magic-link auth, Stripe Checkout for the one-time license, Resend for the parent recap, react-pdf for the ticket, qrcode for student links, and the Anthropic API to turn free-text teacher notes into a structured ladder.

The critical design choice is that the AI never ships a ticket unreviewed. The model proposes measure ranges and the deterministic rules engine builds the five-day ladder; the teacher sees an editable preview before the PDF renders. If parsing fails, the manual fallback still produces a valid ticket in under two minutes. Uploaded scores are deleted after render and never shared between studios — the product sells the plan, not the music.

Build order: data model and auth, then intake, then ladder generator, then PDF and student page, then checkout and recap email. Five days, with day 5 reserved for three end-to-end tests on real method-book pieces.

4. Pricing and monetization

Two one-time licenses: Single Studio at $79 for a solo teacher (12 months, unlimited tickets, student pages, recap emails, twelve templates) and Studio Plus at $149 for two to four teachers sharing a brand and a template library. One-time pricing is deliberate: teachers resist another subscription, and a single $79 decision can be approved without a conversation.

The first revenue offer is the free finished ticket, then the checkout link in the same thread. Expansion comes from Studio Plus upgrades, referral seats given free in exchange for one teacher introduction, and a January renewal cohort as the licenses approach expiry.

5. First-customer acquisition

One channel only: direct outreach to named private teachers in Facebook groups and public state/provincial association member listings. The motion is proof-first. Post one redacted before/after — a handwritten notebook page next to a generated ticket for a common method-book piece — then reply to every response with a finished ticket in 20 minutes. That is the product running, not consulting.

Target 150 named teachers, 60 personalized first messages, one follow-up at day 3 and one at day 10. Reply-rate and ticket-to-paid conversion are logged daily; the two weakest message angles get cut at day 14. Reddit (r/pianoteachers) is a secondary test only after reading each community's self-promotion rules.

6. 30-day execution roadmap

Week 1 (days 1-7): build and freeze the MVP by day 5, generate twelve redacted sample tickets, publish the upload policy, post the before/after in two groups, open 20 conversations. Week 2 (days 8-14): fulfil every free request through the product, target the first paid license on day 9, pull 150 directory prospects, ship the template library, publish a 60-second screen recording, start the referral ask, then score the channel. Week 3 (days 15-21): add a recital-polish ticket flavor for December studios, test Reddit, push Studio Plus upgrades, add the preview-and-edit step so a bad parse never reaches a student, cache common ladders, and decide whether to widen beyond piano. Week 4 (days 22-28): publish permitted proof on the landing page, send 30 unsolicited tickets built from public repertoire lists, run a 48-hour $99 price test, ship the activation email, reconcile Stripe payouts against the TrustMRR report, and send a final 40-message wave. Days 29-30 close warm threads and reconcile verified revenue.

7. Revenue and profit scenarios

All three scenarios are projections, not verified revenue, customers or traction.

Seed-stage math (projection): conservative 3 licenses at a $79 average = $237 gross, $8 processing fees, $22 operating cost, leaving roughly $229 contest profit and $207 business profit. Base case 12 licenses at a blended $83 average (a small Studio Plus mix) = $996 gross, $33 fees, $45 operating cost, roughly $963 contest profit and $918 business profit. Upside 30 licenses at a blended $85 average = $2,550 gross, less $158 refunds, $84 fees and $120 of paid promotion, roughly $2,188 contest profit and $2,078 business profit.

Payment processing is modeled at Stripe's 2.9% plus $0.30 per charge, about 3.3% blended at these ticket sizes. Operating cost covers hosting, email and model inference at under $0.06 per generated ticket. No scenario assumes existing customers.

8. Main risks and validation experiments

Channel risk dominates: if moderators delete the proof posts, acquisition goes to zero mid-run. The test is two posts in week 1 with a reply-rate floor of 8%; below that, shift to directory email. Copyright risk: teachers will upload publisher PDFs. The mitigation is to delete uploads after render, never share scores, and publish the policy on day 6 — validated by asking five teachers directly whether the policy changes their decision. Parse accuracy: a wrong measure range destroys trust permanently, so no ticket renders without a preview step; validate with ten real pieces before day 5. Price sensitivity: a 48-hour $99 test at day 24 answers it with data instead of opinion. Seasonality: December recital season may suppress new-repertoire volume, so build the recital-polish flavor early rather than late.

9. First 24-hour action plan

Hours 1-3: register the domain, create Vercel and Supabase projects, open Stripe live mode and connect it to TrustMRR before any charge exists. Hours 4-6: film or collect one handwritten assignment page from a teacher contact, draft the redacted before/after asset, and write the free-ticket message. Hours 7-9: message 10 teachers across two groups asking one question — how long does the weekly assignment note take you? Hours 10-12: scaffold the database schema and magic-link auth. Hours 13-24: build the intake screen and a first hard-coded ladder for one real piece, then send the before/after asset to the two highest-signal groups.

Section 2 of 8

Smallest sellable MVP

A teacher enters a piece, a student level and daily minutes, and receives a branded one-page Practice Ticket PDF with a five-day ladder plus a QR-linked student page, unlocked by a $79 Stripe one-time license.

Must-have features

  • Score intake via PDF/image upload with manual measure-count fallback
  • Five-day practice ladder: segmented measure ranges, tempo ramp, hands-separate to hands-together, minute budget
  • Editable ladder preview before render
  • One-page branded PDF with studio logo, checkboxes, parent signature line and QR code
  • Tokenized no-login student page with day check-offs and tap metronome
  • Weekly parent recap email via Resend under the teacher's sender name
  • Stripe Checkout with one-time license key and email magic-link sign-in
  • Twelve editable plan templates

Explicitly out of scope

  • Real-time microphone pitch detection or scored gameplay
  • Licensed sheet-music catalog or notation rendering engine
  • Native iOS/Android app
  • Teacher marketplace or student matching
  • Studio admin, payroll or student billing
  • 24/7 support beyond an email address
  • Multi-location enterprise features

Demo flow (what the buyer sees)

  1. Teacher signs in by magic link
  2. Types piece title, measure count, student level and daily minutes
  3. Uploads a score PDF or skips upload
  4. Reviews and edits the generated five-day ladder
  5. Renders the one-page PDF with logo, checkboxes, signature line and QR
  6. Teacher prints or emails the PDF to the parent
  7. Student scans the QR, taps off day 1, and uses the tap metronome
  8. Parent receives the weekly recap email from the teacher's name
Build plan

Technical implementation plan

Stack

Next.js on VercelSupabase Postgres, storage and magic-link authStripe CheckoutResend transactional emailAnthropic API for free-text to structured ladderreact-pdf for ticket renderingqrcode for student page links

Architecture

A Next.js app on Vercel talks to Supabase for students, pieces, tickets and studio scoping. Intake writes a piece record; the ladder service sends teacher free-text to Anthropic for proposed measure ranges, then a deterministic rules engine builds the five-day ladder so output is stable and reviewable. The teacher edits the preview, react-pdf renders a one-page ticket stored as a short-lived signed URL, and a token is minted for the student page where check-offs and metronome run client-side. Stripe Checkout issues a license key that unlocks studio rendering; Resend sends weekly recaps under the teacher's sender name. Uploaded scores are deleted after render and never shared across studios.

Build steps

  1. Create Supabase schema: studios, teachers, students, pieces, tickets, licenses
  2. Ship magic-link auth and studio scoping
  3. Build score upload to storage plus manual measure-count fallback
  4. Implement deterministic ladder rules (5 days, bar segments, tempo ramp, stages, minutes)
  5. Add Anthropic extraction of measure ranges with confirm-and-edit screen
  6. Build PDF template with logo, checkboxes, signature line and QR
  7. Ship tokenized student page with check-offs and tap metronome
  8. Wire Stripe Checkout for $79 and $149 to license key issuance
  9. Send parent recap via Resend with per-teacher sender name
  10. Seed twelve plan templates
  11. Run three end-to-end tests on real method-book pieces and fix rendering bugs

AI components

  • Anthropic API parses free-text assignment notes into structured measure ranges, stages and tempo targets, always behind an editable preview
Hardest technical risk: Turning free-text teacher shorthand and score uploads into correct measure ranges — a wrong bar range silently ships as a wrong practice plan and destroys trust.
Section 3 of 8

Pricing and monetization

Single Studio

Entry offer
$79 one-time

For Solo teacher with 15-60 weekly students

  • Unlimited Practice Ticket PDFs for 12 months
  • One studio profile with logo
  • Tokenized student pages with QR codes
  • Weekly parent recap emails
  • Twelve editable plan templates

Studio Plus

$149 one-time

For 2-4 teacher studio sharing one brand

  • Everything in Single Studio
  • Up to 4 teacher seats
  • Shared template library
  • Per-teacher sender name and reply-to

Model: One-time annual studio licenses: $79 for a solo teacher, $149 for a 2-4 teacher studio.

First revenue offer: Reply with one piece and a student's level and I'll send back a finished Practice Ticket in 20 minutes, free, no signup — then a $79 12-month studio license link in the same thread.

Expected ACV: $79

Upsell path: Upgrade single licenses to Studio Plus at $149 when a buyer mentions a co-teacher, and give a free second studio seat for each named teacher introduction that converts.

Target customers
40
Revenue model
$3,160
Costs
$90
Profit model
$3,070
Section 4 of 8

First-customer acquisition

Primary channel

Direct outreach to named private instrument teachers in Facebook groups and public state/provincial association member directories, led by a finished sample ticket.

Where to find them

  • Private music teacher Facebook groups for piano, guitar and voice with 5k+ members
  • Public state and provincial music teacher association member listings
  • r/pianoteachers and one music-education subreddit (after reading self-promo rules)
  • Independent studio websites listing staff teachers by name
  • Instagram and YouTube teacher accounts that post lesson clips

Exact outreach motions

  • Post one redacted before/after: handwritten notebook page next to a generated ticket for a common method-book piece.
  • DM 20 teachers with the free-ticket offer: one piece plus a level gets a finished ticket in 20 minutes.
  • Pull 150 named teachers from public association listings and send 30 personalized messages quoting a piece from their studio page.
  • Follow up once at day 3 and once at day 10 on non-responders, restating the free ticket, not the price.
  • Send a 60-second screen recording of notes-typed to printed-ticket to every warm thread.
  • Ask each buyer for one teacher introduction in exchange for a free second studio seat.

Message template

Hi [Name] — I saw you teach [instrument] in [city]. Quick question: how long does the weekly practice note for one student take you? I built a tool that turns 'bars 12-24, 72 bpm, hands separate' into a printed one-page ticket with a QR student page. Send me one piece and a student's level and I'll send the finished ticket back in 20 minutes, free, no signup.
Week-one goal: Two proof posts live in teacher groups, 20 personalized conversations open, 10 finished free tickets delivered, and at least 3 replies asking for the license link.
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 1Setup and demand check

Infrastructure plus first conversations

  • Register domain, create Vercel and Supabase projects, open Stripe live mode.
  • Connect Stripe to TrustMRR before any charge exists.
  • Message 10 teachers asking how long weekly assignment notes take.

Deliverable: Working dev environment, Stripe live verified, 10 conversations opened.

Day 2Data model and intake

Auth plus score intake

  • Build studios, students, pieces and tickets tables with studio scoping.
  • Ship magic-link auth.
  • Ship PDF/image upload to storage with manual measure-count fallback.

Deliverable: Teacher can sign in, add 3 students and 3 pieces.

Day 3Ladder generator

Deterministic rules plus AI extraction

  • Write five-day ladder rules: bar segments, tempo ramp, hands-separate to together, minute budget.
  • Add Anthropic extraction of measure ranges with a confirm-and-edit screen.

Deliverable: One call returns a structured five-day ladder for a real piece.

Day 4Ticket and student page

PDF render plus QR page

  • Render one-page PDF with logo, checkboxes, signature line and QR.
  • Ship tokenized student page with day check-offs and tap metronome.

Deliverable: Printable ticket and working QR student page for 3 test students.

Day 5Payments and MVP freezeMVP shipped

Checkout, email, end-to-end test

  • Wire Stripe Checkout for $79 and $149 to license key issuance.
  • Send parent recap via Resend under the teacher's sender name.
  • Run 3 end-to-end tests on real method-book pieces.

Deliverable: Sellable product shipped; MVP deadline met.

Day 6Samples and guardrails

Proof assets and copyright policy

  • Generate 12 redacted sample tickets across piano, guitar and voice.
  • Publish upload policy: no score hosting, originals deleted after render.

Deliverable: Sample library and public upload policy page.

Day 7Soft launch

Two group posts plus 20 DMs

  • Post the redacted before/after in 2 teacher groups per their promo rules.
  • DM 20 teachers with the free-ticket offer.

Deliverable: Two posts live, 20 DMs sent.

Week 2 · Launch & first sale · 7 days
Day 8Fulfil free tickets

Deliver fast, log objections

  • Turn every reply into a finished ticket within 20 minutes using the product.
  • Log piece, level and objection per prospect in a sheet.

Deliverable: First 10 tickets delivered and an objection list.

Day 9First paid conversionFirst sale target

Send license links

  • Send the $79 license link in each delivery thread with 12-month terms.
  • Email everyone who opened but did not buy with one direct checkout link.

Deliverable: First paying customer (target day 9).

Day 10Directory outreach

150 named prospects

  • Pull 150 named teachers from public association member listings.
  • Send 30 personalized DMs quoting a specific piece from their studio page.

Deliverable: 150-row prospect sheet and 30 DMs sent.

Day 11Template library

Twelve editable plans

  • Ship 12 editable templates: new piece, scales, sight-reading, recital polish, exam prep.
  • Surface template picker inside the intake flow.

Deliverable: Template picker live for all users.

Day 12Video proof

Reusable demo asset

  • Record a 60-second screen capture: notes typed, ticket printed, QR page opened.
  • Add captions and publish it as a link in every DM.

Deliverable: One video asset reusable across all channels.

Day 13Referral loop

Ask buyers for introductions

  • Ask every buyer for one teacher introduction for a free second studio seat.
  • Track introductions in the prospect sheet.

Deliverable: Referral ask sent to all buyers.

Day 14Week-two review

Cut weak angles

  • Measure DM reply rate, ticket-to-paid conversion and refund requests.
  • Cut the two lowest-converting message angles.

Deliverable: Channel scorecard and revised outreach script.

Week 3 · Repeat & systematize · 7 days
Day 15Recital wedge

December-specific ticket flavor

  • Build a recital-polish ticket flavor with a four-week countdown.
  • Pitch it to teachers in the 3 best-performing groups.

Deliverable: Recital ticket live and 25 targeted DMs sent.

Day 16Reddit test

Secondary channel probe

  • Read each subreddit's self-promotion rules, then post the before/after to r/pianoteachers.
  • Answer every comment same day with the free-ticket offer.

Deliverable: One Reddit post live with comments triaged.

Day 17Studio Plus push

Upgrade single licenses

  • Offer $149 Studio Plus to every buyer who mentioned a co-teacher.
  • Send a one-paragraph comparison email to all single-license holders.

Deliverable: Upgrade emails sent and upgrades tracked.

Day 18Reliability pass

Never ship a bad parse

  • Enforce an editable ladder preview before any PDF renders.
  • Add a validation warning when measure ranges exceed the typed measure count.

Deliverable: Review step shipped with validation warnings.

Day 19Fulfilment speed

Cut generation time

  • Cache common method-book ladders per piece and level.
  • Log median generation time across the last 30 tickets.

Deliverable: Median generation time under 30 seconds.

Day 20Second outreach cohort

40 new directory DMs

  • Send 40 DMs to the next directory slice.
  • Follow up day-3 and day-10 non-responders once each.

Deliverable: 40 new conversations opened.

Day 21Cohort review

Widen or focus

  • Recalculate revenue against target and per-instrument reply rates.
  • Decide whether to widen to voice and strings or stay piano-first.

Deliverable: Written widen-or-focus decision.

Week 4 · Scale what works · 7 days
Day 22Landing proof block

Permitted real proof

  • Add one anonymized teacher quote and a ticket screenshot to the landing page.
  • Confirm written permission for the quote.

Deliverable: Landing page updated with permitted proof.

Day 23Unsolicited tickets

Gift of work at scale

  • Send 30 finished tickets built from publicly posted repertoire lists.
  • Include the license link but lead with the artifact.

Deliverable: 30 no-strings samples delivered.

Day 24Price test

$79 versus $99

  • Run a 48-hour $99 price test on new visitors against $79.
  • Record conversion counts per arm.

Deliverable: Price test result with both conversion counts.

Day 25Activation and refund prevention

Get licenses used

  • Email all license holders a three-step 'first ticket in five minutes' guide.
  • Flag any license with zero tickets generated for a personal follow-up.

Deliverable: Activation email sent and activation measured.

Day 26Payment hygiene

Clean money trail

  • Confirm Stripe payout schedule and reconcile charges inside the contest window.
  • Publish refund policy text on the checkout page.

Deliverable: Clean payout ledger matched to TrustMRR.

Day 27Referral harvest

Convert introductions

  • Redeem second-seat referrals and message each introduced teacher.
  • Count referral-sourced licenses separately.

Deliverable: Referral-sourced licenses counted.

Day 28Final outreach wave

40 last-wave DMs

  • Send 40 DMs with the December recital angle and a 48-hour free-ticket promise.
  • Triage replies the same day.

Deliverable: 40 final DMs sent and triaged.

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

Close every warm thread

  • Follow up once on every warm thread with a direct checkout link.
  • Ship any 30-minute fix that unblocks a hesitant buyer.

Deliverable: All warm threads closed or marked lost.

Day 30Reconcile and document

Verified numbers and next quarter

  • Reconcile Stripe gross, refunds, fees and ad spend against the TrustMRR report.
  • Write the 30-day retro: what converted, what to build in January.

Deliverable: Verified revenue statement and next-quarter 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: 3 paid licenses from roughly 150 direct conversations, about 2% conversion.
  • Base: 12 licenses with a 85/15 Single Studio to Studio Plus mix, blended ARPU about $83.
  • Upside: 30 licenses with a richer Studio Plus mix, blended ARPU about $85, and 2 refunds.
  • Payment processing assumed Stripe at 2.9% plus $0.30 per charge, about 3.3% blended at these ticket sizes.
  • No paid marketing in Conservative or Base; Upside includes $120 of sponsored group posts and a small Reddit test.
  • Operating cost covers Vercel, Supabase, Resend and Anthropic rendering at under $0.06 per generated ticket.
  • All figures are projections from stated assumptions, not verified revenue, customers or traction.

Conservative

3 customers
$237
collected revenue · avg payment $79
Refunds
$0
Chargebacks
$0
Payment fees
$8
Paid marketing
$0
Hackathon profit
$229
Operating costs
$22
Business profit
$207

Base case

12 customers
$996
collected revenue · avg payment $83
Refunds
$0
Chargebacks
$0
Payment fees
$33
Paid marketing
$0
Hackathon profit
$963
Operating costs
$45
Business profit
$918

Optimistic

30 customers
$2,550
collected revenue · avg payment $85
Refunds
$158
Chargebacks
$0
Payment fees
$84
Paid marketing
$120
Hackathon profit
$2,188
Operating costs
$110
Business profit
$2,078

Model your own numbers

Runs in your browser · nothing is saved
Collected revenue
$948
Payment fees (3.9%)
$37
Paid marketing
$0
Hackathon profit
$911
Business profit
$866

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 derived from stated assumptions; projections only, not verified revenue.

Section 7 of 8

Main risks and validation experiments

Risk 1Facebook group moderators remove the proof posts and the primary acquisition channel goes to zero mid-run.

Mitigation

Keep the association directory and Reddit channels warm from day 7 so no single platform carries all outreach.

Validation experiment

Post the before/after in two groups on day 7 and measure reply rate over 72 hours.

Kill criteria

If reply rate stays under 8% across two groups and 30 directory DMs produce no free-ticket requests, stop group posting.

Risk 2Teachers upload publisher-copyrighted PDFs, creating legal exposure and objections.

Mitigation

Delete uploads after render, never host or share scores between studios, and publish the policy on day 6.

Validation experiment

Ask five teachers directly whether the delete-after-render policy changes their decision to use it.

Kill criteria

If three or more of five say the policy blocks adoption, reposition to text-only intake and drop upload entirely.

Risk 3AI measure-range parsing produces a wrong ladder, and a teacher assigns it to students.

Mitigation

Mandatory editable preview plus a validation warning when ranges exceed the typed measure count.

Validation experiment

Generate ladders for 10 real pieces and manually check every measure range against the score.

Kill criteria

If fewer than 8 of 10 ladders are correct without edits, remove AI parsing and ship manual range entry only.

Risk 4Price resistance from teachers who compare against free worksheet and studio-management tools.

Mitigation

Anchor on 10-20 minutes saved per student per week and offer a 12-month license rather than a subscription.

Validation experiment

Run a 48-hour $99 versus $79 split on new visitors at day 24.

Kill criteria

If $99 converts at under half the rate of $79, keep $79 as the ceiling for the contest window.

Risk 5December recital and holiday scheduling suppresses new-repertoire assignment volume.

Mitigation

Ship a recital-polish ticket flavor by day 15 and lead with recital messaging in all December outreach.

Validation experiment

Compare reply rates on recital-angle messages against new-piece messages across 40 DMs.

Kill criteria

If recital messaging underperforms new-piece messaging by half, drop the recital flavor and rebuild for January.

Section 8 of 8

Hour-by-hour: the first 24 hours

Hours 1-3

  • Register domain, create Vercel and Supabase projects, enable Stripe live mode.
  • Connect the Stripe account to TrustMRR before any charge exists.

Output: Live infrastructure with a verified payment path.

Hours 4-6

  • Draft the free-ticket message and the DM script.
  • Scaffold the studios, students, pieces and tickets schema.

Output: Outreach script and database schema committed.

Hours 7-9

  • Message 10 teachers in two groups with the single question about weekly note-writing time.
  • Join two additional teacher groups and read their promo rules.

Output: 10 conversations opened, group rules documented.

Hours 10-12

  • Ship magic-link auth and the student and piece creation screens.
  • Build a hard-coded five-day ladder for one real method-book piece.

Output: Working intake with one rendered ladder.

Hours 13-24

  • Render the first one-page PDF with a QR student page.
  • Send the redacted before/after asset to the two highest-signal groups and reply to every response with a free ticket.

Output: First sample ticket delivered and the first proof post live.

Complete report

Full 30-day launch report

Read the full generated report

Practice Ticket Studio — 30-Day Launch Report

1. Product opportunity and positioning

Practice Ticket Studio sells a back-office artifact to a professional buyer. Private instrument teachers already spend 10-20 minutes per student per week writing assignment shorthand into a notebook ('bars 12-24, hands separate, 72 bpm, then join'). Parents cannot read it, students lose the page, and the next lesson is spent re-teaching the assignment instead of teaching technique. No notation tool or worksheet pack produces that per-student, per-week handover, because the artifact comes from the teacher's judgment, not from the score.

The JEV score of 61.7/100 (band C) is carried by speed to first revenue (8.3 normalized) and dragged by market-demand evidence (4.46). The plan therefore treats demand as an open question and front-loads proof: the first ten days are a demand test disguised as fulfilment, not a launch party.

Positioning is narrow on purpose. The buyer is a solo piano, guitar, voice, strings or winds teacher with 15-60 weekly students who sells lessons direct to parents in the US, UK, CA or AU, and who is findable by name in public association member listings and in private-music-teacher Facebook groups. The pitch is not 'learn music better'. It is 'stop hand-writing the same assignment sheet forty times a month'. The finished ticket is the entire sales asset: a redacted before/after converts a stranger in one message, with no brand, no audience, no ad budget and no catalog license.

2. Smallest sellable MVP

The smallest sellable thing: a teacher types a piece title and measure count, picks a student level and a daily minute budget, and receives a branded one-page PDF with five days of segmented measure ranges, a tempo ramp (60 to 72 to 84 bpm), a hands-separate then hands-together progression, checkboxes, a parent signature line and a QR code — plus a tokenized student page that needs no login and carries a tap metronome. A Stripe Checkout link issues a 12-month license key and unlocks the studio.

Everything else waits. No native app, no microphone pitch detection, no score catalog, no notation editor, no student billing, no marketplace. Score upload accepts PDF or a phone photo but stores nothing beyond the render; a manual measure-count box is the fallback and is the path most teachers will actually use in week one.

3. Technical implementation plan

Next.js on Vercel, Supabase for Postgres, storage and magic-link auth, Stripe Checkout for the one-time license, Resend for the parent recap, react-pdf for the ticket, qrcode for student links, and the Anthropic API to turn free-text teacher notes into a structured ladder.

The critical design choice is that the AI never ships a ticket unreviewed. The model proposes measure ranges and the deterministic rules engine builds the five-day ladder; the teacher sees an editable preview before the PDF renders. If parsing fails, the manual fallback still produces a valid ticket in under two minutes. Uploaded scores are deleted after render and never shared between studios — the product sells the plan, not the music.

Build order: data model and auth, then intake, then ladder generator, then PDF and student page, then checkout and recap email. Five days, with day 5 reserved for three end-to-end tests on real method-book pieces.

4. Pricing and monetization

Two one-time licenses: Single Studio at $79 for a solo teacher (12 months, unlimited tickets, student pages, recap emails, twelve templates) and Studio Plus at $149 for two to four teachers sharing a brand and a template library. One-time pricing is deliberate: teachers resist another subscription, and a single $79 decision can be approved without a conversation.

The first revenue offer is the free finished ticket, then the checkout link in the same thread. Expansion comes from Studio Plus upgrades, referral seats given free in exchange for one teacher introduction, and a January renewal cohort as licenses approach expiry.

5. First-customer acquisition

One channel only: direct outreach to named private teachers in Facebook groups and public state/provincial association member listings. The motion is proof-first. Post one redacted before/after — a handwritten notebook page next to a generated ticket for a common method-book piece — then reply to every response with a finished ticket in 20 minutes. That is the product running, not consulting.

Target 150 named teachers, 60 personalized first messages, one follow-up at day 3 and one at day 10. Reply rate and ticket-to-paid conversion are logged daily; the two weakest message angles get cut at day 14. Reddit (r/pianoteachers) is a secondary test only after reading each community's self-promotion rules.

6. 30-day execution roadmap

Week 1 (days 1-7): build and freeze the MVP by day 5, generate twelve redacted sample tickets, publish the upload policy, post the before/after in two groups, open 20 conversations. Week 2 (days 8-14): fulfil every free request through the product, target the first paid license on day 9, pull 150 directory prospects, ship the template library, publish a 60-second screen recording, start the referral ask, then score the channel. Week 3 (days 15-21): add a recital-polish ticket flavor for December studios, test Reddit, push Studio Plus upgrades, add the preview-and-edit step so a bad parse never reaches a student, cache common ladders, and decide whether to widen beyond piano. Week 4 (days 22-28): publish permitted proof on the landing page, send 30 unsolicited tickets built from public repertoire lists, run a 48-hour $99 price test, ship the activation email, reconcile Stripe payouts against the TrustMRR report, and send a final 40-message wave. Days 29-30 close warm threads and reconcile verified revenue.

7. Revenue and profit scenarios

All three scenarios are projections, not verified revenue, customers or traction.

Conservative (projection): 3 licenses at a $79 average = $237 gross, $8 processing fees, $22 operating cost, leaving roughly $229 contest profit and $207 business profit. Base case (projection): 12 licenses at a blended $83 average from a small Studio Plus mix = $996 gross, $33 fees, $45 operating cost, roughly $963 contest profit and $918 business profit. Upside (projection): 30 licenses at a blended $85 average = $2,550 gross, less $158 refunds, $84 fees and $120 of paid promotion, roughly $2,188 contest profit and $2,078 business profit.

Payment processing is modeled at Stripe's 2.9% plus $0.30 per charge, about 3.3% blended at these ticket sizes. Operating cost covers hosting, email and model inference at under $0.06 per generated ticket. No scenario assumes existing customers or partners.

8. Main risks and validation experiments

Channel risk dominates: if moderators delete the proof posts, acquisition goes to zero mid-run. The test is two posts in week 1 with a reply-rate floor of 8%; below that, shift to directory email. Copyright risk: teachers will upload publisher PDFs. The mitigation is to delete uploads after render, never share scores, and publish the policy on day 6 — validated by asking five teachers directly whether the policy changes their decision. Parse accuracy: a wrong measure range destroys trust permanently, so no ticket renders without a preview step; validate with ten real pieces before day 5. Price sensitivity: a 48-hour $99 test at day 24 answers it with data instead of opinion. Seasonality: December recital season may suppress new-repertoire volume, so build the recital-polish flavor early rather than late.

9. First 24-hour action plan

Hours 1-3: register the domain, create Vercel and Supabase projects, open Stripe live mode and connect it to TrustMRR before any charge exists. Hours 4-6: draft the free-ticket message and scaffold the database schema. Hours 7-9: message 10 teachers across two groups asking one question — how long does the weekly assignment note take you? Hours 10-12: ship magic-link auth and build one hard-coded five-day ladder for a real piece. Hours 13-24: render the first one-page PDF with a QR student page, post the redacted before/after to the two highest-signal groups, and reply to every response with a finished ticket.

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 →