Devs building solo stack up open projects. What's missing isn't advice. It's someone pulling decisions.
Four steps that separate idea from shipped product. Applied first on my own SaaS before opening as mentorship.

- THE HYPOTHESIS 01
- THE HYPOTHESIS 02
Twitter wisdom and recorded courses don't fit the real context of someone building day to day.
- THE HYPOTHESIS 03
Most of what looks like strategy is procrastination dressed up as planning.
The SOLO Method
Four steps, four skills. Each session delivers one. You leave with a decision tool, not just a plan.
- Situation
Honest diagnosis
Tell apart the story you tell yourself from the data that exists. Know where on the map you actually are, not where you think you are.
- Objective
Concrete destination
Define what success means for this cycle. Not a plan, not a roadmap. A verifiable milestone you recognize when you reach it.
- Launch
Minimum launch
Decide the smallest delivery that proves or breaks your hypothesis. Fight planning perfectionism with the real world.
- Optimization
Optimization without guessing
Read real data from the launch and adjust course. Decide what becomes a new cycle and what gets left behind.
Two formats. Same method.
Pick by the depth that makes sense for you right now.
Diagnóstico SOLO
R$ 697One 2h session. 30 days of WhatsApp.
- One 2h live session via Google Meet, recorded.
- Pre-call form about the project.
- SOLO diagnosis document within 48h.
- 30 days of WhatsApp follow-up (response within 24h, business days).
For when you need quick unblocking with method and are ready to execute next.
Ciclo SOLO
R$ 1.897Four sessions over about 2 months. WhatsApp in between.
- Four 2h live sessions via Google Meet, recorded.
- Spread cadence across about 2 months (one session per method step).
- Document at the end of each session.
- WhatsApp between sessions (response within 24h, business days).
- Templates and references from my own projects.
- Final document consolidating the cycle.
For when you're ready to apply the full method with continuous support.
The SOLO Method was first applied to my own products (ThreadRecap, TeseFirme, CastSpread, among others) before opening as mentorship. The first pilot cycles with mentees are running now. Full case studies will be published here as cycles wrap up.
Frequently asked questions
A 4-step structure: Situation, Objective, Launch, Optimization. It helps separate hunch from data, define a destination, decide the minimum delivery, and read results without bias. You leave with a tool that applies to any project, not only the one you bring.
No. You can be anywhere: idea, MVP, live product, stuck product. The method applies to all of them. What you need is something concrete to work on, not just general interest.
It helps, but it's not required. The focus is decision and direction, not code. If you build with no-code, low-code, or AI tools, the method applies the same way.
Yes. Every session is recorded and the link stays with you. Revisit whenever you want.
Diagnostic is a single 2h session focused on unblocking. You leave with an action plan and 30 days of WhatsApp support. Cycle is the full method applied across 4 spread sessions (one per step) over about 2 months.
You can. The amount paid for the Diagnostic becomes credit toward the Cycle if you migrate within 30 days of the single session.
Mostly solo founders, devs building their own products and professionals in transition. Companies can take the SOLO Diagnostic if it makes sense for the team. For full-team coaching, it's better to talk first by email.
SOLO Diagnostic: full refund if cancelled at least 24h before the session. SOLO Cycle: proportional refund for sessions not yet completed.
Yes. I work in English or Portuguese, and accept payment in BRL, USD or EUR via Stripe. I'm based in Portugal (Lisbon time), with flexibility for hours compatible with Brazil and Europe.