Section 1: The trap of "just build it"
Almost every founder who reaches out to us opens with a feature list. They've already drawn the screens in their heads. They want a quote, a timeline, and a kickoff date. It's tempting to oblige — building is what we're good at, and the work is right there waiting. But the moment a partner shows up with a fully formed solution, our first instinct is to put the keyboard down and ask why.
"Just build it" feels like momentum, but it almost always hides an untested assumption. The features sound concrete. The strategy underneath is usually a vibe. When the build is done six months later, the metrics don't move, and nobody can quite explain why, because nobody agreed on the metric in the first place. The cheapest mistake in our industry is shipping the wrong thing beautifully. Strategy isn't the brake on the build — it's the steering wheel.
Section 2: Define the BHAG before defining the features
We borrow a habit from the old Collins playbook: name the Big Hairy Audacious Goal first, and let the build fall out of it. At European Eye Center, Project Grow started not with a Figma file but with a one-room workshop and four questions on the wall. The team had to answer them in their own words before we wrote a single ticket.
- Why do you want to grow — what changes for you, your team, and your patients if this works?
- What outcomes matter in 12 months — the two or three numbers you'd be proud to point at?
- What's the single biggest constraint between today and that future — people, capacity, conversion, or trust?
- What would guarantee failure — the thing we must not do, even if it feels productive?
None of those questions are about software. All of them shape every line of code that comes later. By the end of the day, the team had a one-sentence BHAG and a shortlist of constraints. The feature list shrank by about two-thirds, and the remaining items finally had a reason to exist.
Section 3: Where the data goes first
Before we set targets, we look at what's actually in the system. At European Eye Center this meant pulling three years of appointment, referral, and procedure data into one place and trying to draw the simplest possible funnel. It fell apart within an hour. Procedures were categorised differently across two clinics. Referral sources had been a free-text field for years. About 11% of records had no outcome recorded at all.
This is normal, and it's the most important quiet step. You can't pick a bottleneck if you can't see the pipeline. So the first week of Project Grow wasn't design or development — it was a small data-cleaning sprint, a shared taxonomy, and a one-page glossary the whole team signed off on. Nothing in the product changed yet. Everything that came after got easier.
If your dashboard disagrees with your front desk, the dashboard is wrong. Fix the source, not the chart.
Once the categories were consistent, the funnel finally rendered. And the answer surprised the leadership team: the leak wasn't where they thought it was. They had been ready to invest in top-of-funnel marketing. The data pointed somewhere else entirely.
Section 4: Pick the bottleneck, not the menu
When the funnel showed itself, the constraint was unambiguous: roughly four out of ten patients who booked a consultation never converted to a procedure, and the gap between consultation and decision was, on average, 17 days. That's not a marketing problem. That's a follow-up and confidence problem. Every euro spent on more top-of-funnel ads would have widened a leak we already had.
So we made a hard call: we built the post-consultation follow-up experience first, and we explicitly deferred everything else. That meant saying no — out loud, in writing — to a handful of things the team genuinely wanted.
What we deprioritized
- A redesign of the public marketing site (real, but not the constraint)
- An Instagram lead-gen campaign (would feed a broken middle)
- A second booking widget for partner referrers (nice, not now)
- A loyalty programme for returning patients (premature; solve conversion first)
Want this approach for your business?
We run strategy-first kickoffs for founders who want to grow without shipping the wrong thing beautifully.
Section 5: What we shipped first
The first release of Project Grow was deliberately small. A patient-facing decision portal that picked up after the consultation, kept the surgeon's recommendation visible, answered the five questions the front desk heard most often, and made it one tap to book the procedure or ask another question. On the operations side, a lightweight queue so coordinators could see exactly who was in the 17-day gap and where each person had paused.
No dashboards, no scoring algorithms, no AI assistant. Just the smallest believable version of the follow-up experience, instrumented end-to-end so we could see whether the bottleneck actually moved. Two weeks after launch, the average decision window had dropped to 11 days. By week six, it was under nine.
Section 6: The compounding effect of strategy-first builds
Strategy-first work feels slow in week one. It feels fast by month three. Because the team built the right thing, the next decisions get easier — you know which experiments are worth running, you know which numbers to watch, and you know what to ignore. Every later release at European Eye Center has been smaller, cheaper, and more confident than it would have been if we had started with a feature list.
This is the part we keep coming back to: the build is never the hard bit. The hard bit is being honest about what would actually make the business move, and being willing to ship less so that the part you ship matters. That's the loop we try to run with every partner, and it's the reason we ask uncomfortable questions on day one.