An empty school corridor at dusk, with light showing beneath a closed office door at the far end.
Growth & Funnels
Reading time:
~ 7 min
Author:
Ela Alptekin

EdTech growth stalls in the meeting you're not in

EdTech buying cycles run 6-18 months and end in a committee, not a click. Here are four shifts that align your growth engine with how schools actually decide.

Early traction isn’t the hard part in EdTech. It’s scale that kills momentum.

You nail the pitch with a few early champion teachers. You run some initial paid campaigns that show promise. Maybe you even get a pilot running in a school or two. The dashboard looks good, green shoots everywhere. But then it stalls. New signups slow to a trickle. Engagement data plateaus or dips. Internal pressure starts to mount.

Growth in EdTech fundamentally doesn’t behave like growth in typical B2B SaaS. You’re not selling into nimble startups or data-driven e-commerce brands. You’re navigating complex institutions, unpredictable government funding cycles, the very real pressures of teacher burnout, understandable parent hesitation, and multi-stakeholder decision-making groups who value trust and proven outcomes over speed and flashy features.

__wf_reserved_inherit

Why growth feels broken in EdTech


EdTech teams often execute the standard B2B growth playbook diligently: Google Ads, SEO, email nurture sequences, a LinkedIn campaign targeting school leaders. Results either don’t scale beyond that initial bump, or they scale once and then fall flat.

That’s because most traditional growth playbooks rest on three assumptions that don’t hold in education:

  • You can optimise for CAC/LTV from day one - when LTV is long-term and tied to renewals that depend on budgets and outcomes.
  • Decision-making is quick, rational, and individual - when it involves committees, takes months, and is deeply human.
  • Trust can be outsourced to brand messaging or influencer marketing - when peer validation and direct relationships are what actually move a school.

The real dynamics look like this:

  • Sales cycles run long (6-18 months isn’t uncommon) and are highly seasonal, aligned to term starts and budget approval periods.
  • Buyers are committees. A teacher, department head, principal, IT director, and procurement officer might all have a say, and any one of them can stop the deal.
  • Referrals and word-of-mouth inside the education community matter far more than cold paid clicks.
  • Emotional and pedagogical alignment - “this genuinely helps my students learn,” “this makes my teaching life easier” - carries as much weight as any ROI calculation.
  • Data privacy and procurement compliance are gating conditions, not paperwork. A deal can survive a lukewarm pedagogical review and still die on a data processing agreement.

If you’re relying on volume metrics and generic funnel tactics, pushing leads through a standard 14-day cycle, your growth will stall the moment it meets these realities.

__wf_reserved_inherit

Shift 1: Design for the education buying group


Educators, administrators, and parents don’t buy the way a typical B2B procurement officer buys software. They need time to evaluate and pilot, genuine buy-in from colleagues and leadership, clear evidence of outcomes for students or staff, and reassurance that you understand the chaotic reality of the school day.

What to do instead:

Map the full buying group. Go beyond the single point of contact. Understand the influence and the specific objection of each role: the teacher champion, the curriculum lead, the principal, the IT manager, procurement.

Arm your internal champions with a pitch kit. Your early users have to sell you internally, in rooms you’ll never enter. Give them materials that survive that meeting without you: a short slide deck, a one-page value summary, a case study, a battlecard for the objections that come up. Think of the teacher trying to convince their principal in a ten-minute window between periods.

Publish your compliance answers before anyone asks. Data processing terms, hosting locations, student data handling, accessibility conformance, integration and single sign-on requirements. Most EdTech companies treat this as late-stage sales collateral. Put it on your website. An IT director who can self-serve those answers in month two won’t stall you in month seven.

Build nurture journeys that span 3-6 months, not 14 days. Deliver value consistently over time: relevant research, webinars on pedagogical topics, check-ins timed to their school year. Trust builds slowly in education. Your job is to make the transfer of that trust easy for the person advocating on your behalf.

What this looks like in practice: when the teacher loved it but the school couldn’t buy it

I worked with an EdTech product where nearly all the early traction came through enthusiastic teachers. They understood the value quickly, used it in their classrooms, and advocated for it internally. From a marketing perspective, it looked like product-market fit.

It wasn’t translating into school-wide adoption.

The problem became obvious once we mapped the actual buying journey. The teacher wasn’t the buyer. They were the internal champion, and to get a rollout approved they had to convince a department leader, a senior decision-maker, and in some cases IT and administration. Each of those people was asking a different question:

  • The teacher: will this genuinely help my students?
  • The school leader: is this worth the budget, and will teachers actually use it?
  • IT: is it secure and compatible with our systems?
  • The budget holder: why this, and why now?

Our marketing was answering the first question and none of the others.

So instead of generating more teacher leads, we changed what marketing was for. We built the resources the champion needed to sell internally: evidence of outcomes, implementation detail, answers to the objections that came up in those meetings, and the language to carry the product from classroom experiment to institutional decision.

