Most firms ask you to trust the portfolio page. I'd rather you check the work. Here is my current client build, the numbers, and where each one comes from.
The build
A CRM and quoting system for a DJ and party rental company. One place for the bookings, the quotes and the follow-up, instead of three apps and a spreadsheet.
Every feature goes through the same pipeline: discovery, failing tests first, implementation, refactor, commit. What broke and what I reverted is published alongside what shipped.
The build, by the numbers
- 5,568commits
- Commits on the build
- as of September
Source
campaign/queue/launch-30.yaml:65 (as of September 2026). Verified 2026-10-07.
- 65,705tests
- Automated tests on the same build
- as of September
Source
campaign/queue/launch-30.yaml:65 (as of September 2026). Verified 2026-10-07.
The first release
- 25pieces of feedback
- After the first release
Source
campaign/queue/launch-30.yaml:106. Verified 2026-10-07.
- 21shipped
- In one sprint
- The other 4 are on the report with a reason each.
Source
campaign/queue/launch-30.yaml:106. Verified 2026-10-07.
Quoting
Building a quote used to take the client 20-30 minutes by hand. In the system I built, it's under 10 minutes.
That's the number they repeat. Nobody asks them what's under the hood. Most businesses have one process like that: the one that eats half an hour, has to be right every time, and only one person really knows how to do it.
Scoping
My last build was scoped at a 345-hour estimate. The industry benchmark for the same scope is 300-500 hours. I put both numbers in the proposal, side by side, so the client could check my arithmetic.
Every piece of feedback was sorted in writing before anything got built: bug, agreed scope, new scope, or a misunderstanding. The client always knows what is being done, what is not, and why.
Check the work
If you're comparing shops for a custom build, ask each one to show you the tests behind their work. Then book the review and I'll show you mine.