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

Redo Pack

Redo Pack turns a photo of a student's worksheet into a branded one-page redo packet — warm-ups, mirror problems, stretch items, a verified answer key and a parent note — for independent tutors, in about 90 seconds.

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.45/10
MVP build (solo)
4 days
Launch price
$49
Sales to $1,000 revenue
21 customers
First paying customer
Direct one-to-one outreach to named solo tutors found in public tutor Facebook groups, Reddit r/Tutors and independent tutoring center 'meet the tutors' pages, offering one free converted packet within 24 hours.
Who pays

Solo math and reading tutors plus small tutoring centers with 1–8 tutors (US/UK/CA/AU) charging $50–$120/hour, triggered by a graded quiz or homework sheet where a student missed several items.

Biggest execution risk

Market demand 4.6/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 12; 21 sales at $49 clears $1,000 of collected revenue; strongest signal is speed to first revenue at 9.0/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
$49
Solo build
4 days
30d base revenue
$1,078
30d hackathon profit
$1,035
Section 1 of 8

Product opportunity and positioning

Target customer

Solo math and reading tutors plus small tutoring centers with 1–8 tutors (US/UK/CA/AU) charging $50–$120/hour, triggered by a graded quiz or homework sheet where a student missed several items.

Why now

Vision-capable models can now segment a photographed worksheet into reliable question cards and a text model can generate checked parallel items, so the whole transformation is one API call plus a renderer — buildable solo in four days with no content library.

Problem

After every graded worksheet the tutor must invent follow-up practice on the exact missed skills: retyping problems, finding similar items at the right difficulty, writing worked solutions and drafting a parent update — 20–40 minutes per student per week of unpaid prep, usually the night before, often skipped.

Solution

Tutor uploads a photo or PDF of the blank worksheet, taps the numbers the student missed, and receives a branded, print-ready PDF: 3 prerequisite warm-ups, 4 mirror problems, 2 stretch items, a worked answer key page and a 2-sentence parent note.

Differentiation · A chatbot produces plausible problems; Redo Pack delivers a fixed, branded, print-ready artifact with skill tagging, a verified answer key on its own page and a parent note — the tutor hands it to a paying parent the same day without editing.

1. Opportunity and positioning

Redo Pack sells to one buyer: the solo math or reading tutor (and 1–8 tutor centers) in the US, UK, Canada and Australia charging $50–$120 an hour. The trigger is weekly and unambiguous — a student returns with a graded quiz, practice test or homework sheet where several items are wrong, and the next session needs material on exactly those skills.

Today the tutor rebuilds that material from scratch the night before: retyping similar problems, hunting for items at the right difficulty, writing worked solutions by hand, and drafting a parent update. That is 20–40 minutes per student per week of unpaid prep, and when the week is busy it is skipped entirely — the student redoes the same sheet.

Three things line up at once. The buyer can approve $49 on a card with no procurement, IT review or pilot committee. The trigger recurs every seven days. And the output is a document the tutor hands to a parent the same afternoon, which turns each packet into a passive distribution unit: the parent sees the tutor's brand, co-tutors see the footer, and further enquiries arrive without ad spend.

The differentiation is the artifact, not the model. A general chatbot will produce plausible practice problems, but it will not reliably pin the missed item to a skill and its prerequisite, verify its own arithmetic, carry the tutor's logo and colours, split the answer key onto a separate page, and land as a print-ready PDF in 90 seconds. Redo Pack's product is that fixed output contract — same shape every time, safe to print, safe to hand to a parent.

The narrow wedge matters. This is not an LMS, a gradebook, a scheduling tool or a student-facing app. It performs one transformation and stops. That keeps the build inside a solo founder's four days, keeps delivery cost under $0.20 a packet, and keeps the sales motion to a single direct message sent to a named tutor.

The honest limit, reflected in the JEV band, is market demand confidence: the pain is real but unproven at the price point, so the first thirty days are structured to convert evidence fast — free sample first, paid ask within 48 hours — rather than to build a broad platform.

Section 2 of 8

Smallest sellable MVP

A single-page web app where a tutor uploads a blank worksheet photo, taps missed question numbers, and gets an emailed, branded, print-ready PDF packet with answer key and parent note, paid for with a $49 Stripe checkout.

