Find the broken parts first. Fix them in 48 hours.
Start with a read-only $49 preflight of one public site, or book the $300 repair sprint for a tested patch and plain-English delivery report.
No redesign pitch. No retainer. No production access until the work is agreed.
Existing websites only
Written scope before payment
Customer-controlled deployment
No credentials in public issues
A repair pass, not an open-ended rebuild.
The sprint is intentionally narrow. That keeps the price fixed and makes the two-day delivery window realistic.
Good fit
- Mobile layout and visible UI breakage
- Forms, calls to action, and broken interaction paths
- Basic accessibility and keyboard fixes
- Metadata, social previews, and obvious SEO gaps
- Performance regressions that fit the existing stack
- A tested patch or pull request and before/after report
Outside this sprint
- A full redesign or brand exercise
- A new backend, app, or content migration
- Paid third-party services or hosting changes
- Production access before the scope is agreed
Four steps, with the risky parts kept in your hands.
Access is limited to what the repair needs. You approve the scope, merge, and production deployment.
Show the problem
Send the public URL, stack, and the one or two outcomes that matter most. Never post credentials in the request.
Choose report or repair
You receive a written scope, exclusions, delivery time, and BTC invoice amount for the $49 preflight or $300 repair sprint.
Inspect or repair
The preflight checks public pages without credentials or changes. The sprint repairs agreed defects in an isolated branch.
Review the evidence
You get the patch, checks run, before/after notes, and one focused revision. You control the merge and deployment.
Start with a $49 public-site preflight.
Within one working day, receive a prioritized report covering up to three agreed public pages: mobile layout, visible interaction paths, accessibility heuristics, metadata, security headers, and practical performance findings. No login, form submission, security probing, or code changes.
A GitHub account is required to submit. Requests are public: include only a public URL and visible symptoms. Never paste passwords, tokens, customer data, or private repository details. Read the exact preflight boundaries.
Choose the repair sprint when
- You already know which defects should be fixed.
- The desired outcome can be tested.
- The work fits one isolated branch.
- You can authorize access, code, and deployment.
Prefer to fix it yourself?
The public repository includes the exact intake, QA, and delivery checklists used for the sprint, plus a read-only website preflight tool. Use them freely. If they save you time, you can support the work with a Bitcoin tip.
Bitcoin tip address
bc1qptn9jxrw5ltaus7gpze6kn96d0nlqfmj3u8c2qTips do not book work. Agree a written scope before paying an invoice.