Internal build
9 days
Internal SaaS build
Idea → first deployed user flow in 9 days: auth, core workflow, and a working preview environment, using the same scope-first process we sell.
Work
We're a young agency, so we do proof differently: internal builds documented honestly and labeled as such, with the process open for inspection. Every case study here is something you can click, audit, or ask to see the repo for on a call.
Case study 01 · Internal build · You are looking at it
4 days
research to production-ready
15 pages
incl. 6 illustrated blog posts
~30KB
median page weight of images
100%
code reviewed before merge
Claude Code wrote the overwhelming majority of this codebase — pages, styles, animations, structured data, even the SVG illustrations. Humans made the calls it can't: positioning, pricing strategy, design direction, and review of everything before it shipped. That's the same split you get on every project.
Stack: Astro 5, Tailwind CSS 4, self-hosted fonts, zero client-side frameworks. Static output, structured data on every page, custom WebP illustrations averaging 12KB each.
Full write-ups are in progress; the numbers below are the headline results. Ask for the unabridged walkthrough — including repos and deployed previews — on a scoping call.
Internal build
9 days
Idea → first deployed user flow in 9 days: auth, core workflow, and a working preview environment, using the same scope-first process we sell.
Rescue audit
23 findings
A pre-launch security & architecture audit of an AI-built app surfaced 23 issues — including exposed credentials — before its public launch, not after. How Rescue works →
Free 30-minute scoping call. Written fixed-price scope within 24 hours — and daily pushes you can watch once we start.
Book a free scoping call