Store Rescue — 30 days, fixed price

A rescue takes a neglected PrestaShop or WooCommerce store and makes it maintainable again. It ends with a store you can safely change, running on monitored infrastructure, with a rollback path and someone whose job is keeping it that way.

What's actually wrong underneath

Legacy server bloatYears of accumulated cruft, oversized processes, and misconfigured stacks quietly taxing every single request.
Unoptimized MySQLSlow queries, missing indexes, and table locking that hold up fine in testing and buckle the moment real traffic arrives.
Broken module upgradesPrestaShop and WooCommerce updates that take out checkout, payments, or an integration, with no rollback plan and no staging copy to have caught it.
Unhandled traffic spikesBlack Friday, a product launch, a viral moment — the day that should be your biggest of the year, engineered to stay up instead of falling over.

Scope, in delivery order

  1. Audit and baseline — code, database, server; guarantee baseline captured.
  2. PHP upgrade to 8.4 minimum.
  3. Platform upgrade — PrestaShop to 9.1, or WooCommerce brought current.
  4. Module triage — keep, replace, remove, or rewrite.
  5. Database work — indexes, slow queries, bloated tables.
  6. Front-end performance.
  7. Migration to managed infrastructure.
  8. Handover — staging environment, deploy process with rollback, backups, monitoring, written documentation. Repository access is yours from day one.

Timeline

Week 1Audit and baseline.
Weeks 2–3Upgrade and module work on staging.
Week 4Performance, security, load testing.
Week 5Cutover, verification against the guarantee, handover.

What I won't do

  • Quote before I've seen the code. A fixed price from a screenshot is a guess with your money inside it.
  • Rescue a store that should be rebuilt. If a rebuild is cheaper I'll tell you, and lose the bigger invoice.
  • Take on a store that can't reach the guarantee economically. You'll hear that at the review stage, before Stage 2 exists.
  • Rewrite abandoned third-party modules inside the fixed price. If a module blocks the upgrade and has no maintained replacement, that's a Stage 1 finding and a decision we make together — not a surprise.

The offer

Stage 1$750

Technical Review

Fixed price. 3 business days from receipt of access. Deliverable: written findings, ranked by business impact, plus the fixed quote for Stage 2. Credited in full against Stage 2 if the client proceeds.

Stage 2from $6,000

Store Rescue

Fixed price, quoted at the end of Stage 1. Never quoted before. 30 working days. 50% on start, 50% on delivery. Guarantee: if the acceptance criteria are not met, the second 50% is not invoiced.

Stage 3$1,500/month

Managed Engineering

Month to month. No contract. No notice period. Begins the day the rescue goes live.

The guarantee. On the three templates named in your Stage 1 report — home, top category, top product — measured with Lighthouse mobile via the PageSpeed Insights API from a US test location, median of three consecutive runs:

LCP under 2.5 seconds · CLS under 0.1 · Total Blocking Time under 200ms · Lighthouse Performance score of 85 or better.

Baseline captured before any change, using the same method. Third-party scripts added after handover — analytics, chat, pixels, review widgets, A/B tools — are excluded. Real-user field data from the Chrome User Experience Report is reported monthly once 28 days of data exist, but is not guaranteed, because we do not control your traffic mix or your visitors' devices.

The 30 working days begin when we have SFTP or SSH, database, admin, DNS, and repository access — not at signature. The clock pauses on any client-side blocker, confirmed in writing.

Book a call