Government & Public Sector
We publish our terms. Procurement notices.
Public-sector buyers evaluate software vendors on questions most firms answer vaguely: What exactly does the estimate include? What happens after delivery? How fast do you respond, in writing? Our answers are already published: a written estimate with stated assumptions, a 180-day defect warranty, and committed response times in business hours, because they're the same terms every client gets.
We've delivered for public-mission organizations including PIDC, Philadelphia's public-private economic development corporation. The work rewards the same habits government requires anyway: documentation as a deliverable, decisions that leave an audit trail, and systems designed for the decade, not the demo.
- Working vocabulary
- Section 508WCAG 2.1 AARFP / RFQ responseAudit-ready documentation
What keeps going wrong
The problems this sector actually brings us.
Vendors who can't survive procurement
RFP responses fall apart when a firm's actual terms are improvised per deal. Ours are standing policy (estimate guarantee, warranty, response times, Net 30), which makes the compliance matrix short and the reference checks boring.
Accessibility as a mandate, not a preference
Section 508 and WCAG conformance are contractual in public work. We build to WCAG AA as a baseline practice; it's in our healthcare and university work too, where the same mandates apply.
Systems that outlast administrations
Public systems change hands: between staff, between vendors, between administrations. Runbooks, knowledge transfer, and architecture a successor can pick up are line items in our estimates, not favors.
Clients in this sector
Government
Philadelphia Industrial Development Corp.
Working inside these constraints right now?
Tell us what you're up against. We'll respond within two business days. That's one of the terms.