Competitive Analysis Example for an Early-Years EdTech Product

Summary of Findings

No product in the England early-years market does the specific thing Nimbletots for Schools proposes: adaptive, child-facing play across maths, English, phonics and science for ages 3-7 that also turns that play into EYFS-aligned class progress summaries with almost no separate data entry. The market is strong at two ends and thin in the middle where those two jobs meet.

The tools already in the room fall into four groups, each excellent at its own job and each stopping short of the overlap:

• Observation and assessment platforms — Tapestry positions itself as "the original and leading Childhood Education Platform" for documenting and evidencing learning ^[1]; Famly as "The Early Childhood Platform" spanning observations, parent communication and nursery admin ^[2]; Evidence Me by 2Simple as an observation and assessment app for practitioners ^[3]. They record learning that happens elsewhere; they do not deliver adaptive activity to the child.
• Adaptive practice apps — DoodleLearning delivers personalised maths and English with an adaptive algorithm and a teacher dashboard for ages 4-14 ^[4]. It is the closest competitor on adaptive delivery, and it skews older and narrower than the full 3-7, play-led, four-subject range.
• Free single-subject games — Teach Your Monster to Read is a trusted, free phonics and reading game funded by the Usborne Foundation ^[5]. It is free and loved, but single-subject.
• Teacher resource libraries — Twinkl supplies subscription EYFS printables and planning across the seven areas of learning ^[6]. It equips the educator to deliver; it does not deliver adaptive activity or generate progress evidence automatically.

Recommended position: compete on the join between play and evidence, not at either end. We should not try to out-observe Tapestry, out-practise Doodle, or out-give a free game. We should win as the tool that turns children's adaptive play into the EYFS progress evidence a setting is statutorily obliged to produce anyway ^[7]. That is defensible because it rests on assets the specialists do not have — an existing 3-7 adaptive engine and four-subject content — and it is the position the pilot evidence supports (median 2.5 educator hours saved per week, 9 of 12 settings willing to pay to continue) ^[8]. The product implication, developed in the sections that follow, is to build the automatic play-to-summary bridge first and to treat free-form observation capture and nursery admin as explicitly out of MVP scope.

Why this works — As the summary, it is answer-first: it names the market gap, groups every competitor by the job it does with a source each, and states the recommended position and the one build decision it drives before a single matrix appears, so everything below reads as evidence for a decision already stated.

Purpose and Initiative Context

This analysis exists to make one scoping decision defensible: what Nimbletots for Schools competes on, and therefore what the MVP must and must not build.

The initiative. Nimbletots for Schools is a proposed educator tier on top of our consumer app. It would let nurseries and reception or Year 1 classes assign Nimbletots activities to groups, track class-level progress, and produce EYFS-aligned progress summaries for staff and parents. It is a B2B expansion of a consumer product: a new buyer (the setting, not the parent) and a new revenue line.

The decision it supports. Leadership has agreed to fund a v1 build (roughly two squads over about four months). This document does not re-open that decision; it informs how the tier is positioned and what the first release contains, so that we build against the real gap rather than against a feature checklist copied from incumbents.

Scope. In scope: the England early-years classroom (EYFS) segment and the tools a setting would actually weigh against us for the assign-activity-and-evidence-progress job. Out of scope: wider Key Stage 2+ practice, the global EdTech market, and full nursery back-office management (billing, occupancy, rotas), which is a different product category we are not entering. The market is real and sizeable, on the order of 59,700 early-years providers registered with Ofsted in England ^[9], but this is a positioning analysis, not a market-sizing one; the numbers live in the Opportunity Assessment.

Why this works — This section fixes the decision the analysis serves and draws a hard scope line (no nursery back-office, no Key Stage 2+), which is what stops a competitive analysis from sprawling into a feature-parity wish list against every tool a setting owns.

User Problem and JTBD Context

