Product Roadmap Example for an Early-Years EdTech Product

Summary

We will roll the schools tier out in three sequenced horizons over roughly the next year, organised around one goal: prove that Nimbletots saves educators time and shows credible EYFS-aligned progress, then turn that into a repeatable paid line. Now, we harden the compliance and safeguarding foundations while finishing v1. Next, we open a controlled launch to the pilot cohort and convert them to paid. Later, we scale onboarding and self-serve before we invest in integrations.

The order is deliberate. The pilot gave us a strong demand signal — 9 of 12 settings said they would pay to continue ^[1] — but a product used by, and reporting on, children cannot go wide until its data-protection and safeguarding obligations are met ^[3]. So compliance gates value, proven educator value earns the right to scale, and expansion waits for evidence rather than enthusiasm.

This roadmap commits to sequence, to the outcomes each horizon targets, and to the gates between horizons — not to fixed dates. Where a step depends on an external review or an unresolved decision, that is called out rather than assumed away.

Why this works — Answer-first: leadership sees the three-horizon shape, the single organising goal, and the reason for the ordering before any detail, and is told up front that the commitment is to sequence and outcomes, not dates.

Purpose and Audience

This roadmap exists to align two audiences on one plan for the schools tier: the leadership team (Tom Fisher and the exec), who are deciding whether the sequence, the resourcing and the risk profile are acceptable; and the two delivery squads, who need to know what they are building now, what is coming next, and what is explicitly not yet committed.

The decisions it communicates are: what we build in each horizon, why in that order, what outcome each horizon must hit before the next one opens, and where the plan depends on things outside the squads' control.

What it commits to: the horizon sequence, the outcome each horizon targets, and the exit gate between horizons.

What it does not commit to: fixed release dates, the scope of the Later horizon (MIS and local-authority integrations are candidates, not promises), or any pause to the consumer roadmap. It is a direction-and-sequence document, not a delivery schedule or a capacity plan — those live alongside it and are refreshed each quarter.

Why this works — Setting the audience and the commitment boundary up front is what stops a roadmap being read as a dated delivery contract — it tells reviewers exactly which lines are firm and which are directional.

Product Vision and Strategic Context

Vision: every young child gets short, playful, adaptive early-learning that grown-ups can actually see working. Nimbletots already does this for about 180,000 families; the schools tier extends the same engine — adaptive maths, English including phonics, and science — into the settings where those children spend their days, and gives educators class-level progress they can align to the EYFS areas of learning ^[2].

Strategic context: this is a B2B expansion of a consumer product. It opens a second revenue line and, more importantly, a second buyer — the setting, not the parent — with a different sales motion, a different duty of care, and a different compliance surface. England has roughly 46,600 providers on Ofsted's Early Years Register ^[4], so the market is real and large, but it is also a regulated, safeguarding-first environment.

The link between the two is direct: the vision only scales into schools if we can evidence learning value and meet a child-facing product's statutory obligations. That is why the roadmap leads with the compliance foundation and educator-value proof rather than with growth — the strategy is gated by trust, so the roadmap is too.

Why this works — This ties every later horizon back to a single vision-to-strategy thread — evidence value, earn trust, then scale — so reviewers can test each initiative against the same north star rather than judging features in isolation.

Outcome Goals

The roadmap is organised around outcomes, not features. Each horizon has to move one of these before it is considered done.

Customer outcomes (educators and settings)

• Save educator time on planning and progress tracking. Baseline from pilot: median ~2.5 hours/week saved, self-reported ^[1]. Target: hold or beat that at v1 scale with a non-pilot cohort.
• Make class progress legible and EYFS-aligned. Target: every paying setting can produce an EYFS-area-aligned progress summary ^[2] without manual re-keying.
• Keep children engaged without over-exposing them to screens. Target: sustain pilot-level engagement (78% of children used it in ≥6 of 8 weeks ^[1]) while respecting the EYFS expectation that providers have regard to screen use ^[2].

Business outcomes

• Prove the paid line converts. Baseline: 9 of 12 pilot settings said they would pay ^[1]. Target: convert the pilot cohort to paid in the Next horizon.
• Establish repeatable, sustainable delivery. Target: onboarding and support that a small team can run at volume before we widen access.
• Validate durable retention and unit economics before committing to Later-horizon expansion.

These are the yardsticks the Success Measures section makes concrete.

Why this works — Leading with outcomes and their pilot baselines — not a feature wishlist — is what lets leadership judge the roadmap on whether it moves the numbers, and it gives each horizon an unambiguous definition of done.

Roadmap Themes

The work groups into five themes. The first three are load-bearing for launch; the last two are where the product grows once launch is proven.

1. Compliance and safeguarding foundation. A child-facing schools product cannot ship without a completed Data Protection Impact Assessment, processor terms, and conformance with the ICO Children's Code ^[3], plus progress reporting mapped to the EYFS framework — including the revision effective 1 September 2026 ^[2]. This theme is the precondition for everything commercial.

