01
Which issues stay inside the launch scope.
App support after launch
Fixes, updates and the next release after launch. Support is a separate agreement, and you keep the code.
Launch ends a build. Support is the next agreement: what we watch, what counts as a fix, and which new features wait for their own plan. A focused MVP from A$15,000 + GST is the build, not a year of maintenance.
After release we can stay on the product: fixes, dependency updates and the next planned slice. The code remains yours.
Because the repository is yours, you can continue with us or move the code. Either way the handover is the repository, the notes and the accesses. We do not lock the product to a private platform.
What we agree before support starts
02
How many hours or which queue the next period includes.
03
Which ideas are new work, not support.
How support is priced
The build and the support agreement are separate. A focused MVP from A$15,000 + GST is the first version, not a year of maintenance.
What changes the support scope
We write the queue before it starts: which fixes stay with the launch, how updates are handled, and which ideas are new work.
- What the launch agreement already covers
- Store and dependency updates
- How quickly fixes need a response
- New features, which are estimated on their own
When support starts
Support can start at handover. The code, notes and accesses are already yours, whether or not you continue with us.
- Handover lists the repository and accesses
- The support scope is written separately
- A larger next release gets its own estimate
How support starts
- 01
Handover
The launch leaves the code, notes and accesses with you.
- 02
Scope
We write what support includes and what is a new feature.
- 03
Queue
Fixes and small updates follow that written list.
- 04
Next release
Larger features get their own estimate.
Who this is for
- A product that already has a first release
- A team that wants the same people after launch
- A client who must keep the code
- A roadmap that should not hide inside the launch price
What support can cover
- Fixes inside the agreed scope
- Updates when iOS, Android or dependencies move
- A next release from the postponed list
- The option to take the code elsewhere
What you keep
- The source code
- A note of postponed work
- Access to stores and servers
- A support scope written separately
Questions about support
Ownership, fixes and new work.
Is support included in the MVP price?
The starting price is the focused build. Ongoing monitoring, dependency updates and new features are a separate agreement.
Can another team take the code?
Yes. You own the repository. Handover is the code, the notes and the accesses.
Do you publish a monthly support price?
No. The queue depends on the product, so we name it in the estimate instead of a single public figure.
Where is the longer explanation?
The article on support after launch describes the split between the first release and the next plan.
Plan support before launch
Tell us what must keep working after release. We will separate warranty fixes from the next piece of work.
Contact page
