Every request for proposals asks the same headline question: what does it cost per year? Vendors answer with a license figure, procurement lines it up against the other bids, and the lowest defensible number tends to win. The problem is that the annual license is usually the smallest line in the real total, and it is the only one the RFP scored.
Total cost of ownership — TCO — is a discipline that came out of enterprise IT procurement in the late 1980s, when buyers realized the purchase price of a computer was a fraction of what they actually spent running it over its life. The same logic applies, almost exactly, to the software a clerk's office runs its meetings on. Procurement bodies like the Government Finance Officers Association and the National Association of State Procurement Officials have said the same thing for years: evaluate the cost over the full life of the contract, not the sticker on the first invoice.
This post is a line-by-line walk through the costs an agenda-and-minutes RFP tends to miss, why each one bites, and a worksheet you can bring to every demo. It is written for the person signing a multi-year contract on behalf of a town, county, school board, or special district — where a surprise line item is not a rounding error, it is a real hit to a budget that was set a year in advance.
First, define the number you are actually comparing
TCO for meeting software is the sum, over the full length of the contract you are about to sign, of four things:
- One-time costs to get live — implementation, migration, integration setup, initial training.
- Recurring costs that repeat every year — the license, plus anything metered or tiered.
- Contingent costs that depend on what happens — escalators, overages, change-order hours, mid-term repricing.
- Internal cost — the staff hours your own people spend, and the cost of getting out at the end.
A five-year contract quoted at "$6,000 a year" is not a $30,000 decision. Add a one-time implementation fee, a migration charge, a 5%-a-year escalator, and the staff time to run it, and the honest number can land 40–70% higher than the license total. The point of a TCO worksheet is not to assume the worst; it is to make every one of those lines visible and negotiated instead of discovered on invoice three.
The one-time costs that don't feel one-time
Implementation and onboarding fees
Enterprise government software almost always carries a separate, one-time implementation or "professional services" fee — configuration, setup, kickoff, and a go-live period. On a small contract this fee can rival or exceed a full year of license, and it is the line most likely to be quoted verbally and then formalized late. Ask for it in writing, ask what specifically it covers, and ask what happens to it if the go-live date slips (a real risk we covered in the CivicPlus vs. Granicus vs. Govably comparison, where multi-month rollouts are normal at the enterprise tier).
Migrating your archive
Your minutes and agendas are a legal record you are required to retain, and moving that archive into a new system is real work. Some vendors include a basic import; many bill migration as a project, price it by volume, or simply hand you a spreadsheet template and tell you to do it yourself. The cost hides in two places: what the vendor charges, and the staff hours if they don't. Get the answer before you sign, not after — and see our guide to migrating off Word and email for what a clean data move actually involves.
Integration and SSO setup
Single sign-on, a website embed, a payments or records-management connection — each of these is sometimes a one-time setup fee, sometimes a recurring add-on, and sometimes both. "Integrates with your website" on a slide is not the same as "included." Make the vendor name the integration, the price, and whether it is one-time or annual.
Training — and retraining
Initial training may be bundled or billed. The line RFPs almost never account for is retraining: clerk turnover is a structural reality in local government, and every departure means someone new has to learn the system. A tool that takes a week of vendor-led sessions to onboard has a recurring human cost every time your office changes hands. A tool a new clerk can pick up on their own does not.
The recurring costs that scale on you
Per-seat and per-user fees
Some platforms price per named user. That looks cheap when it is just the clerk, and it climbs the moment department heads submit items, board members edit agendas, or a deputy needs access. Ask the pricing question the way it will actually play out: what does this cost when eight people touch the system, not one? Unlimited-user pricing removes the incentive to ration access to your own software.
Per-module charges
Bundled suites price by module. The agenda tool is one line; the citizen portal, the minutes add-on, the streaming component, the records piece are others. The demo shows the whole suite working together; the quote may only include the pieces you named. Confirm which modules are in the number, and which are extra.
Storage, bandwidth, and streaming overages
If a platform hosts your video or large packets, there is usually a storage or bandwidth allotment — and an overage rate past it. Meeting video is heavy and it accumulates forever, because you can't delete a public record on a retention schedule you don't control. A price that is comfortable in year one can drift as the archive grows. Ask for the allotment, the overage rate, and what a typical body your size actually consumes.
Support tiers
Standard support is included; the responsive kind is sometimes a premium tier. For an office where a broken agenda the night before a meeting is a genuine emergency, "priority support" as a paid upsell is a cost, not a nicety. Find out what the included tier's response time actually is.
The contingent costs — the ones that depend on time and luck
Annual price escalators
Multi-year government software contracts frequently include an escalation clause — a fixed percentage or a CPI-linked bump each year. A 5% annual escalator compounds to more than a 27% higher price by year five than year one. This clause is negotiable and often overlooked. Read it, cap it, and model the last year of the term, not the first.
Auto-renewal and the evergreen trap
Many contracts renew automatically unless you cancel inside a notice window — sometimes 60 or 90 days before term end. Miss the window and you are locked into another term, frequently at the escalated rate. Put the notice deadline on a calendar the day you sign, and know whether the renewal reprices.
Mid-term repricing after an acquisition
The govtech market is consolidating, and the vendor you signed with may not be the vendor you renew with. Acquisitions routinely bring product sunsets, forced migrations, and repricing at renewal. That is its own subject — we wrote what happens when your govtech vendor gets acquired — but for TCO purposes, treat renewal price as a range, not a fixed line, and ask what protections the contract gives you if ownership changes.
Change-order and professional-services hours
Need a new agenda template, a workflow tweak, a report format? On some platforms you file a request and wait; on others it is billable professional-services time. Ask how routine configuration changes are handled and priced. A tool you can configure yourself has a change cost of zero.
The two lines almost every RFP forgets
Your own staff's time
This is usually the single largest number in a real TCO, and it is the one that never appears on a vendor quote because the vendor doesn't pay it — you do. If a system takes twelve hours to turn a recording into published minutes, that is twelve hours of a salaried employee, every meeting, for the life of the contract. Software that cuts the same job to two hours has a labor value that dwarfs the license difference between two vendors. When you evaluate, time the actual workflow end to end, because that clock is the biggest line on the sheet. (It is also why speaker identification and clean transcription matter so much — the fastest path from audio to an approved record is the one that gets who said what and what passed right the first time; see why "who said it" is the hard part and why AI drafts still need a human approver.)
The cost of leaving
Every contract ends. When it does, can you get your minutes, agendas, packets, and video out in a usable, open format — and does that export cost anything? "Exit cost" is the most-ignored TCO line and the one with the sharpest teeth, because a vendor that makes leaving expensive or technically painful has priced your next decision, not just this one. Before you sign, ask three questions in writing: in what format is our data returned, how long do we have to retrieve it after termination, and is there a fee. Your archive is a public record you are legally obligated to keep; the contract should guarantee you can walk away with it.
An illustrative five-year picture
Here is a deliberately simple, hypothetical comparison — not a quote from any vendor, just a shape to show how the lines stack. Two tools with the same $6,000 headline license, priced out honestly over five years:
| Line item | "Cheaper" enterprise quote | Focused, transparent quote |
|---|---|---|
| Annual license (headline) | $6,000 | $6,000 |
| One-time implementation | $7,500 | $0 (self-serve onboarding) |
| Archive migration | $3,000 | Included |
| Per-seat add-ons (8 users) | +$1,400/yr | $0 (unlimited users) |
| Annual escalator | 5%/yr, compounding | Flat |
| Exit / data return | Fee, format on request | Free open-format export |
| Approx. 5-year total (license side) | ~$51,000 | ~$30,000 |
Two "$6,000" tools; a $20,000 gap over the term — before a single hour of staff time is counted. The numbers are invented, but the structure is exactly what plays out in real evaluations. The headline license told you almost nothing.
The TCO worksheet to bring to every demo
Copy this into a spreadsheet, fill one column per vendor, and make each of them answer every row in writing. The rows they hesitate on are the ones that matter.
| Line item | The question to ask the vendor |
|---|---|
| Implementation fee | Is there a one-time setup or professional-services fee? What does it cover, and what if go-live slips? |
| Data migration | Do you migrate our existing archive? Is it included, priced by volume, or do we do it ourselves? |
| User pricing | Is this per user? What is the cost when eight people need access, not one? |
| Modules | Which modules are in this quote? What is extra — portal, minutes, streaming, records? |
| Storage / streaming | What is the storage or bandwidth allotment and the overage rate as the archive grows? |
| Escalator | Is there an annual price increase? Fixed or CPI? Can we cap it? Model year five. |
| Renewal terms | Does it auto-renew? What is the cancellation notice window? Does the renewal reprice? |
| Change orders | Are template or workflow changes self-serve, or billable professional-services hours? |
| Support | What is the included support response time? Is faster support a paid tier? |
| Staff time | (Measure this yourself.) How many hours does one meeting's full workflow take in this tool? |
| Exit cost | On termination, in what format is our data returned, how long do we have, and is there a fee? |
Where transparent pricing changes the math
Most of the costs above are hidden because the base price is hidden. When a vendor publishes pricing by entity size, several of these lines collapse: there is nothing to discover on implementation because there is no implementation fee, nothing to model on per-seat because users are unlimited, and nothing to fear at renewal because the number is on a public page. That is how Govably prices — published rates by entity size, no per-user fees, no per-module charges, and an export you can take with you — and we say so because it is directly relevant to a post about TCO, not to end it with a pitch.
The broader point holds regardless of who you pick: a transparent price is not just cheaper on average, it is legible. It lets a clerk build a five-year budget that survives contact with the third invoice. An opaque price puts the burden of discovery on you, at the exact moment — mid-contract — when you have the least leverage to do anything about it.
Bottom line
The RFP question — "what does it cost per year?" — is the wrong question, or at least a badly incomplete one. The right question is: what will this cost us, all in, over the full term we are about to commit to, including the hours our own people spend and the price of ever leaving? Run every vendor through the worksheet, make them answer in writing, and model the last year of the contract, not the first. The tool that wins on the headline number and the tool that wins on total cost are frequently not the same tool — and only one of those is the decision you actually have to live with.
If you want to see what a transparent, all-in number looks like for a government your size, request a 15-minute demo and we will price your actual workflow, line by line — including the ones most quotes leave off.
Related reading: How to choose meeting software · When your govtech vendor gets acquired · Moving off Word and email