Selling to universities is not enterprise SaaS with a campus logo. The buying unit is diffuse, the budget calendar is rigid, and a single product touches student privacy law, accessibility law, information security, and academic governance before anyone signs. The founders who win are not the ones with the best demo — they are the ones who understand the institution’s process well enough to move through it without stalling.
This is the map. It reflects what we see running pilots inside Arizona State University at ASU ScaleU, where the path from first conversation to enterprise contract is the whole point of the program.
Understand who actually buys
In higher ed, the person with the problem, the person with the budget, and the person who signs the contract are usually three different people — sometimes more. A typical deal involves a champion (a faculty member, advisor, or director who feels the pain), an economic buyer (a dean, provost’s office, or VP who controls the budget line), and a set of gatekeepers (IT security, accessibility, procurement, legal, the data-governance office). You sell to the champion, but you have to clear every gatekeeper. Map all three groups early; a deal that ignores the gatekeepers dies in the last 20%.
Start with a pilot, not a contract
The first sale to an institution is almost always a pilot, because no university buys unproven software at scale. The pilot is your wedge: it is small enough to approve without a full procurement cycle, and it generates the evidence that justifies the larger purchase. If you have not run one yet, start with our guide on how to run a pilot with a university. The rest of this guide assumes you are converting a pilot into a real contract.
What’s actually driving adoption
Before you sell, understand why institutions switch. We analyzed the switching behavior underneath ten ASU+GSV 2026 panels — not what leaders said they believe, but what they described doing differently. Three jobs kept surfacing:
- “Help me reach more people without hiring proportionally more staff.” The switch happens at a structural ceiling, not incremental dissatisfaction. SpringPod took one employer’s work-experience program from ~100 students a year to 10,000. Frame your product as breaking a ceiling, not as a marginal improvement.
- “Stop wasting people’s time on mechanical tasks so they can do the human work.” A Walmart task that took 60 minutes of barcode scanning dropped to 20 with computer vision — and the point was the time returned to customers, not the minutes saved. The prior approach usually failed because it required active effort from people who were already overloaded.
- “Show me it actually changed someone’s outcome, not just their engagement.” The most charged pattern. After years of EdTech delivering dashboards, the default assumption is your tool will feel better but not change results. Track destination outcomes (reading grade level, job placement, task time), not satisfaction surveys.
Two institutional jobs increasingly gate the deal. The first is change management: as one summit speaker put it, “the bottleneck is no longer the technology capabilities — the bottleneck is change management.” Buyers aren’t hiring a tool; they’re hiring a way to get their organization through the AI change curve. The second is compliance as a product: in the post-ESSER “value for money” era, administrators need dollar-attributed receipts. Services backed by a statutory mandate (special education under IDEA) are durable budget; “wellness” without a mandate wins the pilot and loses the renewal. Productize the receipt — per-minute logs, audit trails, billing — not another analytics dashboard.
Three signals worth designing around:
- Trust is built through relationships, not platform UI. Adoption sticks when a real person the buyer trusts can be called when something breaks. Product-led growth alone structurally underinvests in that human layer.
- One wrong AI answer triggers full abandonment. Frontline and classroom users who get a wrong answer often don’t iterate — they quit the tool. Visible confidence signals and easy correction loops matter more than a headline accuracy number.
- Institutions suppress their own tools’ best features. Districts asked DreamBox to disable adaptive pacing because advanced students got “bored.” Run a feature-adoption audit at 30/60/90 days; suppressed differentiators are a leading churn indicator.
Clear the security and accessibility gates
These two reviews stop more EdTech deals than price ever does, and both are predictable enough to prepare for in advance.
- Information security. Expect a vendor security assessment — often a HECVAT (Higher Education Community Vendor Assessment Toolkit) or a similar questionnaire. Have your data-handling, encryption, hosting, and incident-response answers documented before you are asked. A startup that returns a completed HECVAT in days rather than weeks signals it is safe to buy.
- Accessibility. Public institutions are bound by accessibility requirements (Section 508 / WCAG, increasingly enforced). Be ready to provide a VPAT (Voluntary Product Accessibility Template) and to fix what it surfaces. “We’ll get to accessibility later” is a deal-ender at most universities.
- Student-data privacy. FERPA governs student records. Know what data you touch, where it lives, and what your data-processing agreement says. Institutions will require contractual terms here; do not improvise them in the final week.
Integrate the way institutions expect
Technical fit is part of the sale, not an afterthought. Classroom tools are expected to support LTI 1.3 so they launch from inside the learning management system with single sign-on and roster provisioning. Operational tools are expected to integrate with the student information system and write data back through APIs rather than forcing manual exports. A product that drops cleanly into the existing stack is dramatically easier to approve than one that creates a new island of data and a new login.
Respect the budget calendar
Universities spend on a fiscal calendar, and most run on annual budgets set months in advance. A deal that is “ready to close” in the wrong month waits until the next cycle. Two practical consequences:
- Know your sponsor’s fiscal year and budget timing. Align the contract conversation to when money is actually allocated.
- Have a path for small first dollars. Discretionary funds, grant budgets, and departmental lines can fund a pilot now while the larger purchase routes through the formal budget process for next year.
Use procurement instead of fighting it
Once the dollar amount crosses a threshold, the deal goes through procurement, and possibly an RFP. This is not the place to improvise. Ask your champion how purchases of your size are normally made, whether you can be added to an existing contract vehicle or consortium agreement, and what the sole-source justification process looks like if there is no competitive bid. Procurement moves at its own speed; the founders who close are the ones who start the paperwork early and treat the procurement officer as an ally, not an obstacle.
Sell the second deal with the first
The single most valuable asset in higher-ed sales is a peer reference. Institutions are risk-averse and well-networked; they buy what comparable schools have already validated. Once you convert a contract, invest in the reference: a named case study with real numbers, a sponsor willing to take a peer’s call, and a presence where institutional buyers actually look. Each reference makes the next deal shorter.
Why founders do this with ASU ScaleU
Every gate above — finding the champion, clearing security and accessibility, timing the budget, navigating procurement — is faster from the inside than from a cold email. ASU ScaleU places EdTech startups into paid pilots inside Arizona State University and provides the executive introductions and operational support to convert them into enterprise contracts. We take 1% in-kind equity for that access, not cash. The model exists precisely because the higher-ed sale is hard to run alone.
If you have a working product and real early traction, apply to ASU ScaleU, or see how to choose an EdTech accelerator if you are weighing your options.
The demand-signals analysis is adapted from ScaleU’s “Why Education Leaders Are Switching”, published under CC BY 4.0.