The single biggest reason a well-intentioned pitch fails isn't a weak platform choice — it's a pitch built around what excited the pitching teacher rather than what the person approving budget actually needs to hear. A principal or academic director evaluates a proposal through a different lens than a classroom teacher does, and a pitch that doesn't translate into that lens, however enthusiastic, tends to stall regardless of how good the underlying idea is.
Lead with their priorities, not features
Leaders think in outcomes and budget: exam results, parent satisfaction, teacher workload, and enrollment. Translate every feature into one of those four before the meeting.
Leaders think in a small, consistent set of categories: exam results and academic outcomes, parent satisfaction and enrollment, teacher workload and retention, and budget against known constraints. Every feature of a reading platform worth mentioning in a pitch should be translated into one of these four categories before the meeting, rather than described in the platform's own product-feature language, which rarely maps cleanly onto what a leader is actually weighing.
Bring a number, not just an opinion
A short pilot with one class — even a few weeks — gives you real attendance, engagement, or level-progress data to bring instead of an enthusiastic anecdote.
A number from even a short pilot — attendance rates, quiz scores, a handful of weeks of engagement data — carries far more weight in a leadership conversation than an enthusiastic description of how well a pilot class responded. Leaders are used to hearing that teachers like new tools; what moves a budget decision is evidence the tool produces a measurable outcome, however preliminary that evidence might be.
Answer the workload question before it's asked
Leaders worry new programs mean more work for already-stretched teachers. Lead with what reduces teacher effort — classroom-ready content, automated reporting — not just what's new.
Workload is very often the unspoken objection sitting underneath a leader's hesitation, even when it's never stated directly in the meeting. Addressing it proactively — leading with what the platform removes from a teacher's plate rather than only what it adds — heads off the most common source of quiet resistance before it has a chance to surface as a delay or a soft no.
Structuring the actual pitch meeting
A strong structure runs in this order: state the problem in terms the leader already recognizes (exam pressure, parent requests, workload complaints), present the pilot data as evidence a solution exists, name the specific workload reduction the platform offers, and close with the lowest-risk possible ask — typically a free pilot with one class, not a school-wide commitment. Ending on the smallest reasonable ask is what makes approval easy rather than something that needs escalation to a full budget committee.
Handling common pushback in the room
The most frequent objections are "we already tried something like this" and "our teachers are stretched too thin to learn a new system." Both are best met with the same response: a free pilot is specifically designed to test exactly those concerns with minimal risk, and the workload data from that pilot — not a promise made in the meeting — is what should ultimately settle the question either way.
What to bring even without formal pilot data yet
If no pilot has run yet, bring comparable outcome data from a published guide or case study instead of relying purely on enthusiasm, and frame the ask explicitly as a request to generate the school's own data through a free pilot, rather than asking for a full commitment based on someone else's results. This keeps the ask modest and evidence-oriented even before your own data exists.
Following up after a pilot approval
Securing approval for a free pilot is the beginning of the pitch process, not the end of it — the follow-up conversation after the pilot concludes is where the real budget decision typically gets made. Schedule that follow-up meeting before the pilot even starts, so there's a fixed point on the calendar for reviewing results as opposed to letting momentum quietly fade once the initial excitement of getting approval wears off. Bring the same translated, leader-focused framing to that follow-up as the original pitch — outcome data, workload impact, and a clear recommended next step — rather than assuming the pilot's results will speak for themselves without being actively presented in the terms leadership cares about.
The one-line ask that works: "Can we pilot this free with one class for a term, then decide?" is far easier to approve than a full-year commitment. If a pitch meeting ends with a firm no rather than a request for more information, ask directly what specific data would change the answer, then come back once a pilot has generated exactly that.
See it in iRead: Get the business-case view built for the leadership conversation.
For school leadersKey takeaway
A pitch succeeds or fails based on translation, not enthusiasm — leaders need the platform's benefits converted into their own decision categories, backed by real numbers wherever possible, and offered as the smallest reasonable first step rather than a full commitment asked for all at once.
Frequently asked questions
Who should be in the pitch meeting?
Ideally the academic director or principal plus whoever controls budget — a joint meeting avoids the pitch being relayed secondhand.
What if the answer is no?
Ask what data would change the answer, run a free pilot to gather exactly that, and return with it — most declines are about uncertainty, not the idea itself.
Should a teacher pitch this alone, or bring someone else into the meeting?
Bringing a department head or another teacher who's seen early results adds credibility beyond one person's enthusiasm, but the most important addition is data from even a small pilot — that consistently matters more to a leader's decision than who is in the room presenting it.