Maintenance and Support: Care Plans You Can Take or Leave
After handover, you choose how your software is looked after: run it yourself, hand it to a third party, or take a Globaprom care plan. This page explains what a plan covers, what it costs, and why declining one is a normal, unpenalized choice.
Never Required, by Design
A care plan is never a condition of working with us. You own the code, the repository, the documentation, and the infrastructure accounts, so the software keeps running whether or not we are involved after launch.
We built it this way deliberately. A vendor whose maintenance revenue depends on being irreplaceable has the wrong incentive during the build. Ours is the opposite: the better the handover, the easier you are to leave, and the more likely you are to come back for the next project.
What a Care Plan Covers
One fixed monthly fee covers the operational load of running your software:
- Hosting and operations. We run the infrastructure, or manage it inside your accounts.
- Monitoring and alerts. Problems get noticed by us before they get noticed by your users.
- Dependency updates and security patches. The audits from the build continue on a schedule, so the codebase does not quietly age.
- Backups. Taken, stored, and tested, so restore day is boring.
- Small changes. Text updates, minor tweaks, a new field on a form: handled within the plan rather than quoted separately.
Care plans run €100–300 per month depending on the size of the system and the level of cover. The exact coverage and fee for your software are stated in writing before you choose, as step six of how we work describes. Plans are monthly and cancelable; nothing locks you in.
Running It Yourself Is a Real Option
Self-maintenance is not a theoretical right we mention for legal comfort. The handover is built for it: documentation written for your next developer, a deliberately mainstream stack, and deployment configuration that lives in your repository, not in our heads. If you have an IT team, they can operate the software from day one.
Many clients take a plan for the first months and decide with real usage data. Others never take one. Both paths are normal exits from our process, and neither changes the price of the build, which stays fixed under our fixed-price packages either way.
What a Care Plan Is Not
Two boundaries keep the plan honest:
- Fixes to our own mistakes are free, plan or no plan. If the software fails the written scope and acceptance criteria you approved, correcting it is part of the build, never a maintenance charge.
- New features are new scope. A plan covers small changes; a new module or workflow gets its own written quote, so the monthly fee never becomes a blank check in either direction.
Decide After Launch, Not Before
You do not need to choose a maintenance model to start a project. Book the scoping call, get the fixed quote, and pick your operating model when the software is real.