Must-have features

  • Photo/PDF upload with automatic segmentation into numbered question cards
  • Tap-to-mark-missed selection UI
  • Skill tagger mapping each missed item to one skill plus one prerequisite from a fixed ~120-skill taxonomy
  • Packet generator emitting 3 warm-ups, 4 mirror problems, 2 stretch items as structured JSON
  • Deterministic answer-verification pass before rendering
  • Branded React-PDF renderer with logo, tutor name, colours, footer and separate answer-key page
  • Two-sentence parent-note generator
  • Stripe Checkout for the $49 10-pack and $29 monthly plan with packet metering
  • Magic-link login and emailed PDF delivery via Resend

Explicitly out of scope

  • Auto-grading of handwritten student work
  • LMS, gradebook, scheduling or session notes
  • Student or parent login portal
  • School or district sales, SSO, procurement
  • Licensed textbook or standards-body content library
  • Tutor marketplace or matching
  • Native mobile app
  • Multi-language support

Demo flow (what the buyer sees)

  1. Tutor opens the upload page and selects a photo of a blank worksheet
  2. Vision model segments the page into numbered question cards
  3. Tutor taps the numbers the student missed and confirms
  4. System tags each item to a skill plus prerequisite and generates warm-ups, mirrors and stretch items
  5. Answer-verification pass recomputes every generated item and rejects mismatches
  6. Branded PDF renders with the tutor's logo, the packet page and a separate answer key
  7. Parent note is generated and appended
  8. PDF is emailed to the tutor and stored against the student record
Build plan

Technical implementation plan

Stack

Next.js on VercelSupabase (auth, Postgres, storage)Vision-capable LLM API for page segmentation and skill taggingText LLM API for item and parent-note generationDeterministic answer-check pass in TypeScriptReact-PDF for branded packet renderingStripe Checkout with metered subscriptionResend for PDF email delivery

Architecture

A Next.js app on Vercel holds the upload page and the tutor dashboard. Uploads land in Supabase storage; a serverless route sends the image to a vision model that returns question-card bounding boxes and text, stored as JSON per worksheet. The tutor's tap selection plus the skill taxonomy produce a generation request to a text model that returns strict JSON (warm-ups, mirrors, stretch, worked steps). A deterministic checker recomputes each generated item and drops or regenerates failures before React-PDF renders two pages — packet and answer key — which Resend emails and Supabase records against the student. Stripe webhooks flip plan state and decrement packet credits.

Build steps

  1. Day 1: scaffold Next.js repo, Supabase project with auth plus storage, deploy a hello-world to Vercel
  2. Day 1: write the ~120-skill taxonomy as a JSON file with skill id, label, grade band and prerequisite id
  3. Day 2: build the upload route and the vision segmentation call, returning numbered cards with crops
  4. Day 2: build the tap-to-mark-missed grid UI and persist the selection
  5. Day 3: implement skill tagging and the generation prompt with a strict JSON schema and retry on parse failure
  6. Day 3: implement the deterministic answer-check pass and a regenerate-once policy
  7. Day 4: build the React-PDF renderer with logo upload, brand colours and a separate answer-key page
  8. Day 4: add the parent-note generator and editable text field
  9. Day 5: wire Stripe Checkout, webhooks, packet metering and magic-link auth
  10. Day 5: wire Resend delivery, run one end-to-end packet as the founder, then open to free-sample tutors
  11. Post-launch: add the regenerate-with-new-numbers button and student roster once the first buyers ask

AI components

  • Vision LLM for page segmentation into numbered question cards
  • LLM for skill and prerequisite tagging against the fixed taxonomy
  • LLM for generating warm-up, mirror and stretch items with worked steps
  • LLM for the two-sentence parent note
  • Deterministic (non-AI) arithmetic verification pass on every generated item
Hardest technical risk: Segmentation of dense, low-quality or handwritten-annotated worksheet photos returning wrong question boundaries — if it fails often, the free-sample promise is undeliverable in week one, so the founder manually crops during the first week and logs every failure.
Section 3 of 8

Pricing and monetization

Launch 10-Pack

Entry offer
$49 one-time

For Tutors who received a free sample packet and want more without a subscription

  • 10 branded redo packets
  • Answer keys and parent notes
  • Logo and colour setup

Tutor Starter

$29 / month

For Solo tutors running 5–20 sessions a week

  • 20 packets per month
  • Student roster and packet history
  • Branded PDF with parent note

Tutor Pro

$79 / month

