You are probably paying for five communication tools. Here is how to find out.
The tools are rarely bought by one person. A mass-notification contract from the safety office, a newsletter tool the communications team expensed, a teacher-messaging app three buildings adopted independently, and a survey subscription nobody remembers approving.
| Function | Typically bought by | Also present in | Overlap risk |
|---|---|---|---|
| Mass SMS and voice notification | Safety or operations office | The main comms platform; the SIS's own notification module | High — often three systems can text the same family |
| Email newsletter | Communications team, on a card | The comms platform's own newsletter feature | High |
| Teacher-to-family messaging | Buildings, independently | The district platform; the LMS | High — and the hardest politically |
| Website alert banner | Web vendor | Nothing else, usually | Low — but must be updated by the same person |
| Robocall / voice broadcast | Legacy contract nobody reviews | The comms platform's voice channel | High — the most common orphan renewal |
| Translation | Family engagement or ELL office | Built into the comms platform | Medium — human translation is still needed for statutory notices |
| Surveys and forms | Whoever needed one first | The comms platform, the SIS, the LMS | Medium — consolidation often loses a genuine capability |
The audit, which takes a morning
Two lists, cross-referenced. Neither takes long and together they find things the finance system alone does not.
List one: what finance is paying for. Pull every accounts-payable line under $25,000 from the last eighteen months and read the vendor names. The threshold matters because anything above it went through a formal process somebody remembers; the sprawl lives below it, and specifically on purchasing cards and building activity accounts.
List two: what staff actually use. Ask every principal and every district office lead one question: "list every system you or your staff use to send anything to families." Not a survey with checkboxes — an open question, answered in a sentence. The gap between the two lists is where the discovery is: tools nobody pays for because a vendor's free tier absorbed them, and tools that are paid for and nobody uses.
Categories worth checking explicitly, because they are consistently forgotten: athletics communications, transport notifications, food service, special education, before and after-school care, PTA and booster tools, the emergency notification contract, and the survey tool.
The math, including what consolidation costs
Consolidation is usually right and it is not free. Model all three columns or the business case will be wrong in a way that surfaces six months later.
- Licence savings. The easy number, and the one that gets presented alone. Sum the retired contracts, net of any increase in the surviving platform's cost.
- Retraining and transition cost. Staff hours to migrate lists and learn a new tool, plus a term of reduced fluency. For a mid-size district, 80 to 150 hours per tool retired is a defensible estimate.
- Capability loss. The column everyone omits. When you retire the survey tool, you lose branching logic. When you retire the newsletter tool, you lose the template library somebody spent two years building. Write down what is lost, in specifics, and decide whether it matters — not whether it is replaceable in theory.
Consolidation almost always loses something. A business case that shows only savings has not looked hard enough, and it will be undermined by the first staff member who says "the old one could do X". Name the X in advance, in the paper, and the conversation is about a trade rather than about a mistake.
Three things not to consolidate
- Your emergency notification path, if it is genuinely independent. A district that routes safety notifications through the same system as its newsletter has a single point of failure on the day it matters most. If your emergency contract is with a separate vendor on separate infrastructure, that redundancy may be worth its cost — and it is a decision for your safety officer, not your finance office.
- Anything with a statutory notice requirement your platform cannot meet. Some notices have language, format or delivery-proof requirements set by state law. Verify before retiring the tool that currently produces them.
- Anything the surviving platform does not actually do. Obviously, and yet. In Kastr's case, that list is specific and public: no file attachments, no photo or video sharing, no push notifications, no district website CMS, no payments, no automated notices firing on their own, and audience targeting that resolves only specific people and everyone. If a tool you are considering retiring provides any of those, keep it, and do not let a consolidation narrative talk you out of a capability you use weekly.
What consolidating well actually buys you
Not primarily money, although the money is real. Three operational things:
One contact record per family. When five systems each hold their own copy of a phone number, four of them are wrong within a term and none of them knows it. A single record with a validation state and a consent state, updated in one place, is the difference between a district that can reach families and one that believes it can.
One audit trail. When somebody asks what the district told families about an incident, the answer should be one query rather than five exports and a reconciliation. In Kastr every send writes to a per-organisation hash-chained append-only log; the value of that is proportional to how much of your communication goes through it.
One cadence. Families experience your district as one sender regardless of your org chart. Five tools produce five uncoordinated streams, which is how a district trains its families to ignore it. Consolidation is the only intervention that makes a message calendar enforceable rather than aspirational.
The pricing consequence is worth stating because it is unusual in this category: Kastr is one tier with every feature included at $3.50, $3.25 or $3.00 per student depending on enrolment, so consolidating onto it does not trigger a tier upgrade. The most common frustration with consolidation elsewhere is discovering that the functions you are consolidating in are the ones priced a tier above where you started.
Questions people actually ask
How many communication tools does a typical district run?
Five to nine, once you count what buildings buy independently and what arrives on purchasing cards. The count is almost always higher than the district office believes, because the sprawl sits below the threshold that triggers a formal procurement and is therefore invisible to anyone reading only major contracts.
What do we lose by consolidating onto one platform?
Usually a specific capability in a specialised tool — survey branching logic, a template library, a niche integration — plus a term of staff fluency per tool retired. Name the losses explicitly in the business case. A consolidation paper that shows only savings will be undermined by the first person who says the old tool could do something the new one cannot.
How do we find shadow subscriptions paid at the building level?
Pull every accounts-payable line under $25,000 for the last eighteen months and read the vendor names, then separately ask each principal an open question about what they use to contact families. The gap between the two lists is the discovery. Purchasing cards and building activity accounts are where these live.
Which tools should stay separate?
An emergency notification path that is genuinely independent infrastructure, anything producing statutory notices your platform cannot meet the requirements for, and anything your surviving platform does not actually do. For Kastr that last category is specific: attachments, photo and video sharing, push notifications, website CMS, payments and automated notices that fire on their own.
Does consolidating reduce the number of messages families receive?
Only if you also set a cadence rule. Consolidation makes a message calendar enforceable by putting every sender in one system with visible history, but it does not enforce one by itself. Districts that consolidate without agreeing a cadence end up sending the same volume from one place instead of five, which is easier to administer and no better for families.
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.