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

Tutor Intake Packet

Turns phone photos of a math student's marked-up work into a branded, parent-ready diagnostic one-pager plus a 3-session plan, so an independent tutor can walk into (or sell) the first lesson already looking like an expert.

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.35/10
MVP build (solo)
4 days
Launch price
$19
Sales to $1,000 revenue
53 customers
First paying customer
Direct outreach to independent math tutors inside existing tutor communities (Facebook tutor business groups, r/tutors, tutor Discord and Slack groups), leading with a free sample packet rather than a pitch.
Who pays

Solo and 2-4 person independent math tutoring practices teaching grades 5-9 (pre-algebra/algebra), billing $40-80/hour, 1:1 online or in a home studio, in the US/UK/CA/AU, triggered by a live parent inquiry or a first diagnostic session booked this week.

Biggest execution risk

Operational simplicity 4.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; 53 sales at $19 clears $1,000 of collected revenue; strongest signal is speed to first revenue at 8.4/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
$19
Solo build
4 days
30d base revenue
$836
30d hackathon profit
$755
Section 1 of 8

Product opportunity and positioning

Target customer

Solo and 2-4 person independent math tutoring practices teaching grades 5-9 (pre-algebra/algebra), billing $40-80/hour, 1:1 online or in a home studio, in the US/UK/CA/AU, triggered by a live parent inquiry or a first diagnostic session booked this week.

Why now

Vision models now read legible phone photos of worksheets well enough that a packet costs under $0.50 to deliver, so a $19 self-serve product clears its own delivery cost with zero human operations and no integration for the tutor.

Problem

The first session with a new student is a sales call disguised as a lesson: 30-45 minutes, no history, and a parent waiting for proof of expertise. The tutor improvises, spots a few errors, promises a written plan, and never types it up.

Solution

Tutor uploads 1-5 photos of marked-up work and a grade band. The pipeline transcribes each item, classifies every miss as execution slip, missing prerequisite or active misconception against a curated grade 5-9 concept graph, then returns a 3-session plan (warm-up, mini-lesson, practice, exit check) and a one-page parent brief carrying the tutor's name, logo and booking link.

Differentiation · A chatbot returns advice inside a chat window. This returns two branded PDFs plus prerequisite logic built on an explicit grade 5-9 concept graph that separates a careless slip from a missing fractions prerequisite.

Product opportunity and positioning

A parent emails a tutor about a 12-year-old who "is fine at math but froze on the test." The tutor books a first session. That session is a sales call dressed as a lesson: 30-45 minutes, no history, and a parent listening for the moment the tutor says something specific enough to be true.

Today the tutor improvises. They print a worksheet, watch the child work, spot three errors, name a probable cause, and promise a written plan — which is typed up later, or never. The parent leaves with a feeling, not a document.

The generic alternative is a chatbot prompt. It produces advice in a chat window: no artifact, no branding, no prerequisite logic, and no way to distinguish a careless arithmetic slip from a missing fractions prerequisite that will quietly undermine the next six months of algebra. Advice is not what the tutor needs at that moment. A document is.

Tutor Intake Packet produces the document. The tutor uploads one to five phone photos of the child's marked-up work and picks a grade band. The product transcribes each item, classifies every miss as an execution slip, a missing prerequisite or an active misconception, resolves missing prerequisites against a hand-built grade 5-9 concept graph, and returns two files: a three-session plan (warm-up, targeted mini-lesson, practice set, exit check) and a one-page parent brief carrying the tutor's own name, logo and booking link.

The buyer is a solo or 2-4 tutor independent math practice charging $40-80 an hour in the US, UK, Canada or Australia. They spend $19-$129 from a personal or business card with no procurement, no IT review and no data integration. The trigger is live and dated: a parent inquiry in the inbox this week.