The educator's core job is not "use an app"; it is evidence that each child is progressing, without losing teaching time to admin. That job is statutory, not optional: the EYFS framework requires providers to assess children's development, complete the progress check and the EYFS profile, and report to parents ^[7]. Every setting must produce this evidence anyway. The pain is that today the evidence and the activity are two separate efforts.

The matrix below scores how well each tool category serves the educator's jobs. Score key: 3 = serves it directly, 2 = partial, 1 = does not.

Read-out: no single incumbent category scores above 11, and every one of them loses a point precisely on "without a separate logging task" — because their model is either record-after-the-fact (observation platforms) or practise-without-evidence (adaptive apps). The unmet job is the join: adaptive activity whose completion is the progress evidence. That gap, not any single missing feature, is the user problem Nimbletots for Schools is built to solve. Competitor internal data on how educators actually experience these jobs is not available to us; our evidence for the pain is the statutory duty ^[7] and our own pilot ^[8].

Why this works — It defines the job as the statutory, unavoidable one (cited to the EYFS framework, not asserted), then scores every category against it in a real matrix that mathematically exposes the same missing point across all of them, so the differentiation is derived from the table rather than claimed.

Scope of Comparison

Settings assemble a toolkit rather than buy one product, so the fair way to bound the comparison is by relevance to the assign-and-evidence job, not by brand familiarity. The table scores each candidate on how directly a setting would weigh it against Nimbletots for Schools, and records the in/out decision.

Read-out: six named tools are in scope across the four job categories; two whole categories are explicitly excluded. Famly is admitted only for its observation/parent features, not its back-office, so we do not accidentally benchmark ourselves as a nursery-management system. This keeps the analysis honest: we are compared on the overlap we intend to win, and we state plainly what we are choosing not to compete with.

Why this works — Scoping by scored relevance rather than by brand keeps the set fair and, crucially, records what is excluded and why, so a reader can see the analysis is not quietly stacking the deck by leaving out an inconvenient competitor.

Competitor and Substitute Workflows

Each tool is described from its own public positioning, mapped to the workflow it genuinely serves, and given a fair statement of where it stops. None of these is a bad product; each is simply built for a different point in the day.

Tapestry — record and evidence learning. Tapestry positions itself as "the original and leading Childhood Education Platform", built around observations and learning journals: a practitioner captures a photo, video or note, tags it to EYFS frameworks such as Development Matters, and shares it with families, with reporting on top ^[1]. It is strong on the evidence job and parent engagement. It is not an adaptive activity children play; it documents learning that happens elsewhere. Closest to us on reporting, furthest on play.

Famly — run the setting and evidence learning. Famly describes itself as "The Early Childhood Platform", spanning observations and learning journals alongside parent communication, billing, staffing and occupancy ^[2]. Its observation half competes with the evidence job; its larger half is nursery administration we are not entering. It records; it does not deliver adaptive activity to the child.

Evidence Me (2Simple) — capture and assess on the go. Evidence Me is an observation and assessment app for practitioners: capture photos or video in the classroom (with built-in face-blurring), get automatic objective suggestions against a chosen framework, assess, and share with parents ^[3]. Again strong on capture and assessment, silent on adaptive child-facing activity.

DoodleLearning — deliver adaptive practice. Doodle offers personalised maths and English apps for ages 4-14, using its Proxima adaptive algorithm to give each child a unique programme, with an award-winning teacher dashboard for tracking and exporting progress ^[4]. This is the workflow closest to ours: adaptive delivery plus a teacher view. It skews towards maths and English practice for school-age children rather than play-led activity across the full 3-7 range including science, and its progress data is practice analytics rather than EYFS-profile reporting.

Teach Your Monster to Read — free early-reading play. An award-winning phonics and reading game, free on computer and funded by the Usborne Foundation, taking children through letters and sounds to sentences across three stages, with a teacher classroom-management and Practice Mode for schools ^[5]. Trusted, free, genuinely good, and single-subject: it does not span maths or science and does not produce EYFS progress summaries.

