You signed a contract with a software vendor. A year or two later, you get a letter: the company has been acquired. A new logo appears in the header of your support emails. Then renewal comes around.
This is a normal part of the software landscape — acquisitions and consolidation happen across the whole industry, not just in govtech. It isn't inherently good or bad. But it does mean the contract you sign today may be administered by a different owner tomorrow, so it's worth understanding what to look for up front.
Consolidation Is Common in GovTech
Government software has characteristics that tend to attract investment and consolidation: long-tenured customers, predictable recurring revenue, and a fragmented market of many small vendors serving many small governments. Over the past decade, a lot of local-government software has been brought together under larger platforms through acquisition.
This is well documented in the govtech trade press, and it isn't a knock on any one company — building scale through acquisition is a legitimate business model, and large platforms can offer real breadth. The practical point for a buyer is simpler: ownership and pricing structures can change over the life of a multi-year contract, so the time to understand the terms is before you sign.
What Can Change Over a Contract's Life
Whoever owns the company, software vendors are under ongoing pressure to grow revenue. For customers on long contracts, that can show up in a few predictable ways. None of these are universal, and none are unique to any single vendor — they're just things worth checking for:
Renewal prices can increase
The path of least resistance for any software company with long-tenured government customers is raising renewal prices. Governments face real switching costs — data migration, retraining staff, re-drafting SOPs, going back through procurement — so many absorb an increase rather than go through another selection process. Knowing your renewal terms ahead of time keeps you in control of that decision.
Products can get bundled
Platforms that offer many products sometimes structure pricing so you buy a bundle to get the one tool you need. A 2025 commentary in Federal News Network described the pattern: "Agencies are forced to buy a huge bundle of software to get the one product they actually need." The author — Ryan Triplette, Executive Director of the Coalition for Fair Software Licensing — noted that some software contracts are written in ways that "lock in government customers and thwart free and fair competition for technology contracts." It's worth confirming you can buy just what you need.
Auto-renewal terms vary widely
Auto-renewal windows, cancellation notice periods, and escalation clauses differ a lot from vendor to vendor and contract to contract. These terms are often easy to miss on a first read. Ask for them in plain language before you sign.
Support models can shift
Support staffing and structure can change over time — a named account rep one year, a general support queue the next. This isn't universal, but it's worth asking how support is delivered and whether that's contractually guaranteed.
A 2023 study found that Microsoft and Oracle received 25–30% of government software sales over the prior decade through less than fully competitive procurement.
A 5% increase in competitive procurement could save taxpayers up to $750 million per year. Source: FedScoop / NetChoice study, January 2023.
The Legislative Response
The vendor lock-in problem in government software has gotten serious enough that legislators have started addressing it directly. Six states — Ohio, Colorado, Missouri, Illinois, New Hampshire, and Indiana — have enacted fair software licensing legislation. Ohio passed its law specifically to curtail vendor lock-in and increase agency flexibility in switching providers.
At the federal level, the SAMOSA Act is advancing in Congress, with projected savings in the hundreds of millions annually if it passes and is enforced.
These aren't fringe concerns. They reflect a systemic problem that procurement officers at all levels of government are starting to formalize into policy.
What to Look for in Any Government Software Contract
Whether you're evaluating a new vendor or renewing with your current one, these are the contract terms that matter most:
- Auto-renewal notice window. How many days before renewal do you need to provide notice of non-renewal? 90 days is common, but some contracts use 120 or 180 days — long enough that it's easy to miss the window if you're not watching for it.
- Price escalation clauses. Does the contract allow the vendor to raise prices at renewal without renegotiation? By how much? CPI-linked increases are common and reasonable. Open-ended escalation clauses are not.
- Data portability. If you leave, can you export your full data — all agendas, minutes, vote records, and attachments — in a standard format? What does that process cost, and how long does it take?
- Change of control provisions. What happens to your contract if the vendor is acquired? Do you have termination rights if the acquirer materially changes pricing or terms?
- Bundling requirements. Are you required to purchase other products to maintain access to the one you actually need? Are there pricing penalties for unbundling?
- Support SLAs. Are response times contractually guaranteed? What happens if the vendor misses them?
Most of these terms are negotiable before you sign. They are much harder to change at renewal, after you're already embedded in the product.
The Question Behind the Question
When a clerk asks "how much does this software cost?" the real question is: what will it cost in year three, after we've built our entire workflow around it and switching means going back through procurement?
That's a question about how a vendor is set up to treat its customers over time, not just their price list today. It's a fair thing to ask any vendor — large or small, however they're owned — and the good ones will answer it plainly.
This is why questions about ownership and long-term pricing are starting to appear in government software RFPs. It's not a philosophical preference — it's a sensible procurement risk factor to document.
Where Govably stands.
We publish transparent pricing and design our contracts to be easy to understand and easy to leave. When we make pricing decisions, the question is whether it's fair to the governments we serve.
The Practical Takeaway
If you're currently under a contract you're happy with, you're not in a bad position — most of these contracts are reasonable and the software works. But at renewal, read the escalation clause. Check the auto-renewal window on your calendar. Ask what your data export looks like before you need it. And if a renewal quote comes back well above last year, know that you have options — the switching cost, while real, is not as high as it was five years ago.
If you're evaluating a new platform, ask the vendor who owns them and what happens to your pricing if that changes. Ask to see the auto-renewal and escalation terms before the demo ends. These are reasonable questions for any vendor, and the ones worth working with will answer them clearly.
The goal isn't to avoid any particular company — it's to sign a contract you understand, with terms you can live with for its full length.
Sources: Federal News Network — "The sneaky contracts draining government budgets" (Nov. 2025) · FedScoop — "Major government tech contractors use monopolistic vendor-lock to drive revenue" (Jan. 2023)