For Small tutoring centers and full-time tutors with 20+ students

  • Unlimited packets
  • Multiple tutor profiles under one brand
  • Custom templates and regenerate-with-new-numbers

Model: Low-ticket self-serve: one $49 ten-packet one-time pack to convert free-sample users, then $29/month (20 packets) and $79/month (unlimited, multi-tutor) subscriptions.

First revenue offer: Send the finished free packet, then 48 hours later: 'Next 10 packets are $49 — here is the link, your logo and colours are already set up.'

Expected ACV: $49

Upsell path: Convert $49 10-pack buyers to $29/month after their third packet, then pitch $79 Tutor Pro to anyone with 20+ students or a second tutor on staff; add a $59 bundle of 10-pack plus first month Starter for warm leads in week four.

Target customers
40
Revenue model
$1,960
Costs
$110
Profit model
$1,850
Section 4 of 8

First-customer acquisition

Primary channel

Direct one-to-one outreach to named solo tutors found in public tutor Facebook groups, Reddit r/Tutors and independent tutoring center 'meet the tutors' pages, offering one free converted packet within 24 hours.

Where to find them

  • Public tutor Facebook groups (search 'private tutoring' and 'tutor business')
  • Reddit r/Tutors and r/matheducation public threads
  • 'Meet the tutors' pages on independent tutoring center websites
  • Public tutor profiles on Outschool-style and local directories
  • Tutor YouTube channels and blog comment sections with public contact routes
  • Local tutoring center listings with published email addresses

Exact outreach motions

  • Send 40 one-to-one messages per day to named tutors in public groups, leading with the free packet rather than the product
  • Offer the specific transformation, not a demo call: 'send a photo of a blank sheet and the missed numbers'
  • Deliver the free packet manually within 24 hours and ask exactly one question: 'how long would this have taken you?'
  • Follow up at 48 hours with the $49 Stripe link and a screenshot of the finished packet
  • Post a before/after packet in a group that permits self-promotion, one community per day, never spamming
  • Ask every buyer for one intro to a tutor in the same group chat
  • Message 40 small tutoring centers in week three with a multi-tutor branding angle

Message template

Hi [name] — I built a small tool that turns one of your worksheets into a redo packet for the student who missed questions: warm-ups, similar problems, a worked answer key and a parent note, with your logo on it. Send me a photo of a blank sheet and tell me which numbers they missed, and I'll send you the finished PDF free within 24 hours. No signup needed.
Week-one goal: 60 personalized messages sent, 5 free packets delivered within 24 hours each, reply-rate baseline recorded, and the first paid $49 link sent.
Section 5 of 8

30-day execution roadmap

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

Set up stack and outreach list

  • Create Next.js repo on Vercel and a Supabase project with auth and storage.
  • Seed a ~120-skill math/reading taxonomy with prerequisite links.
  • Connect Stripe in test mode and finish the TrustMRR payment-account connection.
  • Build a 60-name tutor outreach list from public groups.

Deliverable: Deployed skeleton, taxonomy v0, live payment account, 60-name list

Day 2Ingest

Upload and segmentation

  • Build the photo/PDF upload page writing to Supabase storage.
  • Call a vision LLM to segment the page into numbered question cards.
  • Build the tap-to-mark-missed card grid.
  • Log every segmentation failure with the source image.

Deliverable: Upload-to-question-cards flow tested on 5 real worksheets

Day 3Packet engine

Skill tagging and generation

  • Map each missed item to one skill plus one prerequisite.
  • Generate 3 warm-ups, 4 mirrors and 2 stretch items as strict JSON.
  • Add a deterministic answer-check pass that recomputes every item.
  • Persist packet JSON per student in Postgres.

Deliverable: Verified packet JSON generated from a real worksheet

Day 4Branded PDF

Rendering and parent note

  • Build the React-PDF one-pager plus a separate answer-key page.
  • Add logo upload, tutor name, brand colours and footer fields.
  • Add the two-sentence parent-note generator with an editable field.
  • Test print output on US Letter and A4.

Deliverable: Branded PDF with answer key from a real worksheet

Day 5Ship MVPMVP shipped

Billing and delivery

  • Wire Stripe Checkout for the $49 10-pack and $29 monthly plan.
  • Add magic-link login and packet metering.
  • Email the finished PDF via Resend on completion.
  • Run one full packet end to end as the founder.

