Skip to content

Care

Keep routine updates from becoming emergencies.

For a live PrestaShop or WordPress site, we plan updates, check backups and handle agreed small fixes. You get a regular point of contact and a clear boundary for larger work.

Write what you want watched Situations we already know

Included

What the pack is for

Updates, done slowly

Core, plugins, and modules. If a bump should wait, you hear why before it goes on.

Backups and a restore check

Backups with a documented restore check, so recovery is more than an untested button.

Small fixes

Bugs and template tweaks that fit the hours. A large feature does not hide inside them.

A place to send the incident

When the shop misbehaves, it enters the same pack. Priority stays inside the hours we agreed.

How we approach the work

From first review to handover

  1. 1

    You send the URL and what you want watched

    Tell us which site needs attention and roughly how many small tasks come up in a typical month. We can discuss a care format after that.

  2. 2

    We agree hours or a task pack

    What is inside. What becomes its own scope. PrestaShop and WordPress both fit. Hosting does not.

  3. 3

    Updates go through a checklist

    You hear if something should wait. Updates follow an agreed checklist, with risky changes scheduled deliberately.

  4. 4

    Small fixes stay in the pack

    A bigger idea is quoted as its own stage. You see the line before it starts.

Common situations

Issues that often share a cause

  • The shop works, and nobody wants to touch the update button.
  • A freelancer used to do the small things, and then disappeared.
  • Backups exist. Nobody knows if they restore.
  • A module warning has been ignored for months.
  • You want one person who already knows the shop, not a fresh introduction every ticket.

Scope boundaries

What is not in the pack

  • A large feature. That is its own scope.
  • A redesign from nothing.
  • A round-the-clock desk or an enterprise response promise.
  • Hosting sold as a product.

If you want to hand over routine updates

Send the URL and the updates you want covered. We will discuss a suitable scope after an initial review.

Write about upkeep

A practical question

“Do you need the keys to everything?”

We need a way in to update: an admin user, or staging. We do not need your personal mailbox. We say what we touched. If you would rather not share production yet, staging is enough for the first look.

A useful first message

Start with the key details

The URL, and what you want someone else to watch. We reply with what we need to see, and what would sit outside a care pack.

Go to contact See situations