What this engagement addresses
- The public meets your court on a phone, at night, and the current site or portal was built for the institution.
- A workflow your office depends on lives in a spreadsheet, because the case management system never covered it.
- Two systems do not exchange data, so a person retypes the record from one screen into another.
- Custom software burned this agency before: an application nobody documented, on a stack nobody chose, that became yours when the consultants left.
Scope, price, and deliverables
We design and build websites, portals, applications, and integrations under a written scope, with source code in your repository from the first commit.
A written scope fixes the price before your agency commits to anything. After that, the price changes only through the published change process.
- Starting price
- From $60,000
- Timeline
- 8 to 20 weeks
- What moves it
- Scope, how many systems it integrates with, and whether the systems it must talk to expose an interface today.
What your team uses
- The system, accessible to WCAG 2.2 AA and tested with assistive technology
- Source code in your repository throughout, with integration documentation and an operations runbook
- Training for the staff who will maintain it
What documents the result
- The written scope and acceptance criteria the build was verified against
What we need from you
- A decision maker who can approve scope in one meeting
- Access to the systems it must integrate with
- Staff time for research and review, about 3 hours every two weeks
- Third-party services
- Builds usually depend on services such as hosting, email, messaging, identity, or payments. Your existing services are the starting point.
Your agency owns everything we deliver: the deliverables, the source code, and the data. What happens after a build and how to buy this work are published alongside the full schedule.
What changes for your agency
A service the public can finish
A task that used to need a phone call or a counter visit gets completed on a phone, and the counter and phone queues feel it.
A system your team can maintain
Documentation, training, and a technology stack chosen with your IT team, so the system does not become the next legacy problem.
No invoice surprises
Scope, acceptance criteria, and the change process are written before work starts, so the price moves only through a gate you control.
Exit designed in from the start
Source in your repository from the first commit, self-hosting always available, and any transition priced in advance.
The standards the work is held to
These are written into the engagement agreement, and each one can be checked during the work rather than taken on trust. The full posture is published under security and compliance.
- WCAG 2.2 AA accessibility
- Accessibility is an acceptance criterion, tested with assistive technology before handover.
- Plain language
- Public-facing content is written in plain language, and language access is treated as an acceptance criterion where your obligations require it.
- Your environment, your access controls
- Builds run in your environment against your access controls. Where criminal justice information (CJI) is involved, security addenda and personnel screening are completed before access.
- Your identity system
- Staff access runs through your single sign-on (SSO), with role-based access and audit logging appropriate to a court record.
Common questions
How do we know whether to buy or to build?
We recommend configuring or extending what you already own wherever a product fits, and we put that recommendation in writing before proposing a build. We build where nothing fits, and the recommendation is releasable to any bidder.
What technologies do you build on?
Mainstream, well-documented ones, chosen with your IT team and recorded in the scope. The deciding question is whether your staff can run the system in year three.
Can our IT team be involved during the build?
Yes, and the result is better when they are. The source is in your repository throughout, demonstrations run on a fixed schedule, and IT takes delivery at handover.
What does the starting price include?
A defined scope agreed in writing: typically one system with its integrations, accessibility testing, documentation, and training. The variables that move the price are published on this page.
What happens after launch?
You choose: self-host after a transition engagement, self-host with our support, or managed hosting in your own cloud tenancy. Moving between the options has no exit fee.
Get a written scope and a price
Send us your name and agency. We reply within one business day with a short set of clarifying questions, followed by a written scope and a fixed price for your agency. There is no obligation, and the scope document is yours to keep whether or not you proceed.
Prefer to talk first? Start a conversation