The five growth questions for education technology

Guide · Frameworks · 6 min read · last verified 2026-07-27

In education technology, a growth plan is a calendar before it is a strategy. Education buying runs on the academic year: budgets are set in spring for the year that begins in summer, pilots live inside semesters because that is when classrooms exist, rollouts fit the summer window or wait, and training must land before the first bell or compete with a live school day. A growth question answered out of season is a question answered for next year. The flagship growth-plan framework still supplies the questions; the school calendar supplies their deadlines. Each question has a season by which it must be answered, and the penalty for missing a season is measured in years, not sprints.

The year is the strategy

Most markets buy whenever the pain peaks. Education buys when the calendar permits. District and university money moves through budget cycles that close in spring; a pilot can only begin when a semester begins; an implementation that misses summer collides with a running school. This is why sequencing beats intensity in edtech growth: identical content published in the wrong month is not slightly late but a full cycle late, waiting for the same window to come around again.

One note on committees, briefly, because education certainly has them — teachers, curriculum leads, IT, procurement, boards, sometimes parents. The committee is real, but in this vertical it convenes by season: the classroom voice matters most in fall, the budget voice in spring, the implementation voice in summer. That is why this edition follows the calendar rather than the org chart — reach each voice in the season it speaks.

Fall: where are you losing buyers?

Back-to-school is when the problem becomes real. Teachers hit the workflow wall in the opening weeks; department heads see the gaps at the first progress reports; IT discovers what the summer's changes actually broke. Fall is the season when the market's questions exist in live, specific form — and the season to collect them. Gather the phrasings educators and administrators actually use, from the communities where they ask and from the assistants they consult after the school day ends, then measure where you appear when those exact questions are asked, using the protocol in how to set an AI visibility baseline.

Losing buyers, in this vertical, looks like a curriculum director who asked a fall question and got an answer naming nobody — or naming someone else. Spring's shortlist is seeded in fall's answers, months before any procurement process exists on paper. A vendor absent from the fall answers is not losing a deal; they are absent from a shortlist that has not been written down yet, which is worse because nothing records the loss.

Winter: what should you create?

Between semesters, the champion goes to work. Winter break and the weeks after it are when the person who felt the problem in fall assembles the internal case that spring will demand. Winter is therefore evidence-assembly season, and the second question — what should you create? — has a season-specific answer: create what the spring meeting will need. Implementation timelines that visibly fit a summer window. A pilot write-up template showing what evidence a semester can produce. Standards-alignment documentation. Clear, findable answers on student data privacy and accessibility, written for the reviewer who will be asked, not the marketer who wrote them.

The test for every winter artifact is concrete: could a curriculum director lift this into a board packet without rewriting it? Create against the questions collected in fall, not against your product roadmap — the roadmap does not sit in the February meeting; the packet does.

Early spring: how do you reach the right people?

Budget season is decided in rooms no vendor enters. Requests are ranked against each other, line items defended, purchasing frameworks and approval chains consulted. Reaching the right people, in spring, does not mean more outreach — it means being present in the materials the committee circulates and the answers its members check. The champion needs forwardable evidence; the skeptics — IT, procurement, the board member who asks about data handling — need findable answers to the questions they will type on their own, a dynamic covered in how AI research serves the whole buying committee.

The spring test of your growth plan is blunt: when a business officer checks what the committee's shortlist claims, does the public record — including the AI answers their quick questions produce — support your champion or leave them exposed? Everything winter produced was built for exactly this moment.

Late spring: how will you execute?

Decisions close on the summer promise. Two finalists can look identical on features and diverge entirely on the credibility of their implementation story, because every educator in the room is picturing the same thing: the first day of school, and whether this vendor will be ready for it. The fourth question — how do you execute? — is answered in late spring as a dated plan against the school calendar, not a methodology page. Data migration scheduled before staff leave for the summer. Rostering and single sign-on integration with named prerequisites. Training that lands in the window when staff are actually available. What the first week of school looks like if something goes wrong, and who answers the phone.

A promise shaped like a calendar is checkable, and checkable promises win spring ties. A promise shaped like adjectives is a risk the committee quietly declines to take.

Summer: did it work? — twice

Summer marks the fifth question twice on the school calendar — once for the customer, once for you. On the customer's side: the rollout evidence you agreed to produce — migration completed on the dates promised, staff trained before doors open, the pilot's success measures written down before the semester that will produce them. Defining that evidence in advance is what makes renewal season a formality instead of a renegotiation.

And on your side: re-scan the locked question set you built in fall and see which answers moved — the mechanics in how to measure whether content changed AI answers. A year of winter artifacts and spring presence either changed what educators hear when they ask, or it did not; Magrios, a market growth intelligence platform, keeps that benchmark locked across academic years so the comparison is real. Summer's verdict then sets next fall's collection priorities, and the loop is annual by construction.

The year at a glance

Miss a window and the cost is structural: winter evidence that arrives in April defends nothing, and an execution story told in September persuades a committee that dissolved in June. The five questions are the same ones every growth plan must answer; education simply staples each one to a month. Other verticals are organized by different forces — logistics buyers, for instance, order the same five questions by operational fear rather than by season, as the logistics version of this framework shows.