01 / REVIEW
Build and release path
Reproduce the documented build, deployment assumptions, environment setup and recovery steps.
For indie founders and small web agencies
Before you ship, know what still needs attention.
A practical review of your web app’s release basics: what works, what’s risky, and the next fixes to make. Clear findings, no 40-page scare report.
First three pilot reviews: R1,250 fixed scope · 3 business days · no subscription
What you get
A short route from “it runs” to “we can release it.”
Useful when an MVP is close to launch, has changed hands, or was assembled quickly and nobody has time for a structured pass.
02 / CHECK
Common launch blockers
Review dependency alerts, exposed configuration risks, basic access-control paths and failure handling within the agreed scope.
03 / HANDOFF
Ranked fix list
Get evidence, severity, suggested next step and a 30-minute walkthrough. Findings are not a certification.
Pilot offer
One app. One clear decision.
For a small web app with a working repository and a reproducible setup. We agree the exact scope before access or work begins.
- One repository, one main deploy target, up to 90 minutes of hands-on review
- Short written report with evidence and priorities
- 30-minute handoff call or screen-share
- Delivered within 3 business days after access and scope are confirmed
- No production changes, no secrets required, no certification or guarantee
The R1,250 pilot price is a hypothesis to test, not a verified market rate. Larger or sensitive apps need a separately scoped proposal. Monthly release checks (hypothesis: R750–R1,500/app/month) only make sense if customers ask for repeat help.
Good fit and limits
Who is this for?
Solo founders, indie makers and small agencies shipping a modest web app without a dedicated release or security reviewer.
What is this not?
Penetration testing, legal/compliance advice, a formal security audit, uptime monitoring or a promise that an app is “secure.”
How do you handle code?
We agree access and handling first. No production credentials are needed for the initial review; use a limited, read-only repo invite where possible. Don’t send secrets by email.
Can you fix what you find?
If useful, a separate small remediation scope can follow. You approve it before work begins; findings and fixes are not bundled into the pilot price.
Start with a conversation
Tell me what you’re trying to ship and where you’re stuck.
I’ll reply with a fit check and a proposed scope before asking for repository access.
Email Joshuavanstraaten100@gmail.com →