What to Send a District Buyer During the January Planning Window

School district planning table with a fiscal-year calendar, budget documents, and connected EdTech decision makers

If your sales calendar runs from January to December, it is probably out of step with the people you are trying to sell to.

Many school districts operate on a July 1 through June 30 fiscal year. That means January through April is not simply the middle of your sales year. It is a critical planning window for the district’s next fiscal year.

This is when priorities become more specific, departments shape budget requests, and leaders compare possible solutions. By the time a formal RFP appears, much of the decision may already be influenced by earlier conversations.

That is the timing problem at the center of any effective K12 sales strategy:

The seller who waits for the RFP is responding to a decision that may have been shaped months earlier.

The better approach is to show up while the district is still deciding what it needs, how it will pay for it, and what a successful implementation should look like.

What is happening inside a district between January and April?

The exact calendar varies by district, but the planning pattern is familiar.

Evidence from the current school year is being reviewed. A pilot may be producing early feedback. School and department leaders are discussing what worked, what did not, and which problems deserve more attention next year.

Those conversations can turn into:

  • Department priorities
  • Technology or curriculum requests
  • Program expansion plans
  • Budget proposals
  • Pilot recommendations
  • Procurement requirements
  • Board or leadership presentations

A district buyer is not only asking, “Do we like this product?”

They may also be asking:

  • Does this support a priority we already have?
  • Can we explain the need to finance or senior leadership?
  • What would implementation require?
  • Which schools or teams would use it?
  • What will IT and legal need to review?
  • How would we purchase it?
  • What evidence supports moving forward?

Your outreach should help answer those questions. During this window, the most useful sales material is not another generic product deck. It is a small, practical package that helps your contact build an internal case.

1. Send proof from a similar district or existing pilot

Start with evidence that makes the problem and solution easier to understand.

This might be:

  • A short case study from a similar district
  • A summary of an existing pilot
  • Before-and-after workflow examples
  • Feedback from participating staff
  • A description of the implementation process
  • Early results tied to the district’s stated goal

The proof does not need to make unsupported claims. It needs to show what happened, who participated, how the product was used, and what the district learned.

For example, if you sell a student support platform, explain how another team organized the rollout, which staff members were involved, and what the district reviewed before deciding whether to expand.

If you do not yet have a formal case study, create a one-page pilot summary. Keep it specific and honest:

  • The original problem
  • The scope of the pilot
  • The users involved
  • The implementation steps
  • The evidence collected
  • The next decision

This is especially useful in January because district leaders are converting current-year experience into next-year recommendations.

2. Send a one-page implementation plan

A district buyer needs to know more than what your product does. They need to understand what adopting it would involve.

Send a one-page implementation plan that covers:

  • Who will use the product
  • Which schools, grades, or departments are included
  • Key setup steps
  • Training and professional learning
  • Required integrations
  • Internal district owners
  • A realistic launch sequence
  • How progress will be reviewed

Avoid making the plan sound more complicated than it is. A simple timeline is usually more useful than a long project document.

The goal is to help your champion answer a question from leadership:

“If we approve this, what happens next?”

An implementation plan also gives curriculum, technology, and finance leaders something concrete to review together. It can expose gaps early, before they become late-stage objections.

Budget-ready EdTech sales packet with an implementation plan, evidence summary, pricing sheet, and security checklist

3. Offer a reference call, not just a reference name

A reference is more useful when you make it easy to use.

Instead of writing, “We can provide references,” offer a specific option:

“If it would help your team evaluate the rollout, we can arrange a short conversation with a district leader who has been through a similar implementation.”

Give the buyer context about the reference call:

  • What type of district or team is involved
  • What problem they addressed
  • What stage of implementation they are in
  • Which questions they can answer
  • How long the conversation would take

A good reference call helps the buyer understand the parts that a demo cannot show:

  • How staff adoption went
  • What internal approvals were needed
  • What the vendor had to provide
  • What the district would do differently
  • How the product fits into existing routines

This is particularly valuable when your prospect is trying to turn interest into a defensible budget request.

4. Send clear pricing and the procurement path

Unclear pricing creates work for your champion. During the January planning window, they may need to put a potential purchase into a budget conversation before every detail is finalized.

Give them a straightforward view of:

  • What the license includes
  • Implementation or onboarding costs
  • Training and support
  • Renewal terms
  • Any pricing differences by scope
  • What is included in a pilot
  • The likely purchasing route

You do not need to force a final proposal before the district is ready. But you should make it possible for the buyer to understand the shape of the investment and the steps between interest and purchase.

