Post-Implementation Maintenance
Post-implementation maintenance covers configuration changes, new integrations, additional users and fixes to a system after it has gone live. GullySystem provides this as ongoing support, distinct from the original implementation project.
What Post-Implementation Maintenance Covers
Once a system is live, the requests do not stop — a new price slab, a new branch, a report someone in a review meeting asked for. This is the ongoing support that handles those requests after the original implementation project has closed, on whichever platform your business runs.
What Changes After a System Has Been Running
A Business Rule Changes
An electrical-components trading company's pricing structure changes after a GST slab revision or a new discount policy, and the configuration built at go-live no longer matches how the business actually prices its orders.
A New Branch or Team Joins
A location opens, or a department that was left out of the first phase is finally ready to come on board, and needs the same configuration and training the earlier rollout received.
Something That Worked at Go-Live Stops Working
A platform update, an integration partner's API change, or simple wear on a customisation causes something to break that was fine some months ago, and needs diagnosis rather than a rebuild.
What This Support Covers
- Configuration changes — new fields, workflows, approval rules or report layouts
- New integrations as you adopt further software
- Onboarding additional users, roles or branches
- Diagnosing and fixing issues that surface only under real, live use
- Periodic review of whether the configuration still matches how the business runs
How This Differs From the Implementation Project
The original implementation has a defined scope, phases and an acceptance point at the end. Maintenance has no fixed end date — it is a standing arrangement for the smaller, ongoing requests that come up after a system has been live for a while, sized to how much change your business generates rather than to a project plan.
What Shapes Maintenance Cost
- How frequently your configuration needs to change
- Whether requests are occasional fixes or a steady stream of new requirements
- Number of users, branches and integrations under support
- Response-time expectations for issues that affect daily operations
Frequently asked questions
Do we need a maintenance arrangement, or can we call you when something comes up?
Either works. Some businesses prefer a standing support arrangement for predictable response times; others call as issues arise. We size the arrangement, or the absence of one, to how often your configuration actually changes.
Will you support a system somebody else implemented?
In most cases, yes. We review the existing configuration and data first to understand what we are taking on, then support it going forward the same way we would a system we implemented ourselves.
What counts as a maintenance request versus a new project?
A configuration change, a new integration or onboarding a branch onto an existing setup is maintenance. A new module, a different platform, or a scope large enough to need its own phased plan is a new project — we will tell you which one a request actually is.
How quickly do you respond to an issue affecting daily operations?
Response expectations are agreed as part of the maintenance arrangement, since a billing outage and a cosmetic report request do not need the same turnaround. We do not promise a fixed time here without knowing your specific arrangement.
Can you add new branches or users to our existing system later?
Yes, onboarding an additional branch or user group onto a system that is already live is one of the most common maintenance requests we handle.
What do you need from us to keep the system maintained?
One point of contact who can raise requests and confirm changes, and advance notice of larger shifts — a new price structure, a new branch, a merger — so configuration changes do not become a scramble.
Tell us what you need.
Send a short brief and one of our engineers will come back to you — usually the same day.
- No obligation
- We reply the same working day
- Your details stay private