Deliverable: Live MVP accepting payment — MVP deadline day 5

Day 6Proof

First free sample delivered

  • Send the 3-line offer to 5 tutors from the list.
  • Deliver the first free packet manually within 24 hours.
  • Ask 'how long would this have taken you?' and record the answer.
  • Fix the top segmentation bug found in that packet.

Deliverable: One finished free packet delivered and reaction logged

Day 7Pipeline

Outreach batch one

  • Send 40 more one-to-one messages.
  • Deliver 3 more free packets.
  • Record reply rate and objections in a tracking sheet.
  • Patch taxonomy gaps found in real packets.

Deliverable: 45 messages sent, 4 free packets delivered, reply-rate baseline

Week 2 · Launch & first sale · 7 days
Day 8Paid ask

First revenue attempt

  • Follow up every week-one free-sample tutor.
  • Send the $49 Stripe link to anyone who replied positively.
  • Post one before/after packet in a group that permits self-promo.

Deliverable: First paid ask sent; conversion objections documented

Day 9Objections

Fix conversion

  • Rewrite the offer around the top objection recorded on day 8.
  • Ship a landing page: 'send your sheet, get it in 90 seconds'.
  • Deliver 3 more free packets.

Deliverable: Revised offer and landing page live

Day 10Volume

Outreach batch two

  • Grow the list to 150 named tutors.
  • Send 40 messages.
  • Deliver 4 free packets.

Deliverable: 150-name list, 40 sends, 4 deliveries

Day 11Reliability

Ship v1.1

  • Add a retry hint for low-quality photo uploads.
  • Ship the regenerate-with-new-numbers button.
  • Add the student roster and packet history view.

Deliverable: v1.1 deployed with regenerate and roster

Day 12RevenueFirst sale target

First paid sale target

  • Close at least one $49 10-pack or $29 Starter subscription.
  • Ask that buyer for one intro to another tutor.
  • Log the exact message that converted.

Deliverable: First verified payment collected

Day 13Repeat

Outreach batch three

  • Send 50 messages.
  • Deliver 5 free packets.
  • Clear every 48-hour follow-up in the tracker.

Deliverable: 50 sends, 5 deliveries, follow-ups cleared

Day 14Review

Week-two funnel data

  • Compute reply rate, free-to-paid rate and packets per buyer.
  • Cut the lowest-performing message variant.
  • Set the week-three target from real numbers only.

Deliverable: Week-two funnel report with conversion rates

Week 3 · Repeat & systematize · 7 days
Day 15Subscriptions

Shift 10-pack buyers to monthly

  • Offer $29/month Starter to every 10-pack buyer.
  • Add an in-app upgrade prompt after packet three.
  • Send 50 outreach messages.

Deliverable: At least two monthly subscriptions active

Day 16Referral loop

Make every PDF a distribution unit

  • Add a 'Made with Redo Pack' footer with a referral code to every PDF.
  • Ask every buyer for one group-chat intro.
  • Deliver 5 free packets.

Deliverable: Referral footer shipped, intros requested

Day 17Centers

Reach multi-tutor accounts

  • List 40 small tutoring centers (1–8 tutors) from public sites.
  • Send a center-specific message about multi-tutor branding.
  • Deliver 3 center sample packets.

Deliverable: 40 center names contacted, 3 samples delivered

Day 18Trust

Answer-check reliability

  • Flag packets for manual review when the checker is unsure.
  • Add packet history with one-click re-download.
  • Fix the top three tutor-reported issues.

Deliverable: v1.2 with answer-check flag and re-download

Day 19Volume

Outreach across two communities

  • Send 60 messages including centers.
  • Deliver 6 free packets.
  • Post one worked example in a second tutor community.

Deliverable: 60 sends, 6 deliveries, two communities active

Day 20ARPU

Pitch Tutor Pro

  • Pitch $79 Tutor Pro to tutors with 20+ students.
  • Offer multi-tutor branding to one center.
  • Collect one testimonial quote with written permission.

Deliverable: At least one $79 conversation live

Day 21Review

Week-three channel decision

  • Recompute messages-per-sale and churn risk.
  • Kill the worst channel and double the best.
  • Set the week-four revenue target from actuals.

Deliverable: Week-three report with a channel decision

Week 4 · Scale what works · 7 days
Day 22Retention

Reduce month-one churn

  • Email every subscriber their packet count this month.
  • Offer a 5-packet top-up to low-usage subscribers.
  • Deliver 5 free packets.

