Learn to build software with AI, on your own product.
One-on-one work with an engineer who has built and shipped over 50 products. No generic lessons: your project, your level, your pace.
- 15+
- years of production software
- 50+
- products built and shipped
- 6
- products you can open today
- 1
- person accountable for the work
The problem
Why tutorials and courses are not enough
Generic content gives you tools, but not judgment: what to build first, what to skip, and when something is good enough to ship.
AI writes the code, but who checks it?
A model writes a thousand lines in minutes. Without someone who knows what to look for, the bugs reach production along with the code.
The project is stuck halfway
The prototype runs on your machine, and between it and real users stand sign-in, payments, servers and a hundred small things.
You get no feedback
You make decisions alone and do not know whether they are good until they get expensive. An experienced eye sees it in five minutes.
The tools change every week
What worked three months ago has a better replacement today. Without someone who works with those tools every day, you keep falling behind.
The solution
What you get from mentoring
Everything you need to stop guessing and start shipping software that works.
A plan for your product
An order of steps made for your project and your level, with no templates.
Live calls with screen sharing
We go through your code, tools and decisions together, and change them in real time.
Code and architecture review
What is good, what is risky, and what to change before it gets expensive.
Working with AI agents
How to let AI tools do a large part of the work while you keep control and quality.
From prototype to production
Sign-in, payments, servers, monitoring and everything else that separates a prototype from a product.
Someone who keeps you on track
I follow your progress and do not let the project stall when it gets hard.
Comparison
Alone, a course, or mentoring?
| Alone, a course, or mentoring? | Alone | Course | Mentoring |
|---|---|---|---|
| A plan for your project | × | × | ✓ |
| Feedback on your code | × | × | ✓ |
| Direct access to an experienced engineer | × | ~ | ✓ |
| You learn the system, not just the tool | ~ | ✓ | ✓ |
| A fast road to production | × | ~ | ✓ |
Process
How mentoring works
-
01
Apply and meet
You fill in a form so I understand where you are and where you are going, then we talk briefly to see whether we are a good fit.
-
02
Plan
Based on your project, experience and time, I make a plan: what we do, in what order and why.
-
03
Work and support
We work on calls, I follow your progress and we change the plan when needed. Between calls you have support for questions.
Who it is for
Is mentoring right for you?
It is for you if...
- you have an idea or project and want to bring it to real users
- you want to learn to work with AI tools, not just try them
- you are ready to work between calls
- you value honest judgment more than praise
It is not for you if...
- you want someone to build the product for you (that is product development)
- you expect results without your own work
- you cannot spare a few hours a week for the project
Questions
Frequently asked questions
Do I need to know how to code?
No. We start at your level. If you have never coded, the first part of the plan is learning enough to understand what the AI tools produce.
How long does mentoring last?
We agree after the intro call, based on the goal. Most often it is a few months, with calls every week or two.
How much does it cost?
You get the price and package after the intro call, once we know the goal and the pace.
Which tools do we use?
The ones I use every day for products in production, and the ones that suit your project. The tool is chosen for the work, not the other way around.
Ready to make your project work?
Places are limited because I lead every mentee personally.
Apply for mentoring