Twinkl — equip the educator. Twinkl is a subscription library of teacher-made EYFS resources and printables covering all seven areas of learning, with a free tier and a 30-day trial ^[6]. It arms the educator to plan and deliver; it does not deliver adaptive activity to the child or generate progress evidence automatically.

Across all six, the pattern is consistent: the reporting tools do not deliver adaptive play, and the delivery tools do not auto-produce EYFS evidence. That seam is the Nimbletots for Schools workflow.

Why this works — Every competitor is profiled from its verifiable public positioning with a citation, mapped to the workflow it truly serves, and credited for what it does well before its boundary is named, which reads as fair analysis rather than rivals being talked down.

Evaluation Criteria

Before comparing features we fixed the criteria, and their weights, so the feature matrix is scored against what actually matters to an EYFS buyer rather than against whatever we happen to be good at. Weights sum to 100 and reflect the pilot's read of what settings said drove value.

Read-out: 65 of the 100 weight sits on the top three criteria — automation, fit and time saved — which is exactly the overlap the incumbents miss. Trust and safeguarding carry a deliberate 15 because it is where we are weakest and a new B2B entrant can lose the sale regardless of feature strength; the criteria are honest about our exposure, not tuned to flatter us. Price is weighted low because pilot settings consistently ranked value and trust ahead of headline cost ^[8].

Why this works — Setting and weighting the criteria before the feature matrix is what makes the comparison a scored evaluation rather than a feature beauty-contest; weighting trust at 15 where the product is weakest shows the criteria were not reverse-engineered to make Nimbletots win.

Feature, Capability and Workflow Matrix

This is the side-by-side, scored against the criteria above. Cells read Strong / Partial / None for how well each tool supports that capability for an EYFS setting. Ratings reflect each product's public positioning ^{[1][2][3][4][5][6]}; competitor internal roadmaps are not visible to us.

Read-out (weighted to the criteria): Nimbletots for Schools is the only column marked Strong on both auto progress summary and evidence without separate logging — the two capabilities carrying the heaviest weight and the seam every incumbent misses. The honest counterweight is visible in the same table: we are only Partial on free-form observation capture (Tapestry, Famly and Evidence Me are Strong), None on nursery admin, and None on price-to-free (Teach Your Monster wins outright). The recommendation the matrix supports is therefore narrow and deliberate: build the play-to-summary bridge as the wedge, accept that we will not match a dedicated observation platform on open-ended capture, and stay out of nursery admin entirely.

Why this works — The core deliverable of a competitive analysis: a real side-by-side matrix that both proves the wedge (only column Strong on the two heaviest-weighted rows) and shows the product losing openly on three rows, then draws a build recommendation directly from the pattern rather than from opinion.

User Journey Comparison

The capability matrix says what each tool has; this compares what the educator actually does to complete the recurring job: produce a week's EYFS progress evidence for a group of children. Steps and minutes are our modelled estimate of the typical workflow, calibrated against pilot observation ^[8]; they are directional, not a stopwatch study.

Read-out: the observation-platform journey front-loads manual capture and tagging; the adaptive-app journey removes capture but leaves the educator to translate practice analytics into EYFS-shaped evidence themselves. Nimbletots for Schools collapses both by making the evidence a by-product of the play — which is the mechanism behind the pilot's median 2.5 hours saved per educator per week ^[8]. Our journey's own friction moves to a different place, honestly noted in the last row: educators must trust an auto-generated summary, so the review-and-confirm step in that journey is a first-class design problem for the MVP, not an afterthought.

Why this works — Comparing the journeys rather than the feature lists surfaces where each model spends the educator's time and, by scoring our own new friction point (trusting an auto-draft), turns the analysis into a concrete MVP design requirement instead of a victory lap.

UX and Interaction Pattern Review

