I’m Ruslan Hrekov, a solo builder based in the US. I collaborate with Claude to ship production software that’s honest about how it was made — commit hashes, DEVLOGs, locked files. The usual.
Cases · 4 of 6
Commit hashes, DEVLOGs and the decisions that made or broke each build.
01 / 06 · Meta · solo build · 2026
The portfolio that documents itself — forty-seven memory files, one recursive proof.
Outcome: A site that is its own proof: every decision dated, every rule earned, all of it public.
04 / 06 · Personal · solo · 2026
An Instagram team of zero humans. Eight agents, three-tap Slack approval.
Outcome: 40 posts in two months at about $0.40 a week — with every taste call still human.
05 / 06 · Full build · solo · 2026
Booking SaaS for solo barbershops — 234 commits, one locked file.
Outcome: $15 a month against ~$2,600 a month in no-shows — about 170× payback.
Pre-launch06 / 06 · Client · lead · 2026
Five-stage AI pipeline before a single production line of code.
Outcome: One platform for all four jobs, designed so every feature follows the same five-role pipeline.
Engagements · 3 of 5
2 weeks · fixed
Technical + product assessment, a prioritized roadmap, and one working spike aimed at whatever scares you most.
2 days/week · monthly retainer
Shipped features, unblocked engineers, and a technical direction your team owns after I’m out.
1–3 months · milestone
A concrete deliverable shipped together — MVP, migration, or rewrite — with AI collaboration baked in, not bolted on.
Process · 5 stages
One paragraph in. Constraints, users, stakes. If we can’t name what should stay locked, we’re not ready to spec.
specs/<slug>/spec.md lands first. What we’re building, what we’re not, and the shape of “done”.
plan.md sequences the risky bits early. Every task numbered, blocked-by set, DEVLOG format decided.
Opus for architecture, Sonnet for features, Haiku for volume. DEVLOG goes in after every work block — not at the end, when memory lies.
QA loop, memory/qa-iteration-N.md, retrospective, tag a release. The next feature restarts at Discovery.
Benefits · 3
Every feature lands in specs/<slug>/ as spec + plan + tasks before any production code. Disagreements happen on paper, where they're cheaper.
Case studies come with commit hashes, DEVLOG entries, and named bugs. If a number isn't verifiable, it doesn't go in the copy.
Claude does the typing. The pivots, the calls on what to lock down, and the moment to stop and think — those stay mine. That's where the taste shows up in the diff.
Experience · 3 of 7
Shipping five production case studies with Claude as pair. Every build ships spec + plan + DEVLOG. ShipLoop discipline as the operating system.
Next.js + Supabase + Stripe stacks for boutique clients — moonlighting builder work concurrent with the PIMU design day-job. Learned to measure everything and to trust commit hashes over screenshots.
Marketing-department contract in Kharkiv — social campaigns, presentations, and publication visuals, in parallel with the PIMU product-design day-job.
Voices · 2
Ruslan owned the arc from requirements to shipped design — creative, responsible, and someone every stakeholder wanted in the room.
Ruslan is the collaborator you keep. Fresh, high-quality work, and the discipline to stay late when a client date needed defending.
