A legacy tool, replaced. With AI where it pays.
- Sprint
- Platform Sprint
- Price
- $50,000 to $100,000
- Time
- 8 to 12 weeks
- Fix window
- 90 days
Example builds.
- An operations portal replacing spreadsheets and a legacy app
- A customer portal with document processing and self-service
- One internal dashboard with an AI assistant over your data
- A back-office app with a few AI workflows, no migration
What is included.
- Included: A multi-tenant data model with roles and permissions
- Included: Migration from the existing system, with a rehearsal before cutover
- Included: Three or more AI workflows with evaluation sets
- Included: An audit log of every change
- Included: An API for your other systems
- Included: A load test and an external security review report
- Included: Deployment on your cloud account, monitoring, runbook
- Included: A 90-day fix window
How the AI part works.
- What the model does
- Only the parts that pay. Reading documents, classifying tickets, drafting replies, finding the record someone is looking for. The rest of the tool is plain, fast software.
- What it must not do
- Change data without a trace. Every AI-assisted change is logged with what the model suggested and who approved it.
- How we test it
- Each workflow has its own evaluation set from your historical data. Migration is rehearsed on a copy, with a reconciliation report, before the real cutover.
- What it costs to run
- Cloud and model usage on your accounts, measured per workflow. For most internal tools it is a small fraction of the licence it replaces.
What this looks like
The tool your team runs on was built years ago, or it is a set of spreadsheets and a licence you pay for but do not like. It holds real data and real habits. Replacing it is a project nobody wants to start because nobody can say what it will cost.
A Platform Sprint starts with a five-day Scoping Review that ends with a price and a date. Then the sprint builds the new system next to the old one, migrates the data in a rehearsal first, and cuts over in one planned step.
How the sprint goes
Scoping Review: five days, a written scope, an architecture sketch, a risk list, a fixed quote.
Weeks one to four: data model, roles, the first workflows, the first migration rehearsal. Weekly demos. Week-one exit applies.
Weeks five to eight: the remaining workflows, the API, the audit log, a load test, the security review.
Weeks nine to twelve, where needed: final migration rehearsal, cutover, monitoring, runbook, training for your team.
What you get at the end
One system in production on your own cloud account, your data in it with a reconciliation report, a security review report you can show auditors, and 90 days of fixes.
Questions we get on the first call.
Why does a Platform Sprint need a paid Scoping Review first?
Because migration and integrations hide surprises. The Scoping Review is five days, $1,500, and ends with a written scope, an architecture sketch, a risk list and a fixed quote. It is credited against the sprint if you sign within 30 days.
Can we keep using the old system during the build?
Yes. The new system is built alongside, migration is rehearsed on a copy, and the cutover is one planned step with a rollback.
Who is on the team?
The founder leads and reviews everything. A part-time second engineer, a designer for the key screens, and an external security reviewer join for the parts that need them. Agents do the volume.
What about our data and compliance?
The system runs on your cloud account in the region you choose. We build GDPR-aware and HIPAA-aware systems; the certification itself stays with you, and we say that plainly.
Book a call, or send the brief. A written price in three working days.
No NDA needed for the call. We sign one within 24 hours if you want it.