The incumbents set clear interaction conventions that a new setting-facing tier should meet rather than reinvent, and one anti-pattern we should avoid.

Patterns worth matching.

• Capture-first, minimal-friction input. Evidence Me's model of capture-then-auto-suggest-objectives, with built-in face-blurring for safeguarding ^[3], sets the bar for how little an educator should have to type. Our play-to-summary flow should feel at least as light.
• A single teacher dashboard as home base. Doodle's award-winning dashboard as the one place to track, analyse and export progress ^[4] is the mental model settings already have; our class view should map onto it, not introduce a novel navigation.
• Child-facing warmth, adult-facing calm. Teach Your Monster's playful, character-led child journey alongside a separate, plain teacher area ^[5] mirrors the split we already run in the consumer app; keep the two audiences visually distinct.
• Parent sharing as a built-in surface, not a bolt-on. Tapestry, Famly and Evidence Me all treat parent sharing as core ^[1][2][3]; educators will expect it present from day one.

Anti-pattern to avoid. The observation platforms' strength — infinitely flexible, free-form capture — is also a friction source: every item is a small manual authoring task. Our differentiation is precisely not to make the educator author evidence, so we should resist the temptation to add a full open-ended observation editor in v1 and keep the auto-drafted summary as the default surface, with light edit rather than blank-canvas authoring.

Accessibility. As a child-facing product used in settings, the tier must meet recognised accessibility expectations (clear targets, non-colour-dependent cues, screen-reader-friendly educator screens); this is a build requirement carried into the PRD, not a differentiator to claim here.

Why this works — It reads the incumbents' interaction conventions as constraints to meet and one specific anti-pattern to avoid, converting UX observation into concrete MVP guidance (match the dashboard model, resist a free-form editor) rather than generic praise of competitor design.

Pricing, Packaging and Commercial Signals

Bottom line: named-competitor pricing is mostly not publicly disclosed, so we treat pricing as a signal to read, not a number to match. What is observable, and what is not:

• Tapestry — no price shown on its public pages; costs sit behind a separate pricing page and enquiry ^[1]. Public figure: not disclosed.
• Famly — positions as a full platform and routes to demo requests; no per-child or per-setting price published ^[2]. Public figure: not disclosed.
• Evidence Me (2Simple) — free to download, but requires a paid Evidence Me account to use; the account price is not shown on the store listing ^[3]. Public figure: not disclosed.
• DoodleLearning — school pricing is behind a "contact us / pricing page" route, not published on the schools overview ^[4]. Public figure: not disclosed.
• Teach Your Monster to Read — genuinely free on computer, funded by the Usborne Foundation, with paid app versions ^[5]. This is the one hard public data point, and it sets the "why pay at all?" bar.
• Twinkl — subscription with a free tier and a 30-day free trial; individual and school membership tiers exist but exact prices are not shown on the EYFS landing page ^[6]. Public figure: not disclosed.

Signals we can read despite the missing numbers. Nearly every setting-facing incumbent hides price behind a demo or enquiry, which tells us procurement in this segment is relationship-led and quote-based, not self-serve. A free, trusted phonics game exists, so any paid tier must justify its cost against "good enough and free" for the single-subject use case. Our own proposed model is an internal figure, not a competitor benchmark: illustratively around £3-4 per child per year or a flat £300-500 per setting per year, with small settings preferring the flat option (Nimbletots internal pricing model, 2026, illustrative) ^[10]. We deliberately do not claim to undercut or match any competitor price, because we could not verify a single one to compare against.

Why this works — It states plainly that competitor pricing is undisclosed for five of six tools and refuses to invent it, then extracts the genuinely useful commercial signal (quote-based procurement, a free substitute setting the floor) and labels our own pricing as internal and illustrative, never as a competitor comparison.

Strengths, Weaknesses and Product Gaps

We win on the overlap and lose, today, on maturity. A symmetric read:

Where we are strong.

