How it works
Bring the problem. Leave with a next step.
No discovery marathon. No slide deck. You bring the real problem, worry or challenge in front of you. Together we work out what matters now and what can wait.
- 01
You bring the problem
Something slowing you down: a quote, a hire, an MVP scope, rising hosting costs, an AI question, an architecture worry, or anything about to lock in time, money or focus.
- 02
We add the context
What you are building, who the customer is, what the team can handle, what budget is on the table and where the real constraint sits. Without context, every call is a guess.
- 03
We sharpen it
I look at it through product, technology, execution, risk and priority at the same time. What belongs here now? What can wait? What gets expensive later if you do not see it now?
- 04
You leave with a workable step
No long report. No drawn-out analysis. One concrete next step that fits where you are right now.
What working together feels like.
Direct
I say it when an idea is weak, a quote is inflated, or a hire does not make sense.
Overview
I bring calm when product, technology, regulation, security and people have become tangled together.
Creative
Constraints usually point to a simpler solution, not to more complexity.
Persistent
I stay with a hard problem until we understand it and see a workable next step.
Independent
I do not build, do not deliver and do not earn anything from the choice you make. That is what makes the trade-off trustworthy.
Practical
You leave with clarity, a shorter route to release, or a concrete next step.
Preparation
Bring the messy version.
A quote, a half-finished roadmap, a hiring dilemma, a voice note. Honest context is more useful than a tidy presentation.
Limited availability
I work with no more than 8 companies at a time.
That limit keeps the advice personal, responsive and properly informed. New companies can start when capacity opens.
Honest boundaries
When I am probably not the right person.
- You are looking for someone to build the software.
- You are looking for a full-time CTO.
- You want confirmation instead of pushback.
- You need daily project management.
- You do not yet have a concrete problem or question.
Common questions
How working together actually works.
Practical questions about the conversation, what to bring and what happens after.
- What should I bring to the first call?
- No pitch deck needed. A quote, a half-finished roadmap, a hiring dilemma, a voice memo or a few sentences about the problem on the table is enough. The messier the real context, the more useful the conversation. Polish comes later, or not at all.
- How long is a conversation?
- The first call is 30 minutes. Follow-up calls in monthly plans usually run 45-60 minutes. Long enough to get sharp, short enough not to drift. For some founders, 30 minutes turns out to be enough for a workable next step.
- Do you sign an NDA?
- On request, without issue. By default everything discussed is treated as confidential, no NDA is needed for that. For sensitive situations (competitive strategy, people matters, financial details), an NDA is easy to arrange.
- What happens after the call?
- A short written summary of the trade-off and the next step. No report, no long analysis, only what helps you actually move forward. After that you are free to continue, wait, or stay in touch via a monthly plan.
Tell me what you’re struggling with.
Development is taking too long. Costs are rising. You’re unsure about a choice. Or your startup simply feels stuck. Let’s figure out what is really going on.