The non-technical founder's starter path
I am not a developer. I built this site, and the things behind it, by describing what I wanted and letting AI write the first version. This page is the path I wish someone had handed me at the start — no jargon, no lectures, just the next step.
Decide what to build
Start with a small, real problem you actually have. Not "an app" — a specific thing you want to exist. Smaller beats ambitious here.
Pick the right AI tool
You do not need to learn to code to start. Answer a few questions and get a shortlist of tools that fit how you work — from no-code builders to AI assistants.
Build the first version in plain language
Describe what you want; let the AI write the first draft. You steer with everyday words and decide what is good enough to keep.
Ship, then learn out loud
Put it in front of a real person early. Keep notes on what worked and what broke — that record is worth more than any tutorial.
Honest questions, answered
Do I need to learn to code first?
No. Many of the tools here run in your browser and turn plain descriptions into working results. Learning a little later is optional, not a prerequisite.
Is this only for software products?
Mostly, because that is what AI tools do well today. But the same habit — describe it, build a draft, ship, learn — applies to content, sites, and small automations too.
Will the AI just do everything for me?
It writes a first version; you stay the decision-maker. The results still need your judgement about whether they are actually what you meant.
Read my story →
Why a non-technical person started building with AI, and what this site is really for.
Browse the technical notes →
When you are ready to go deeper, the full library of hands-on guides lives here.