Product building mentorship
I teach people to build products themselves. We have 1–2 hour calls where you work on your own project and I help. After a few sessions you won't need me.
Who it's for
For people who want to build prototypes and tools themselves without spending years learning to code:
- Product managers build a prototype or an MVP themselves instead of writing a spec for developers.
- Designers turn a mockup into a working site.
- Founders test an idea over a weekend without hiring developers.
- Marketers make landing pages and the tools they need.
- Analysts automate routine work and visualize data.
How it goes
- You write to me on Telegram or by email about what you want to build.
- We have a call of 1–2 hours and work on your project.
- After that, one session or regular ones: you decide whether to continue.
What I teach
- Which tool to pick for the job: Cursor, Claude Code or Replit Agent
- How to describe a task so you get working code, and how to fix errors without knowing the language
- How to pick a stack, deploy to a server, and set up a domain, a database and analytics
- How to decide what to build first and launch in a weekend, not six months
What you can build this way
In a couple of hours you can build a landing page, a Telegram bot, a browser extension or an automation script. Over a weekend, a SaaS with sign-in or a tool with a database.
What my students did
- A designer learned to deploy to a server in one session.
- A product manager built her first SaaS.
How I build myself
This is how I build chess.rodeo: I write the code and run the servers alone. Since May 2026 more than 1,100 pull requests have gone into it, and about 20,000 people use it each month. I write about the mistakes on the blog: for example, how I spent a week moving Supabase to my own server and ended up with plain Postgres in containers.
I'll set up the same process in your project
If you already have a product and you or a small team work on it, I can set up development with agents the way it works for me on chess.rodeo. I described it in detail in Six changes a day: how chess.rodeo is built.
What can be set up:
- rules for the agent written for your code, each with the reason it exists;
- a separate copy of the repository for each agent, so they don't get in each other's way;
- a stand for every branch and before-and-after frames right in the pull request;
- CI checks and releases whose description says what's included and how to roll back;
- a check after deploy and a canary that runs tests against the live site;
- scheduled jobs: error reviews, reports, a digest of what competitors released.
We start with a call: you tell me how the work is set up now, I look at the repository and say what to set up first.
FAQ
Do I need to know how to code?
No. Mentoring is for people who want to build prototypes and tools without spending years learning to code. We go through how to describe a task so you get working code, and how to fix errors without knowing the language.
How long is a session?
1–2 hours on a call. We work on your project.
How many sessions will I need?
As many as you decide: mentoring can be a single session or ongoing. One designer learned to deploy to a server in one session.
Which tools will I learn?
The one that fits your task: Cursor, Claude Code or Replit Agent. Besides the tool, we cover the stack, deploying to a server, the domain, the database and analytics.
What should I bring to the first call?
The project you want to build, or the idea of it. We work on it from the first session.
Can you set up development with agents in our project?
Yes: rules for the agent, stands, before-and-after frames, checks and scheduled jobs. The section on setting up the same process in your project lists what exactly.
What if I need it built for me?
Then it is MVP development: I design it, write the code and deploy it myself. If the question is what to build at all, start with product consulting.
Get in touch
Other formats: product consulting and building an MVP, if you need me to build it.