Post-Go-Live: The First 90 Days After a System Launch
Go-live is not the finish line. The first 90 days decide whether a new system becomes how the company works or a costly parallel to the old spreadsheets. A phase-by-phase plan.

Go-live day often ends with relief and a team lunch. The vendor’s consultants leave the following week, the project manager returns to their old job, and the users are left with a system they have used for real for only a few days. Within a month, someone in finance is quietly keeping the old spreadsheet “just in case,” and the warehouse has found a workaround for a screen that is too slow.
The first 90 days after go-live decide whether the new system becomes the way the company works. They deserve a plan as deliberate as the implementation itself.
Days 1 to 14: hypercare
The first two weeks, often called hypercare, are a period of intensive support that keeps the business running while people find their feet. Problems will surface that testing did not catch, because real volume and real exceptions behave differently from test scripts.
- Keep the experts close. Agree in the contract that vendor consultants or your implementation partner stay on site or on immediate call for at least the first two weeks. Key users from each department should have reduced normal workloads so they can help colleagues.
- One place to report issues. A simple log, shared list or ticketing tool where every issue is recorded with who raised it, what happened, the business impact and who owns the fix. WhatsApp groups are fine for alerts but useless as a record.
- A daily stand-up. Fifteen minutes each morning with key users, IT and the vendor. Review new issues, agree priorities and confirm what was fixed yesterday.
- Watch the critical flows. Can you take orders, ship goods, invoice customers, receive stock and pay staff? Check each one daily. Anything blocking these gets fixed first.
Days 15 to 45: stabilise
Once the business runs without daily emergencies, the focus shifts to accuracy and habits. This is where the quieter problems appear: data that drifts, reports that do not match, and users who have stopped using part of the system.
Run the first month-end close on the new system with extra care. Reconcile stock between the system and a physical count of high-value items, reconcile receivables and payables against the old balances carried over, and compare key reports with what managers expect to see. Every unexplained difference is either a data problem, a configuration problem or a training problem, and each needs a different fix.
This is also the time to find and close workarounds. Ask each team directly: what are you still doing outside the system? Every parallel spreadsheet is a sign that something in the system or the process does not fit, and it will eventually create a conflicting version of the truth.
Days 46 to 90: improve and hand over
By the second month the system should feel routine. The remaining work is about getting value from it and making sure support does not depend on the people who built it.
Review the deferred items. Most projects push some reports, automations and nice-to-have features past go-live. Re-prioritise them based on what users now know, since some will no longer matter and new needs will have appeared. Deliver the most valuable few, one at a time.
Set up long-term support. Decide who handles first-line questions internally, which issues go to the vendor, what the agreed response times are, and how configuration changes are requested, tested and approved. Document the configuration and key settings so that the knowledge is not held by one consultant.
Refresh training at this stage too. The go-live training was delivered before anyone had used the system for real, so much of it did not stick. Short sessions built around the questions in the issue log, and around the mistakes seen in the first month-end, land far better than a repeat of the original course. New joiners also need a proper induction on the system, not a quick tour from whoever sits next to them.
Finally, hold a short review with the steering group: what was promised, what was delivered, what is still open, and what the business has learned for the next phase.
Measures to track through the 90 days
| Measure | Why it matters | How often |
|---|---|---|
| Open issues by priority and age | Shows whether support is keeping up | Daily in hypercare, then weekly |
| Transactions entered in the system versus outside it | The clearest sign of real adoption | Weekly |
| Active users per module | Reveals teams that have drifted back to old habits | Weekly |
| Order-to-invoice and receipt-to-stock times | Confirms the core flows are not slower than before | Weekly |
| Reconciliation differences at month end | Tests data integrity | Monthly |
An illustrative scenario: a medical supplies distributor
A distributor of medical consumables in Amman is moving from an old accounting package and several spreadsheets to a new ERP (enterprise resource planning system) covering sales, purchasing, inventory with batch and expiry tracking, and finance. Go-live goes well. In week two, sales staff report that creating an order takes longer than before, because the new system asks for batch selection on every line.
The daily stand-up logs the issue as high priority because it affects every order. The fix is configuration, not training: the system is set to suggest the earliest-expiring batch automatically, with the option to override. Order entry time drops back. In week five, the month-end reconciliation shows stock value differences on a group of items. Investigation finds that opening balances for those items were migrated without their batch details. Finance and the warehouse correct them together, and the migration checklist for the next phase is updated.
By day 90, the old spreadsheets have been archived, the vendor’s support contract has clear response times, and two internal key users handle most questions. The steering group agrees the next priorities: a customer portal for order tracking and automated reorder alerts.
Protecting the investment after launch
An implementation is judged by what happens after the consultants leave. If your go-live date is set, add three things to the plan now: who stays on call for the first two weeks, the date of the first month-end reconciliation, and who owns support after day 90. Supporting organisations through go-live and the months after it is part of our Enterprise Systems service, with adoption and data quality measured as outcomes.



