Skip to content

What each engagement includes, and what it costs

Every engagement has a defined scope, a published starting price, and a stated timeline. Your agency can evaluate cost and fit from this page, before contacting anyone.

The schedule of engagements

Engagements are listed in the order agencies typically take them. Each stands alone, and none requires another. Every engagement produces working assets your team continues to use after the work ends.

Prices are in US dollars. Each engagement has its own page listing what moves the price above its starting point, what your team uses afterward, what we need from your agency, and the third-party services the work depends on. A written scope fixes the price before your agency commits. After that, the price changes only through the documented process below.

To see where your agency stands before purchasing anything, the readiness assessment is free, takes about 20 minutes, and runs entirely in your browser.

What happens when scope changes

Scope changes on nearly every project. We manage changes through a documented approval process, so your agency sees the cost of a change before any work happens.

  1. The change is documented

    Anything outside the written scope is raised as a change request, in writing, as soon as we identify it.

  2. The change is priced

    You receive the cost and the schedule impact in writing before any work on the change starts.

  3. Your agency decides

    You can approve, defer, or decline the change. Declining does not affect the rest of the engagement.

  4. No work proceeds without approval

    No change is built or billed without your written approval.

What happens after a build

Your agency owns the deliverables, the source code, and the data throughout the engagement, and the source code sits in your repository from the first commit. When the build is complete, you choose how the system runs, and you can change that choice later.

There is no exit fee. Your agency can move between these options at any time, and the transition work is scoped and priced in advance.

  • Self-host, with transition support

    A one-time engagement. We hand over the system, the infrastructure code, and the runbook, then work with your team until it is deployed in your environment.

  • Self-host, with an ongoing agreement

    Your team operates the system. We remain available for patches, dependency upgrades, and incident support under an ongoing agreement.

  • Managed, in your cloud tenancy

    We operate the system for you, by default inside your agency’s own cloud account, so the environment, the data, and the audit logs remain under your control.

Buying this work, and how we stay independent

How to buy

We contract directly with your agency, and our fixed-scope engagements are sized with small-purchase thresholds in mind. We complete vendor registration, tax documentation, insurance certificates, and accessibility documentation ourselves, without adding work for your team. The procurement page lists exactly what we hold and what we do not.

Government procurement

Our independence rules

A firm that writes requirements and also builds systems has a potential conflict of interest, and we govern it in writing. Our assessments are releasable to every bidder, we do not bid on builds we specified, and the free assessment creates no advantage in a later procurement. The full rules are published with our methodology.

Our approach and independence rules

The safe first step

The readiness assessment is free, takes about 20 minutes, and returns a scored report you keep. It creates no obligation, no call, and no follow-up.