BookedIn build notes — finding the positioning
How a generic CPD platform became something nursery owners actually felt was built for them. The repositioning, in steps.
Most platforms don't fail because they don't work. They fail because nobody feels like they were built for them.
BookedIn nearly became one of those platforms.
The original positioning (and why it made sense)
At the start, BookedIn was positioned as a platform to book CPD speakers, consultants, coaches, mentors, and training.
On paper, that's solid. It's clear. It's logical. It's technically accurate.
But it's also exactly the problem.
Because it describes what the platform does — not why someone would actually use it.
The friction was always there
The shift didn't come from a single idea. It came from repeated exposure to the same problem from different angles.
Inconsistent expectations, last-minute changes, and very little structure across the sector.
Back-and-forth emails, chasing availability, and constant uncertainty around quality.
Watching the same friction surface again and again — across roles, across organisations, across years.
And then there was the moment that made it undeniable.
The moment it clicked
A webinar speaker pulled out last minute.
No backup. No visibility on alternatives. No system to rely on. Just a scramble.
That's when it became obvious:
This isn't a discovery problem. It's a system problem.
Because the issue wasn't "where do I find a speaker?" — it was "why does this entire process feel so unreliable?"
What nursery owners were actually saying
Conversations with nursery owners reinforced the same thing. The frustration wasn't about access. It was about everything around the booking itself.
This just feels harder than it should be.
That's the real insight.
The reframe
| Was solving | Is actually solving |
|---|---|
| A platform to book CPD | The friction behind CPD booking |
| Discovery of speakers | Confidence in the decision |
| Listings and profiles | A reliable booking system |
| Serving "everyone" | Serving decision-makers, not browsers |
- Is actually solving
- The friction behind CPD booking
- Is actually solving
- Confidence in the decision
- Is actually solving
- A reliable booking system
- Is actually solving
- Serving decision-makers, not browsers
That distinction changes everything.
The repositioning — step by step
This didn't happen overnight. It was a series of deliberate shifts.
From "platform" to "system"
"Platform" is broad, abstract, generic. "System" is specific — it implies structure, consistency, reliability.
BookedIn became a CPD booking system. Not a marketplace. Not a directory. A system that removes the mess behind the process.
From "features" to "friction"
The original focus was on speaker profiles, listings, browsing. But that's not what people actually care about.
The messaging shifted to the messy middle: back-and-forth emails, unclear availability, pricing confusion, last-minute cancellations.
From "everyone" to "nursery owners"
The original positioning tried to serve broadly — organisations, educators, trainers. That diluted the message.
The shift was simple: build something nursery owners feel is specifically for them. Speak their language. Understand their constraints. Design around their reality.
From "access" to "confidence"
The most important shift. People don't just want access to speakers — they want confidence in who they're booking, reliability, clarity in decision-making.
That's the real product. Not access. Confidence.
What changed as a result
Once the positioning became clearer, everything else followed.
- Product decisions became easier
- Messaging became sharper
- Direction became more focused
Because there was now a filter:
Does this remove friction… or just add another feature?
What we're learning
The mistake is thinking "if the product makes sense, people will get it." They won't. It needs to feel obvious, relevant, and built for them.
The real shift
BookedIn didn't evolve by adding more functionality. It evolved by getting closer to the problem.
The takeaway
Most products start too broad. Too feature-led. Too focused on what they do.
The real work is narrowing. Clarifying. Reframing.
The difference between "this looks useful" and "this is exactly what I need" is positioning.
What comes next
This isn't the final positioning. It's a step. But it's a critical one.
Because once you understand the real problem… you stop building features. And start designing systems.
The Console — my personal newsletter, in your inbox.
Long-form pieces, frameworks, teardowns, and the thinking behind what's being built. Stay close to the work — and to what's next.
Read by founders, operators, and people building what's next.
Education is infrastructure
What I've learned building in EdTech: the products that endure treat learning as compounding infrastructure, not content.
Read articlePositioning comes before product
Why founders who chase features before clarity end up rebuilding twice — and how to sequence the work correctly.
Read article