What Is Your Actual Selling Unit?

In conversations with EdTech founders about go-to-market planning, there is one question I find myself asking before almost any other: what is your actual selling unit?

It seems like a small question. It is not.

The default answer in EdTech is "the district." That is the language the industry uses. RFPs are issued by districts. Procurement happens at the central office. Conferences talk about district sales cycles. The whole vocabulary of EdTech revenue assumes the district is the buying unit.

For some products that frame is exactly right. For others, the actual buying unit is smaller, and the longer route through the district is where deals slow down or stall.

Why the district frame is so easy to default to

The pull toward district-level selling is reinforced from every direction. The largest EdTech success stories are district-scale. Investors ask about district contracts as a proxy for legitimacy. Competitors talk about their district customers when they talk about traction. Trade press covers district wins, not school adoptions.

So when a company is thinking about its next stage of growth, the natural shape of the conversation is "how do we get into more districts." It is the language everyone is speaking.

What is also true: for some products, the actual buying behavior is happening at a different layer. Sometimes that is one school at a time, often with discretionary funds the principal controls, often without an RFP at all.

A simple math example

Take a tool priced at two dollars per student seat, built specifically for middle school English Language Arts teachers. The addressable population at any given school is roughly 200 to 400 students.

A single school adoption looks like this:

• 300 students at $2 per seat = $600 annual contract
• One school principal can approve this from discretionary funds
• Decision timeline: weeks
• No RFP, no central office approval, no procurement process
• Average cycle measured in weeks, not quarters

A single district adoption for the same product looks like this:

• 30 schools across a district = a much bigger contract value
• Multiple stakeholders involved: superintendent, curriculum director, IT, procurement, possibly board approval
• Decision timeline: typically one to two budget cycles
• RFP required if the contract crosses certain dollar thresholds
• Average cycle measured in quarters

When the district really is the right answer

There are products where the district is unambiguously the right selling unit:

• Platforms that the whole district will use, like a learning management system, an assessment platform, or a single sign-on provider
• Products where the price point requires district-level budget approval to clear normal discretionary spend thresholds
• Products that need district-wide infrastructure to function, such as rostering, data integration, or central reporting
• Products that replace or augment curriculum across multiple subjects or grades

For products that fit those criteria, the district is the correct selling unit and the longer sales cycle is the cost of doing business at that scale.

For products that do not fit those criteria, running a district sales process can mean dragging a school-sized opportunity through a district-sized process. That is where deals stall and momentum gets lost.

Questions worth sitting with

The question of selling unit is not always obvious from the outside, even for the founder who built the product. A few honest follow-up questions can help clarify it:

• Who has decision authority for a purchase at my price point?
• What is the smallest unit that can adopt my product without requiring approval up the chain?
• When my best customers describe their adoption story, do they describe a district-level decision or a school-level one?
• What is the shortest path from a teacher discovering my product to a contract signed?
• If I drew a histogram of my customer contract sizes, what shape would it have?

The answers tell a story about where the buying unit actually lives. Sometimes that is the district. Sometimes it is the school. Sometimes it is the individual classroom or even the individual teacher.

The point is not to argue for any one answer. The point is to make sure the answer is the right one for the product, and not just the one the industry vocabulary is suggesting.

A district-shaped pitch run on a school-shaped product loses traction. A school-shaped pitch run on a district-shaped product also loses traction. The first move in any go-to-market thinking is to figure out which one the product is actually built for.