• Against observation tools (Tapestry, Famly, Evidence Me), our edge is that the evidence is a by-product of children actually playing, not a separate logging task — the mechanism behind the median 2.5 hours per educator per week saved in the pilot ^[8].
• Against adaptive apps (Doodle), our edge is breadth across maths, English, phonics and science for the full 3-7 range, framed for EYFS rather than Key Stage practice ^[4].
• Against free games (Teach Your Monster), our edge is the educator layer — class assignment and auto EYFS summaries — that a free consumer game does not attempt ^[5].

Where we are weak.

• Maturity and trust. Incumbents have years of settings-sector track record and established safeguarding credentials; we are a consumer brand asking educators to trust a new B2B product.
• Free-form observation depth. Dedicated observation platforms will out-capture us on open-ended evidence; we are Partial there by design.
• Price floor. A trusted free option exists for the phonics job.

The product gap we exploit: the automatic play-to-EYFS-summary bridge that no incumbent offers. But we should hold that claim to its counter-evidence:

What would change this view. The differentiation collapses if any well-resourced incumbent ships the same bridge first. Tapestry or Famly already hold the evidence and parent-sharing surface; if either bolts a lightweight adaptive-activity layer onto it, or Doodle adds EYFS-profile-shaped reporting to its existing dashboard, our wedge narrows sharply. Their internal roadmaps are not visible to us, so we cannot rule this out. The honest conclusion is that our advantage is a timing and focus advantage, not a structural moat: it holds only while we ship the bridge faster and keep it sharper than a larger incumbent bolting it on as a feature. That argues for a narrow, fast MVP over a broad one.

Why this works — A credible strengths-and-weaknesses read is symmetric and self-critical: it grounds the wins in pilot evidence, lists three real weaknesses, and the required counter-evidence blockquote names the specific move (an incumbent shipping the same bridge) that would erase the advantage, reframing it honestly as a timing edge rather than a moat.

Customer Evidence

Honest gap first: the customer evidence we would most like — competitors' real retention, usage and win-loss data — is not knowable to us. Those are internal metrics that Tapestry, Famly, Evidence Me, Doodle, Teach Your Monster and Twinkl do not publish, and no amount of desk research will surface them. We do not estimate them.

What we can legitimately use is threefold:

• Public proxies for competitor traction — the observable facts that these products are widely adopted and, in several cases, award-recognised (for example Teach Your Monster's award-winning status and Doodle's award-winning dashboard, per their own positioning ^[5][4]). These indicate the incumbents are trusted, which is a real competitive fact even though the underlying numbers are opaque.
• Our own first-party pilot evidence, which is the strongest customer signal we have and is genuinely ours to cite: across 12 settings, 40 educators and about 600 children over eight weeks, 78% of children used Nimbletots in at least six of the eight weeks, educator weekly-active reached 83%, and 9 of 12 settings said they would pay to continue (Nimbletots pilot data, spring 2026, illustrative) ^[8]. Full method and caveats sit in the Product Validation Report.
• A named evidence gap to close — we have pilot data on our product but no structured buyer-interview data on why settings would drop or keep a competitor if they adopted us. That is the highest-value missing evidence and is carried into Recommended Next Steps.

The discipline here is to keep first-party pilot evidence (ours, cited as illustrative internal) strictly separate from competitor internals (unknowable), and never to let a plausible-sounding competitor retention figure slip in dressed as fact.

Why this works — It leads with the unknowable honestly — competitor internal metrics are not available and are not guessed — then distinguishes three legitimate evidence types (public proxies, our own first-party pilot, and a named gap), modelling exactly the source discipline the document is meant to demonstrate.

Source Dates and Evidence Freshness

Every external claim here is a public-positioning snapshot taken in July 2026 and will age. Competitor product pages change without notice, so freshness is a live risk, not a footnote.

Read-out: our regulatory and market anchors (EYFS framework, Ofsted statistics) are low-risk and dated; the competitor-positioning claims are the volatile part and should be re-checked before any go/no-go that leans on them.

