New: CentriCall AI voice agents that answer, qualify, and book around the clock
Choosing a Partner7 min read

How to choose a government software development company: accessibility, security, and the contract

Government buyers are judged on the process as much as the product. Here is what separates a custom government software development company that delivers from one that wins the bid, and the checks to make before you sign.

The short version
  • Government software is judged against a written specification, an accessibility standard, and a records schedule, usually before anyone asks whether it is good. Choose a company that builds to those gates from sprint one.
  • Accessibility is a contract condition, not a polish step. Ask for evidence produced continuously, not a conformance report written the week before delivery.
  • The system of record usually outlives the project. Prefer a plan that puts a modern service layer in front of it over one that assumes it can be replaced.
  • Read the contract for what happens at the edges: change requests, acceptance, data ownership, and what you can do if you want to move to another vendor.

Buying custom software for a state agency, county, city, or public authority is different from buying it for a company. The money is public, so the process has to be defensible. The users are the general public, so accessibility is not optional. The records outlive the project, so the data model carries legal weight. And the requirements are usually fixed in a document before the first line of code is written.

A government software development company that has not worked inside those constraints will discover them at acceptance, which is the most expensive place to find them. This guide covers what to look for, what to ask, and what to put in the contract. It is written for program owners, IT leaders, and procurement officers, and for companies that sell into government and need a build partner.

What makes government software different

ConstraintWhat it means in practiceWhere it bites
Written requirementsScope is fixed in a solicitation or statement of work before the vendor is chosen.Change is a contract action, so ambiguity found late is costly for both sides.
AccessibilityWCAG 2.1 AA is the working standard for most public-facing services, and Section 508 applies to federal work.Retrofitting a finished interface costs several times what building to the standard would have.
Records and retentionRetention schedules, legal holds, and public records requests decide what the system must produce years later.Records treated as an export feature force a rebuild of the data layer.
Security frameworkNIST CSF or NIST 800-53 controls, and cloud authorization programs where they apply.Evidence has to be produced by the system, not assembled for an assessment.
Systems of recordAuthoritative data lives in a mainframe or case management system that will not be retired by this project.Plans that assume replacement stall when someone asks what happens to thirty years of records.
Peak load on policy datesEnrolment windows and filing deadlines set demand, not marketing.A service that works in testing can fail on the one day the public needs it.
Check current requirements for your jurisdiction. Rules, thresholds, and dates change, and counsel should confirm them.

Accessibility: ask for evidence, not assurances

Accessibility is where government projects most often fail late. In the United States, the Department of Justice's 2024 rule under Title II of the ADA sets WCAG 2.1 AA as the technical standard for state and local government web content and mobile apps, with compliance dates phased by population, and federal agencies work to Section 508. Confirm the dates and scope that apply to you; the point for a buyer is that conformance is a legal and procurement condition.

What to ask a vendor:

  • How is accessibility tested during development? Automated checks in the pipeline catch some issues; manual testing with a screen reader and keyboard-only navigation catches the rest.
  • Who writes the accessibility conformance report, and from what evidence? A report assembled from continuous testing is credible; one written the week before submission is not.
  • Do designers and developers get accessibility training, and is it part of the definition of done?
  • What is the process when an audit finds a defect after launch, and is remediation inside the contract?

Security, hosting, and the framework you are held to

Government buyers rarely ask for security in the abstract. They ask for conformance to a framework: NIST CSF for a risk-based programme, NIST 800-53 for control-level detail, and for cloud services a recognized authorization programme such as FedRAMP federally or GovRAMP (formerly StateRAMP) at state level. Some data adds its own rules, such as CJIS for criminal justice information or IRS Publication 1075 for federal tax information.

A vendor does not need to hold every authorization. It needs to tell you plainly which controls it can evidence, which depend on your hosting environment, and which would need new work. Be wary of any company that answers every framework question with "yes". The useful answer is specific: here is the control, here is how the system evidences it, and here is the part that sits with you.

Records, retention, and data ownership

A public system has to answer a records request years after it was built. That is a data modelling problem. Ask how the vendor designs for retention schedules, legal hold, audit history, and export in open formats, and make sure the contract says the agency owns its data and can take it elsewhere without a fee or a rewrite. Vendor lock-in in government is rarely about code; it is about data that cannot be extracted cleanly.

Integrating with the system you cannot replace

Most agencies have a core system, often a mainframe, a decades-old case management platform, or a vendor product, that holds the authoritative record. A credible plan keeps it and puts a modern service layer in front: new interfaces and workflows that read from and write to the system of record, with reconciliation between them that is monitored rather than assumed. Replacing the core is a separate, larger programme.

