What happens after launch.
Launch isn't the end of the engineering relationship. We stay available for bug fixes, security updates, performance work and new features, on your terms.
- Billing
- Per scope, fixed price
- Standing fee
- None
- Fixes
- Root cause, not patches
- Reporting
- Every change written up
Support is not a retainer.
We don't lock clients into monthly retainers just to get help with their own system. Post-launch work is scoped and priced like the original project: per scope, per milestone, fixed price.
You pay for work that gets done. There is no standing fee for the chance you might need us.
The full scope of post-launch work.
Bug fixes
Issues found after launch are traced to the root cause, not just patched at the symptom, so the fix holds.
- Reproducible test case before and after
- Logged in the project changelog
Security updates
Dependencies age and vulnerabilities get disclosed. We watch advisories for your stack and patch on a schedule, or urgently when it matters.
- Dependency vulnerability monitoring
- Compatibility tested before upgrading
Performance work
Systems that launched fast can slow as data grows. We find the bottleneck and fix it.
- Query profiling and indexing
- Bundle and loading analysis
New features
Requirements change after launch. New features use the same fixed-scope process as the original build.
- Scoped and priced per feature
- Full IP transfer on completion
Infrastructure and scaling
Capacity planned before you hit the limit, rather than emergency fixes after.
- Database and server scaling
- CDN and caching tuning
Handover to your team
If you hire in-house engineers, we hand over properly: documented, walked through and runnable.
- Architecture documentation
- Runbooks and deployment guide
Need help with a system already live?
Tell us what it is, what's wrong and what you need. We'll assess it and come back with a clear, fixed-scope quote.
- Written scope
- Within 24 hours
- Pricing
- Fixed per milestone
- Ownership
- 100% of code and IP