The scoring is honest about the shape of this business. JEV rated the concept 63.5/100 in band C — strong on speed to first revenue (8.37 normalized) and reachable customers (6.29), weak on operational simplicity (4.78) because the product touches photographs of minors' schoolwork and depends on vision accuracy. This plan is built around exactly that: sell inside the first ten days, keep the data surface to a stored image with a 30-day deletion clock, and never let a wrong prerequisite chain reach a parent.

The wedge holds because the price is anchored to a single booking. Twenty sessions at $60 is $1,200. A $19 packet is noise against that, and the output is shareable: every parent brief carries the tutor's brand, which is what makes the tutor send it — and what makes the next tutor ask what produced it.

Section 2 of 8

Smallest sellable MVP

A $19 self-serve flow: pick a grade band, upload 1-5 photos of marked-up work, pay by card, receive a branded parent one-pager PDF and a 3-session plan PDF by email the same day.

Must-have features

  • Intake form: grade band (5-9), topic, optional context note, 1-5 image uploads or pasted answers
  • Vision extraction into structured items (problem, student answer, correct answer) with a confidence flag per item
  • Error taxonomy classifier: execution slip / missing prerequisite / active misconception, with named concept
  • Hand-curated grade 5-9 concept graph (~150 concepts with prerequisite edges) committed as versioned JSON
  • 3-session plan generator: warm-up, targeted mini-lesson, practice set, exit check per gap
  • Parent one-pager PDF renderer using the tutor's name, logo and booking link
  • Stripe Checkout credit packs ($19/$39/$129) plus a reusable intake link that decrements credits
  • Landing page with two worked sample packets built on synthetic student work

Explicitly out of scope

  • No student-facing accounts or live AI chat tutor
  • No scheduling, tutor-to-parent payments, or CRM
  • No subjects outside grade 5-9 math in the first 30 days
  • No school, district or franchise sales motion
  • No team seats, SSO or admin roles
  • No 24/7 support promise beyond a shared inbox and a documented FAQ

Demo flow (what the buyer sees)

  1. Tutor opens the public landing page and clicks 'See a sample packet'
  2. Tutor views a synthetic parent one-pager and its matching 3-session plan
  3. Tutor buys a $19 Single Autopsy via Stripe Checkout and gets a reusable intake link
  4. Tutor uploads 1-5 photos of marked-up work and selects grade 7
  5. Extraction returns structured items with confidence flags on any illegible line
  6. Classifier assigns each miss an error type and a named concept
  7. Graph resolver produces an ordered gap list capped at three prerequisite levels deep
  8. Plan and parent brief PDFs render with the tutor's name, logo and booking link
  9. Both PDFs land in the tutor's inbox via Resend within minutes
Build plan

Technical implementation plan

Stack

Next.js on VercelSupabase (Postgres, storage, magic-link auth)Anthropic Claude vision APIAnthropic Claude text calls for classification and plan generation@react-pdf/rendererStripe Checkout + webhooksResend for delivery emailStatic concept-graph JSON committed to the repo

Architecture

Next.js on Vercel serves the intake form and a thin tutor dashboard. Supabase holds tutors, credits, packets and the uploaded images. On submit, a serverless route sends each image to Claude vision with a strict JSON schema, writes structured items to Postgres, runs the classifier, resolves prerequisites against the graph bundled in the repo, generates the plan, renders both PDFs with @react-pdf/renderer, stores them in Supabase storage, and emails signed links via Resend. Stripe webhooks top up credits; the reusable intake link decrements them. A scheduled job deletes images 30 days after upload.

Build steps

  1. Define the concept JSON schema (id, label, grade, prerequisite ids) and write a cycle validator
  2. Seed 40 fraction, ratio and integer concepts by hand to prove the schema
  3. Scaffold Next.js on Vercel, connect Supabase, ship magic-link auth
  4. Build the tutor profile (name, logo upload, booking link) and the intake form
  5. Wire Supabase storage uploads and signed URLs for 1-5 images
  6. Implement the Claude vision extraction call with a strict schema and per-item confidence
  7. Implement the classifier and the graph resolver with a depth cap of three
  8. Implement the 3-session plan generator with a fixed JSON output contract
  9. Build the parent one-pager template in @react-pdf/renderer with logo and booking link
  10. Add Resend delivery and store rendered PDFs in Supabase storage
  11. Add Stripe Checkout for three credit packs, webhook credit top-up and the reusable intake link
  12. Ship the landing page with two synthetic sample packets
  13. Add the 30-day image deletion job and the data policy page
  14. Deploy, run five synthetic packets end to end, fix the two worst outputs

