Product Discovery Brief Example for an Early-Years EdTech Product

Summary

There is a credible, sizeable educator problem worth investigating before we commit a line of code. Every early-years setting in England works to the statutory Early Years Foundation Stage (EYFS), which requires practitioners to assess and evidence each child's development on an ongoing basis ^[1]. That planning-and-evidencing load falls across roughly 59,700 registered childcare providers, including about 27,900 nurseries and pre-schools ^[2]. We already have unprompted inbound interest from settings and a large consumer base to learn from ^[4].

What we are recommending is not a schools product. It is a short, time-boxed discovery to test whether this educator problem is one Nimbletots is well placed to solve, and to quantify the assumptions that would make or break a later business case. We should not design, price or build anything until that discovery has run.

Why this works — The summary opens by naming the problem and the decision, not a solution. Leading with the bottom line, and explicitly declining to propose a build, keeps the document honest about where it sits in the lifecycle.

Goal and Decision

The decision on the table is whether to fund a bounded discovery now, and the timing case rests on two things we can stand behind. First, the educator problem is durable, not faddish: the statutory assessment and evidencing duty is a permanent feature of every setting's week ^[1], so a tool that genuinely reduces that load has an enduring market rather than a passing one. Second, our consumer traction gives us distribution, a content library and adaptive-learning data that a standing-start competitor lacks, which means that if the problem is real we are unusually well placed to solve it responsibly.

Neither point proves demand. Together they establish why discovery is worth funding now rather than later: the problem is lasting and our right to win is real, so the one open question is whether educators will actually pay to have it solved — which is exactly what discovery exists to answer, and what this brief asks leadership to authorise.

Why this works — The goal-and-decision case is argued from a durable, statutory problem plus a genuine internal advantage, establishing why discovery is worth funding now without leaning on urgency, screen-time panic or fear of missing out.

Problem and Users

The EYFS makes formative assessment a statutory duty: practitioners must observe children, plan next steps and produce progress summaries for parents and, at points, for the local authority ^[1]. In practice much of this is done by hand or across disconnected tools, on top of a full teaching day. The hypothesis we want to test is that planning and progress-tracking is a significant, recurring time cost for educators, and that a class-level tool could reduce it without displacing professional judgement.

The stakes of getting early learning right are well evidenced. The Education Endowment Foundation finds that structured early-literacy approaches add around four months of additional progress on average, with the largest gains for children from disadvantaged backgrounds ^[3]. That cuts both ways for us: it means good tools matter, and it means any Nimbletots schools tool must support sound pedagogy and evidencing, not merely add screen time to a classroom.

The affected population is well defined and countable. As at 31 March 2026 there were around 59,700 childcare providers registered with Ofsted in England, of which about 27,900 were nurseries and pre-schools operating on non-domestic premises ^[2]. Reception and Year 1 classes in primary schools sit alongside this as a related, larger population that the same EYFS duties partly reach.

At discovery stage the point is narrow: the problem is not niche. Tens of thousands of settings face the same statutory task, which is the shape of problem that could support a new revenue line if the value is real. Sizing the payable market is out of scope here and belongs in the Opportunity Assessment and Market Research Report.

Why this works — Grounding the problem in a statutory duty and independent evidence, then sizing the affected users with a real, dated official statistic, is what makes this section decision-grade rather than a pitch — and it defers revenue sizing to the right document.

Questions and Assumptions

Three early signals point the same way, and none of them is proof:

• Nurseries have contacted us unprompted asking to use Nimbletots with a whole class, which is unusual for a consumer app.
• A first round of around fifteen educator conversations surfaced a consistent complaint about the time spent planning activities and documenting progress (Nimbletots educator interviews, spring 2026, illustrative) ^[4].
• Our roughly 180,000 consumer family accounts give us a large base of children, content and adaptive-learning data to build a credible educator experience on ^[4].

These signals are suggestive, not conclusive. Settings that email a children's app are self-selected enthusiasts, and fifteen conversations cannot be projected onto 27,900 nurseries. That skew is precisely why we are proposing discovery rather than a build.

Discovery should test the assumptions that would sink the initiative if wrong, in rough order of risk:

1. Problem — how much time do educators actually lose to planning and progress-tracking, measured rather than recalled?
2. Value — is class assignment plus EYFS-aligned progress summaries the wedge, or a nice-to-have alongside what settings already do?
3. Buyer and adoption — who holds the budget, and will a setting pay from a real line rather than say they would?
4. Feasibility — can we meet the safeguarding and data-protection bar for a child-facing product used in a school context?

Riskiest assumption, and what would change this view. The initiative rests on planning-and-progress admin being painful enough that a setting will pay to reduce it. If measured time loss turns out to be small, or educators tell us the binding constraint is staffing and ratios rather than admin, the value case collapses and the right answer is to stop, not to run a pilot. We should also weigh the opposing read already visible in our own data: every educator we have heard from volunteered, so silence from the wider population is unmeasured, not evidence of demand.

Why this works — Presenting the internal signals with their enthusiast bias named, listing the riskiest assumptions across problem, value, buyer and feasibility, then stating in a counter-evidence callout exactly what would flip the decision to stop, is what makes a questions-and-assumptions section decision-grade. The illustrative internal source is labelled and carries no external URL.

Scope and Approach

This is a time-boxed discovery aimed squarely at the assumptions above, not at designing or costing a solution.

In scope

• Measuring where educators actually lose time in planning and progress-tracking.
• Testing whether class assignment and EYFS-aligned progress summaries are the wedge.
• Identifying the buyer, the budget line and the safeguarding and data-protection bar.

Out of scope

• Any product, feature or pricing design.
• Market sizing and revenue modelling — these follow in the Opportunity Assessment and Market Research Report.

Activities, in sequence

1. Structured interviews with a broader, less self-selected set of settings, including some that have not approached us.
2. A lightweight prototype walkthrough to pressure-test the class-assignment and progress-summary concept.
3. A small unpaid pilot across a handful of settings, as the decisive next gate.

Evidence from each activity is captured against the specific assumption it tests, so we finish discovery with a defensible read on each rather than a general impression.

Why this works — Splitting in-scope from out-of-scope and sequencing the activities from interviews to prototype to pilot keeps the discovery bounded, and tying captured evidence to each assumption shows leadership a concrete plan rather than an open-ended research request.

Success and Decision Checkpoint

The pilot is the checkpoint for the decision. To justify proceeding we need converging evidence on the four assumptions: a measured, non-trivial time cost; educators treating class assignment and progress summaries as the wedge rather than a nice-to-have; a named buyer with a real budget line; and a credible route to the safeguarding and data-protection bar. Pilot results are reported in the Product Validation Report, and we would return to leadership with an Opportunity Assessment only once these questions have evidence behind them.

This brief deliberately does not do three things. It does not size the payable market or model revenue, because willingness to pay is still an untested assumption. It does not specify a product, feature set or price, because doing so before discovery would anchor us to a solution we have not justified. And it does not claim the problem is proven; the internal signals here are enthusiast-skewed and small in number. What it does is make the case that the problem is credible, countable and durable enough to justify a bounded discovery investment — and no more than that.

Why this works — Naming the pilot as the checkpoint, setting an explicit evidence threshold across all four assumptions, and pointing to the Product Validation Report and a later Opportunity Assessment as the gates beyond it gives leadership a clear proceed-or-stop line — while stating plainly what the brief does not assert protects that decision from over-reading an early-stage document.