How I work
Value now, not perfection later. A working first version, improved from real use.
Big technology projects often fail the same way: months of planning, a long build, a big launch, and a system that no longer matches what the business needs. Meanwhile, the costs keep running.
I work the other way round.
The principles
Build first
A working first version, as early as possible, often in a build session in your office. Real feedback beats speculation.
Evolve, don't perfect
Improve the system from how it's actually used. Each step has to earn its place. Features nobody needs never get built, so you never pay for them.
One person, start to finish
Because I've worked in development, project management, consultancy, design, DevOps and security, a project stays with one person who understands all of it. Fewer handovers, fewer misunderstandings, faster delivery.
Common sense
The best solution is often the simplest one that works. Sometimes that's a new system; sometimes it's a better use of what you already have.
How a project runs
- A free conversation. What's slowing you down, and what would make the biggest difference?
- A build session. A working first version of one idea, built with you. How it works
- Agree the next steps, and their cost, before any further work
- Build in steps, each one useful on its own, with you trying each as it's ready
- Hand over clearly. You keep your systems, your data and the documentation
Working together
- You deal with me, directly. No account managers, no handoffs to juniors
- On site or remotely across the UK and Europe; further afield remotely, or on site with travel costs
- Your data is treated with care: how I handle data and AI