Build It Yourself - Claude Code Playbook
By Zeel Jain
For the founders who don't code. How a non-developer on my team shipped our recruitment app to production in a week, covering the spec, the prompts, and the traps.
Six months ago I'd have told you that real software needs a real engineer. Then a guy on my team with zero coding background, patience and clear head opened Claude Code and shipped our entire recruitment system in seven days.
It's in production. HR uses it daily. Nothing about it is hacky.
This is what he did. So you can do it too.
WHAT'S CHANGED
It's not vibe-coding.
Claude Code isn't a no-code tool dressed up as AI. It writes actual code in actual files. It runs on your laptop, opens projects in real IDEs, deploys to real servers, breaks in real ways and fixes itself when you tell it what's wrong.
What changed isn't that you can build without writing code. What changed is you don't need to know syntax. You need to know what you want, and you need to read what the AI writes carefully enough to catch when it's wrong.
That's the whole shift. Treat it like that and it works. Treat it like ChatGPT and you'll ship something half-baked.
Before you start
Three things you need ready:
01 · Claude Code installed.
Free to try, runs on Mac, Windows, Linux. Takes 5 minutes to set up.
02 · A clear problem.
Not 'I want an app.' Closer to: 'HR is drowning in a 2000-row Google Sheet every month and we need it sortable, filterable, with a status pipeline.'
03 · 5–7 days you can actually focus.
Day one is the worst. Stuff breaks. By day three you'll be flying.
THE BUILD
Four phases. Seven days.
Don't skip the order. Spec → Scaffold → Build → Ship. Each phase earns the next.
The spec is the work. Everything else is execution.
THE PROMPTS
What he actually typed.
Four prompt patterns covered the whole build. Copy them, fill in the brackets, you're 80% there.
01 · Scaffold the project
02 · Build a feature
03 · Fix a bug
04 · Hand it over
THE TRAPS
Three things that'll waste your week.
01 · You're not vibe-coding. You're directing.
Skip the spec, get the wrong app. The two hours you spend writing what each page does upfront saves you two days of debugging later. Boring discipline, big payoff.
02 · Test every feature before building the next.
Errors compound. If the login is half-broken and you keep building on top, by day four you won't know what's wrong with what. Click every button as soon as it's built.
03 · Don't fight the stack.
When Claude Code picks tools like Next.js, Supabase, Tailwind, Vercel, use them. They have great docs and the model knows them cold. Custom stacks mean more debugging, not better software.
ONE LAST THING
Permission isn't the problem.
You don't need a developer to build software anymore. You need a clear head, a defined problem, and a week.
Most founders are still hiring agencies for what their existing team could ship in seven days. That's the gap. Close it before someone else does.
— Zeel
Founder, Know AI · @zeeeljain