Founding districts, 2026–27
We’re taking a small number of California districts, on purpose.
This isn’t a waitlist and it isn’t a free trial. It’s a partnership with districts willing to put their real questions and their real security review in front of us.
What you get
- Founding pricing, locked for three years. Materially below list, and it doesn’t reset when we raise prices.
- Direct access to the people building it. Not a support queue. A standing call with the team writing the code.
- Roadmap influence that’s real. Founding districts vote on connector priority and capability sequencing.
- Integration work done with you, not billed to you. Your connectors, your document library, your metric definitions.
- Full procurement support. Security packet, CA-SDPA, questionnaire responses, and a board presentation your team can present as its own.
- An honest exit. If it isn’t working at the end of year one, you leave with your data and we say so publicly.
What we ask
- A real executive sponsor. A superintendent or assistant superintendent who will actually use it, not delegate it into a pilot that quietly ends.
- Access to your CTO early. The integration and the security review are the project. Starting them in month three is how pilots die.
- Ten real questions. Things your team has genuinely been unable to answer. We build against those, not against a demo script.
- Candor. Tell us when an answer is wrong, when the interface is confusing, and when we’ve misunderstood how districts work.
- A reference, but only if we earn it. We’ll never ask you to say something you don’t believe.
Implementation
Ninety days from signature to answers your cabinet trusts.
Deliberately narrow at the start. One SIS connection, one assessment source, one document library, one group of users.
| Phase | What happens | Your team’s effort | What you have at the end |
|---|---|---|---|
| Weeks 0–2 Agreement |
Security review, CA-SDPA execution, county office coordination if you use one. | Your CTO and counsel, a few hours. We complete your questionnaire. We don’t ask you to complete ours. | A signed agreement your board can see, and a named data element exhibit. |
| Weeks 2–5 Connect |
SSO, read-only SIS connection, one assessment source, document library ingestion. | A read-only credential and one or two working sessions. No migration, no data entry changes. | Your district’s records joined into one view, with a reconciliation report you can check. |
| Weeks 5–8 Define |
Metric definitions, permission mapping, role scopes, LCAP goals and thresholds loaded. | Ed Services and Assessment confirm the definitions. This is the highest-value week of the project. | Every number Quilt produces computed the way your district defines it. |
| Weeks 8–10 Verify |
We run your ten questions and a permission test suite against your live configuration, with your team watching. | A half day. Bring your skeptics. | Evidence, not assurance. Including the denials. |
| Weeks 10–13 Launch |
Cabinet first, then principals, then wider staff on your schedule. Training built for people who don’t want training. | One session per group. Most people need fifteen minutes. | A working tool, an audit log your administrators control, and a usage report you own. |
Timelines assume a district with a supported SIS and an available technology contact. We’ll tell you honestly, before you sign, if we think your situation will take longer.
Sequencing
Capabilities turn on when your district decides they do.
Nothing expands automatically. Each phase requires a configuration change by your administrator and, where scope changes materially, a written amendment.
Most districts stay in Phase 1 for a full year, and we think that’s the right call.
- Phase 1 · Read and reasonAsk, analyze, summarize, compare, recommend, draft. No writes anywhere. This is where every district starts and where the value already is.Default
- Phase 2 · PrepareDraft family communications, prepare intervention documentation, assemble board materials, build reports. Everything produced sits in a queue for a person.Opt in
- Phase 3 · Execute with approvalA named person reviews and approves a specific action before it happens. Approval is per action, logged, revocable and never delegated back to the model.Amendment required
Pricing
One number, once a year, with no meter on curiosity.
No charge per question, per seat or per token. A district that hesitates before asking gets no value from this.
- One annual subscription based on district enrollment.
- Unlimited staff accounts within the scope you configure.
- Standard connectors and implementation included, not a separate professional services line.
- Founding-district pricing held for three years.
- Quotable in a form your business office can put on a board agenda.
We’ll price it on the first call. We aren’t going to make you sit through three meetings to find out whether this is affordable.
Funding sources districts use
LCFF supplemental and concentration where the use aligns to your LCAP goals and services for unduplicated pupils. Title I, II and III where the use fits. Local general fund. County office cooperative purchasing where available.
We’ll help your business office document the alignment. We won’t tell you a funding source is allowable when it isn’t.
Procurement
We complete your vendor security questionnaire, sign the California Student Data Privacy Agreement, provide insurance certificates and W-9, and give your team a board presentation they can deliver as their own work.
Before you ask
The questions we get on the first call.
You’re early. Why should we take that risk?
You should weigh it honestly. In return you get a product shaped around your district instead of a mature one shaped around someone else’s, pricing that reflects the risk, and direct access to the people building it.
To reduce it, the boundaries go in the contract and the agreement is annual rather than multi-year. You can export your data whenever you want, and we’ll tell you before you sign if we think your district is a bad fit. We would rather have twelve districts that renew than forty that regret it.
Our county office handles a lot of this. Can they be involved?
Yes, and we prefer it. County offices are often where the sharpest privacy and data governance questions come from, and they usually have the clearest view of what neighboring districts are running into. We’re happy to present to a county technology or curriculum group, and to structure agreements through a county office where that’s how your districts buy.
What if our data is a mess?
It is, and everyone’s is. Attendance codes drift, program flags get set inconsistently, a school changed its master schedule convention three years ago and nobody wrote it down.
Part of what happens in weeks two through five is that we produce a reconciliation report showing where your sources disagree with each other. Several districts have told us that report was worth the engagement on its own. Quilt surfaces the discrepancy rather than silently picking a side.
Our board is nervous about AI. How do we handle that?
Lead with the boundaries, not the capabilities. In our experience the concerns that come up in public comment are specific. Will it replace staff, will it make decisions about my child, will it train on student data, could it be wrong and nobody notices.
Every one of those has a concrete answer in this product, and we’ll give you the slides. We’ll also join the board meeting and answer questions directly if that’s useful to you.
What happens after the founding year?
You renew at founding pricing, or you leave with a full export and we destroy our copies on the agreed schedule and certify it. There’s no auto-renewal trap, no data hostage situation, and no penalty for deciding this wasn’t right for your district.
Founding cohort, 2026–27.
Tell us about your district and the question you’ve been unable to answer. We’ll tell you honestly whether we can help.