Plan a math pilot around teacher conditions

A district that just went through a rough software rollout will ask for a pilot before it commits to anything else. That request sounds simple. Underneath it sits a real question about whether you can be trusted with teacher time, and whether the next tool will actually work in their classrooms. As an EdTech account executive, how you respond to that ask sets the tone for the whole relationship, long before a contract exists.

Why this conversation goes wrong

Most reps hear "pilot" and think proof of concept, a fast demo of value inside a tight window. The district hears something different. They hear a chance to test whether you understand their constraints, their device inventory, their union rules, their teachers who already feel burned by the last rollout. When you answer a pilot request with a sales timeline instead of a design conversation, you confirm their worst fear, that you see the pilot as a formality on the way to a bigger deal rather than a real test.

The pressure gets worse because the person asking, often an assistant superintendent or curriculum director, is under their own pressure. They need to show their board and their teachers that they vetted this tool properly. If you promise results in one semester without knowing device ratios or training time, you hand them a number they cannot defend later. Then the pilot becomes evidence against you instead of for you.

How to prepare before you sit down

Before you agree to any timeline, gather the facts that actually decide whether a pilot can work. Ask your champion inside the district for device ratios by school, current bell schedules, and whether the teachers union reviews training requirements. Find out who else needs a seat at the table, usually someone from IT and a labor representative if the union is active in that district.

Write down, in one sentence each, what you actually need to learn from the pilot. Not "prove the product works," something specific like "confirm that a teacher with no prior experience can run a full unit using the platform inside a normal planning period." A vague goal produces a pilot that satisfies no one. A specific goal gives you and the district something to check against later.

Have a small number of pilot shapes ready, not one plan you are trying to sell. A six week pilot in two schools with strong device access looks different from a full semester across a district with mixed infrastructure. Bring options instead of a single ask, because a single ask reads as pressure and options read as flexibility.

What to say when the pressure hits

The district leader will usually open with a deadline and a worry about staff time. Curriculum director Lee says, "Can you show us results in one semester? And I need to know teachers will not be working extra hours for this."

Account executive Harper answers, "A semester can produce useful evidence, but only if we agree on the conditions first. Which schools have the device access and the leadership support to make this a fair test?"

Lee says the device ratios vary by building and that any training time has to go through the union for review.

Harper continues, "Then I cannot promise a specific result by a specific date, because the outcome depends on conditions we have not set yet. Training expectations need to come from the district and your labor representative, not from me. Could we get IT and the union liaison in a room together, pick two or three schools where the pilot has a real chance, and agree on a training plan and a short list of measures the district actually cares about?"

Notice what Harper never does. Harper never argues that a semester is too short, and never promises a semester is enough. Harper turns a deadline demand into a design question, then names the people who need to answer it. That keeps ownership of teacher time and training with the district, where it belongs, and keeps Harper's credibility intact.

Mistakes that undermine a pilot before it starts

Promising a result by a date is the biggest one. You do not control classroom conditions, so a promised outcome puts you on the hook for things outside your control. Say what a pilot can tell the district, not what it will prove.

Skipping the teachers is another common failure. A pilot designed only with administrators and rolled out to teachers without their input repeats the exact pattern that made the district cautious in the first place. If you want a model for keeping a hard conversation honest and specific instead of vague, look at how a firm boundary works when you Handle a medical absence question with clear boundaries. The same discipline applies here, name what you can commit to, name what belongs to someone else, and stop there.

Treating training time as a footnote causes trouble later. If the union has a say in training requirements, that conversation needs to happen before the pilot starts, not after teachers complain. And do not let the pilot measure only what makes your product look good. If the district cares about teacher time saved as much as test scores, put both in the plan, or the pilot will produce a result nobody trusts.

This kind of boundary setting shows up across education conversations, including moments as different as when you Respond when a student asks a coach for mental health advice. The skill is the same in both cases, know what is yours to answer and what belongs to someone else.

How to practice and score this conversation

Ask a manager or a peer to play a district leader who is anxious about staff time and wants a fast answer. Have them push on the deadline at least twice before they let you redirect to conditions. Notice whether you hold the line on not promising an outcome, or whether you cave under repeated pressure.

After the roleplay, write a one page pilot brief. Include these parts.

1. Scope, which schools and how many classrooms.
2. Participants, the teachers, IT contact, and union liaison by name or role.
3. Evidence, the two or three measures the district actually cares about.
4. Decision date, when the district will review results and decide what happens next.
5. Owners, who is responsible for each part of the plan.

Read the brief aloud before you send it. If any sentence sounds like a promise about outcomes rather than a description of a review process, rewrite it. A good brief describes what you will learn and how you will learn it, not what the answer will be.

DealSpeak scores this kind of exchange by checking whether you asked about conditions before agreeing to a timeline, whether you named the right people for training decisions, and whether your language stayed descriptive instead of promissory. Practicing this scenario alongside other Education practice conversations helps you build the same habit across different pressure points, whether the topic is a pilot, an absence policy, or a student in crisis.

A pilot built around real conditions costs you a little speed up front. It buys you a district that trusts your next answer, which is worth more than a fast semester one.