Ask practical questions about the school district procurement process, such as:

  • Does this require a formal bid or RFP?
  • Is board approval required?
  • Which office reviews the agreement?
  • Does the district use a cooperative purchasing contract?
  • What documents are needed before a purchase order can be issued?
  • Is there a target date for the budget recommendation?

The answers will vary. Do not assume that one district’s process applies to another.

Also have your privacy and security materials ready. IT and legal may ask about student data, access controls, retention, integrations, FERPA, or COPPA depending on the product and use case. Provide clear information about how your product works, but avoid making broad legal claims. The district’s own IT, privacy, and legal teams will determine what their requirements are.

5. Make one specific ask

A useful January email should not end with “Let me know what you think.”

The buyer needs to know what decision or action you are proposing.

Your ask might be:

  • A working session to map the product to a budget priority
  • An introduction to the curriculum or technology lead
  • A review of the implementation plan
  • A short call with finance or procurement
  • Agreement on pilot success criteria
  • A reference conversation
  • Confirmation of the district’s planning timeline

For example:

“Would it be useful to spend 25 minutes reviewing the implementation scope and procurement steps with you and the person who owns technology review?”

Or:

“If this is being considered for next year, could we schedule a working session with the curriculum and finance leads to determine what would need to be included in the budget request?”

That is a better ask than another product demo because it matches what the district is trying to accomplish during the planning window.

Send the package to more than one person

You do not need to contact every person in the district at once. But you should avoid treating one enthusiastic contact as the entire buying committee.

The school-level champion understands the day-to-day problem and can help you prove that the solution works in practice.

The curriculum or instruction lead evaluates academic fit, staff adoption, and alignment with district priorities.

The technology or security lead needs to understand integrations, data handling, access, and implementation risk.

The finance or procurement owner needs to understand the cost, funding source, approval process, and purchasing path.

Each person may need a different part of the same package. The champion may need the implementation summary. Curriculum may need the evidence. IT may need the security overview. Finance may need pricing and procurement details.

For a deeper explanation of how to map these roles, see K12 District Decision Makers Explained: How to Map the 6 People Who Actually Approve Your Contract.

Use board agendas and minutes as free research

Public board agendas and meeting minutes can give you useful account intelligence before you send an outbound message.

Look for references to:

  • Budget workshops
  • Strategic planning
  • Curriculum or program reviews
  • Technology initiatives
  • Student support priorities
  • Cybersecurity or data privacy policies
  • Contract renewals
  • Pilot recommendations
  • Requests for proposals

A winter budget workshop matters because it can reveal what the district is actively considering while there is still time to influence the plan.

A cold email in June may arrive after the priorities are set, the budget is approved, or the procurement process is already underway.

Use board materials carefully. Do not pretend to know the district’s internal plan from one agenda item. Instead, use the public signal to create a relevant question:

“I saw that the district is discussing student support priorities for the coming year. Is your team still evaluating possible approaches, or has that work moved into a formal procurement process?”

That is the difference between researched EdTech outbound sales and generic volume outreach.

School board budget workshop papers connected to a district buying committee map for curriculum, technology, finance, and school leadership

A simple January email structure

You can keep the message short:

  1. Mention the district priority or planning context.
  2. State why your product may be relevant.
  3. Offer two or three useful materials.
  4. Name the internal roles that may need to review them.
  5. Make one specific ask.

Example:

Subject: Materials for your next-year planning

Hi [Name],

Based on your team’s work around [priority], I thought it might be useful to share a short implementation plan, a summary of a similar pilot, and an overview of pricing and the procurement steps.

If this is being considered for the next budget cycle, would you be open to a brief working session with the curriculum or technology lead to review scope and evaluation criteria?

Best,
[Name]

The message works because it supports the district’s process instead of asking the buyer to start over with another product presentation.

Use the printable version of this planning framework

January through April is a high-leverage period for selling to K12 districts, but it is only one part of the annual cycle. The right message in the fall is different from the right message during budget drafting, procurement, or implementation.

For a practical, printable view of the full cycle, visit the free K12 District Sales Calendar guide. It is available at no cost and with no obligation through a short name-and-email form on the guide page.

The guide helps you organize when to research districts, build relationships, support evaluations, and advance procurement conversations.

If your team already has a product districts are buying but needs more qualified conversations with K12 district decision makers, DistrictPipeline can handle the prospecting and outbound work as a fractional K12 team, without requiring you to hire a dedicated SDR team.