Approach
How we work
Four stages. Each one is contracted on its own and ends in something you keep.
The four stages
-
Assessment
We review the systems in scope and talk to the people who run them. You get a written report: current state, options, what we would do first, and an estimate. Fixed price.
-
Pilot
One slice of the system, built on your data in your environment and checked against your system of record. Weeks, not months. You get working code and a revised estimate for the full build. Fixed price.
-
Build
The full system. Infrastructure as code, automated tests, monitoring, and documentation written as we go. Security and accessibility requirements go into the design at the start. Time and materials against a written estimate, invoiced monthly.
-
Handover
Runbooks, architecture documentation, and working sessions with the team taking over. The code has been in your repositories and your cloud accounts since week one, so there is no transfer step.
Why a pilot first
Long discovery phases produce estimates that are wrong in predictable ways. The problems that move a schedule, such as an undocumented field or an approval step nobody mentioned, show up when code first runs on real data. A pilot gets there in weeks.
What we need from you
- Access to the real data, or a faithful copy.
- One person who can settle questions of scope.
- The person who will own the system after handover, involved from the build stage.
- Early sight of the security review, accessibility standard, and procurement route.
- A named contact for environment access. It is usually the longest lead time.
Staffing and reporting
The people who scope a project are the people who deliver it. There is no sales team and no handoff after signature.
You get a written status note every week: what moved, what did not, and what is at risk. If a date is going to slip, you hear it when it becomes likely, in writing, with options.
Accessibility and security
Section 508, records retention, audit trails, and authorization documentation shape the architecture, so they go in at the start and the supporting documents are produced as we build.
This site is built the same way: static, no cookies, no third-party requests, one short script for motion, checked for heading structure and colour contrast on every build.
Federal · State & local · Utilities · Enterprise · Nonprofits
Together, we get the work filed.
Send a short note about what you are working on. We reply within two business days.