Ongoing Development & Support
After launch: maintenance, support, new features and integrations, from the people who built or took over your product and still look after it.
Launch is the start of a product's commercial life. Ongoing development and support is the engagement that follows: maintenance, fixes, new features, integrations and automation, delivered by the people who built the product or took it over, so nobody has to learn the codebase from scratch.
Who this is for
Businesses with software already in production: a product with paying customers and a wishlist that keeps growing, or an operational system the business relies on every day. It suits products we built and products we have taken over and stabilized.
What it covers
How it runs
A standing roadmap, reviewed together at a rhythm that suits the business. Work stays scoped and billed per milestone, so the product grows at the pace it earns.
Every change is documented in the repository, next to the code it describes. If you ever move the product to another team, the knowledge goes with it.
Proof
EvitaAmenda moved from rescue into exactly this kind of engagement. The system is in daily operational use, and we continue to develop it.
Read the EvitaAmenda case study
Questions we get asked
Can you support a product you did not build?
Yes. It starts with a takeover: we read the code, map what it does, put tests around the riskiest behavior and document what we find. Support begins once we understand the system well enough to be accountable for it.
Are we tied in?
No. The code, the accounts and the documentation stay in your company's name, so you can change supplier whenever you choose.
What client ownership means in practice
If your product is live and the wishlist keeps growing, this is the engagement built for it.