Founder Clarity Partner
Helping founders build
the right product
before they build the product right.
Most products don't fail on execution. They fail because the right problem was never clearly named. I work with founders to find that clarity — usually in far less time than they expect.
No pitch, no obligation. I reply personally within one working day.
Two places open this quarter — a maximum of 2–3 founders at a time. Start here, read lessons, or see the guide to product strategy for founders.
Recognition
You're probably here because…
- You're shipping steadily, but you're no longer sure it's the right thing.
- The roadmap keeps growing and the story keeps getting harder to tell.
- Your team is busy, capable, and quietly pulling in different directions.
- You've raised, or you're about to, and the narrative needs to hold up.
- Something feels off, and you can't yet name what it is.
- You're the only person who can see the whole picture — and no one to think it through with.
None of these are technology problems. They're clarity problems that eventually show up as technology problems.
Most products don't fail because of bad execution. They fail because the right problem was never clearly named.
Outcomes
What founders leave with
A problem you can name
One sentence you can say out loud to a customer, an investor, or your own team without hedging.
A shorter roadmap
Not more to do. Less — with a clear reason why each remaining thing survived.
Language that travels
Words your team repeats without you in the room. Clarity that survives your absence.
A decision you'd been avoiding
Usually one. Usually the one you already knew about. Made, and made calmly.
Evidence, not opinion
A way to test the next assumption cheaply, so the following months cost less to learn from.
Your own thinking back
Most founders don't need answers. They need two uninterrupted hours to hear themselves think.
Method
The questions I ask
I don't arrive with answers. I arrive with questions that are hard to answer quickly — and that's usually where the clarity is hiding.
- What would have to be true for this to work?
- Who is worse off if this succeeds?
- What are you protecting that no longer needs protecting?
- If you had to cut half the roadmap tonight, what would you keep?
- What do your customers do the day before they need you?
- What's the most expensive assumption you haven't tested?
- Which part of this is the business, and which part is the habit?
- What would you build if you couldn't write any code?
The Founder Clarity Session
Two hours. One problem, properly named.
A single, focused conversation about what you're actually building and why. No deck, no discovery phase, no proposal at the end.
New — a fixed-price service
Product Reality Check
Send me your product. I'll tell you what's wrong with it.
I use it as a new customer, cut through the assumptions, and send back a short written assessment with annotated screenshots. €149, back within 48 hours.
- What's confusing
- What users may not trust
- Where they may drop off
- The 3 things I'd fix first
Writing
Lessons from the Workshop
Short reflective pieces on building, stewardship, and the cost of learning. Written slowly, on purpose.
Fractional vs full-time: what a founder actually needs.
Fractional leadership isn't a cheaper full-time hire. It's a different instrument, and using the wrong one is what makes founders think it didn't work.
Founders don't need more information. They need permission.
By the time a founder asks me what to do, they usually already know. What's missing is someone to say it out loud with them.
Complexity is a decision you postponed.
Systems don't get complicated on their own. Every branch in the logic is a choice somebody declined to make.
Technology is not the product. Clarity is the product. Technology is just the evidence that the clarity was real.

Who you'd be sitting with
Michael O'Callaghan
Twenty-five years building, breaking and rebuilding products — as a founder, an engineer, and a product and UX lead. The platforms I've shipped have trained over 50,000 people, and plenty that found no one at all. The second kind taught me more.
Technology isn't what I sell. It's the evidence that the thinking underneath was sound.
Read the longer story →If we keep going
Other ways to work together
Most work starts with a clarity session. These are what sometimes follows.
Ongoing clarity partnership
When a single session isn't enough, we continue — a standing rhythm of thinking time as the product and the company change shape.
Monthly or quarterly
Direct, founder to founder.
Embedded product & systems leadership
Occasionally a team needs the thinking held from the inside for a while. Senior product, UX and technology judgement, embedded directly — hands-on, and always me.
Past work spans fintech, healthtech and SaaS
Fractional leadership
Limited capacity. Not outsourced delivery.
Build & operate
Some products I build and run myself. They're where the ideas get tested at full cost — the evidence behind everything else on this page.
50,000+ users trained · 2,500+ training companies · 98% satisfaction · 15M+ courses delivered
Learning platforms that work for how people actually learn.
Start a conversation
Tell me where you are and what's nagging at you. A few paragraphs is plenty — context helps more than polish.
25+ years building products, including CourseCo — 50,000+ people trained. I read every note myself and reply personally within one working day.
Not ready to write a note? Book a free 20-minute call instead — no pitch, no obligation, nothing to buy at the end.