Available for new work Remote - worldwide hello@wordpressfixe.com
wordpressfixe

Process

From “it's down” to “it's fixed”.

The same four steps on every job. No discovery phase that bills for three weeks, no invoice that arrives before the diagnosis does.

  1. 01

    Send the details

    5 minutes

    The URL, what you see, and what changed just before it broke. Access details come later, once we agree the job is a fit.

    • The URL, and whether the whole site or one page is affected
    • What changed in the days before it broke — update, plugin, host, DNS
    • Whether you can reach wp-admin, and whether a backup exists
  2. 02

    Diagnosis and a fixed scope

    Same business day

    I confirm the likely cause, then send the scope, timeframe and price in writing. No work starts, and no invoice appears, before you approve it.

    You get a written scope with three parts: the cause, the work, and the price. No work begins until you reply with a yes.

  3. 03

    Fix on a copy, then live

    1–3 days typical

    Where the host allows it, the fix is proved on a staging copy first. Live changes happen with a rollback point ready and a short maintenance window if needed.

    • Staging copy where the host allows it
    • A snapshot before any live change
    • A maintenance window only when the work needs one
  4. 04

    Verification and handover

    Same day as the fix

    Templates, forms and checkout tested. You get a written summary of what broke, what changed, and what to watch — plus a follow-up window on the same fault.

    Seven days of follow-up on a single fix. Thirty days of reinfection monitoring after malware work. Both are included, not sold again.

AccessWhat I need

Access, and how to limit it.

Temporary accounts, not your main passwords. Everything below can be revoked the day the work is verified.

WordPress admin
Needed for almost every job. A temporary administrator account is fine — create it the day we start.
SFTP or SSH
Needed when wp-admin is unreachable, for file-level diagnosis, or for server-side fixes.
Hosting panel
Only for server faults: PHP version, error logs, disk quota, SSL issuance, DNS records.
Staging environment
Where the host provides one, fixes are proved there first. Where it does not, a snapshot serves the same purpose.

LimitsWhere the line is

What I will not do.

Some requests are not repairs, and saying yes to them would make the site worse.

Install or distribute nulled code
Pirated plugins and themes are a common infection route. If one is in place, it gets replaced with a licensed equivalent or removed.
Edit a live database without a snapshot
No exceptions. The snapshot is taken before the change, not after something goes wrong.
Promise a ranking or a score
Technical work can be guaranteed. Search positions and PageSpeed numbers cannot, and a guarantee is a sales tactic rather than a result.
Hide a problem to close a ticket
If a fix is temporary, you are told it is temporary and what the durable option costs.

ContactCommunication

How updates work.

Email, in plain language

Progress notes without ticket-speak. If something needs a decision, you get the options rather than a question that assumes the answer.

One reply per business day

Minimum. Emergencies get updates more often. If I am blocked by the host or a third party, you hear that the same day, not at the deadline.

Bad news early

If the site cannot be saved, or the repair costs more than a rebuild, you hear it before the invoice — with the reasoning behind it.

Step one

Start with the symptom.

Five minutes of detail is usually enough for a useful first answer. No access details until we agree it is a fit.

Or email hello@wordpressfixe.com — first reply within 1 business day.