AI components

  • Claude vision: transcribe problem, student answer and correct answer from each photo
  • Claude text: classify each miss into execution slip, missing prerequisite or active misconception
  • Claude text: generate the 3-session plan and the plain-language parent brief
Hardest technical risk: Vision misreading messy handwriting and confidently naming the wrong concept — one wrong prerequisite claim repeated to a parent destroys tutor trust and triggers a refund.
Section 3 of 8

Pricing and monetization

Single Autopsy

Entry offer
$19 one-time

For A tutor with one specific student in front of them this week

  • 1 diagnostic packet
  • 3-session plan
  • 1 branded parent one-pager PDF

Solo Pack

$39 one-time

For A solo tutor onboarding 4-8 new students a month

  • 5 diagnostic packets
  • Branded parent one-pagers
  • Reusable intake link

Practice Pack

$129 one-time

For A 2-4 tutor practice handling a steady inquiry flow

  • 25 diagnostic packets
  • Custom logo on parent one-pagers
  • Reusable intake link
  • Priority email turnaround

Model: One-time credit packs sold self-serve through Stripe, priced against a single tutoring booking.

First revenue offer: $19 Single Autopsy, with the first packet free: reply with 2-3 photos and the grade band, get the PDFs back the same day, pay only if you want the next one.

Expected ACV: $59

Upsell path: Free packet to $19 Single Autopsy, then $39 Solo Pack once the tutor has two or more inquiries, then $129 Practice Pack when a second tutor joins the practice.

Target customers
30
Revenue model
$1,770
Costs
$120
Profit model
$1,650
Section 4 of 8

First-customer acquisition

Primary channel

Direct outreach to independent math tutors inside existing tutor communities (Facebook tutor business groups, r/tutors, tutor Discord and Slack groups), leading with a free sample packet rather than a pitch.

Where to find them

  • Facebook groups for independent tutors and tutoring business owners
  • r/tutors and r/matheducation threads about first sessions and assessments
  • Tutor Discord and Slack communities (side-hustle tutoring, test-prep tutor groups)
  • Outschool and Wyzant tutor profiles with recent activity in grades 5-9 math
  • Posts where a tutor says they are taking on new students this month
  • Local tutor association forums in the US, UK and Australia

Exact outreach motions

  • Read two days of posts in each community before posting anything, logging the vocabulary tutors use for first sessions
  • Publish a 'Wrong-Answer Autopsy' teardown on synthetic work with the parent one-pager image and the 3-session plan attached
  • Offer a free packet to anyone who comments, delivered through the public intake link within four hours, no card required
  • DM 20 tutors a day who posted about new students, referencing their exact post and offering the free packet first
  • Follow up once at 24 hours with the $19 Single Autopsy link, and again at day 4 with the $39 Solo Pack
  • Ask every recipient whether the parent one-pager actually got sent, and publish that count (not revenue) as social proof

Message template

Hi [Name] — saw your post about taking on a new algebra student. I built a tool that turns phone photos of a kid's marked-up worksheet into a branded one-page parent brief plus a 3-session plan you can bring to session one. Want one free for that student? Reply with 2-3 photos and the grade band; I'll send the PDFs back today. No card.
Week-one goal: MVP live and purchasable by day 6; 150 tutors logged with post links, 2 teardowns published, 20 DMs sent, and at least 3 free packets delivered.
Section 5 of 8

30-day execution roadmap

MVP deadline: day 6First sale target: day 1030 days planned
Week 1 · Build & validate · 7 days
Day 1Concept graph