What would change this view. We have treated public product pages as an accurate guide to what each competitor actually does. That can be wrong in two directions: a page may lag the product (a competitor may already ship, in beta, the play-to-evidence bridge we think is unclaimed but simply not yet marketed), or it may oversell (positioning copy that a hands-on trial would not bear out). Either would move our conclusions. The correction is cheap and specific: before committing MVP scope, run a hands-on trial of Tapestry and Doodle rather than relying on their pages, and re-date this table. Until then, the competitor rows are positioning intelligence, not verified product behaviour.

Why this works — It dates and risk-rates every source in a table, separating stable regulatory anchors from volatile competitor copy, and the counter-evidence blockquote names the concrete failure mode (a page lagging or overselling the product) plus the cheap correction, so the freshness caveat is actionable rather than boilerplate.

Opportunity Areas

The analysis points to a small number of high-conviction opportunities, ranked by how cleanly they exploit the gap the matrices exposed.

1. The play-to-EYFS-summary bridge (the wedge). No incumbent turns adaptive activity into EYFS-shaped progress evidence automatically. This is the single differentiated capability and the reason to buy; everything else supports it.
2. Four-subject breadth at ages 3-7. Doodle owns adaptive maths and English but skews older and omits science and dedicated early phonics play; our existing engine already spans the four subjects for the full range, so breadth is a reuse of an asset, not new build.
3. Educator time as the headline promise. Time saved, not feature count, is what the journey comparison and pilot both point to; the opportunity is to make "2.5 hours back a week" the organising claim of the whole tier.
4. Trust and safeguarding as a product surface. Because trust is where we are weakest and where procurement is decided, visible safeguarding and data-protection design is an opportunity to neutralise the incumbents' maturity advantage rather than merely a compliance cost.
5. Parent sharing parity. A lower-conviction but table-stakes area: settings expect it, so we match rather than lead here.

The first three are where Nimbletots for Schools can be distinctively better; the last two are where it must simply be credible.

Why this works — It ranks opportunities by how directly each exploits the proven gap and separates the two or three areas where the product can genuinely lead from the ones where it only has to reach parity, which is what keeps the roadmap focused on the wedge.

Prioritisation Implications

Translated into backlog terms, the analysis argues for a deliberately narrow MVP built around the wedge, with two whole areas explicitly deferred.

Sequencing: ship the bridge, the review step and class assignment first, because together they are the smallest thing that delivers the differentiated value and the time saving. Defer the observation editor even though incumbents have it, precisely because matching them there spends build effort on a job we chose not to win. The trade-off is conscious: a narrower launch that is unmistakably better at one job beats a broader launch that is second-best at several — and, per the strengths section, speed is our only real defence against an incumbent bolting on the same bridge.

Why this works — It converts the comparison directly into a prioritised backlog with an explicit deferral and an out-of-scope line, and defends sequencing the wedge first on the same timing-advantage logic established earlier, so prioritisation is traceable to the competitive evidence rather than to preference.

Risks, Assumptions and Open Questions

The load-bearing assumptions and the biggest unknowns, stated plainly.

• Assumption: public positioning reflects real product behaviour. We profiled competitors from their pages, not a hands-on audit. Risk: a page lags or oversells the product (see Source Dates).
• Assumption: the pilot generalises. Nine of twelve settings willing to pay is encouraging but small, single-window and self-selected; it is a signal, not proof of market demand ^[8].
• Assumption: the bridge is defensible for long enough. It is a timing advantage, not a moat; an incumbent could close it.
• Open question: would settings actually drop a tool to adopt us, or add us as yet another app? We have no structured buyer-interview data on this — the single most important gap.
• Open question: does the auto-summary clear the trust bar with educators who are accountable for EYFS judgements? Untested outside the pilot.

