A one-day workshop for founders and operators with zero coding experience. By 6pm, you'll have shipped a working tool. With AI doing the heavy lifting and an operator showing you the rails.
"You don't need a developer. You need one day."
Average weeks a founder waits for IT to build them a basic internal tool.
You have an idea. A form. A dashboard. A workflow that should take five seconds instead of fifty.
You ping a developer. Two weeks of back-and-forth. A demo that's wrong. Another two weeks. Maybe it ships. Maybe it doesn't.
Meanwhile, the problem you wanted to solve has changed twice.
You are the bottleneck. Your dependency is the bottleneck.
Python, Node, Git, GitHub CLI, VS Code — all installed, configured, and working. No more "command not found."
You'll move around your computer with words. Stop being scared of the black window. Start using it as a superpower.
Variables, functions, loops, packages. Read code AI gives you and know what's happening. Modify it without breaking it.
Save your work, recover from mistakes, push to GitHub, and never lose a project to a bad save again.
Frontend, backend, databases, deploy. The vocabulary you need to talk to AI — and to actual developers — without flinching.
Your name on a URL. Pushed to GitHub. Deployed on Vercel. Yours forever as proof of what you can do.
Nine modules. Sequenced so the next one always builds on the last. No detours, no theory dumps, no "we'll come back to that later."
The mental model that makes everything else click. Five minutes that save you a week of confusion.
Mac and Windows paths run side-by-side. Homebrew, Python, Node, Git, GitHub CLI, VS Code. Everything on the machine before we explain a single thing.
Now that it works, what is each piece for? PATH explained. python vs python3. The reason any of this matters.
Lobby vs office. cd, ls, pwd, mkdir. The parent folder trick that saves your sanity. The five commands you'll use forever.
Write it. Save it. Run it. The white circle that means you forgot to save. The errors that look scary and aren't.
Why you don't write everything from scratch. How to install someone else's code. The two commands that unlock 90% of Python and Node.
Seven words of vocabulary. Three commands you'll repeat forever. Saving your work like a professional from day one.
Variables, functions, loops, lists, dicts. Enough to read 90% of what AI writes for you and modify it without fear.
Frontend, backend, database. HTML/CSS/JS, React, Flask, Supabase. The map of the territory you've been navigating blind.
Push to GitHub. Deploy to Vercel. Get a real URL. Send it to your mum. Or your investors.
Twelve seats. One day. Live with Riz. Real installs on real machines, with real errors solved in real time. The format is built for the actual messy reality of getting set up — not for a polished demo.
"I built and shipped a hand-tracking arcade game in the browser. With zero prior coding experience. Using AI."
I'm not a developer. I'm an operator. I spent a decade leading operations at Careem, Bolt, Motive, and Wise — building processes, not product. Then AI changed what an operator can ship alone, and I started building.
This workshop is the foundation I wish someone had given me. Not theory. Not "learn to code." The practical, ground-level setup that turns AI from a chatbot you talk to into a co-builder you ship with.
If I can do this, you can. The gap is one day of foundation.
Two ways in. The earlier you commit, the less it costs.
Booking for a team of 3+? Email us about team pricing.
Most participants expense this through L&D. Ask for an invoice.
Zero. The workshop is built for someone who has never opened a Terminal, never written a line of code, and gets nervous when they see a black screen with white text. The first three modules assume you know nothing.
A laptop (Mac or Windows — both supported), at least 5GB of free disk space, and admin/install permissions on the machine. We send a pre-workshop checklist 48 hours before so you arrive ready to go.
Cohort size is capped at 12 specifically so this doesn't happen. Riz works the room live, debugging in real time. Most "stuck" moments are predictable — they're already addressed in the manual's Emergency Troubleshooting Map.
Both work. The manual and the live workshop run Mac and Windows paths in parallel. We split into breakouts when OS-specific issues come up so neither group waits on the other.
The cohort Slack stays open for 7 days for follow-up questions. Early bird seats get a 30-minute 1:1 with Riz in the two weeks following. The manual is yours forever — it's designed to be a reference you come back to, not a notebook you lose.
Most participants do. We issue a proper VAT invoice from our Estonian entity. Many L&D budgets cover this directly. Email riz@withsoch.com if you need a pre-payment quote for procurement.
Full refund up to 7 days before the cohort starts. After that, you can transfer your seat to the next cohort or send a colleague in your place. We don't refund within 7 days because we've already capped seats and turned other people away.
YouTube tutorials work fine until something breaks. Then you spend an hour Googling the error and quit. The whole point of a live cohort is that someone is there when reality hits — and reality hits constantly when you're setting up a dev environment for the first time.
Twelve seats per cohort. Next one starts [COHORT_DATE]. Reserve yours before early bird closes.
Reserve your seat →