Start a literacy platform evaluation with the teaching problem

A district leader who calls about a literacy platform rarely has one problem. Reading results vary by school, teachers already juggle several digital tools, and nobody has agreed yet on what counts as improvement. As the account executive on that call, your first job is not to describe your product. It is to help the district name the instructional decision sitting underneath the request, then build a fair way to evaluate whether any tool, including yours, actually helps.

Why This Call Goes Wrong

Most literacy evaluation calls go sideways in the first two minutes. The district leader asks a direct question, something like whether your platform will raise scores, and the rep answers with a direct claim. That answer sounds confident, but it sets a trap. Student reading results depend on instruction quality, how much time teachers get to use the tool, how well it fits the existing curriculum, and dozens of things a software company does not control. Promise a score increase and you have made a claim you cannot back up, and the district will hold you to it later during renewal.

The second failure is treating the call as a demo booking. A curriculum director asking about literacy software is usually managing real tension between three or four existing tools, a staff that already feels stretched, and a board asking for results. If you skip past that tension and go straight to a feature walkthrough, you miss the actual decision the district needs help making, and you look like you were not listening. This same story plays out across other education software categories, not just literacy. The pattern repeats whenever a rep tries to skip the discovery work and lead with a claim the buyer cannot verify until months later.

Prepare Before You Dial

Before the call, write four discovery questions, one for each part of the decision the district is actually making. Ask about instruction, meaning how teachers currently teach reading and where the gaps show up. Ask about current tools, meaning what is already installed and how much of it teachers actually use. Ask about measures, meaning which assessment or score the district trusts enough to base a decision on. Ask about review owners, meaning who besides the curriculum director needs to be in the room, since IT, principals, and teachers all see different parts of the problem.

This preparation matters because the district leader on the phone often cannot answer all four questions alone. Curriculum directors know instruction and standards. They rarely know which login systems IT has already vetted, or which teachers are quietly avoiding a tool because it adds work. Naming that early, before you propose a workshop or a pilot, saves you from designing an evaluation around the wrong group of people. Write the workshop invitation list before the call too, since naming curriculum, IT, principals, and teachers ahead of time keeps you from improvising an invite list on the spot and forgetting someone whose buy in you will need later. You can find more Education practice conversations that show this same pattern across other roles in a district.

What To Say On The Call

Curriculum director Dana opens the call plainly. Dana says, "Reading results vary a lot by school. Can you tell me your platform will raise our scores, and will teachers need to manage another login on top of everything else?"

Account executive Theo does not answer the score question directly. Theo says, "I cannot guarantee a score change, because results depend on local instruction and how the tool gets used, not just on the software. What I can do is help you build an evaluation around the outcome you actually want to understand. How are teachers using the three tools you already have in place, and which measures does the district trust for this kind of decision?"

Dana admits the district has not settled on baseline measures yet. Theo follows up. Theo says, "That is common, and it is worth settling before any pilot starts. On the login question, your IT team should validate identity access before I describe what that experience looks like for teachers, since every district's setup is different. Would it help to bring curriculum, IT, a couple of principals, and two or three teachers into one working session? We would look at current workflows, the measures you are considering, and what evidence each group needs before they sign off."

Dana agrees, and the call ends with a scheduled workshop instead of a demo. That is the outcome you want. Theo gave Dana a process for making a good decision, not a promise Theo could not keep.

Mistakes That Undermine The Evaluation

A few mistakes show up again and again on these calls. Reps answer the score question with a guarantee, then spend the rest of the relationship managing the gap between that promise and what actually happens in classrooms. Reps also describe the login and access experience before IT has weighed in, which forces IT to correct the account executive in front of the customer later, and that costs trust. Some reps propose a pilot before anyone in the room agrees on what measure will decide success, so the pilot ends with a pile of data nobody trusts enough to act on. And some reps meet only with the curriculum director, skip the teachers who will actually use the tool daily, and then wonder why adoption stalls after the contract is signed. The same mistake shows up when teams try to Review LMS reporting integration before a workforce deadline without first agreeing on what the integration needs to prove, and it shows up again whenever a team tries to Plan a math pilot around teacher conditions without asking teachers what time and support they actually have.

How To Practice And Score This Conversation

You cannot fix these habits by reading about them once. Set up a roleplay where a manager or a peer plays the curriculum director and pushes hard for an outcome guarantee, right in the first minute, the way real prospects do. Listen for whether you drift into a promise about scores or logins before you have gathered basic facts. A good run keeps the outcome question open, redirects to local conditions, and ends with a concrete next step, like a workshop with named attendees, instead of a vague promise to follow up.

Score the practice run on three things. Did you avoid a guarantee you cannot support? Did you ask about all four areas, instruction, current tools, measures, and review owners, before proposing a next step? Did you name specific people who need to be in the room, rather than leaving the group vague? DealSpeak scores exactly this kind of exchange, checking whether you held the line on outcome claims while still moving the conversation toward a real decision. A manager listening to this roleplay should flag any moment where the account executive answers a hard question with a soft deflection instead of a clear boundary, since vague answers train buyers to distrust future claims. Practicing this once is not enough. Run it again with a harder version of Dana, one who pushes back twice instead of once, and see whether your answers hold up under repeated pressure.

Close

A literacy platform evaluation starts well when you treat it as a decision the district owns, not a sale you are trying to close in one call. Ask about instruction, current tools, measures, and the people who need a seat at the table, and you will earn the kind of trust that survives past the first year of the contract.