Why this site exists
This site exists because we kept having the same conversation. Smart, non-technical friends and colleagues would start building with AI and stall in the same place: not the prompting, but the layer of software knowledge underneath it, the things every AI tool assumes you already know. Instead of explaining that layer one person at a time, we wrote it down.
Technical Enough is the result: a free course that teaches that layer, so you can use AI tools like a builder and finish with a real product that people can use. Our essay The Missing Layer tells the story behind it.
This site is a free resource to help you get there.
There is no paywall, no account, no ads, and nothing we are trying to sell you.
Our Privacy and Terms spell out exactly what that means. We collect almost nothing, and we never sell or share it.
Built with AI
We built this site with AI, primarily Claude Code, using the same methods we teach in this course. Claude Code wrote the code, helped us identify relevant industry examples and research sources, generated the diagrams, explored design systems with us, and drafted nearly all of the prose. We brought the core source material and used Wispr Flow extensively to dictate ideas, feedback, and early drafts whether we were on the move or an idea struck unexpectedly. This helped us capture our thinking while it was fresh and keep Claude working from its latest iteration. Here is exactly who did what.
What Claude Code did
- Wrote the code for every page and feature
- Drafted the prose from our material and briefs
- Generated the custom diagrams
- Produced the page layouts and visual design
- Revised everything we sent back
What we did
- Wrote the source material and designed the curriculum
- Set the voice standard and held every sentence to it
- Wrote all the briefs and prompts
- Reviewed, corrected, cut, and redirected the drafts
- Made every call on what shipped
A large share of our build prompts were corrections. That tension is the method: use AI for speed, keep people in charge of what “good” means.
We gladly accept the vibe-coder label. Claude worked as our engineer, designer, and writing partner; we supplied product judgment, taste, domain expertise, and years of experience building products people trust. We stayed hands-on throughout, sending back corrections that were often some version of “simpler,” “revert,” or “none of these.”
This site has two siblings
Technical Enough is one of three things we run. The second is ainativeproductmanager.com (opens in a new window), our flagship site on building AI-native products, which is where to go once the foundation on this site is in place. The third is FuelTheFam, our family nutrition app and the working product this course gets tested against; its full story is the FuelTheFam case study.
Using this material
The chapters, essays, diagrams, and other material on this site are our work. You are welcome to read it, share it, link to it, and reference it in your own work; if you reuse a substantial passage or a diagram, credit Technical Enough and link back. If you want to use substantial parts of it in a commercial product or paid course, ask us first.
Who we are
Hi. We are Shivali and Girish.
Before the titles, we are builders. We are early adopters of AI and deeply curious about how it is reshaping the work we know best, which is building products, setting strategy, and solving real business problems.
Director of Strategy and Growth, Cloudleap
Shivali is a technology and growth leader who works across the full business, from sales and strategy to product implementations and AI adoption. Her work focuses on making AI a meaningful part of products and processes, not something added on the side.
Everything shared here reflects our own views. We build this in our personal time, and nothing on this site represents, is affiliated with, or is endorsed by our employers.
Glad you are here.
Build with us
If a chapter does not land, if something on the site is wrong, or if you built something because of this course, we want to hear about it. The fastest way to reach us is LinkedIn. We would love to partner with our readers to improve this, because a probabilistic system is never finished and we are just getting started.