Ask the vendor how they would integrate with your specific platform, what they would do if its API is limited, and how they test against realistic data volumes. Our guide to legacy system modernization cost covers what drives that work, and modernizing without a big bang explains the incremental approach.

Procurement and contract: what to check

Procurement route varies: competitive RFP, cooperative purchasing contract, GSA schedule, or a small-purchase threshold. The route is set by your rules, but several contract terms are within your control and matter more than the headline price.

Contract terms to check before signing
  • Acceptance criteria are written, measurable, and tied to payment milestones.
  • The change-request process states how scope changes are priced and approved.
  • The agency owns the code or has a perpetual licence, and owns the data outright.
  • Source code, documentation, and runbooks are delivered, so another vendor can maintain the system.
  • Accessibility conformance is a stated acceptance condition with defined remediation.
  • Security and breach-notification obligations are explicit, with the framework named.
  • Warranty and support terms cover the period after go-live, with response times.
  • Exit and transition assistance is defined if the relationship ends.

Pricing model matters too. Fixed price gives budget certainty but only works when the specification is genuinely complete; time and materials fits discovery and uncertain scope. Our comparison of fixed price vs time and materials sets out when each fits, and a short, separately priced discovery phase often resolves the uncertainty before the fixed-price commitment.

Questions to ask a government software development company

1

Show how you evidence accessibility and security

Ask to see the artefacts from a past project: test reports, pipeline checks, and the structure of the conformance documentation. You are looking for evidence produced as a by-product of the work.

2

Walk us through a failed acceptance

Every delivery team has had a milestone rejected. How they describe it, and what they changed, tells you more than the success stories.

3

Who will actually do the work?

Confirm the named team, their experience in public sector delivery, and whether any work is subcontracted, since many agencies restrict that or require approval.

4

How do you handle a requirement we got wrong?

Specifications written before design are often wrong in places. A good vendor has a clear, fair process for surfacing and pricing that rather than hiding it until acceptance.

5

What can we do without you?

Ask what the agency would need to maintain or move the system independently: documentation, deployment automation, and data export. The answer reveals whether the vendor expects to be kept.

Build, buy, or modernize

Custom development is not always the answer. A configurable commercial product is often faster and cheaper when your process matches what it was built for. Custom government software development earns its cost where the process is specific to your statute or program, where the product would need heavy customization, or where you need to integrate several systems into one citizen-facing service. Our guide to build vs buy software gives the decision framework.

Custom government software development from Centricone

Centricone Technologies builds software for state and local agencies and for companies delivering into government. We build to WCAG 2.1 AA as a release gate, design records and retention into the data model, integrate with the systems of record that already exist, and deliver against written acceptance criteria. See our public sector software development page for the approach, or talk to our team to discuss your program. After launch, our maintenance and support service keeps the system running.

Working through this on a real project?

Tell us what you are building. You will get a scoped estimate and an architecture you own, not a capability deck.

Common questions

It designs, builds, integrates, and supports software for government agencies: citizen-facing services, case and licensing systems, internal workflow tools, and integrations with existing systems of record. What distinguishes it from a general software company is experience with accessibility conformance, security frameworks, records and retention obligations, and delivery against fixed written requirements.
Look for evidence of public sector delivery, a clear approach to accessibility and security, a realistic plan for integrating with your existing systems, and contract terms that give you ownership of the code and data. Ask to see artefacts from past work and ask how they handled a rejected milestone. Weigh these above the headline price.
Yes. Federal agencies work to Section 508, and in the United States the Department of Justice's 2024 Title II rule sets WCAG 2.1 AA as the standard for state and local government web content and mobile apps, with phased compliance dates. Check the dates and scope that apply to your entity, and treat conformance as an acceptance condition in the contract.
Use a commercial product where your process matches what it does; it is usually faster and cheaper. Build custom where the process is specific to your statute or program, where a product would need heavy customization, or where several systems must be combined into one service. Many agencies end up with a product at the core and custom software around it.
Fixed price works when the specification is complete and stable, and it suits public budgeting. Time and materials suits discovery and uncertain scope. A common approach is a short, separately priced discovery phase, followed by a fixed-price build against requirements that have been tested rather than assumed.
It depends on scope, integration, and the approvals the project must pass, and procurement itself often takes longer than expected before any build starts. Plan against the approval calendar as well as the development schedule, and avoid any vendor that commits to a date before understanding the integration with your system of record.
Yes, and it should be negotiated explicitly. Agencies commonly own the data outright and either own the custom code or hold a perpetual licence, with source code, documentation, and deployment automation delivered so another vendor can maintain it. This is the main protection against lock-in.