What would change the recommendation. The core recommendation — position and build on the play-to-evidence wedge — would weaken materially under any of three findings: (1) buyer interviews reveal settings would add rather than substitute us, making the "time saved" promise weaker because the old logging habit persists; (2) a hands-on trial shows Tapestry or Doodle already ships an equivalent bridge, removing the differentiation; or (3) educators in wider testing will not trust an auto-drafted EYFS summary they are accountable for, which would make the review step heavier than the time it saves. Each is testable before or during the MVP, and each has a cheap first test (structured interviews, competitor trials, a summary-trust usability round). None is a reason to stop; each is a reason to validate early rather than to treat this analysis as settled.

Why this works — It exposes the load-bearing assumptions and names the highest-value open question rather than burying uncertainty, and the counter-evidence blockquote specifies three concrete findings that would change the recommendation plus a cheap test for each, which is what makes the risk section a validation plan rather than a disclaimer.

Recommended Next Steps

Decision: position Nimbletots for Schools as the bridge between play and evidence — adaptive 3-7 activity that automatically produces the EYFS progress summaries settings already owe parents and inspectors ^[7] — and scope the MVP narrowly around that wedge. Lead the go-to-market on educator time saved and four-subject breadth, not on head-to-head feature parity with any single incumbent, because we will not out-specialise a specialist at its own job.

Immediate actions, with owners:

1. Lock MVP scope to the wedge (bridge + review step + class assignment + safeguarding surface; defer the observation editor; exclude nursery admin). Owner: Priya Nair (Product Manager). Feeds the PRD.
2. Run 8-10 structured buyer interviews asking which tools a setting would drop or keep if they adopted us — closing the biggest evidence gap. Owner: Sam Whitfield (Head of Growth).
3. Hands-on trial of Tapestry and Doodle to verify positioning against real product behaviour before scope is frozen. Owner: Dr. Amara Okoro (Head of Learning Design).
4. Usability-test the auto-summary trust step with EYFS-accountable educators. Owner: Product + Learning Design.
5. Invest early in trust markers — visible safeguarding, data protection, and settings-sector references — where incumbents lead. Owner: Priya Nair, with Léa Dubois (Engineering Lead) on data-protection design.

Each action maps to a specific risk or open question above, so "next steps" are validation, not activity for its own sake.

Why this works — It gives one clear decision plus a short list of owned, dated actions each tied back to a named risk or gap, so the analysis ends in accountable validation work rather than a vague call to differentiate.

Ownership and Review

Owner: Priya Nair, Product Manager, owns this document and its conclusions. Contributors: Dr. Amara Okoro (Head of Learning Design, EYFS/pedagogy and competitor-trial input), Sam Whitfield (Head of Growth, buyer interviews and commercial signals), Léa Dubois (Engineering Lead, feasibility of the bridge and data-protection design). Decision rights: MVP scope recommendations here inform the PRD and are ratified with the CEO, Tom Fisher, at the scope-freeze review.

Where the evidence lives. External claims are cited inline to the sources list below (public product pages, GOV.UK statutory and statistical pages). First-party pilot figures come from the spring 2026 pilot dataset and are set out in full, with method and caveats, in the Product Validation Report; market sizing sits in the Opportunity Assessment. This document deliberately does not repeat those; it references them so the analysis stays a positioning read.

Review rhythm and triggers. Refresh before MVP scope-freeze, and thereafter whenever any of these fires: a named competitor publicly ships adaptive-to-EYFS-evidence reporting; the EYFS framework or its assessment duties change ^[7]; the buyer interviews or auto-summary usability tests return findings that move the recommendation (per Risks); or the pilot is superseded by post-launch data. Competitor-positioning rows should be re-dated at each refresh, given the freshness risk recorded above.

Why this works — Stated once and only here, ownership consolidates the cross-cutting governance — owner, contributors, decision rights, where evidence lives, and the specific events that trigger a revisit — so the rest of the document never has to repeat sign-off or caveat plumbing.