The build sequence, the two release gates, and the sprint plan that has to hold for test-prep season. This is the team-facing version: real dates, real risks, real open decisions.
The whole roadmap in prose, for anyone who would rather read than trace a diagram — and for phones, where the charts below scroll sideways.
Until August the platform was an operations tool: replace Acuity, then Skool, then Class Companion, and call it done when a subscription got cancelled. On 23 August that reversed. The platform is now the thing that proves the tutoring worked — every assessment question coded to a unit and a skill, so a parent can log in and see that their student actually improved. Joe calls it precision-guided tutoring. That single reversal pulled assessments forward from 2027 to the next build, parked the Skool clone, and is upstream of everything since.
Nov 15 is the core release — real students inside, finding the fringe cases. Dec 15 is prepped for volume. But February is the real deadline: exam-panic season is the revenue window that pays for the year, and a slip past December does not cost a month, it costs the season.
There are 4.4 sprints between now and Nov 15, and roughly three of them are migration — the old test-prep platform is 60–70% of the effort by Wenbo's own estimate. That leaves about 1.4 sprints for six admin items, parent accounts, the comms rebuild, the credit ledger and self-serve signup, on one part-time senior plus a junior. The date holds only if the scope behind it gets cut out loud.
Five decisions gate the build, and four of them are a sentence from Joe. The most expensive is D-1: what a self-serve signup actually gets — registration is still closed, an affiliate lands within the month, and there is nothing to sell them. D-2, the three-currency credit ledger (SupportED, TestED, AccepteD), blocks the data model outright: nothing can be built on a ledger nobody has defined.
On the board itself: every open issue is unassigned and unestimated, there are no sprint cycles configured, and self-serve registration has no issue at all. Which is why nothing on this page is a commitment yet — it is a plan awaiting an estimate pass.
Two and a half minutes, regenerated every Monday from the live board, the week's calls, and where we actually sit against the gates. It is written to be heard once — it opens on the thing that matters and does not pad.
Generated Mondays. Board state, the week's decisions, what is blocking, and the ask.
Five stages. Each one is defined by a capability the business did not have before it, not by a list of features.
Ten two-week sprints, six workstreams, three gates. Bars are where work actually sits — not where we hope it lands. Read the migration lane first: it is 60–70% of the effort and it blocks almost everything to its right.
Two lanes never run in parallel in reality — there is one part-time senior and one junior. Where bars overlap, one of them is waiting.
Solid arrows are the happy path. Dashed arrows are fail-loops — what actually happens when a gate says no. Diamonds are binary gates: they have one answer and it is yes or no. The right rail carries who owns it, how long it takes, and what it depends on.
Click any stage to open it. Green bullets are shipped.
Mar – Jun 2026 · the thesis that started the build
Jun – Oct 2026 · every session books, holds and settles in the platform
app.supporteduniversity.com — still does not resolveOct – Dec 2026 · the Nov 15 release. The differentiator
Jan – Apr 2027 · revenue that does not need a sales call
2027+ · the data starts teaching
Two-week sprints from 15 September. Nov 15 lands inside Sprint 5 — which means four full sprints exist before the core release, and roughly three of them are migration.
61 days from 15 Sep to 15 Nov — 4.4 sprints, and the first has not started.
60–70% of effort is migrating the old platform, per Wenbo's own estimate. Against 4.4 sprints, that is ~3 sprints of migration before a new feature ships.
That leaves ~1.4 sprints for six admin items, parent accounts, the comms rebuild, the credit ledger and self-serve signup.
Capacity is one part-time senior plus a junior who has not yet worked in the main repo.
And this team's measured calendar-to-reality gap runs ~4×.
Read: Nov 15 is real for the migration plus the assessment core. The admin suite and the parent account are the two most likely to slide. Cut them out loud now rather than discover it in November.
Ideas are welcome. Unpriced ideas are not. Every request runs the same route: grilled against the job it serves, vetted against what already exists, staged, and only then allowed near a sprint — and nothing enters a running sprint without naming what leaves.
Read straight from Linear when this page loads — so it cannot drift from the board.
Loading the board…
Ideas are welcome. Untraded ideas are not — every addition after a sprint is agreed costs something, and the cost gets named before the yes.