After go-live
The weeks after cutover are when untested paths, slow queries and month-end jobs show up. Here is what we watch, and the maintenance plans that take over once things settle.
Rehearsals can't cover everything. Real customers take paths nobody tested, real integrations send payloads nobody sampled, and a scheduled report that only runs at month-end hasn't run yet. The weeks after cutover are when a migration proves itself, and they deserve as much planning as the cutover did.
Slower cycles come next. Month-end close, renewals, annual-discount rules and regulatory or tax reports all exercise code that may have sat idle during testing. We keep a list of these from the assessment and watch each one the first time it runs.
This is also when to shut the old system down properly. Keep a read-only copy for as long as your records require, confirm nothing still calls it, and then cancel the hosting. Forgotten old servers are a common security problem: they stay online, unpatched, with real data on them.
Our Laravel maintenance plan is USD 99/month, invoiced in the customer's local currency. It includes backups every 2 hours to S3-compatible storage with tested restores, framework, package and PHP updates, routine security checks, server management, page-speed and uptime monitoring, and a change-request channel.
For WordPress and WooCommerce, the care plans are Premium USD 89/month or Enterprise USD 159/month, invoiced in the customer's local currency. No setup fee, no lock-in, cancel anytime. Unused edit minutes don't roll over.
We have looked after a high-volume Belgian WooCommerce store for three years. Over that time PHP went from 7.4 to the current release, plugins and theme were brought up to date, performance was improved, and the Microsoft Dynamics sync for orders and customers has been kept running, with backups every two hours and tested restores. It shows what we think maintenance should do: the system ends up newer than when we took it on, instead of merely staying up.
We can pick up systems we didn't move. We start by reading the code and checking the backups actually restore, then fix what is urgent and agree the routine. If the handover documentation is thin, writing it becomes part of the first few weeks.
Three years keeping a high-volume Belgian WooCommerce store up, fast and in sync with Microsoft Dynamics: PHP 7.4 to current, two-hourly backups to S3-compatible storage, monitoring, and every change request handled.
At least through one full business cycle, including month-end if the system touches accounting. Keep a read-only copy for as long as your record-keeping rules require, and take it offline from the public internet.
No. We monitor uptime and speed, respond to problems and take tested backups, but we don't offer an uptime guarantee or SLA figure on these plans.
Tell us what moved and what has gone wrong so far. We will read the code and check the backups before suggesting a plan.
We reply within one business day (IST).