The Non-Coder CEO's AI Stack
This page — and the entire platform it sits on — was built by one person with no developer background: 370+ commits, 64,000 lines of code and more than 70 pages in six weeks. Here are the exact tools, the prompts used every day, and the things you should not use AI for. No course, no signup — just the recipe.
The tools
Seven tools. The first five require no technical background to understand — the AI is the one operating them.
Claude Code — builds
Writes the code, fixes its own mistakes and explains what it is doing in plain language as it goes. You describe what you want; it builds it. It is the only "developer" behind this platform.
Codex — checks
A second AI reviews every single change before it goes live, like a critical senior developer. Two AIs watching each other catch the mistakes you cannot see yourself.
GitHub — remembers
Stores every version of everything. If something breaks, you roll back to yesterday. It is the safety net that makes letting an AI build feel safe.
Netlify — publishes
Puts the site on the internet automatically every time a change is approved. No servers, no IT department.
Supabase — stores
The database. Your business data, stored safely — the kind of thing you used to hire people to run.
Stripe — charges
Payments and subscriptions. Connect it, and billing runs.
A file-based "second brain"
Ordinary folders with research, decisions and logs that the AI reads before it works. It is the difference between an assistant that knows your business and one that guesses.
The five prompts used every day
The tools are half of it. How you talk to them is the other half. These five are copy-ready:
1. The build prompt
"I am not a developer. I want to build [X]. Ask me questions one at a time until you can write a complete plan. Then build it step by step and explain in plain language what you did."
2. The review prompt
"Review the change you just made as a critical senior developer would. List what could break, and fix it before you show me the result."
3. The translation prompt
"Explain this error in plain language, no jargon. Give me my options and recommend one."
4. The decision prompt
"Read these files and give me the three decisions I still need to make — with pros and cons drawn from my own material, not from general knowledge."
5. The proof prompt
"Do not tell me it is done. Show me the proof: what did you test, and what was the result?"
What not to use AI for
This section is missing from most AI guides. It is the expensive half:
- Facts you have not verified yourself. AI sounds most confident precisely when it is wrong. Demand sources and proof — every time.
- Anything published without a human in between. The AI builds; you approve. Always in that order.
- Your judgement calls. Pricing, people, strategy. The AI can lay out the groundwork — the choice is yours.
- Selling. AI builds the product — it does not bring the customers. The daily conversations, the trust, the relationships — that part is still yours. Plan for it from day one.
The proof
Everything you see on boardready.dk — every page, every feature, every animation — was built with the tools and prompts above. Not as a demo, but as a real platform with login, payments and live data.
Questions?
Happy to share what worked and what did not. Message me on LinkedIn — I answer myself.
Message Kenneth on LinkedIn