Built with Claude Code
Not a demo, not a toy repo — the live internal system this company runs on every day: payroll, client billing, commissions, partner accounts, property P&L, access control. Every page, every migration, every line below was written by Claude Code, reviewed and shipped by one non-technical owner.
Nobody chose a friendly stack for it. This is a flat-file app with a hard security policy — no build step, no CDN, no framework — talking to a Postgres database where the access rules live in the database itself.
Every line below is a real commit on main, with its real timestamp.
This is a single day: twelve pull requests, from the morning through to late evening — each one
specified in plain English, built, checked and shipped to production.
The 19:50 to 22:17 stretch alone shipped seven pull requests and 2,461 lines — profit history extended back to 2018, a growth series at four different time grains, and a partner-settlement page. Deploy is a push: the server pulls from GitHub every two minutes, so "shipped" above means live for every user within two minutes of the commit.
Writing code fast is the easy half. These are cases from this repo's history where the job was to notice something was wrong, prove it, and refuse to guess — the part that actually decides whether you can hand work over.
Not a list of things it could theoretically do. Each row points at work that is live in this repository right now.
| The job | Done here |
|---|
This page would be worth nothing if it only listed wins. These limits are real, they are written into this project's own rules, and they are the reason the work holds up.
The fastest way to settle the question is to give it a job you already know how to do, and time it. Three suggestions, in rising order of nerve.