I expect execution
A session is where we make decisions and corrections. Change happens between sessions: in work, training, conversation, code, budget, and daily rhythm.
1:1 mentoring for people ready to change
Whole-system mentoring.
Code is only the entry point. We work on technology, money, health, communication, and direction so you can perform with more leverage, calm, and awareness after the program ends.
- We start with an intake and decide whether collaboration makes sense
- No templates - the plan is built around your pace and context
- Relationship, networking, and support can continue after the program
First filter
Everything starts with an intake
I do not accept every request. First I need to understand your situation, motivation, and direction. Only after that conversation do I decide whether I am the right person for the collaboration.
-
01
Context
We talk about work, learning, energy, money, relationships, ambition, and blockers. Without diagnosis, there is no useful plan.
-
02
Decision
I check whether I can genuinely help. I work with people who are decisive, passionate, and ready to do the work between sessions.
-
03
Contract
We define the rules: rhythm, scope, responsibility, feedback, and what must happen between sessions.
-
04
First cycle
We start with a short work loop. We do not plan a perfect year - we test direction, measure impact, and correct.
01
Context
We talk about work, learning, energy, money, relationships, ambition, and blockers. Without diagnosis, there is no useful plan.
High standard
This is not ordinary mentoring
This program is not a purchase of hours. It is shared work on your operating standard: how you think, choose, deliver, recover, and build reputation.
I design for context
There is no one syllabus for everyone. The plan depends on your goal, constraints, energy, ambition, market, and current level of responsibility.
I build relationship
If the collaboration has quality, contact, networking, and space for future conversations or shared initiatives remain after the program.
Work scope
We develop the whole system, not one isolated skill
Technology can be important, but it does not operate in isolation. A high standard requires energy, clear priorities, communication, money under control, and a direction that makes sense.
Technical craft
Architecture, backend, frontend, DevOps, security, tests, and code review. We do not learn technology for a checklist - we build the ability to make better technical decisions.
Capital and choices
Budget, emergency fund, negotiations, offer selection, and basic investment thinking. This is not financial advice - it is foundation and decision hygiene.
Energy and body
Sleep, recovery, training, nutrition, daily rhythm, and work hygiene. Without energy, there is no quality code, communication, or consistency.
Growth, soft skills, and career
We connect self-development, communication, feedback, assertiveness, portfolio, interviews, leadership, and ikigai. The point is direction, reputation, and the ability to work with people, not another technology alone.
Kaizen engine
Change is built through iterations
We do not build a grand declaration that dies after a week. We build small, repeatable loops: observe, decide, act, correct.
After the program
The goal is a real bond, not a closed transaction
If we work well, the program does not end with an artificial wall. The relationship can remain: conversation, networking, shared ideas, and space for future collaboration.
- You can come back with a question, career decision, or problem worth thinking through.
- If I see a valuable connection, I can help with networking or a recommendation.
- I am not building a client list. I am building an environment of people worth working with.
Format
Flexible, concrete, no fixed packages
After intake, we choose the rhythm, scope, and level of support. The program can be intense or calmer - it has to work in your life, not only in a calendar.
1:1 sessions
Usually 60-90 minutes online, weekly or bi-weekly. We match the rhythm to the goal and your availability.
Tasks between sessions
There is no change without execution. Tasks can cover code, decisions, communication, training, finance, or work organization.
Asynchronous support
Depending on scope, we can work on a repository, documents, notes, weekly plan, or interview preparation.
Operating system
At the end, you should have not only more knowledge, but better decisions, rhythm, self-awareness, and agency.
FAQ
Common questions
The main rule: the approach is individual. I do not sell a fixed plan; I design collaboration around a real person and real context.
There is no single length. The first meaningful cycle usually takes 8-12 weeks, but the final shape depends on the goal, pace, availability, and scope. After intake we set a rhythm that is actually doable.
I do not publish one fixed price because the scope can vary significantly. Pricing is defined after the intake call and depends on session intensity, asynchronous support, and the areas we work on.
You will receive a plan, but not a template. We build it from your situation, goal, constraints, and pace. If we need to slow down, speed up, or change priority, we do it deliberately.
No. Technology is often an important area, but we also work on personal finance, health, energy, communication, self-development, career, and professional direction.
People who are decisive, passionate, and ready for real change. You do not need to be perfectly prepared, but you must be willing to work, receive feedback, and own the execution.
I do not automatically disappear after the last session. If the collaboration was valuable, you can count on contact, conversation, networking, potential future collaboration, and support around important decisions.
Next step
If you are ready to work seriously, start with a conversation
Write briefly where you are now, what you want to change, and why it matters. After the intake, I will honestly tell you whether I am the right person for this collaboration.