2. Educator value. The pilot's core signal was time saved and legible progress ^[1]. This theme protects that value at scale: class assignment, a class-progress dashboard, and an EYFS-aligned progress report that educators trust.

3. Commercial readiness. A paid tier needs setting-level billing, a simple procurement path, and single-setting onboarding — the plumbing that turns willingness-to-pay into revenue.

4. Scale and self-serve. Self-serve setting sign-up, in-product onboarding and support tooling, so the funnel can widen into the ~46,600-provider market ^[4] without the team scaling linearly.

5. Deeper reporting and integrations. Candidate later bets — MIS and local-authority reporting, and richer early-literacy reporting grounded in evidence such as the +6 months' progress that structured phonics can add ^[5]. Each expands the data-protection surface, so each earns its place only after a fresh review.

Why this works — Grouping work into themes with an explicit rationale — and flagging which themes gate launch versus which drive later growth — lets reviewers see the shape of the bet before the horizon detail, and ties each theme to either a pilot signal or a real external standard.

Now, Next and Later

Confidence is deliberately high for Now, moderate for Next, and low/thematic for Later — the further out, the less we commit.

Recommendation from the table: open only the Now horizon for committed delivery. Fund Next's discovery (pricing, procurement) in parallel so it is ready when the Now gate is met, and keep Later as a candidate list reviewed after the Next gate — do not resource it yet.

Why this works — The core of the roadmap as a real table: every horizon carries named initiatives, an honest confidence level, the value it targets and a hard exit gate — so leadership can see the sequence and how firm each commitment is at a glance, and the recommendation is drawn straight from the rows.

Prioritisation Rationale

Three principles decide order. First, compliance gates value: nothing reaches general availability until the DPIA, the processor terms, and Children's Code conformance are signed off ^[3]. Second, we earn the right to scale: we convert the settings that already know the product before we chase new logos, because that is where retention risk is lowest and the pilot demand signal is strongest ^[1]. Third, we sequence for evidence, not enthusiasm: integrations and expansion wait until onboarding and support can absorb volume.

Each horizon has an exit gate, and if a gate is not met the horizon does not open. We would rather slip a horizon than launch a child-facing product that has not passed review.

Trade-offs made. We are deferring MIS and local-authority integrations, secondary-phase content, an in-schools parent account, and any fixed general-availability date — these are recorded as candidates, not commitments. We are also not pausing the consumer roadmap: the schools tier is resourced as an addition, and any contention for the shared platform is a trade-off we will surface rather than absorb silently. Deferring the expansion bets keeps the near-term plan achievable and, just as importantly, keeps the compliance surface contained until we have proven we can operate it.

Why this works — Gathering the ordering principles and the deferrals in one place lets reviewers see that every omission is a deliberate choice with a stated reason — the mark of a prioritised roadmap rather than a wishlist.

Dependencies and Risks

The plan rests on three dependencies. The register below gives each a likelihood, an impact, an owner and a mitigation.

The single largest schedule risk is compliance sign-off, because it is external to the squads and gates revenue.

What would change this view: if the compliance review surfaced a blocker that could not be mitigated in the Now horizon — for example, a Children's Code requirement that forces a re-architecture of how class data is stored ^[3] — the sequence itself would change: we would pause the commercial build, not just slip it, and re-scope v1 around what can lawfully ship. Equally, if pricing discovery showed the pilot's willingness-to-pay ^[1] did not survive contact with real procurement, the Next horizon's business case would need re-testing before we built billing at all.

Why this works — A risk register with likelihood, impact, owner and mitigation, plus an explicit counter-evidence blockquote naming what would overturn the plan, is what separates a roadmap from a timeline — it tells leadership where to look when a horizon slips and what evidence would make them rethink the whole sequence.

Key Milestones

Milestones are anchored to horizons and gates rather than to invented calendar dates; the one fixed external date is the EYFS revision. "Trigger" states what has to be true for the milestone to land.

The two decision gates (compliance sign-off; sustainable support proven) are the milestones leadership should watch most closely — they are where a horizon either opens or does not.

Why this works — Expressing milestones as gate- and trigger-anchored rather than date-stamped keeps the roadmap honest about what it can promise, while still pinning the one genuinely fixed external commitment (the EYFS revision date) so nothing slips through.

Success Measures

Each horizon is judged against a small set of measures with a baseline, a target and a timeframe, plus guardrails we will not trade away and leading signals we watch in-flight.

Now — did we ship a trustworthy v1?

• Compliance: all three artefacts signed off (binary). Target: yes, before any paid launch.
• Leading signal: EYFS-area mapping reviewed against the revised framework ^[2] before build sign-off.

Next — does the paid line work?

• Time saved (primary): baseline median ~2.5 hrs/week (pilot, self-reported) ^[1]; target: hold at ≥2 hrs/week with the paying cohort.
• Conversion: baseline 9 of 12 settings said they would pay ^[1]; target: convert the majority of the pilot cohort to paid.
• Educator weekly-active: baseline 83% (pilot) ^[1]; target: sustain ≥70% post-launch.

Later — is it durable?

