Track 02 · For Builders

From vibe coding
to product.

Build a real product without waiting for a dev team you cannot afford yet. Infrastructure, security, and discipline for AI-assisted builders.

4 weeks · 1:1 Minimum viable rails You keep the playbook
01 // QUALIFIER

Who this is for.

If you are

  • A solo founder or small team shipping with Claude, Cursor, or Codex.
  • A builder with a working prototype and no engineering function behind you.
  • An operator who can build, but cannot yet tell where the prototype ends and the product begins.
  • Someone who does not want to wait six months for a dev hire to make the next move.

Probably not you if

  • You have not built anything yet. Build the prototype first; come back when you have something real to harden.
  • You have a full engineering team. They should handle this.
  • You want me to build the product for you. This is coaching, not contracting.
  • You only need a designer or a marketer.
02 // THE PROBLEM

A working prototype is not a real product.

The gap is mostly invisible: infrastructure, deployment, auth, databases, security, observability, error handling, undo. Without those rails, every new feature is one outage away from being your weekend. With them, the same AI workflow that built the prototype can build the company.

03 // THE SPRINT · 4 WEEKS · 1:1

Four weeks. Minimum viable rails.

Week 1

Intake

Current stack, the prototype, what is real and what is duct tape. Risk audit.

Week 2

Rails

Repos, environments, deployment, auth, database hygiene, secrets, observability basics.

Week 3

Discipline

Demo-good versus production-safe. Testing and review patterns for a non-traditional team.

Week 4

Your OS

Written playbook, escalation rules. The boring document that lets you sleep.

What's covered.

Infrastructure

  • Infrastructure basics for a one-person team
  • Deployment without a DevOps engineer
  • Auth and identity that does not embarrass you
  • Database design for AI-assisted iteration
  • Security baseline
  • Observability and error handling

Discipline

  • GitHub workflows
  • Product architecture decisions
  • Demo-good versus production-safe
  • Secrets handling
  • Backup, undo, recovery
  • When to manual, when to automate
04 // PRICING

Same pricing across every track.

1 credit = 30 minutes. $150 per credit.

Package
Credits
Price · Duration
Best fit
Diagnostic
Start here
2
credits
$300
60-min call
Diagnoses the work, writes you a plan of action. Credited toward your sprint.
Small Team
Teams 2–5
48
credits
$7,200
6 weeks · up to 5
Small team building product together. Shared rails across the team.
Premium Bespoke
Established orgs
112
credits
from $16,800
8–10 weeks
Cross-functional org, founder-led transformation, higher-stakes rollout.

Prices in USD · ex. VAT

05 // FAQ

Common questions.

Q1
Do I need to be technical?
You need to be comfortable running a terminal, or willing to learn one. Reading code, deploying, infrastructure: I take you zero to one if you're not there yet. You do not need to be an engineer.
Q2
Will I end up doing my own DevOps?
No. The point is the minimum viable rails, not an enterprise stack.
Q3
Should I just hire a dev?
Eventually, yes. This buys you the runway and the judgement to hire the right one when the time comes.
Q4
Which AI tools do you cover?
Claude Code and Codex from the terminal. The discipline transfers to other terminal-first code agents. Not AI app or site builders like Framer AI or Lovable — those make the prototype; my work picks up after.
Apply

Start with a Diagnostic.

60-min call, written plan, credited toward your sprint. I will tell you straight whether this is the right track, or where you should be instead.