#solo_founder
You have an idea, three Lovable projects, and 0 shipped. You don't need a co-founder; you need 4 hours a month with someone who's seen this pattern.
Vibe coding — building with AI tools as your hands and eyes — works. Until it doesn't. Until Lovable burns 200 credits in a loop, or Claude rewrites your auth, or Cursor makes you wonder if you're a fraud.
That's where mentorship pays for itself. I help vibe coders ship. Not by turning you into a senior engineer — by giving you the specific 10% of "real" coding skills you actually need to keep momentum.
The first 80% of any project flies. The last 20% — auth, deploys, payments, the bug that only happens on someone else's browser — is where vibe coders get stuck. Not because the tools fail. Because the tools work fine, but you don't have the language to debug them.
I teach you the language. Not "learn to code from scratch" — that's a 6-month detour. The specific minimum: how to read an error, when to git revert, what an env var is, why your deploy is failing.
Vibe coding mentorship is a shortcut to shipping, not a CS course in disguise.
You have an idea, three Lovable projects, and 0 shipped. You don't need a co-founder; you need 4 hours a month with someone who's seen this pattern.
You ship specs and Figmas all day. Now you want to build the thing yourself. AI tools work — until you hit infrastructure. That's where I come in.
You've coded for years and want to integrate AI tools without losing your standards. Less mentorship, more sparring partner — but I take this kind of mentee too.
Tailored per mentee, but here's the standard arc.
The single most under-taught skill. Most vibe-coding stalls are "I don't understand what the error is telling me, so I just paste it back to the AI and hope."
commit, branch, revert. That's it. The minimum to never lose work to an AI that decided to refactor your entire /src.
Where API keys go, why they're not in your code, how to deploy without leaking them. The chapter that prevents 80% of "Why doesn't it work in production?"
Vercel, Netlify, Railway — what they're for, when each is right, and why your domain isn't pointing where you think it is.
When to use Lovable vs Cursor vs Claude Code vs v0. They're not interchangeable, and using the wrong one is most of your friction.
Sometimes the AI is lost and the fastest path is to write 4 lines yourself. Teaching you to recognize that moment is the most expensive thing I do — because it saves you the most time.
{
"first_session": "$149", // 60 min · fit-check
"per_session_after": "$129",
"monthly_package": "$449", // 4 calls + Discord DM
"min_commitment": "none", // pay per session if you prefer
"refund_window": "24h before session"
}
First session is $149. We talk about what you're trying to ship and where you're stuck.
Bring your half-finished project. We'll get something unblocked in the first hour, then talk about whether ongoing mentorship makes sense.
No, and that's the point. The goal is to ship — not to pass a coding interview. You'll learn enough to be dangerous (in a good way) and to debug your own AI tools. If you find you love coding and want to go deeper, I'll point you to better resources.
Yes — that's exactly the audience. AI tools mean you don't need to write loops. You just need to read what they wrote and know if it's right. That's a skill I can teach in a few sessions.
Whatever you're already using. I'll meet you in your stack. If you don't have one yet, my opinion is: Lovable for fast UI, Cursor for editing existing repos, Claude Code when you want to go deeper. We figure out the right mix for your project in session 1.
Claude Code Mentor is a deep-dive on one tool for people who want to master it. Vibe Coding Mentorship is shipping-focused and tool-agnostic — we use whatever gets you to launch fastest.
Yes — that's the most common reason people book. Repeated stuck-points usually mean a missing fundamental (Git, env vars, async, etc.). One module-sized session fixes it for good.
$149 first session. Bring the project; we'll get it moving.