Deliverable: Usage email sent to all active subscribers

Day 23Inbound proof

Publish a case study

  • Publish one public before/after packet case study.
  • Record a 60-second screen capture of the 90-second flow.
  • Send 60 messages linking the case study.

Deliverable: Public case study and demo clip live

Day 24Speed

Cut packet latency

  • Reduce median packet time to under 60 seconds.
  • Prefill branding for returning tutors.
  • Fix upload errors found in the logs.

Deliverable: Sub-60-second median packet time

Day 25Referrals

Reactivate non-buyers

  • Offer 2 free packets per referred paying tutor.
  • Message 20 tutors who replied but never bought.
  • Deliver 5 free packets.

Deliverable: Referral offer live, 20 reactivations attempted

Day 26Close centers

Higher-ARPU pilots

  • Follow up all 40 center contacts.
  • Offer a $79 multi-tutor pilot to two centers.
  • Deliver 4 center packets.

Deliverable: Two center pilots formally proposed

Day 27Bundle

Lift average order value

  • Bundle 10-pack plus first month Starter at $59.
  • Email the bundle to every free-sample tutor.
  • Deliver 5 free packets.

Deliverable: Bundle mailed to all warm leads

Day 28Reconcile

Week-four audit

  • Reconcile Stripe collected revenue against packets delivered.
  • Refund any undelivered order the same day.
  • Set the final two-day push target.

Deliverable: Reconciled revenue sheet with zero undelivered orders

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

Close warm leads

  • Send a last-call message to every warm lead.
  • Take 20 fresh DMs in the highest-reply group.
  • Deliver every outstanding packet before midnight.

Deliverable: All warm leads contacted, packet backlog cleared

Day 30Verify

Lock the numbers

  • Export final Stripe and TrustMRR figures.
  • Confirm every PDF delivered and no chargebacks pending.
  • Write the public 30-day summary using real numbers only.

Deliverable: Verified profit figure and public summary

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

  • Blended price of $49 per paying customer is used across scenarios (mix of $49 one-time, $29 monthly and a few $79 monthly).
  • Payment processing assumed at roughly 4% blended (Stripe 2.9% + $0.30 on a $49 charge plus card mix).
  • All traffic is organic one-to-one outreach; ad_spend is 0 in Conservative and Base and only appears in Upside for paid group sponsorship tests.
  • Operating costs cover Vercel, Supabase, domain, Resend and LLM/vision usage; delivery cost per packet is modelled under $0.20.
  • Conservative: outreach reply rate stalls and only 8 tutors pay in 30 days.
  • Base: roughly 350 targeted messages at a 6% paid conversion yields 22 paying customers.
  • Upside: 600 messages plus referral loop and two center pilots yield 42 paying customers, with one refund.
  • All figures are projections derived from stated assumptions, not verified revenue or existing customers.

Conservative

8 customers
$392
collected revenue · avg payment $49
Refunds
$0
Chargebacks
$0
Payment fees
$16
Paid marketing
$0
Hackathon profit
$376
Operating costs
$25
Business profit
$351

Base case

22 customers
$1,078
collected revenue · avg payment $49
Refunds
$0
Chargebacks
$0
Payment fees
$43
Paid marketing
$0
Hackathon profit
$1,035
Operating costs
$55
Business profit
$980

Optimistic

42 customers
$2,058
collected revenue · avg payment $49
Refunds
$49
Chargebacks
$0
Payment fees
$82
Paid marketing
$120
Hackathon profit
$1,807
Operating costs
$95
Business profit
$1,712

Model your own numbers

Runs in your browser · nothing is saved
Collected revenue
$1,078
Payment fees (3.9%)
$42
Paid marketing
$0
Hackathon profit
$1,036
Business profit
$981

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. No customers, revenue or partnerships exist yet; all three scenarios are projections only.

Section 7 of 8

Main risks and validation experiments

Risk 1Generated math items contain wrong answers, destroying tutor trust on the first packet.

Mitigation

Deterministic recomputation of every generated item before render; regenerate once on failure; manual review flag when the checker is unsure.

Validation experiment

Run 20 real worksheets through the pipeline and have one tutor grade the answer keys blind.

Kill criteria

If more than 2 of 20 packets ship with a wrong answer after verification, stop selling and rebuild the checker.

