Early on I thought the goal was to eliminate all problems.
Now I understand the goal is to trade up to better problems.
"How do I get any users?" → "How do I support this many users?"
"Will anyone pay?" → "How do I manage cash flow at scale?"
The problems never stop. They just evolve.
And weirdly, that's what makes it sustainable. You're not chasing an end state. You're building the capacity to navigate whatever comes next.
#buildinpublic
Something I wish I'd definitely understood earlier
You don't need permission to start.
You don't need a perfect plan to move.
You don't need external validation to trust your own read on a problem.
The waiting is 100% the trap.
Something I wish I'd understood earlier:
You don't need permission to start.
You don't need a perfect plan to move.
You don't need consensus to trust your gut.
The people who told me to wait until I was "ready" were never going to think I was ready.
Readiness is a feeling you manufacture by starting before you feel it.
The best founders I know aren't the ones who never feel doubt.
They're the ones who feel it constantly and build anyway.
Doubt isn't the opposite of conviction. It's the tax you pay for caring enough to get it right.
If I can find 200-500 paid users within x3 months of my SaaS launch.
Paying £7-10 per month.
It will value my start up at 6figures according to my research.
Why does this seem to easy?🤣
What kills most MVPs?
A) Bad design
B) Not enough features
C) No clear behavioural signal
I’m learning it’s C.
If you can’t measure behaviour, you’re guessing.
Building a startup is mostly about:
A) Adding features
B) Making it look good
C) Designing behaviour
This week I realised it’s C.
If behaviour doesn’t change, nothing else matters.