Skip to content

Emergency website fix: when your site, shop or app is down right now.

We reply within 24 hours on working days. Within 2 working days of your report we find what is wrong and tell you what the fix costs.

Reply within 24 hours

on working days, to your report

Diagnosis within 2 working days

what is wrong, and what causes it

Then you decide

knowing the price of the fix, before anyone touches it

In writingAfter the diagnosis

The fix is priced as one sum in the proposal.

What is broken right now

  • Your own site greets you with a blank page this morning, and your ad spends all day sending people to it.

  • A customer fills the basket, gets an error at payment, and the order lands with a competitor.

  • The shop broke after an update, and nobody can say what changed.

  • Your contact form has sent nothing for days, and you only noticed because enquiries dried up.

Which one is your situation?

  • The site will not load

    A site or shop that is down: we find whether hosting, the domain, the certificate or the code is at fault.

  • Payment or the basket fails

    A checkout that stalls: we walk through a purchase and see whether the payment provider, a plugin or an update breaks it.

  • Something broke after an update

    A broken update: we find what changed, whether the earlier state can be restored, and what a lasting fix needs.

  • Spam goes out, forms go quiet

    Email and forms: we see why enquiries are not arriving, or why the site is sending mail nobody asked for.

How an emergency fix runs

Diagnosis first, before anyone touches unfamiliar code.

Nobody can responsibly change unfamiliar code within hours, which is why the diagnosis comes first. It ends with a written account of what is wrong and what the fix costs, and then you decide.

  1. You get in touch and describe the fault

    You tell us what is broken and since when, and who we can ask for access.

  2. 2 working days

    Diagnosis and a written price

    We find what causes the fault and put in writing what the fix is and what it costs. That price holds until the fix is done.

  3. A proposal for one sum

    From the diagnosis you get a proposal for one sum, with a deadline, and you decide whether to go ahead.

  4. The fix, handed back

    We fix it, check it live, and write down what we changed.

One report, from the reply to the repair quote

What was sent in, what we checked, the cause and the repair quote, on one sheet with timestamps.

Sample screen, made-up data
Emergency report · Sample Store

Card payments fail at checkout

Urgent · from the contact form

  1. ReportMonday 9:12
  2. First replyMonday 11:40
  3. Diagnosis and quoteTuesday 16:05

The report

What broke
Card payments show an error and no order is created.
Since when
Since Sunday evening, after the plugins were updated.
What you see
“Something went wrong, please try again” after pressing pay.

What we checked

  • CheckedTest purchase with a test cardThe error appears on every attempt.
  • CheckedThe payment provider's logThe payment request never reaches them.
  • CheckedVersion before and after the updateThe payment plugin's new version sends the request to the wrong address.

Repair quote

Cause
Sunday's update of the payment plugin.
Repair
Restore the earlier version, then fix the plugin's configuration for good.
Price
In the attached quote, as one sum.
repair-quote.pdfAwaiting your approval
ApproveI have a question

What the diagnosis contains

  • Where the fault is: which page, which step
  • What causes it, in plain language
  • What the fix needs, and what can wait
  • The price of the fix, as one sum
  • What access the fix needs
  • A quick fix, or the sign of something deeper

Companies we've built for

GlosterInternal AI content platform
Palm GroupSubscription chatbot service
HabibiWebsite and table booking
The GarageThe tuning workshop's website
Kék Padlizsán
D+D SolarMarketing site with a quote form
FawaLanding page

Who else you could call

When a site goes down, the host and the original developer are the first two calls, and they are often the faster ones.

What they look at

Brecon
The fault and its cause, and we put in writing what the fix costs.
Your host
The server, the domain and the certificate, not the code.
The original developer
Their own work, which they know best.
A freelancer by the hour
Whatever fits into the hours booked.

What happens to the fault

Brecon
Fixed for one sum, with the deadline in the proposal, and if we slip, the next payment waits.
Your host
If the server is at fault, they bring it back.
The original developer
If they are available, they fix it fastest.
A freelancer by the hour
They fix it by the hour, and the total shows up afterwards.

What you keep afterwards

Brecon
The code was yours before, and the source code, the accounts and the documentation stay with you.
Your host
The server log, if you ask.
The original developer
Whatever they write down, if they do.
A freelancer by the hour
The invoice, and whatever they write about the fix.

When they are the better choice

Brecon
When you do not know what causes the fault and want to know the cost first.
Your host
When the whole site is unreachable and your host’s own dashboard shows an error.
The original developer
When they are available and have time, because they know what they left where.
A freelancer by the hour
When the fault is known and it only needs one pair of hands.

Who an emergency fix fits, and who not

This fits you if

  • Your website, shop or app is down right now, or an important part of it is stuck.
  • The original developer cannot be reached, and you do not know where to look for the fault.
  • You want to know what is wrong and what it costs before anyone touches it.

We would point you elsewhere if

  • The system works but is fragile or half-built and needs taking over. That is software rescue.
  • The site has to be back within the first hours. Your hosting provider or the original developer is faster at that, from an earlier backup. Send us the report in the meantime, and the diagnosis is already under way.

If the system works but is fragile or half-built, software rescue is the right fit.

How we work

An emergency fix from diagnosis to live

  • We find what causes the fault and how much it touches
  • A fixed price for the fix, as one sum, and the decision is yours
  • We work in your accounts as invited users, and the access stays with you
  • After the fix we write down what we changed

In writing

After the diagnosis

The fix is priced as one sum in the proposal.

What causes the fault, and how much of the system does it touch? The diagnosis answers that, and the price is set from there.

Request a diagnosis

What happens after the fix

After an urgent fix the cause of the fault stays the weakest point, so we write down what caused it and what would stop it coming back.

If it runs deeper

A separate proposal, your call

If the fix shows that the whole system needs putting right, you get a separate proposal for that.

If you want it

Monthly maintenance

Updates, fixes, extensions, in a separate proposal.

If something breaks

You write, we answer

A first reply within 24 hours on working days, to every enquiry.

What people ask when something is broken

Before the diagnosis we make no promise on that. First we have to see what causes the fault; after the diagnosis you get a price, and the proposal states the deadline for the fix.

The price list says after the diagnosis: until we have seen what causes the fault, any number would be a guess. The diagnosis ends with the price of the fix as one sum, in the proposal.

Full price list, every service

The address, a short note on what is broken and since when, and if you have it, a way to reach whoever built the site. We ask for access for the diagnosis, read-only where we can.

Yes, that is what the diagnosis is for: we look at what they left behind and write down what can be fixed quickly. If it turns out the whole system needs taking over, that is software rescue, and we quote it separately.

You do, as you always have. For the fix we work as invited users in your accounts, and at the end the source code, the accounts and the documentation are with you.

The diagnosis records what caused it, and if the fix shows the problem runs deeper, we tell you what a lasting repair would take. At handover you can also ask for a monthly maintenance proposal.

Tell us what is broken

The address, what is wrong, since when, and who built the site are enough to start the diagnosis.

We reply within 24 hours on working days, and the diagnosis is ready within 2 working days. We send no newsletter.