The change showed up in the pipeline within two terms. Pilot-to-school-wide conversion rose from 22% to 41%, because champions finally had the evidence and internal resources to move the conversation beyond their own classroom.

The teacher stopped being a lead to convert and became a champion to enable. It’s a subtle shift in framing and a total shift in what the marketing team produces.

__wf_reserved_inherit

Shift 2: Time your campaigns to the school calendar


Education is profoundly cyclical. The vast majority of significant buying decisions, pilots, and implementations happen in narrow windows before the start of major terms or fiscal years. Running always-on paid campaigns or launching major features mid-semester wastes budget and misses the decision window entirely. Push a new curriculum tool to a US school in April and you’re pitching against a budget that was settled weeks ago.

What to do instead:

Concentrate performance marketing into tight sprints around decision periods. Focus ad spend and outreach on the windows when schools are actively researching and budgeting. In the US that’s roughly November to January for spring pilots and March to June for autumn planning. Map the equivalent windows for every system you sell into, because they don't align: UK, Australian and Gulf academic calendars will each shift your sprint by months.

Use off-peak periods for value, not pressure. Mid-term and summer are for content, success stories, product updates, training resources, and community building. Nurture the relationship while nobody is being sold to.

Align onboarding to the academic year. Don’t expect teachers to implement a complex tool during peak teaching weeks. Structure implementation so schools can get set up over the summer or a quieter stretch, and be ready before they need it daily.

‍

__wf_reserved_inherit

Shift 3: Build word-of-mouth into your growth engine


Shift 1 is about helping one champion win the argument inside their own school. This is about what happens between schools. What a teacher says about your tool in a staffroom or a subject-specific Facebook group travels further than anything you say on LinkedIn.

What to do instead:

Incentivise referrals with more than money. Recognition in a newsletter, exclusive content, early access, elevated status in a community forum. Teachers share because it makes them useful to their peers. Design for that motivation.

Make your best users visible. Find the educators who love the product and help them build a profile: case studies, video testimonials, conference talks, webinar slots. Their credibility is not transferable to your brand, but it is lendable, and only if they get something out of it too.

Create spaces where educators share practice, not just product tips. Teachers already trade lesson plans and classroom strategies. If your community is a place where that exchange happens and your tool is incidental to it, adoption follows. If it’s a support forum with a nicer name, it won’t.

__wf_reserved_inherit

Shift 4: Optimise for activation in real classroom conditions


Getting a teacher to click “sign up” is the first tiny step. The real test is whether they successfully use the tool in a way that delivers value fast, ideally in the first session, under the conditions they actually work in.

Those conditions are specific and they are unforgiving. Four minutes between lessons. A locked-down district laptop where they can’t install anything. School wifi shared by thirty students on aging devices. A projector that only mirrors at one resolution. An interruption every ninety seconds. Onboarding designed for someone sitting undisturbed at a desk with admin rights will fail in that environment no matter how elegant it is.

‍

What to do instead:

Build onboarding around a job, not a feature tour. “Set up your first assignment.” “Get students into their first lesson.” One task, completed, in under ten minutes.

Test your first-run experience on the actual hardware. Constrained bandwidth, a managed device, no admin permissions, a shared login. Most activation drop-off in EdTech is environmental, not motivational.

Offer live quickstart sessions for school and district leads. A single co-pilot webinar for the person who will model usage for twenty colleagues is worth more than any in-app tour.

Use behavioural triggers for targeted rescue. If someone signs up and stops before a key activation step, reach out with help specific to where they stopped, not a generic re-engagement email.

‍

Measure the cycle you actually have

If the sale takes twelve months, monthly CAC tells you nothing useful and the board still needs a number. The answer is to report leading indicators that predict a committee decision rather than lagging ones that only confirm it.

Track the things that actually move a deal forward: how many accounts have a named internal champion, how many have circulated your pitch kit, how many have cleared IT and data review, how many have a pilot with a defined success measure and a date attached. Track pilot-to-purchase conversion and time-to-second-school-in-a-district, which is the single clearest signal that word-of-mouth is working.

These are the metrics that tell you in month three whether month twelve is going to land.

__wf_reserved_inherit

Final thoughts


Growth marketing in EdTech isn’t about shouting louder or running more campaigns. It’s about earning trust, respecting timing, and building something educators want to hand to a colleague.

Sustainable scale in this sector comes from becoming easier to share, easier for an internal champion to explain in ten minutes, and easier for a cautious administrator to believe. That means fewer broad assumptions and more listening to what a school day actually looks like.

Start with the meeting you’re not in. Find the teacher who already likes your product, ask what happened the last time they tried to convince their principal to buy it, and build the next quarter of your marketing around fixing whatever they tell you.

Like what you’re reading?
Sign up to my newsletter.

No noise. Only honest strategy, occasional reflection, and the kind of insights you actually want in your inbox.

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.