Founder, vibecoding.tech and RuBench

Vibe coding is a chat with an AI. It works until your project turns into a mess: every fix breaks something else, and nobody remembers why.
Agentic engineering is different. Agents work by written rules: they check their own work, roll back mistakes and never break what is already done. You write the rules and accept the work. I run my company this way: 7,500 commits in 114 days, a commit every 22 minutes, all of it live at vibecoding.tech/open. I am not an engineer, and I did not write a line of it.
In four weeks we set this up on your project. Every week you take home a working thing: a repo that runs on rules, a gate that stops broken changes, a fleet of agents working in parallel, and a day when your product ships without you. The method is Spec-Driven Company. The starter is open source. The numbers are live.
Go from chatting with an AI to running a product that ships daily under your rules, with you reviewing instead of coding.
Install the open-source Spec-Driven Company starter in your repo: rules file, task worktrees, docs as the source of truth
Ship your first task end-to-end with an agent: branch, code, checks, pull request. You only accept the work
What a model is, tokens and the context window, generation / family / effort, how to read a benchmark honestly
Which agent for which job (Codex, Claude Code, Cursor) and a stack any agent handles: TypeScript, Next.js, Convex, Git, hosting
Tests and CI the agent sets up and respects, a quality gate and a self-fix loop: a broken change never reaches main
Your rules file in full, the 11 steps of one task, docs as the steering wheel and the watchman that catches drift
Task worktrees and subagents, so three agents build three features at once without stepping on each other
A journal of decisions and a page with live numbers from git, like vibecoding.tech/open, so you see the pulse of your product
Cron jobs, a self-heal watchman and a writer pipeline: the machine does its own routine work, from an empty folder in 35 minutes
24 hours of your product shipping while you only watch the journal. Demo day and your Spec-Driven Company practitioner certificate

Not an engineer. Ships a product with a fleet of AI agents every 22 minutes.
Product people who build with AI but don't code: PMs, designers, marketers, founders. Your chat-built project turned into a mess.
Engineers tired of babysitting agents: you want rules, a gate and a journal instead of re-reading every diff.
Solo builders with a product or an idea and 5 hours a week. Not for you if you want to learn to code by hand.
Lifetime access
Go back to course content and recordings whenever you need to.
Private cohort chat
A small group of up to five builders and me, in one chat for the whole four weeks.
Certificate: Spec-Driven Company practitioner
Share it with your employer or on LinkedIn.
4 live sessions, 90 minutes each
Wednesdays 12:00 PM ET, recorded. We build on your project, not on slides.
Weekly written review of your repo
Every week I read your repo and your agent's pull requests and write back what to fix.
58 text lessons
The full textbook, chapter by chapter, with a task in every lesson.
A real product from an empty folder to first money
A short-video machine: it writes the script, assembles the video, publishes on schedule, takes orders and payments. We build every part.
Spec-Driven Company starter on GitHub
One paste into your agent and in 35 minutes you have a site, a database, a password-protected admin panel, hosting and a check before every deploy.
Maven Guarantee
Your purchase is backed by the Maven Guarantee.
Maven for Teams
Reimbursement
Get your company to pay
Everything L&D needs: email template, receipts, and certificate of completion.
Get reimbursedPrivate cohort
Run a cohort for your org
A dedicated cohort with a custom schedule and curriculum, tailored to your team.
Book a private cohort