Model the prerequisite graph

  • Define concept JSON schema: id, label, grade, prereqs
  • Seed 40 core fraction, ratio and integer concepts by hand
  • Commit graph v0 plus a cycle validator script

Deliverable: concept_graph_v0.json with 40 concepts and a passing validator

Day 2App skeleton

Auth and intake form

  • Scaffold Next.js on Vercel, connect Supabase
  • Magic-link auth plus tutor profile with name, logo, booking link
  • Intake form: grade band, topic, context note, 1-5 uploads

Deliverable: Deployed intake form writing rows to Supabase

Day 3Extraction

Vision pipeline

  • Store uploads in Supabase storage with signed URLs
  • Claude vision call returns structured items with confidence
  • Persist items and low-confidence flags

Deliverable: Photos to structured items in Postgres

Day 4Diagnosis

Classification and graph resolution

  • Classify each miss: slip, missing prerequisite, misconception
  • Resolve prerequisites against the graph, cap depth at three
  • Emit an ordered gap list per packet

Deliverable: Gap report JSON for any uploaded packet

Day 5Outputs

Plan and parent PDF

  • Generate 3 sessions with mini-lesson, practice and exit check
  • Render parent one-pager with tutor name, logo and booking link
  • Email both PDFs via Resend

Deliverable: Two branded PDFs delivered by email

Day 6Payments and launchMVP shipped

Stripe and landing page

  • Stripe Checkout for $19, $39 and $129 credit packs
  • Reusable intake link that decrements credits
  • Landing page with two synthetic sample packets; deploy

Deliverable: Public MVP live and purchasable (MVP deadline)

Day 7Channel prep

Community research and list building

  • Join five tutor communities and read only
  • Log recurring vocabulary about first sessions and parent inquiries
  • Build a list of 150 tutors who posted about new students

Deliverable: Outreach list of 150 tutors with post links

Week 2 · Launch & first sale · 7 days
Day 8Teardown content

First public artifact

  • Create a synthetic marked-up worksheet
  • Publish teardown #1 with the parent one-pager image
  • Cross-post to r/tutors and one Facebook group

Deliverable: Two public teardown posts live

Day 9First outreach

Free packet offer

  • DM 20 tutors with the free-packet offer
  • Deliver requested packets the same day
  • Track replies and objections in a sheet

Deliverable: 20 DMs sent, 3-6 free packets queued

Day 10First sale pushFirst sale target

Convert free to paid

  • Follow up at 24 hours with the $19 Single Autopsy link
  • Deliver free packets within four hours of upload
  • Ask each recipient whether the parent PDF was sent

Deliverable: First paid packet (target day 10)

Day 11Volume

Widen the top of funnel

  • DM 20 more tutors
  • Post teardown #2 in two new communities
  • Fix the top three friction points in the intake flow

Deliverable: 40 total DMs and two teardowns live

Day 12Trust

Reduce data objections

  • Add confidence-flag display and manual paste fallback
  • Publish a one-paragraph data policy: 30-day deletion, no training
  • Update the FAQ page

Deliverable: Data policy page live

Day 13Graph depth

Improve prerequisite accuracy

  • Expand the graph from 40 to 90 concepts
  • Add unit-rate and proportion edges
  • Spot-check prerequisite claims across delivered packets

Deliverable: Graph v1 at 90 concepts

Day 14Review

Measure week two

  • Count packets delivered, PDFs sent, and paid conversions
  • Retire the worst-performing message angle
  • Write a fresh list of 100 tutors

Deliverable: Week-2 metrics note and a new outreach list

Week 3 · Repeat & systematize · 7 days
Day 15Scale DMs

Push the winning angle

  • DM 25 tutors with the best-performing angle
  • Offer $39 Solo Pack to anyone with two or more students
  • Log objections verbatim

Deliverable: 25 DMs sent and an objection log

Day 16Objection handling

