How Local Government Boards Can Vet Software Vendors and Custom Builds
Weighing COTS platforms against custom software builds in local government procurement.

Local government boards and development authorities review complicated proposals for physical infrastructure all the time. Board members know how to read engineering bids, look over site plans, and evaluate construction contracts.

Software is different. When a board needs an application to manage grants, track commercial site inventory, or run local economic programs, judging the technical proposals gets hard. [1] Tech jargon, vague vendor promises, and shifting scopes often end in budget overruns or systems nobody can use.

Software proposals deserve the same rigor as a building project. Below is how I’d vet software vendors, decide between custom development and a commercial platform, and protect public dollars along the way. It ties right into the discoverability and content-structure issues I wrote about in What your web developer won’t tell you: AI Aggregation and Zero-Click Searches.

Commercial Off-the-Shelf vs. Custom Development

Before you put out a solicitation or look at bids, figure out whether you need custom software at all.

  • Commercial Off-the-Shelf (COTS): Pre-built software platforms that already have users.
    • Pros: Lower upfront costs, fast deployment, vendor-managed maintenance, routine security updates.
    • Cons: Recurring subscription fees, limited customization, rigid workflows, vendor lock-in.
  • Custom Development: Software built to match your own workflows or local mandates.
    • Pros: Fits exact statutory requirements, full ownership of the platform, no per-user license fees.
    • Cons: Higher upfront costs, longer delivery timeline, ongoing maintenance responsibilities.

The Rule of Thumb: If a process works the same way in most cities (meeting agendas or basic accounting, for example), buy existing software. If a process is driven by unique local ordinances, specialized grant structures, or local economic workflows, custom development is often the better long-term investment. [2]

Buy COTS When… Build Custom When…
Workflows are standardized across municipalities Processes are governed by unique local ordinances
Upfront budget is limited Long-term capital is available
Immediate deployment is required Specific workflow automation is non-negotiable

Vetting Vendor Capabilities Beyond the Pitch

Sales demos show off polished prototypes and feature lists. A board has to look past the demo and check what the vendor can actually deliver and support:

  1. Source Code Ownership: Require full ownership of the custom code and intellectual property. If the vendor goes out of business, the board still needs access to the source code and databases.
  2. Technical Stack Longevity: Make sure the software runs on modern, mainstream open-source languages and libraries. Stay away from proprietary, obscure stacks that make it impossible to hire developers later.
  3. Security and Public Records Compliance: Require written protocols for data encryption (in transit and at rest), user access controls, and compliance with open records retention laws. [3]

Structuring Public Software Contracts

Time-and-materials software contracts tend to grow in scope and blow past their budgets. Boards should build technology contracts around fixed-phase milestones. Real estate redevelopment agreements work the same way, especially when the public side needs risk divided up plainly and obligations tied to milestones:

  • Discovery and Architecture Phase: Pay a fixed fee for a detailed system spec, user interface wireframes, and database architecture before you commit to full build costs.
  • Milestone-Based Payments: Tie each payment to software components you can test and see working.
  • Service Level Agreements (SLAs): Spell out response times for critical bugs, uptime guarantees, and fixed hourly rates for enhancements after launch.

Frequently Asked Questions

Buy commercial off-the-shelf software when the workflow is the same from one city to the next. Build custom when local ordinances, grant structures, or specialized workflows call for a system made to fit.

At minimum, ownership of the source code, a durable mainstream technical stack, and written security and public records compliance requirements.

Use fixed-phase contracts that start with a discovery and architecture phase, pay on milestones tied to working software, and include service level agreements for support and uptime.


References

  1. Georgia Department of Community Affairs. (2022). Technology Implementation and Vendor Management for Municipalities. State of Georgia. https://dca.georgia.gov
  2. Georgia Municipal Association. (2023). Digital Infrastructure Procurement Guidelines for Local Officials. Georgia Municipal Association. https://www.gmanet.com/
  3. General Assembly of Georgia. (1982). Georgia Open Records Act. Official Code of Georgia Annotated (O.C.G.A.) \S 50-18-70 et seq.. https://law.justia.com/codes/georgia/2022/title-50/chapter-18/article-4/section-50-18-70/