• Retention: renewal rate across a full setting cycle (no pilot baseline yet — first real read comes in this horizon).
• Unit economics: support cost per setting trending down as self-serve lands.

Guardrails (all horizons): no measure is chased at the expense of children's screen-time appropriateness ^[2], data-protection posture ^[3], or safeguarding overhead capacity. A growth number that breaches a guardrail is treated as a failure, not a win.

Why this works — Pairing every target with a real pilot baseline, a timeframe, and explicit guardrails means success is defined before the work starts — and the guardrails stop the roadmap optimising growth against the trust obligations that make the schools market viable at all.

Evidence and Confidence

The evidence base is a mix of one strong internal signal and well-established external standards.

Internal (recent, directly relevant, but small and self-reported): the spring-2026 pilot across 12 settings, 40 educators and ~600 children ^[1]. It is the freshest and most on-point evidence we have — time saved, engagement and willingness-to-pay all point the same way — but it is a single 8-week study, self-reported on the time-saved measure, and biased toward settings that opted into a pilot. We treat it as a strong directional signal, not proof of durable retention.

External (authoritative and current): the EYFS statutory framework and its 1 September 2026 revision ^[2], the ICO Children's Code ^[3], the Ofsted provider count ^[4], and the EEF's phonics evidence ^[5]. These are stable, dated, official sources and we hold high confidence in them.

Coverage and consistency: the internal and external evidence are consistent on the problem (educator workload, EYFS reporting burden, a large regulated market). They diverge on the durability question — the pilot shows early enthusiasm, but no source, internal or external, yet tells us whether paying settings renew.

Contradicting signal we are honest about: 3 of 12 pilot settings would not commit to pay ^[1]; we have not yet diagnosed why, and that is a live gap for the Next horizon.

Overall confidence: high on the near-term plan (Now/Next are grounded in evidence we hold today), low on the Later horizon (it depends on retention data that does not exist yet).

Why this works — Grading the evidence by recency, authority and coverage — and naming the contradicting signal and the durability gap out loud — is what lets a reader trust the confidence levels attached to each horizon rather than taking them on faith.

Recommended Next Steps

Bottom line: commit the Now horizon, fund Next's discovery in parallel, and hold Later as candidates. The concrete next steps, with owners:

1. Start the compliance foundation now — DPIA, processor-terms template and Children's Code conformance review ^[3], in parallel with the v1 build. Owner: Priya Nair (with legal/DPO).
2. Map the progress report to the revised EYFS framework effective 1 September 2026, not the outgoing version ^[2]. Owner: Dr. Amara Okoro.
3. Build v1 — class assignment, class-progress dashboard, EYFS-aligned progress report. Owner: Léa Dubois.
4. Run pricing and packaging discovery in parallel, anchored to the pilot's willingness-to-pay of ~£3–4 per child/year or ~£300–£500 per setting/year ^[1], and diagnose the 3-of-12 who would not commit. Owner: Sam Whitfield.
5. Approve the Now exit gate criteria (v1 feature-complete + three compliance artefacts signed off) as the single decision that opens the Next horizon. Owner: Tom Fisher / leadership.

Decisions needed from leadership this cycle: confirm the two-squad resourcing as an addition to (not a replacement for) the consumer roadmap, and confirm the gate criteria above.

Why this works — Turning the roadmap into a short, owned action list with an explicit leadership decision at the top converts a direction document into something the team can act on Monday — and names the one gate decision that everything downstream waits on.

Ownership and Review

Roadmap owner: Priya Nair (Product Manager) owns this roadmap end-to-end and is accountable for keeping it current.

Accountable owners and contributors:

• Product / sequence: Priya Nair.
• Learning design and EYFS alignment ^[2]: Dr. Amara Okoro.
• Engineering delivery: Léa Dubois.
• Pricing, packaging and go-to-market: Sam Whitfield.
• Executive sponsor / gate decisions: Tom Fisher.

Where the source evidence lives: the pilot dataset and analysis ^[1] sit in the schools-pilot workspace; the compliance artefacts (DPIA, processor terms, Children's Code review ^[3]) are held with legal/DPO; external standards are the public sources cited below. This roadmap links to, rather than restates, those artefacts.

Review rhythm and decision rights: reviewed at each horizon exit gate and at the quarterly planning cycle. Priya Nair decides in-horizon sequencing; opening a new horizon is a leadership decision (Tom Fisher) against the stated exit gate. Pricing sign-off rests with Sam Whitfield; EYFS-alignment sign-off with Dr. Amara Okoro.

Triggers to revisit ahead of schedule: a compliance blocker from the Children's Code review ^[3]; a material change in the EYFS framework beyond the known September 2026 revision ^[2]; pricing discovery contradicting the pilot willingness-to-pay ^[1]; or support load exceeding the capacity the Later gate assumes.

Why this works — Concentrating ownership, evidence location, decision rights and revisit triggers in one place — stated once, not repeated across sections — gives the roadmap a clear governance spine and tells a cold reader exactly who decides what and when the plan gets reopened.