Landing page rewrite

  • Rewrite the hero around the top objection
  • Record a 20-second screen demo
  • Ship both to production

Deliverable: Landing v2 with demo video

Day 17Second channel test

Public replies over DMs

  • Post a wrong-answer autopsy thread on X
  • Reply to 10 tutor questions with a free packet
  • Keep paid spend at zero

Deliverable: 10 reply-based free packets

Day 18Delivery quality

Fix the worst outputs

  • Review 15 generated plans for correctness
  • Tighten prompts on the three worst outputs
  • Add an exit-check item bank per topic

Deliverable: Prompt v3 and an item bank

Day 19Practice Pack push

Higher ticket test

  • DM practices with 2-4 tutors
  • Offer $129 Practice Pack with custom logo upload
  • Ask for a two-sentence testimonial about the PDF

Deliverable: First Practice Pack conversation opened

Day 20Referral surface

Slow referral loop

  • Add an optional 'made with' line to the parent PDF
  • Email past buyers their reusable intake link
  • Ask each for one named introduction

Deliverable: Referral loop shipped

Day 21Review

Price and mix decision

  • Recount customers, blended ARPU and refunds
  • Decide whether to hold price or discount
  • Refresh the outreach list

Deliverable: Week-3 metrics and a pricing decision

Week 4 · Scale what works · 7 days
Day 22Community trust

Give before asking

  • Answer five non-promotional questions in each community
  • Publish a free grade-5 fractions packet template
  • Keep the post pitch-free

Deliverable: Free template download page live

Day 23Volume DMs

Restart stalled conversations

  • DM 30 tutors
  • Follow up every unpaid free-packet recipient once
  • Send the $19 link exactly once per person

Deliverable: 30 DMs and 15 follow-ups sent

Day 24Refund defense

Set expectations before purchase

  • Add a sample PDF preview before checkout
  • State exactly what a packet contains
  • Add one-click resend of any delivered packet

Deliverable: Preview and expectations page shipped

Day 25Graph breadth

Reach full coverage

  • Add grade 9 algebra and geometry edges to reach 150 concepts
  • Run the validator over every edge
  • Version-stamp the graph inside each PDF

Deliverable: Graph v2 at 150 concepts

Day 26Conversion fix

Message test

  • A/B test free-first vs paid-first DM copy
  • Measure reply-to-paid rate per angle
  • Keep the winner and delete the loser

Deliverable: Message test result with two rates

Day 27Upsell

Expand existing buyers

  • Email $19 buyers a discounted upgrade to Solo Pack
  • Track upgrade link clicks
  • Add the upgrade link to the delivery email

Deliverable: Upgrade email sent to all buyers

Day 28Review

Verified profit inputs

  • Recount revenue, refunds, fees and ad spend
  • List every refund with its stated reason
  • Set the final-week target

Deliverable: Week-4 profit input note

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

Maximum outbound

  • DM 40 tutors with the winning angle
  • Publish a final teardown post
  • Deliver every packet same day

Deliverable: 40 DMs and a final public post

Day 30Close

Verified numbers only

  • Export Stripe revenue, refunds and processing fees
  • Publish a build log using real numbers only
  • Decide post-hackathon pricing and retention offer

Deliverable: Verified revenue export and public build log

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: 5 buyers, mostly $19 and $39 singles, blended ARPU $27.
  • Base: 22 buyers over 30 days with roughly one in six taking the $129 Practice Pack, blended ARPU $38.
  • Upside: 45 buyers after a teardown post lands in a large community, blended ARPU $48.
  • Payment processing assumed at Stripe 2.9% + $0.30, modeled at 5% of gross because tickets are small.
  • Refunds: one packet in conservative, two in base, three plus one chargeback in upside.
  • Operating costs cover Vercel, Supabase, Resend and Claude API at roughly $0.40 per packet plus about $15-20 fixed monthly.
  • Ad spend is zero in conservative and base (organic DMs only); upside assumes $200 of sponsored community posts and boosts.
  • No customers, revenue, partnerships or traction exist yet; every figure here is a projection.

