SupportED Tutoring · Internal

Product Roadmap: MVP1 to launch

The current Linear baseline, the decisions that unblock MVP1, and the path to a simple paid tutoring or low-ticket entry.

Core release targetNov 15Real students inside, finding the fringe cases
Readiness targetDec 15Staged release, shakeout complete
The real deadlineFebruaryExam-panic season. The revenue window
Cadence2-week sprintsProposed cadence; cycles set in Linear

MVP1 first. Progress from Linear.

Linear owns issues, owners, estimates and sprint commitments. This roadmap explains the release path and the product decisions around it. Editorial revision: 12 October 2026 (UTC).

Reading the current board… Progress unavailable until the read completes.

Execution states and product gatesThe live board below shows the team's existing Linear status names. New request → refinement → accepted scope → release is the proposed review flow, not a new set of saved Linear statuses. Backlog does not prove a request has been refined or accepted; Done does not prove deployment or production acceptance. Those gates remain unverified until their evidence is recorded.

Progress over time

A burnup compares total scope with completed work, so added scope is visible instead of looking like slower delivery. Use the existing Linear project graph for historical progress. This read-only view has today's baseline; historical project membership, scope added/removed and acceptance history are unavailable. No past trend or finish forecast is inferred from issue creation dates.

Counts show tickets, not estimated effort. Project membership is not yet a confirmed release exit scope. Deployed and accepted work needs environment, release evidence and a named reviewer in Linear; Done alone does not prove it.

Product updates

Editorial context, separate from the live execution state. Source cutoff: #app-dev through 9 October; Linear is read at page load.

Scheduling · 9 October

SUP-33, SUP-34 and SUP-35 cover admin cancellation/refund control, rescheduling and overlap locking. The last verified Linear read marked them Done and assigned to Wenbo, with a staging-to-production PR linked. Production deployment and end-user acceptance remain unverified.

BAMFAM (SUP-19) has a production announcement from 26 September; admin first-booking was reported 29 September. Its ticket remains partly open. Reconcile the remaining criteria rather than treating the entire feature as unbuilt.

Scheduling issue in Linear

Assessments · 9 October

SUP-26/27/28/29/31 are component builds marked Done in the last verified read. Jay was still testing uploads and preparing the walkthrough, Wenbo review and team feedback. SUP-30 (admin uploads, tutors verify), SUP-32 (known gaps) and SUP-13 (integration) remain open in that read.

Keep MVP2 workflow, timers/accommodations, notifications and release QA visible. Built components do not establish a released assessment journey.

Assessment workflow in Linear
John's current updateWenbo is updating Linear now. This is John-reported work in progress; the live read below shows the saved execution state. No conclusion is drawn from weekend silence.

12–18 October: proposed priorities

A product recommendation for the week, pending scope and engineering acceptance in Linear.

1. Lock the MVP1 exit scope

Resolve parent/family rules (SUP-9), one student channel and its membership (SUP-10), and self-registration (SUP-21, currently outside the project). Decide whether SUP-18 invitation tracking and the supplementary booking issues are required for this release.

Joe + John decide the product boundaries; Wenbo confirms decomposition, estimates, owners and the cycle. These are decision roles, not new ticket assignments.

2. Accept the scheduling changes

Verify SUP-33–35 and the remaining SUP-19 criteria against the named staging/production environment. Test overlapping requests, allowed roles, credits/refunds, rescheduling and all calendar confirmations. Record evidence and the acceptance reviewer before calling the release shipped.

3. Prove one simple entry journey

For direct tutoring: create account → pay → book a qualified tutor → attend → receive the summary. Resolve trial/payment policy and family credit ownership first. For low ticket, choose one concrete paid deliverable and its first-value event; a simplified AP game plan is a candidate, not a settled offer.

New scope has an explicit cost

Capture discoveries in Linear Backlog. Before adding one to a sprint, agree the owner, acceptance criteria, estimate and what moves out or which target changes. Keep MVP2 work separate unless its inclusion is accepted. There is no second editable task tracker here.

Core product KPIs

Proposed operating definitions. Actuals are not measured here, and targets are not yet accepted team commitments.

Weekly KPIDefinition / proposed bar
Release scope ready100% of included release items have owner, criteria, estimate and agreed target; include required work outside the project.
Accepted commitmentsDeployed + accepted items / the frozen original weekly commitments. ≥85% provisional; calibrate after two weeks. Scope removed is shown separately.
Critical defects0 open release blockers; newer blockers count too.
Critical journey tests100% of a finite agreed required suite pass with evidence; untested required cases remain in the denominator.
Booking/payment integrity0 wrong credits, duplicate charges/grants, overlaps or orphan paid purchases in a nonzero audited population. No audit means unknown.
Bookable subject coverage100% of advertised subjects have a qualified slot within a proposed 7-day promise; confirm that promise before launch.

Pilot later, separately by offer: checkout completion within 24 hours; paid-buyer first value within 7 days; unplanned manual repair within 7 days. Use mature cohorts and server-confirmed payment. Low-ticket first value must be defined before scoring it.

Research basis: DORA delivery metrics for team-level baselines, and Stripe fulfillment for payment truth and idempotent delivery. Release frequency alone is not the launch gate.

