A Proposal the District Helped Build Doesn't Need a Follow-Up

Every founder knows the feeling. You send a proposal to a district administrator, then keep checking your inbox, hoping for a response. After a few days, you start to question yourself. Did you include enough detail? Was there too much? Was the pricing right? Should you follow up or wait a bit longer?

That feeling of uncertainty after you hit send is a sign that something went wrong before you even wrote the proposal, not after.

If you feel anxious about whether your proposal will be accepted, it often means the administrator wasn't involved in creating it. You wrote it based on your assumptions, not on what they actually told you. Now, you're just hoping it's a good fit.

One idea changed how I approach proposals: a proposal should confirm what you've already agreed on, not introduce new information. By the time the administrator reads it, everything in the proposal should be familiar because you discussed and agreed on it together. The pricing, timeline, outcomes, and plan should all come from your earlier conversations. When you do this, sending the proposal feels easy. It's simply putting in writing what you already built as a team.

Where the anxiety actually comes from

The anxiety founders feel after sending a proposal usually comes from missing important conversations before writing it.

They didn't ask about money. It's not just about how much the district has, but how they fund projects like this, where the money comes from, and if there's a timeline for the funding. Without these details, your proposal's pricing is just a guess.

They didn't ask who else needs to approve the proposal. The administrator you're working with might need approval from a superintendent, a board, or a finance committee. If you don't know who these people are or what matters to them, your proposal will be reviewed by people you've never met, and they may have questions you haven't addressed.

They didn't ask about past experiences. Districts remember their history with vendors. If a previous project didn't go well, there may be skepticism that your proposal doesn't address because you never brought it up. That doubt is present during the review, even if you don't realize it.

Every missing conversation leaves a gap in your proposal. Each gap gives the administrator a reason to put it aside instead of moving forward.

What changes when you build the proposal together

When you have these conversations before writing, the proposal turns out very differently. More importantly, it feels different to the administrator reading it.

The problem statement is specific. It describes the district's exact challenge, using the administrator's own words from your conversations. When they read it, they think, "this person understands our situation," instead of, "this could have been sent to any district."

The solution is not just a product overview. It's a detailed plan you and the administrator created together. You discussed how implementation would fit with teachers' schedules, what a phased rollout would involve, and agreed on what success means and how to measure it. All of this is in the proposal because the administrator helped shape it.

The pricing section doesn't cause anxiety because you've already talked about money. The administrator knows the cost, where the funding comes from, and has agreed the investment is worth it. There's nothing new in the pricing section.

When the administrator reads the proposal, they see their own words, priorities, and definition of success throughout. They don't have to review it like a typical vendor document because they helped create it. Approving it feels like the obvious next step.

Why does the follow-up disappear

When you build a proposal this way, you don't need to send follow-up emails. It's not because you were pushy or used a strategy. It's simply because there are no unanswered questions.

The administrator already knows the proposal's contents before they receive it. The decision-maker has been updated by the administrator who helped create the plan. Any concerns that would usually come up during the review have already been addressed in your conversations.

Now compare this to writing a proposal on your own. You send it and wait. The administrator reads it and has questions you can't answer because you're not there. They pass it to the decision-maker, who has even more questions. The proposal gets postponed for another meeting, and you find yourself at your desk, refreshing your inbox, wondering what happened.

Nothing actually went wrong at that moment. The real issue was writing the proposal before having the necessary conversations.

The question to ask yourself before you write anything

Before you start with a template, ask yourself: could I write this proposal using the administrator's own words?

Can I describe their problem the way they described it to me? Can I explain why this matters to their district using their words? Do I know exactly what success looks like to them—not just in general, but the specific outcomes they told me they need? Do I know how the money works and who else needs to approve it?

If you can answer yes to all of these questions, your proposal is ready to be written. And when you send it, you won't feel anxious about the outcome. You'll know it will land because the administrator has already agreed to everything in it.

If you can't answer yes, you still have more conversations to have. That's not a setback—it's just how the process should work.

This is part of what we work on

In the EdTech Impact Accelerator, founders learn how to have all these conversations before writing a proposal. You practice with a real deal from your pipeline, figuring out what you know, what you still need to learn, and which conversations need to happen before you start writing.

The program starts June 1. If you've been sending proposals and not getting responses, there's a reason—and it can be fixed. Send me a message if you want to talk about your deals.

#EdTech #K12Education #SellOnValue #EdTechSales #DistrictSales