Risk 2Photo segmentation of dense or low-quality worksheets fails often enough that the 24-hour free-sample promise breaks.

Mitigation

Founder manually crops during week one; add a retry hint and quality check on upload; log every failure with the image.

Validation experiment

Upload 25 varied worksheet photos and record the share that segment into usable cards without manual help.

Kill criteria

If fewer than 70% segment cleanly by day 9, narrow the promise to PDFs and clean scans only.

Risk 3Tutors decide a general chatbot plus a word processor is good enough and refuse to pay.

Mitigation

Lead with the finished artifact, not the technology; show the branded PDF and answer-key page side by side with a chatbot output.

Validation experiment

Send the $49 offer to 20 tutors who received a free packet and record the exact refusal reason for each.

Kill criteria

If 20 free-sample tutors produce zero paid conversions by day 15, change the price or the artifact contract.

Risk 4Free-sample outreach attracts many requests and few paying customers, burning the 30 days.

Mitigation

Cap free samples at 5 per day, always attach a 48-hour paid follow-up, and track free-to-paid rate daily.

Validation experiment

Compare paid conversion for tutors who got the packet versus tutors who only saw a screenshot.

Kill criteria

If free-to-paid conversion stays under 5% after 30 samples, switch to paid-first with a money-back guarantee.

Risk 5Facebook group moderators treat the DM outreach as spam and remove channel access.

Mitigation

Only message where group rules permit; prioritize Reddit and center 'meet the tutors' pages as backup channels; never post the same text twice in one group.

Validation experiment

Track message-to-reply rate per community daily and drop any community below 3% reply.

Kill criteria

If two of three primary communities block access, shift primary channel to center website emails.

Risk 6Payment-account or TrustMRR connection is not live before launch, costing revenue days.

Mitigation

Complete the Stripe and TrustMRR connection on day 1 before any code beyond the skeleton, and test a live $1 charge to self.

Validation experiment

Run one live charge and refund it in the first 24 hours.

Kill criteria

If the connection is not live by end of day 2, freeze build work until it is.

Section 8 of 8

Hour-by-hour: the first 24 hours

Hours 1-2

  • Create the Next.js repo and Supabase project; deploy hello-world to Vercel.
  • Open Stripe and complete the TrustMRR payment-account connection.

Output: Deployed skeleton and a live payment account

Hours 3-4

  • Write the ~120-skill taxonomy JSON with prerequisite links.
  • Draft the 3-line outreach message and the free-packet promise.

Output: taxonomy.json v0 and final outreach copy

Hours 5-6

  • Build a 60-name tutor list from public Facebook groups, r/Tutors and center 'meet the tutors' pages.
  • Record name, public contact route and source for each.

Output: 60-row outreach sheet with contact routes

Hours 7-9

  • Build the upload route and wire the vision segmentation call.
  • Return numbered question cards with cropped thumbnails.

Output: Working upload-to-question-cards route

Hours 10-12

  • Run 3 real worksheets through segmentation and log failures.
  • Send the first 5 free-sample offers so replies arrive while you build.

Output: Segmentation baseline plus 5 outreach messages sent

Complete report

Full 30-day launch report

Read the full generated report

Redo Pack — 30-Day Launch Report

1. Product opportunity and positioning

The buyer is one person: a solo math or reading tutor, or a 1–8 tutor center, charging $50–$120 an hour in the US, UK, Canada or Australia. The trigger is weekly and unambiguous — a student returns with a graded quiz or homework sheet where several items are wrong, and the next session needs material on exactly those skills.

Today the tutor rebuilds that material from scratch the night before: retyping similar problems, hunting for items at the right difficulty, writing worked solutions by hand, drafting a parent update. That is 20–40 minutes per student per week of unpaid prep, and when the week is busy it is skipped, so the student redoes the same sheet.

The JEV score of 64.5 (band C) flags market demand as the weak link, not speed to revenue (9.0). So the plan spends its first week proving willingness to pay with a finished artifact rather than building a platform. The wedge holds because the buyer can approve $49 on a card with no procurement, the trigger recurs weekly, and the deliverable is a document handed to a paying parent the same afternoon — which makes every packet a distribution unit.

Differentiation is the artifact, not the model. A chatbot writes plausible problems; it will not reliably pin the missed item to a skill and prerequisite, verify its own arithmetic, carry the tutor's logo, split the answer key onto its own page, and land as a print-ready PDF in 90 seconds.

