One eligible web-app bug · £149
One broken part of your app, fixed and checked.
Tell us about one reproducible fault in an existing Rails or React/Node app. We repair it, check the affected flow with you in a safe test environment and hand back a working change.
Describe what a user does, what happens and what should happen. Do not send passwords, customer data or repo invites yet.
Scope and limits
A clear defect with a checkable result.
For an existing Rails or React/Node app, we need one reproducible flow, an expected result, access to a safe test setup and someone who controls the code and deployment. We agree the check and a company-controlled handoff before taking source. If you do not know the framework, start with the broken screen.
Included: reproduce one issue, make a bounded code or configuration change, add a regression check where feasible, get a separate review and send you a written walk-through of the result. Not included: multiple unrelated bugs, new features, payment or security incidents, data recovery, emergency support or a guarantee against future faults. A third-party outage or larger rewrite needs a different scope.
The work
Check the flow, not just the patch.
Describe and agree.
Tell us the steps to reproduce and what changed. We agree the acceptance check and safe code handoff without sharing secrets or real customer data.
Repair and review.
AI agents reproduce and fix the issue in an isolated workspace; a separate reviewer checks the patch. We run relevant tests and show the affected flow on a safe setup, stating what we could not test.
Accept and deploy safely.
We send you the test result in writing and check it with you by email. Your developer can deploy; if you have none, any temporary live access and checks need a separate, informed agreement before work. If there is no safe way to verify and hand over the fix, we do not take this as a fixed-price job.
Before you decide
No emergency promise.
We confirm timing after seeing the fault; this is not a same-day SLA. A passing test-environment flow is not proof that every live interaction works. Your team retains the keys and decides when to deploy.
Start without access.
Email about one web-app bug with steps to reproduce and the expected result. We reply within one working day.