When a checkout fails, a contact form stops sending, or a login breaks, and the person who built the site is gone, it’s hard to even know who to call. I take one clearly defined problem at a time and fix it inside a scheduled 48-hour window, for a flat $600 agreed in writing before you pay anything.
Before you send anything, check who I am: LinkedInPortfolioGitHub
The job is one production problem with a clear finish line. Typical examples:
Most of this work is on sites built with React, Next.js, or Node, but the first question is always the symptom. If you don’t know what your site runs on, send the problem anyway and I’ll work it out from there.
Use the form at the bottom of this page: what happens now, what should happen, what the site runs on if you know it, and your deadline. It takes about five minutes, and no phone call is needed.
I reply with one of three things: a firm $600 scope, a $200 diagnostic proposal if the cause is unknown, or a no with my reasons. You pay nothing at this stage.
A $360 deposit and access to the code reserve a scheduled 48-hour window. The remaining $240 is due only when you accept the work.
You receive tested code, help getting it live, and a short written summary of what was wrong and what changed. Every job includes one revision and a seven-day regression warranty.
| Rescue sprintOne problem, up to eight engineering hours inside a scheduled 48-hour window. Includes deployment help, a written summary, one revision, and the warranty. | $600 |
|---|---|
| DiagnosticA written diagnosis and a recommended fix, for when nobody knows what is wrong yet. Prepaid, and useful even if someone else ends up doing the repair. | $200 |
| Extended sprintThe same terms with a higher hour cap, agreed in writing up front, for problems clearly bigger than eight hours. | $900 |
Payment comes in two parts: a $360 deposit (60%) after you approve the written scope, and the $240 balance when you accept the work. The price does not change after you approve the scope.
I’m Anthony Hayward, a full-time software engineer. I take a small number of these fixed-price jobs outside my working hours, on my own equipment and accounts. The written scope and the hour cap are what make that reliable: each job is small, defined, and scheduled, or I don’t take it.
There are no testimonials or client logos on this page. Look me up directly instead:
No. Each job runs in a scheduled window with a hard eight-hour cap, and I hold very few windows at a time. If I can’t give a problem proper attention, I decline it. It also means you’re hiring someone who builds and ships software every working day.
You hear that in the written decision, before any money moves. From there the options are a $200 diagnostic to pin down the cause, an extended sprint agreed in writing, or stopping there with my reasons in hand.
I only accept problems I’m confident fit inside the cap, and the written decision exists to filter out the rest. If the diagnosis changes once I’m in the code, work stops: you get my findings in writing and decide the next step. Hours never quietly pile up.
Money moves only after you have a written scope in hand: the symptom, the definition of done, the price, and the exclusions. The $360 deposit books the window, and the $240 balance is due when you accept the work, after you’ve seen the fix running. If you’d rather take a smaller first step, start with the $200 diagnostic.
No. Everything arrives in writing: your form, my scope, the delivery summary. Written answers are easier to check later and easier to hold me to. Replies usually come in the evening. If you’d rather talk one through, ask.
Usually, yes. If you control the website’s code, hosting, and the accounts it depends on, or can regain control of them, I can work without the person who built it. List whatever access you still have in the form, and my reply will say whether it’s enough.
Describe it in plain words: what happens now, what should happen, and when you need it fixed. You’ll get a written answer with a firm $600 scope, a $200 diagnostic proposal, or a no with reasons.
No call, no follow-up sequence, no mailing list. If you’d rather skip the form, write to anthonyhayward1000@gmail.com.