2. Smallest sellable MVP

One page: upload a blank worksheet, tap the missed question numbers, receive a branded PDF. That is the entire sellable unit. It needs nine things and nothing else — segmentation, the tap UI, skill tagging against a fixed ~120-skill taxonomy, packet generation (3 warm-ups, 4 mirrors, 2 stretch), a verification pass, a branded renderer with a separate answer-key page, a parent note, Stripe checkout and emailed delivery.

Explicitly out: auto-grading handwriting, LMS features, parent logins, school procurement, a licensed content library, a marketplace. Everything on that list would add weeks and remove the ability to close a tutor by DM in week one.

3. Technical implementation plan

Next.js on Vercel, Supabase for auth, Postgres and storage, two LLM calls (vision for segmentation and tagging, text for item generation), a deterministic TypeScript answer checker, React-PDF, Stripe Checkout with metered billing, and Resend.

Order matters: foundation and taxonomy on day 1, upload and segmentation on day 2, generation and checking on day 3, rendering on day 4, billing and delivery on day 5. The single riskiest component is segmentation of messy phone photos — the founder manually crops for the first week and logs every failure, so the 24-hour free-sample promise never breaks while the automation improves.

4. Pricing and monetization

Three tiers: $49 one-time for 10 packets, $29/month for 20 packets, $79/month unlimited with multi-tutor branding. The $49 pack exists to convert a free sample into cash immediately without a subscription decision; the $29 plan is the default landing spot after packet three; $79 is for centers and full-time tutors. Delivery cost per packet is under $0.20, so every tier clears its marginal cost by a wide margin. Expected blended ACV used in all projections is $49.

5. First-customer acquisition

One channel only: direct one-to-one messages to named tutors in public tutor Facebook groups, Reddit r/Tutors and center 'meet the tutors' pages. The offer is never a demo — it is a finished packet. 'Send a photo of a blank sheet and tell me which numbers they missed; I'll send the PDF free within 24 hours.' Deliver, then ask one question: 'how long would this have taken you?' Forty-eight hours later, send the $49 link. Ask every buyer for one intro, and let the PDF footer carry the referral loop.

6. 30-day execution roadmap

Days 1–5 build the MVP; day 5 is the hard deadline to accept payment. Days 6–7 deliver the first free packets and establish a reply-rate baseline. Days 8–14 convert: paid asks, objection-driven rewrites of the offer, first sale targeted for day 12. Days 15–21 shift buyers from one-time packs to $29 subscriptions, add centers, ship the referral footer and pitch $79 Pro. Days 22–28 focus on retention, a public case study, sub-60-second packet latency and a $59 bundle. Days 29–30 close warm leads, reconcile Stripe against packets delivered, and publish only real numbers.

7. Revenue and profit scenarios (projections only)

Conservative: 8 customers at $49 = $392 gross, $16 fees, $25 operating. Base: 22 customers at $49 = $1,078 gross, $43 fees, $55 operating, giving $1,035 hackathon profit and $980 business profit. Upside: 42 customers at $49 = $2,058 gross, one $49 refund, $82 fees, $120 ad spend, $95 operating, giving $1,807 hackathon profit and $1,712 business profit. These are hypotheses built from message volume and conversion assumptions, not verified revenue — no customers exist yet.

8. Risks and validation experiments

Wrong answers in a packet would end trust, so every generated item is recomputed deterministically and 20 real worksheets are blind-graded by a tutor before scaling. Segmentation failure is tested with 25 varied photos; below 70% clean segmentation by day 9, the promise narrows to PDFs and clean scans. Chatbot-substitution risk is tested by tracking the exact refusal reason across 20 free-sample tutors. Free-sample overload is capped at five per day with a mandatory 48-hour paid follow-up. Channel loss is monitored per community, with center website emails as the backup. Payment setup is validated on day 1 with a live $1 self-charge.

9. First 24 hours

Hours 1–2: repo, Supabase, Vercel deploy, Stripe and TrustMRR live. Hours 3–4: taxonomy JSON and final outreach copy. Hours 5–6: 60-name tutor list with public contact routes. Hours 7–9: upload route and vision segmentation returning numbered cards. Hours 10–12: three test worksheets logged and the first five free-sample offers sent so replies arrive while the build continues. End of day one: a live skeleton, a live payment account, and messages in inboxes.

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 →