Support and evolution after launch
Monitoring, maintenance and continuous improvement with the same team that built the product. Between USD 600 and 2,500 per month depending on committed hours and response time. A product that ships and is never maintained decays on its own, through dependencies that expire and errors nobody looks at.
What it costs
USD 600 to 2,500 per month.
How many hours a month are committed and what response time you need when something breaks.
What's included
- Monitoring and alerts, so we find out before your users do.
- Bug fixes within the agreed response time.
- Dependency updates and security patches, the first thing to be abandoned and the most expensive thing to neglect.
- Small improvements within the month’s hours, without opening a project for every tweak.
- A monthly report of what was done and where the hours went.
- A direct channel to someone who knows the code, not a ticket form.
When this is NOT what you need
- This is not a pool of hours for building a new product. If you want a version 2, that is development and is quoted separately.
- If your product has no users yet, you probably do not need this yet.
How we work
Discovery
We understand the problem, define scope and risks, and hand you a clickable prototype.
Design and architecture
Interface, data model and integrations defined before the first line of code.
Build
Weekly deliveries with a demo. First usable version from week two.
Launch and support
Production release, monitoring and continuous improvement with the same team.
What backs this up
We keep our own products running in production, so the cost of not doing this is one we pay first.
Frequently asked questions
Is there a minimum term?
No. It is monthly and cancellable with a month’s notice. Tying a client into a long contract is a way of not having to earn the renewal.
What response time do you offer?
It depends on the plan and is agreed in writing before starting. It is one of the two things that move the price, so it is not left vague.
Can you maintain something you did not build?
Yes, after a code review that is charged separately. Without that review we cannot commit to response times on a system we do not know.
What happens to hours I do not use?
They expire at the end of the month, and we say so plainly rather than in small print. If they are left over every month, the right move is to drop you to a smaller plan, and we will be the ones to suggest it.
Does this fit what you need?
Write to us with two lines about the problem. We reply within 48 hours with a first assessment, no strings attached.
Email contact@neongate.co