Apptegy alternatives for districts
Apptegy sells a bundle: district website, mobile app and communications under one contract with one team. The decision facing a district looking at alternatives is not really which vendor to pick. It is whether to buy another bundle or to unbundle, and that choice has staffing consequences that outlast any licence.
| Replace with another bundle | Unbundle into best-of-breed | |
|---|---|---|
| Typical vendors | Finalsite, ParentSquare, Apptegy itself | A website vendor plus a comms platform |
| Contracts to manage | One | Two or three |
| Security reviews | One | One per vendor |
| In-house staffing needed | Minimal | Someone who owns the website |
| Price transparency | Bundles are quote-only | Comms side can be published |
| Renewal leverage | Low — all eggs, one basket | Higher — renegotiate one at a time |
| Consequence of a bad renewal | Website, app and comms all move at once | One component moves |
| Best fit | Small districts, no web staff, one-throat-to-choke | Districts with a technology team and a renewal problem |
Kastr only exists on the right-hand path, and only for the communications component. We do not build websites or district apps and have no plans to.
What the bundle is actually buying you
Bundled district platforms are not a con, and the reflexive best-of-breed argument underrates them. What you are buying is not software; it is the absence of a job. Somebody has to own a district website — accessibility compliance, content that goes stale, a principal who wants a photo carousel, ADA remediation when a complaint arrives. In a district with no communications staff and a two-person technology team, paying a vendor to own that is straightforwardly cheaper than the alternative.
The cost is concentration. When website, app and communications sit with one supplier, your renewal is a single conversation in which the vendor knows that saying no means replacing three systems in one summer. That is the structural reason bundle renewals escalate, and it has nothing to do with the vendor being unpleasant.
The question to ask yourself before shortlisting anything: if this renewal came back thirty per cent higher, what would you actually do? If the honest answer is "pay it, we cannot move three systems", you are not in a negotiation, and no amount of shopping changes that until you unbundle.
If you unbundle, do it in this order
The failure mode of unbundling is a gap: a period with no public website, or worse, no notification channel. Sequence removes it.
- Communications first, website second. Comms migration is bounded and testable; a website migration is a content project with a long tail. Doing comms first also gives you a working channel to announce the website change on.
- Register 10DLC before anything else. Brand and campaign registration takes two to six weeks and gates every SMS you will send. Start it the day you decide, not the day you cut over.
- Run both comms platforms for one term. Send the same low-stakes message on each and compare who was reached. That single exercise finds more data problems than any audit.
- Do the website in summer, with a content freeze. Never mid-term. Decide what is not migrating before you start, because half of any district site has not been touched in four years.
- Keep the mobile app decision until last. Districts frequently discover, once comms is working properly, that the app was solving a notification problem rather than an app problem.
Yes, you can split a bundle. Districts assume a bundled vendor will not sell one component; frequently they will, because keeping the website is better for them than losing everything. Ask what the website costs on its own before assuming the choice is all or nothing.
The consolidation risk worth writing into a contract
This category consolidates continuously. ParentSquare acquired Remind in November 2023. PowerSchool acquired SchoolMessenger. A district whose website, app and communications all sit with one supplier has concentrated its exposure to whatever that supplier's next corporate event happens to be.
Three clauses to ask for from any vendor on either path, and none of them are unusual:
- A written maximum annual increase. As a number. Ours is §3.2: fixed for 36 months, then the lesser of CPI-U or five per cent.
- Export as a contract right. Ours is §7.1 — complete, machine-readable, on demand, without notice or fee. Precisely today: we run it for you on request, there is no self-serve button, and we would rather write that sentence than a better-sounding one.
- A change-of-control exit right. Ours is §11.2 — if we are acquired or materially change our data terms, you may leave within 90 days with an export and a prorated refund, no penalty.
On the comms component specifically, our rate is $3.50 per student per year under 5,000 students, $3.25 to 14,999 and $3.00 above — one tier, every feature included. And the disqualifiers, since they are shorter to read than to discover: no single sign-on, no attachments, no push notifications, no website CMS, no district app, no SOC 2 audit, and no customers, because we are pre-launch.
Questions people actually ask
What are the alternatives to Apptegy for districts?
Either another bundle — Finalsite and ParentSquare are the usual comparisons — or unbundling into a website vendor plus a communications platform. Bloomz and Kastr publish prices on the communications side; the bundled vendors are quote-only.
Should we keep our website and comms with one vendor?
If your district has no in-house web capability and a small technology team, probably yes; the bundle is buying you a job nobody wants to own. If your renewal has escalated for several years running, the concentration is what removed your leverage, and unbundling is how you get it back.
Can we leave Apptegy for comms but keep our website with them?
Often, yes. Ask what the website costs as a standalone line. A vendor generally prefers keeping part of the contract to losing all of it, and districts routinely assume the answer is no without asking.
Which alternative is best for a district with no in-house web staff?
A bundle, almost certainly. Website ownership is real work — accessibility compliance, content maintenance, remediation — and if nobody in the district will own it, a vendor should. In that case buy the bundle deliberately and negotiate a written cap on annual increases, because that is the exposure you are accepting.
One price. Every feature. Locked for three years.
$3.50 per student per year under 5,000 students. No tiers, no add-on modules, no per-message fees. Published on the site because you should not have to book a call to learn a price.