Finalsite pricing: separating the website from the messages
Finalsite is a website company that also sends messages, which makes its pricing a web-platform lifecycle question rather than a per-student one. Districts consistently underestimate what a web platform costs over its real life, because the redesign is a capital event that arrives every few years and never appears in the annual comparison.
| Year | Typical event | Cost character | Usually in the comparison? | Effect on the annualised figure |
|---|---|---|---|---|
| 1 | Design, build, migration, training | Large one-time capital | Quoted, then forgotten | Dominates year one; must be amortised |
| 2 | Platform licence and support | Recurring | Yes | This is the number everyone quotes |
| 3 | Licence, plus first add-on module | Recurring, growing | Rarely | Add-ons compound the base |
| 4 | Licence with escalator applied | Recurring, escalating | Rarely | The escalation clause starts to bite |
| 5 | Refresh or partial redesign | One-time capital, again | Almost never | Second capital event; the one districts forget |
| 6 | Licence, plus accessibility remediation | One-time plus recurring | No | Frequently triggered by a complaint rather than planned |
| 7 | Licence with compounding escalator | Recurring | No | Year-one price is now historical |
| 8 | Full redesign or migration to a new vendor | Large one-time capital | No | Resets the cycle, and reveals the exit cost |
Two capital events in eight years is the normal pattern for a district website, and neither appears in a comparison built from annual licence figures. The messaging component, by contrast, is a straightforward recurring cost that behaves like every other per-student platform. That difference in cost shape is the reason the two components have to be separated before either can be compared with anything.
Isolating the communications line
Finalsite quotes are usually structured across three things: the CMS and hosting platform, the messaging product, and add-on modules with one-time design and implementation alongside. To get a number you can put beside a comms-only vendor:
- Ask for the messaging component priced standalone, as though you were buying nothing else. Vendors dislike this because the bundle discount is where the negotiation lives, but they can usually produce it, and the refusal tells you how much of your quote is cross-subsidised.
- Divide that figure by enrolment for a per-student rate.
- Add any metered usage. Voice minutes are the big one. Model your worst year rather than your average one, because the years you communicate most are the years something is going wrong.
- Check what messaging depends on. If the messaging product requires the CMS to function, or loses meaningful capability without it, the standalone figure is theoretical and you should note that in the evaluation.
The output is one number: implied communications cost per student per year. That is the only figure that belongs on the same line as any other comms platform's rate, ours included.
What drives a quote up, and what drives it down
Up. Number of school sites, each typically carrying its own configuration and content. Design complexity and how bespoke the build is. Content migration volume, particularly where an old site has thousands of pages nobody has audited. Add-on modules. Multilingual site requirements. Accessibility remediation of legacy content, which is frequently underscoped because nobody counts the PDFs. Bespoke integrations with the SIS or a portal.
Down. Taking a template rather than a bespoke design, which for most districts is the single largest available saving and costs surprisingly little in outcome. Reducing site count by consolidating school sites into one district site with school sections. Ruthlessly cutting content migration scope — most districts should migrate a fraction of what they have and archive the rest. Buying through a purchasing co-operative award. Timing the purchase against the vendor's fiscal year end, which is not cynicism, it is how enterprise software has always been bought.
One thing that does not move a web platform quote much: enrolment. A 2,000-student district and a 6,000-student district with the same number of school sites and the same design scope will be quoted similarly, which is why per-student normalisation flatters larger districts here and penalises small ones.
Deciding whether the website vendor should send your messages
This is the actual decision, and it is not primarily a cost decision.
The case for buying both from one vendor: content published once appears in both places, one support relationship, one renewal, and no argument about whose fault it is when an emergency notice does not appear on the homepage.
The case against: the two products have completely different lifecycles. A website is replaced every four to eight years on a capital cycle driven by design fashion, accessibility law and leadership change. A communications platform should be replaced when it stops working, which ought to be much less often. Tying them together means a website redesign becomes a communications migration, and that is a large amount of avoidable risk to accept for the sake of one renewal date.
The honest comparison with us. Kastr does not build a CMS and will not. If you need a district website, we are one of two vendors you would be buying rather than one. Our number is published so you can do the arithmetic without a call: $3.50 per student per year under 5,000 students, $3.25 to 14,999, $3.00 at 15,000 and above, one tier, everything included, fixed 36 months with year four capped at the lesser of CPI-U or 5 per cent. Set that against the implied per-student communications figure from your Finalsite quote, then decide whether the integration is worth the difference. Note also what we do not have: no single sign-on, no attachments or media, no push notifications, no SOC 2 and no district references.
Questions people actually ask
How much does Finalsite cost a school district?
Finalsite publishes no pricing and quotes are built from site count, design scope, content migration volume and module selection rather than from enrolment. Any figure without a source and a date is unverified. The honest route to a comparable number is a board packet from a district with a similar number of school sites, plus your own itemised quote.
Is Finalsite Messages priced separately from the website?
It is normally quoted as a component of a wider agreement rather than sold standalone. Ask explicitly for the messaging component priced as though you were buying nothing else; that gives you a figure you can divide by enrolment and compare with a comms-only platform. A refusal to price it standalone is itself useful information about how much of the quote is cross-subsidised.
What are typical Finalsite implementation costs?
Implementation on a web platform is a project fee covering design, build, content migration and training, and it varies enormously with site count and how bespoke the design is. Whatever your figure, amortise it across the contract term before comparing anything, and assume a second capital event around year four or five for a refresh, because that is the normal district pattern.
How does Finalsite pricing compare per student?
Poorly, as a comparison — web platform pricing tracks site count and design scope rather than enrolment, so per-student normalisation makes large districts look efficient and small ones look overcharged without either being true. Separate the messaging component out, normalise only that per student, and compare the website on its own terms against other CMS vendors.
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.