Raw Code Handoff
$6,000 sample USD
Estimated completion: 14–25 business days
Technical transfer for another team to finish. No formal test package, launch, training, or care.
Your services menu
Choose the work.
Know the result.
See what each service gives you, why it matters, and what remains if you decline it.
These are sample prices, not a quote.
Examples cover one small job tracker: one organization, two roles, four main screens, and no payments, offline work, or old-data import. The signed quote sets actual prices, scope, dates, reviews, and terms. Outside fees and recurring costs are separate.
Find your starting point
Start with your business need.
These are routes into the catalog, not new packages. Every service and delivery level remains available below.
Plan with a range
Illustrative estimates only—not a quote. Prices, work hours, and completion ranges are examples for planning purposes and may not reflect your project’s actual cost or delivery time. Final pricing, scope, and schedule are determined after reviewing your requirements and are confirmed in a written project quote. Estimated completion ranges are not guaranteed delivery dates.
Completion ranges include your planning allowance of four to five business days. Count it once per standalone service or whole delivery level.
Choose the finish line
Four delivery levels
Every total uses the same small sample app. Choose the result you need. Count each included service only once.
Working Pilot
$11,000 sample USD
Estimated completion: 24–43 business days
A test-space trial with sample data. No public launch, whole-release QA, dedicated security review, or care.
Launch Ready
$14,000 sample USD
Estimated completion: 30–53 business days
Pilot plus release QA, scoped security review, deployment, and operations notes. Launch depends on passed checks.
Guided Launch
$15,400 sample USD
Estimated completion: 33–59 business days
Launch Ready plus a five-task guide and two live training sessions. Ongoing care is separate.
How to read the estimates
Ranges begin after the agreed kickoff, required inputs, access, and prerequisite work are ready. Business days exclude weekends and agreed holidays. The model assumes one small project, roughly 3–6 focused work hours per day, prompt consolidated feedback, and the existing service limits. Hours describe effort; ranges also allow for coordination, review, and dependencies. Waiting for client materials, third-party approval, or an independent assessor can extend the schedule. These are industry-informed planning inferences, not measured industry averages or our historical delivery times.
Add four business days to the low estimate and five to the high estimate once per standalone purchase or whole delivery level. Package ranges account for shared preparation and overlapping documentation/review. Do not add the buffered service ranges together or add another allowance to a displayed range. Extra services need a combined schedule based on dependencies.
For monthly services, the displayed range is estimated activation time after kickoff. Support and planning continue on the agreed monthly cycle; this is not a completion promise for all monthly work or a response-time guarantee. Existing monthly hours and prices are unchanged.
Research and estimate basis
Published comparisons inform the model. Each catalog range is an inference for the stated scope, not a universal industry standard.
- thoughtbot: Rapid prototyping and design sprints
Describes one- to two-week design sprints and a prototype sometimes made in one day. A scope comparator, not a benchmark for every catalog service.
- Nielsen Norman Group: Usability Testing 101
A simple prepared usability study can use three days for planning, sessions, and analysis. Distinct from feature testing; used only to account for separate preparation and review phases.
- Atlassian: Project estimation methods
Supports comparable-scope estimation and accounting for uncertainty and dependencies. It supplies no universal duration for these services.
- GOV.UK Service Manual: Discovery phase
Larger government-service discoveries often take four to eight weeks. This is deliberately not copied onto the catalog's two-talk, single-workflow discovery.
Catalog release 2026-09-17. The downloadable guides use the same ranges.
When the idea changes
Approve the change before the work
Describe the request
Write what changes and why. Check the effect on design, code, tests, guides, and launch.
Review the full price and dates
List the work, exclusions, agreed credits, revised total, and date impact. Decide approve, decline, swap, or defer.
Record written approval
Keep the approved scope and named decision maker. A new idea is not permission to start work.
A sample text-alert change
Assessment 1 hour + design 1 + build 5 + tests 2 + guide and deployment 1 = 10 hours. The sample change price is $1,000. A $14,000 project becomes $15,000. Outside message fees are separate.
Do not add S08 again for the same integration. Credit assessment already paid when it is part of the approved total.
Put your choices in writing
Choose a level or individual services. Name owners for anything declined or deferred. Some work must still be completed before the software can be used as planned.