Conservative

5 customers
$135
collected revenue · avg payment $27
Refunds
$19
Chargebacks
$0
Payment fees
$7
Paid marketing
$0
Hackathon profit
$109
Operating costs
$18
Business profit
$91

Base case

22 customers
$836
collected revenue · avg payment $38
Refunds
$39
Chargebacks
$0
Payment fees
$42
Paid marketing
$0
Hackathon profit
$755
Operating costs
$45
Business profit
$710

Optimistic

45 customers
$2,160
collected revenue · avg payment $48
Refunds
$78
Chargebacks
$19
Payment fees
$108
Paid marketing
$200
Hackathon profit
$1,755
Operating costs
$90
Business profit
$1,665

Model your own numbers

Runs in your browser · nothing is saved
Collected revenue
$418
Payment fees (3.9%)
$16
Paid marketing
$0
Hackathon profit
$402
Business profit
$357

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. Hackathon profit excludes hosting, tooling and AI delivery costs; business profit deducts them.

Section 7 of 8

Main risks and validation experiments

Risk 1Tutors substitute a free chatbot prompt and never pay, because the branded PDF's marginal value is invisible until seen.

Mitigation

Lead every touch with a rendered sample parent one-pager image, not a description, and give the first packet free.

Validation experiment

Send 20 free packets in week two and count how many recipients ask for a second packet or send the PDF to a parent.

Kill criteria

If fewer than 10% of free-packet recipients ask for another packet or open a paid link, the artifact is not the value; re-cut to a sellable plan-only product or stop.

Risk 2Cold DM conversion lands nearer 1% than the modeled 3-5%, cutting the 30-day customer count by two thirds.

Mitigation

Run two DM angles in parallel from day 9 and shift all volume to the winner by day 16.

Validation experiment

Track reply rate and paid rate per angle across 40 DMs each by day 14.

Kill criteria

If 120 DMs produce zero paid packets by day 18, change channel to the free public teardown and template download before day 22.

Risk 3Vision misreads messy handwriting and names the wrong prerequisite, and the tutor repeats it to a parent.

Mitigation

Per-item confidence flags with a manual paste fallback, plus a hard rule that low-confidence items are shown as unclassified rather than guessed.

Validation experiment

Run 10 packets on deliberately degraded photos and have one tutor review the gap list for correctness.

Kill criteria

If more than 20% of items on legible photos come back low confidence, restrict to pasted answers and typed problem text before selling more.

Risk 4Community moderators treat the teardown posts as promotion and remove them, closing the main channel.

Mitigation

Post the artifact as a free answer to a real question first, keep the link out of the body, and never post the same teardown in two communities the same day.

Validation experiment

Publish teardown #1 and measure whether a moderator acts and whether comments convert to free-packet requests within 24 hours.

Kill criteria

If two of five communities remove the post, eliminate community posting and move entirely to one-to-one DMs plus the template download.

Risk 5Handling photographs of minors' schoolwork raises COPPA/GDPR-adjacent objections and blocks the cautious buyers.

Mitigation

No student accounts, 30-day automatic image deletion, no training on uploaded work, and a plain-language data policy page linked from checkout.

Validation experiment

Publish the policy page and record how many DM conversations raise a data objection before and after day 12.

Kill criteria

If data objections appear in more than a third of DM replies, add a client-side redaction step that strips names before upload.

Section 8 of 8

Hour-by-hour: the first 24 hours

Hours 1-2

  • Write the concept JSON schema with id, label, grade and prereq ids
  • Hand-seed fractions, ratios and integers to 40 concepts
  • Run a cycle validator over every edge

Output: concept_graph_v0.json and a passing validator script

Hours 3-5

  • Create the Next.js repo and deploy the skeleton to Vercel
  • Provision Supabase, enable magic-link auth
  • Create tables for tutors, credits and packets

Output: Live deployed shell with Supabase connected

