1M+ lines in six months — how I build with AI
187
Build sessions
485h
Hands-on hours
4,621
Commits
15h 17m
Longest single session
Echify's MVP — iOS app, web app, and a serverless backend — was built by a team of one, pairing with AI.
Y Combinator's Paxel report analyzed my working patterns: over a million lines shipped across 187 sessions and 485 hours. 11.7 commits per active hour. 63% of sessions started from a written plan. Four parallel workstreams at peak.
The workflow that makes it possible: written plans before code, prompt files and handoff docs between sessions, strict branch and PR rules, and relentless real-device QA. The craft isn't typing — it's architecture decisions, catching AI overreach, and knowing exactly what 'done' looks like.
This is what building a company looks like now: one founder, disciplined systems, and agents doing the heavy lifting. It's also exactly the leverage Echify hands to every business on the platform.
The operating loop
1. Plan in writing
Every session starts from a written plan — scope, contracts, acceptance checks.
2. Build in parallel
Multiple AI pair-sessions at once, each with its own branch and handoff prompt.
3. Review like an architect
Catch overreach and wrong abstractions early; 322 of 393 logged decisions were architectural.
4. Verify on real devices
Nothing ships without hands-on QA in the real app, on real hardware.