News
App support after launch
What launch includes
The 3-week engagement ends with a version people can use for the core scenario. Alongside it we leave a short note of what the next release should test, based on the features already postponed.
Issues that belong to the agreed scope stay with us. Monitoring, new features, and ongoing changes continue as a separate support format with its own capacity.
Support without losing the code
Because you own the code, after launch you can continue with Inu-apps or take the repository to another team. Handover is the same either way: repository, documentation, and accesses.
The first release exists to collect evidence. The next budget should follow what users actually did, and support is how that next step is staffed.
Questions about this topic
Do you support the app after launch?
Yes. Warranty items inside the agreed scope stay with us. Monitoring, fixes beyond that scope, and new features continue under a separate support agreement.
Can support start right after the MVP?
Yes. We can move from the 3-week MVP into an agreed support capacity, with the source code remaining yours.
Related reading
Want to discuss your project?
Describe the goal and the main user journey. We will reply with whether a 3-week MVP fits and what to prepare for an estimate.