Executive review archive

Generated on demand. The recording and transcript reflect their own date, not the current board. No automatic weekly run is confirmed.

Sprint·
Weekly briefing

Loading the latest review…

Loading the dated archive. Current progress is above.

The spine

Five stages. Each one is defined by a capability the business did not have before it, not by a list of features.

Stage 0
Idea
One platform, not four tools
Stage 1
MVP1 · Operations
Sessions run themselves
Stage 3
MVP3 · Membership
Revenue without a sales call
Stage 4
MVP4 · Cyborg
The data starts teaching

The stages

Click a stage to open it. Live issue status is distinct from release evidence.

0

Idea: one platform, not four tools

Mar – Jun 2026 · the thesis that started the build

Shipped
Validated
⌄
Acuity caps out around 36 tutors. Scheduling, comms, courses and assessments each lived in a different tool, and the texts and emails leaked around all of them. One branded platform breaks the cap and stops admin work scaling with student count.

What it established

  • The four-tool problem: Acuity, Slack/Discord, Skool, Class Companion
  • Tutors run on their own free Gmail and Fathom. No per-seat cost
  • Credits as the unit of account
  • Target shape: 1,000 students on 50–100 tutors

What it got wrong

  • Defined "done" as a cancelled subscription. Reversed on 23 Aug. Done is now a measurable student outcome
  • Put assessments in 2027. They are now the next build
  • Assumed Skool gets replaced. It is being deep-linked instead
1

MVP1: Tutoring Operations

Immediate priority · confirm release scope and acceptance in Linear

In progress
Cycle pending Linear confirmation
⌄
A student books, a tutor shows, the credit moves, the parent gets a summary, with nobody in Slack arranging it. Acuity dies for tutoring. And a stranger can sign up without an admin creating their account.

Historical production reports

  • Admin suite production announcement: September 26.
  • BAMFAM production announcement: September 26; admin first-booking reported September 29.
  • Subject selector and tutor-subject restrictions reported live October 1–2.

Historical reports are not fresh acceptance tests. See the issue evidence and validate the current journey.

Current Linear items

  • Reading Linear…
Exit criteria
Real students booking with zero Acuity bookings and zero scheduling traffic in Slack · admin scheduling hours down measurably · a person who has never met us can create an account and pay.
3

MVP3: The Membership Product

Jan – Apr 2027 · revenue that does not need a sales call

Later
Sprints 8–10+
⌄
A parent finds us through an affiliate, signs up without talking to anyone, and pays monthly. The platform becomes the destination for the low-ticket funnel instead of a fulfilment tool for high-ticket sales.

The build

  • Membership tiers and entitlement gating
  • Courses: open access and progression-gated
  • Group classes + a community calendar carrying the Zoom links
  • Affiliate and referral tracking in-product
  • Capacity tooling: tutor onboarding at volume, utilisation view
  • Joe's two existing apps brought in: automated session notes, the initial diagnostic prompt

The timing constraint

  • Feb–Apr is exam-panic season and the revenue window that pays for the year
  • Capacity tooling has to be ready before the peak, not built during it
  • Tutor recruiting must front-run January: 4 per subject, 6 for test prep
Exit criteria
A membership tier sells itself end to end with no human in the loop, and an affiliate can be paid from tracked in-product attribution.
4

MVP4: Cyborg Tutoring at Scale

2027+ · the data starts teaching

Horizon
Gated on MVP2 data
⌄
Precision-guided tutoring, running on its own. The AI reads the skill profile and tells the parent and the tutor exactly what to work on next. And the accumulated assessment data becomes an asset in its own right.

The build

  • AI tutor connected to the assessment data, not bolted on
  • AccepteD credits: college coaching moves off Acuity at its own exchange rate
  • Mobile app with two-way parent ↔ student link invites; timing requested, pending Wenbo estimate
  • Outcome modelling: this much practice reliably produces this result

Hard gate

  • Clean, diagnosed assessment data has to exist first. A disconnected prototype is allowed before that; an integrated one is not
  • Three credit currencies must already be live and behaving

Release decisions to close

Account, family and channel

D-1: account creation and alerts are the agreed direction. Pay-first versus trial was Joe's leaning, not a final prohibition on free trials. Joe + John must settle the offer before SUP-21 is accepted.

SUP-9 needs two-parent/two-child linking and permissions; SUP-10 needs the channel creation and membership rules. Do not ask families to share account passwords.

Credits and assessment release

The existing tutoring unit is 30 minutes per credit. Test-prep balances, overtime with insufficient credits and no-show/refund rules still need explicit decisions. SUP-30 must implement admin upload and tutor verification; timers/accommodations, notifications, content approval and integration remain acceptance gates.

Dates and capacity

Nov 15 core release and Dec 15 readiness remain product targets, not engineering commitments. Confirm estimates, scope and capacity in Linear before promising a finish date. The prior 60–70% migration estimate from September is not a current allocation or forecast.

Historical progress

Use the existing MVP project graphs in Linear for scope history. New release and acceptance evidence belongs on the issue; this view should read it rather than create another operating system.

The board, live

Reading the current Linear SUP board… Cache age and source time will be shown.

Loading the board…