Advice is cheap when it comes from nowhere. These pages set out what I actually learned founding Wocal (300+ venues, £2.7M pre-money) and Co-Ride, and working inside Just Eat, Sage and Echo-U — and how each lesson changes what I would do in a seed-stage company today.
I could write these lessons as a list of abstract principles and they would read fine. But principles detached from where they were learned tend to flatten into platitudes — "listen to your customers", "measure what matters" — the kind of thing that sounds true everywhere and changes nothing anywhere. So instead I've organised what I know by the place I learned it: a two-sided marketplace at Just Eat, a churn-and-renewal business at Sage, a support queue at Echo-U, a venue SaaS platform I founded and scaled myself at Wocal, and a carpooling platform I'm building right now at Co-Ride.
Each of these is a different kind of company with a different kind of pressure. Just Eat taught me about liquidity and network effects at a scale I couldn't have simulated. Sage and Echo-U taught me what actually decides whether an enterprise customer renews, and how often that decision has nothing to do with the product roadmap. Wocal taught me what it costs — in time, attention and money — to build and sell something from nothing, and what a founder does differently from an employee with a similar title. Co-Ride is teaching me, in real time, how much of that earlier learning transfers to a different market and a different kind of network.
What carries across all of them is less a technique than a discipline: watch what people actually do, not what they say they'll do; be honest about which metric you're really optimising for; and treat every "obvious" feature request as a hypothesis to test rather than a instruction to follow. The detail below is where that discipline came from.
WOCAL · 2020–2025 · FOUNDER & CHIEF PRODUCT OFFICER
I founded Wocal in 2020 and grew it to more than 300 venues, eventually reaching a £2.7M pre-money valuation before it wound down in 2025. The lesson that stayed with me longest isn't a growth tactic — it's how much of a founder's job is deciding what not to build. Every venue owner had a different idea of the one feature that would fix everything, and most of those ideas were wrong for the platform even when they were right for that one venue. Holding the line on a smaller, more coherent product than the market kept asking for was harder than raising the round or landing the accounts. I also learned how differently founders and employees experience the same problem: when the product doesn't work, there's no other department to blame, and no roadmap that survives contact with a venue owner who needs it to work tonight.
See how this shapes my product philosophyJUST EAT · 2021–2025 · ENTERPRISE / PARTNER SALES
Four years at Just Eat, working the marketplace and partner side, showed me how a two-sided platform actually behaves once it's operating at national scale. Liquidity isn't a company-wide number — it's a local, postcode-by-postcode problem, and a platform can look healthy in aggregate while failing badly in specific areas. I also saw how much of what looks like a product decision is really an operational one: courier availability, restaurant onboarding capacity and support load shape the customer experience as much as any feature does. And watching which metric leadership actually reported on told me more about the company's real priorities than any strategy deck did.
Read the full Just Eat lessonsSAGE · ENTERPRISE SAAS
Sage put me in front of enterprise buying decisions repeatedly enough to see the pattern behind them: the person who buys the software, the person who uses it every day, and the person who pays the invoice are often three different people with three different sets of incentives. A feature that delights the daily user can still lose the account if it doesn't answer the buyer's question or justify the payer's cost. I also learned that churn is rarely decided at the renewal conversation — it's decided much earlier, in how the first weeks of use go, and by the time a renewal call happens the outcome is usually already set.
Read the full Sage and Echo-U lessonsECHO-U · CONTACT CENTRE / CUSTOMER SERVICE
Working close to a contact centre at Echo-U changed how I read support data. A support queue isn't just an operational cost centre to be minimised — it's one of the richest, least-used sources of product research a company has. The questions customers ask repeatedly, the workarounds support staff invent because the product doesn't do what it should, and the complaints that get resolved without ever reaching product or engineering are all signal that most roadmaps never see. I try to make sure any product I'm involved with has a direct, un-filtered line back into that queue, rather than a summarised version that's already had the awkward edges removed.
More on this in the Sage and Echo-U lessonsCO-RIDE · NOV 2025–PRESENT · PRE-SEED · FOUNDER & CPO
Co-Ride, a community carpooling platform I'm building at pre-seed, is where I'm actively testing how much of the Wocal and Just Eat experience genuinely transfers. Carpooling has its own liquidity problem — drivers and riders both need to trust the network before it works for either of them — and it's a different shape of two-sided market than food delivery or venue software. So far the clearest carry-over isn't a specific tactic, it's the habit of designing the smallest possible test for a network effect before committing engineering time to it, and being honest early about which assumptions are still guesses.
See how this fits the Crossley Method2021-2025 · Marketplace
Liquidity is local, operational cost dominates engineering cost, and the metric a company optimises explains its behaviour better than its roadmap.
ReadEnterprise SaaS · Contact centre
Support queues as product research, churn decided in the first thirty days, and why buyer, user and payer are three different people.
ReadPrinciples
Subtraction over addition, evidence over opinion, one metric with one owner, weekly contact with a real customer, and engagements designed to end.
ReadFramework
The seven-stage framework these lessons feed into: Discover, Validate, Prototype, Build MVP, Launch, First Revenue, Scale.
ReadTHE FRAMEWORK
EXPLORE NEXT
Every stage from first idea to first revenue, mapped end to end.
How I lead product, stated plainly.
Read moreThe seven-stage framework that takes an idea to first revenue.
Read moreBoard-level product advice, audits and investor due diligence.
Read moreRetention, expansion and pricing for B2B SaaS products.
Read moreProduct leadership on retainer for pre-seed and seed teams.
Read moreDirect answers to the questions founders ask about product, MVPs and AI.
Read more