Hours 6-8

  • Build the intake form with grade band and topic
  • Wire 1-5 image uploads to Supabase storage
  • Create the tutor profile fields for name, logo and booking link

Output: Working intake form that stores a packet row with images

Hours 9-11

  • Create a synthetic marked-up grade 7 worksheet
  • Call Claude vision with a strict JSON schema on it
  • Write structured items with confidence flags to Postgres

Output: One real extraction row from a synthetic worksheet

Hours 12-14

  • Join five tutor communities and read only
  • Log the vocabulary tutors use about first sessions
  • Collect 40 tutor posts about taking on new students

Output: Outreach list of 40 tutors with post links and quotes

Hours 15-16

  • Draft the free-packet DM and the $19 follow-up
  • Set up a tracking sheet for DMs, packets and payments
  • List the remaining MVP tasks against the day 6 deadline

Output: DM copy, tracking sheet and a day-by-day build checklist

Complete report

Full 30-day launch report

Read the full generated report

Tutor Intake Packet — 30-Day Solo Launch Report

Concept: Tutor Intake Packet v1 · JEV score: 63.5/100 (band C, confidence 0.66) · Window: 30 days, one founder, no team.

1. Product opportunity and positioning

A parent emails a tutor about a 12-year-old who is "fine at math but froze on the test." The tutor books a first session. That session is a sales call dressed as a lesson: 30-45 minutes, no history, and a parent listening for the moment the tutor says something specific enough to be true.

Today the tutor improvises. They print a worksheet, watch the child work, spot three errors, name a probable cause, and promise a written plan — typed up later, or never. The parent leaves with a feeling, not a document.

The generic alternative is a chatbot prompt. It returns advice in a chat window: no artifact, no branding, no prerequisite logic, and no way to separate a careless arithmetic slip from a missing fractions prerequisite that will quietly undermine six months of algebra. Advice is not what the tutor needs in that room. A document is.

Tutor Intake Packet produces the document. The tutor uploads one to five phone photos and picks a grade band. The product transcribes each item, classifies every miss as execution slip, missing prerequisite or active misconception, resolves gaps against a hand-built grade 5-9 concept graph, and returns two files: a three-session plan (warm-up, mini-lesson, practice, exit check) and a one-page parent brief carrying the tutor's own name, logo and booking link.

The buyer is a solo or 2-4 tutor independent math practice at $40-80/hour in the US, UK, Canada or Australia. They approve $19-$129 personally: no procurement, no IT review, no data integration. The trigger is dated — a parent inquiry in the inbox this week.

JEV was honest about the shape of this business. Strongest axis is speed to first revenue (8.37 normalized); weakest is operational simplicity (4.78), because the product touches photographs of minors' schoolwork and depends on vision accuracy. This plan is built around those two facts: sell inside the first ten days, and keep the data surface to a stored image with a 30-day deletion clock.

The price is anchored to one booking. Twenty sessions at $60 is $1,200. A $19 packet is noise against that, and every parent brief carries the tutor's brand — which is why the tutor sends it, and why the next tutor asks what produced it.

2. Smallest sellable MVP

One page: grade band, 1-5 photo uploads, optional context note. Behind it: a vision call, a classifier, a concept graph, a plan generator, a PDF renderer. In front of it: Stripe Checkout and a reusable intake link.

Sellable unit: $19 for one packet delivered by email within hours. The MVP is done when a stranger can pay $19, upload photos, and receive two branded PDFs without the founder touching it.

Not built: student accounts, live chat tutoring, scheduling, CRM, non-math subjects, school or district sales, team seats, and any support promise beyond a shared inbox and a documented FAQ.

3. Technical implementation plan

Next.js on Vercel, Supabase for Postgres, storage and magic-link auth, Claude vision for transcription, Claude text for classification and plan generation, @react-pdf/renderer for the parent one-pager, Stripe Checkout for credits, Resend for delivery. The concept graph is a JSON file committed to the repo and version-stamped inside every PDF so a tutor can see which graph produced the claim.

