Ask an edtech founder who their customer is and you'll hear one of two very different answers. One is a school district, where a teacher loves the product, a curriculum lead evaluates it and a finance office pays on a fixed calendar. The other is a learner or a parent with a credit card and a short attention span.
Many companies end up doing both, a district product and a consumer app, and their tools get muddled as a result. Decide which motion pays the bills this year, set up the company around it, and keep the other one small until it earns more attention.
Who pays decides your tools
Here's how the two motions differ in practice, and which parts of Nautis each one leans on.
| Question | Schools and districts | Learners and parents | Main Nautis modules |
|---|---|---|---|
| Who decides | Several people: teacher, curriculum lead, technology office, finance | One person, often in one session | Leads CRM for institutions, GTM Planner for consumers |
| When money arrives | In chunks, often once a year when contracts start | Every day, in small amounts | Startup Health for both, Invoices for institutions |
| What proves value | Pilot results, usage and teacher feedback | Conversion, completion and repeat purchase | Custom forms for feedback, GTM Metrics for conversion |
| Paperwork | Pilot agreements, purchase orders, data privacy agreements | Terms of service and app store rules | Docsign and Data rooms for institutions |
| Biggest operating risk | Missing the budget window and waiting a year | Paying too much to acquire a learner who quits | Task boards and Decision Loop |
Working back from the school budget year
In the United States, the National Center for Education Statistics labels a school fiscal year by the year it ends, with the year running from July 1 to June 30. Its finance report also notes exceptions: in the year it covers, Alabama started on October 1 and Nebraska and Texas on September 1. Check each state and district you sell into, because a deal planned for the wrong calendar slips by twelve months.
The practical rule: a district usually has to know about you, and want you, before its budget for next year is set. If you first meet a curriculum lead in May, you may be selling for the year after.
- Create a District sales pipeline in the Leads CRM with stages such as Teacher champion, Pilot running, Budget request, Board or finance approval, Purchase order and Closed Won. Every pipeline can have its own stages, so a consumer partnerships pipeline doesn't have to share these.
- Set each lead's Expected Close Date to the start of the fiscal year it depends on, not the date you hope to sign. The forecast panel then shows a realistic picture of when revenue lands.
- Add a custom field for the district's fiscal year start, since custom fields hold anything the default form doesn't.
- Build a Task board for each selling season with KPI tasks such as "8 pilots converted by June 30", so progress toward the deadline is visible every week.
Pilots, evidence and renewals
Many districts want to try a product before they buy it, and a pilot is only as useful as the evidence you collect from it. Plan that evidence before the pilot starts.
- Pilot agreement. Send it through Docsign with signers in order, for example the curriculum lead then the business office, and set the link to expire in 30 days so it doesn't sit in an inbox all term. Keep the audit log PDF.
- Teacher feedback. Build a short survey in Custom forms with a Rating field on the NPS scale and one open question. Ask only about the teacher's experience, and don't collect student names or details.
- Evidence pack. Put the pilot summary, case notes and your privacy documents in a Data room, then share a passcode-protected link with an expiry. The Analytics tab shows which files the district opened, which tells you what they're worried about.
- Demos and check-ins. Share a Meetings booking link with buffers so teachers can book around their timetable.
- Renewal invoices. Annual contracts work well as yearly recurring invoices in Invoices. The aging view shows which districts are paying late, and the briefing flags overdue ones.
Cash will come in lumps. In Startup Health, a July with several renewals can look like a growth miracle and an October like a collapse. The guide says to count recurring revenue only, so enter each annual contract at its monthly value in the MRR field, and explain the cash lumps in the snapshot so your investors read the trend correctly.
Student data stays out of Nautis
Edtech carries privacy duties that most startups never meet. The US Department of Education describes FERPA as a federal law giving parents the right to access their children's education records and some control over disclosure, with those rights moving to the student at 18 or on entering a postsecondary institution.
For apps used by children under 13, the FTC's COPPA guidance generally requires verifiable parental consent before collecting personal information. A school can consent on parents' behalf, but only in the educational context, and the operator may not use that data for its own commercial purposes. The FTC is explicit that compliance is the operator's job. States add their own student privacy laws on top.
Here's the line to hold. Nautis is for running your company: district contacts who are adults, deals, contracts, plans, money. It isn't certified for student data and you shouldn't put any there. That means no student names in leads or notes, no pupil data in forms, and no class lists in data rooms. Get advice from a lawyer who knows education privacy before your first district contract, and treat the privacy agreement as part of the sale.
Consumer learners run on a different clock
If learners or parents pay you directly, your year follows their calendar: exams, the start of term, the moment someone decides to change careers. Your own sign-up data will show the peaks better than any outside benchmark, so record it from the first month.
The GTM Planner suits this motion. Write the ideal customer profile for one learner type, not three, then run experiments with a hypothesis, channel and metric, for example "If we offer a free diagnostic test, we expect trial-to-paid conversion to rise from 4% to 6%, because learners see their gap." Plan exam-season campaigns in the Social calendar and tag every link in the URL shortener so you can see which channel brought paying learners rather than browsers.
If your consumer product is a mobile app, the store rules and retention questions on our consumer app page apply too. The Financial Planner has a Mobile App template as a starting point.
A spring for a six-person K-12 startup
Take a reading-practice product with pilots in nine districts. In March, the founder filters the District pipeline by expected close date and sees five pilots due to decide before June 30. Two have no teacher feedback yet, so the customer success lead sends the survey link and books check-ins.
In April, a technology director asks for the privacy documents. They go into the evidence data room, and the analytics show the director opened the data processing summary three times and the pricing sheet once. The team prepares for a privacy conversation, not a discount.
In May, three pilot agreements convert to annual contracts through Docsign, and the founder logs a Decision Loop entry to hire a second customer success person, with a 60-day review on renewal rates. In June, the board update goes out as a Startup Health snapshot with history turned on, explaining why July revenue will jump.
Specialist tools, and when Nautis is the wrong pick
An edtech company still needs its own product stack: a learning platform or app, the sign-in and class rostering connections schools may ask for, product analytics, a support desk, and accounting software. If you sell to many districts, procurement and bid-tracking services can help you find formal opportunities. Nautis connects to outside tools through Integrations, where agents call them on demand, and nothing syncs in.
- You need a place to store or analyse student data. Nautis isn't that place.
- Your sales team works dozens of districts at once with formal bids. A dedicated CRM with education data may go deeper.
- You're a solo founder testing a course. A course platform and a spreadsheet may be enough before paying $49 a month for Launch at the time of writing. See pricing.
- Districts ask for vendor security certifications for every tool you use. Don't assume Nautis has any. Ask before you list it in a questionnaire.
- You want a vendor with years of history. Nautis launched publicly in July 2026.
FAQ
What software for edtech startups selling to schools matters most?
A CRM pipeline built around the school budget year, an e-signature tool for pilot and data agreements, and a way to share evidence securely. Your product also needs the privacy controls schools ask about. Nautis covers the first three for the company side; student data stays in your own product.
When should an edtech startup start selling for the next school year?
Before the district sets next year's budget. NCES reports date the US school fiscal year from July 1 to June 30, with a few states starting later, so for most districts that means the spring before. Check each district's calendar, because a missed window can delay a deal by a full year.
Can I store student information in Nautis?
No. Nautis isn't certified for regulated data, and student records fall under laws such as FERPA, COPPA and state privacy laws. Use Nautis for adult business contacts, deals, contracts and plans, and keep student data in your product under your privacy agreements.
Does Nautis work for consumer edtech too?
Yes, for the company side. The GTM Planner runs experiments and metrics, the Social calendar plans seasonal campaigns, and the URL shortener tracks which links convert. It doesn't replace your course platform, payments or product analytics.