The Story
A pianist and technologist who became the UK’s highest-rated events performer within a year. The combination of good thinking, sharp systems, and a completely different approach to the business did what raw talent alone never could. That same combination is what Good Thinking is built on.
The Backstory
1,200 competitors.
Built better systems
than all of them.
No agency, no marketing budget. Just a decision to out-engineer everyone else. Better booking flow, faster response times, smarter follow-up. When you can't outspend the competition, you out-build them.
It’s like being obsessed with climbing a mountain, only to realise at the summit that what you loved was the climb, not the view.
That obsession transferred completely. First a chatbot for a small business with a customer service backlog. Then data connections between disconnected tools. Then automation layers, dashboards, booking systems, management platforms. What started as helping one business now serves tens of thousands of people every month. The approach hasn’t changed: understand the workflow first, then build to fit it.
What's Been Built
Work starts with the real problem — usually a chatbot, a flow, or one painful manual process. From there it grows: automated sequences, booking systems handling thousands of transactions, dashboards that give teams actual visibility. Each build comes from something that was genuinely broken.
The systems built here now serve tens of thousands of people every month — chatbots fielding over 60,000 conversations a year, booking flows processing real money, automated messages reaching audiences reliably every day. None of it required a big tech team or a big budget.
Every project starts by mapping the actual workflow before touching any code. That's why the things built here stay stable and teams can run them without depending on the person who built them. Minimal input in. Maximum value out.
The Process
Before any code gets written, the real day-to-day gets mapped: what your team does, where the friction is, and what's been tried before. The build follows from that, not from a template.
Each stage delivers something visible you can test and sign off. No black boxes. No surprises. You stay in control of scope and can adjust priorities before anything expensive needs rewriting.
Handover, training, and support paths are built into the project from the beginning, not bolted on after go-live. Your team can take ownership quickly, without ongoing dependency on an external developer.
Next Step
Tell me what’s driving you mad. I’ll come back with a plain answer on how to sort it. No pitch, no jargon.
Start by email →