Build order is deliberate: schema and 40 hand-seeded concepts first (day 1), extraction second (day 3), classification and graph resolution third (day 4), outputs fourth (day 5), payments last (day 6). The hardest failure is confident misreading of handwriting; the mitigation is a per-item confidence flag and a hard rule that low-confidence items are shown as unclassified rather than guessed.

4. Pricing and monetization

Three one-time credit packs: $19 Single Autopsy (one packet), $39 Solo Pack (five packets, reusable link), $129 Practice Pack (25 packets, custom logo, priority email). Blended ARPU is projected near $38-48 depending on how many practices take the top tier. Nothing is subscription because the trigger is episodic and a one-time price removes the "will I use this monthly" objection from a cold DM.

5. First-customer acquisition

One channel: direct outreach inside existing tutor communities, led by a free packet. No ads in the base case. Sequence: two days of reading, a public "Wrong-Answer Autopsy" teardown built on synthetic work, 20 DMs a day to tutors who just posted about taking new students, free packet delivered within four hours, $19 link at 24 hours, $39 Solo Pack at day 4. The social proof published is the count of parent briefs actually sent — never revenue claims.

6. 30-day execution roadmap

Week 1 (days 1-7) build and launch: graph, extraction, classification, PDF outputs, Stripe, landing page with two synthetic samples — MVP live day 6. Week 2 (8-14) first revenue: teardowns, 40 DMs, free packets, first paid packet targeted day 10, data policy page. Week 3 (15-21) scale the winning angle, second channel test, quality fixes on the worst generated plans, Practice Pack attempt, referral footer. Week 4 (22-28) volume and refund defense: 30 more DMs, sample preview before checkout, graph expanded to 150 concepts, upgrade email to every $19 buyer. Week 5 (29-30) final push and a verified-numbers export. Day-level tasks and deliverables are in the roadmap table below.

7. Revenue and profit scenarios

Projections only, built on stated assumptions, not verified revenue.

  • Conservative: 5 customers at $27 blended ARPU = $135 gross, $19 refunds, $7 processing fees, $0 ads, $18 operating costs.
  • Base: 22 customers at $38 = $836 gross, $39 refunds, $42 fees, $0 ads, $45 operating costs.
  • Upside: 45 customers at $48 = $2,160 gross, $78 refunds, $19 chargebacks, $108 fees, $200 ads, $90 operating costs.

Hackathon profit deducts refunds, chargebacks, processing fees and paid ads. Business profit additionally deducts hosting, tooling and AI delivery. Processing is modeled at 5% of gross because average tickets are small. Every packet still clears its own delivery cost at roughly $0.40 of API spend against a $19 floor.

8. Main risks and validation experiments

  1. Free chatbot substitution. Test: 20 free packets, count who asks for a second. Kill if under 10%.
  2. DM conversion near 1%. Test: two angles, 40 DMs each by day 14. Kill the channel if 120 DMs yield zero paid packets by day 18.
  3. Vision misreads handwriting. Test: 10 deliberately degraded photos reviewed by a tutor. Kill if over 20% of items are low confidence on legible images.
  4. Moderators remove teardowns. Test: teardown #1 in one community, watch for removal and conversion. Kill posting if two of five communities remove it.
  5. Minors' data objection. Test: count data objections before and after the day-12 policy page. Kill risk if it appears in over a third of replies — add client-side name redaction.

9. First 24-hour action plan

Hours 1-2: schema plus 40 hand-seeded concepts and a validator. Hours 3-5: Next.js deployed, Supabase connected, three tables. Hours 6-8: intake form with uploads and tutor profile. Hours 9-11: first real Claude vision extraction on a synthetic grade 7 worksheet. Hours 12-14: join five communities, read only, log vocabulary, collect 40 tutor posts. Hours 15-16: write the free-packet DM, the $19 follow-up, the tracking sheet, and the remaining build checklist against the day 6 deadline.

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 →