How I Work
Most consultancies arrive with an answer already picked out. I'd rather start with your problem, and stay honest about whether technology's actually part of the fix.
Listen
I start with a conversation, not a pitch. I want to know what's actually slowing you down - not what tech you think you need.
Understand
I spend time with the people who'll actually use whatever we build - your team, your customers, your residents. Good ideas come from how work really happens, not how it's supposed to.
Prototype
Instead of a long proposal, I build something you can see and react to, often within days. Sometimes that's a piece of software. Sometimes it's a workshop, or a different way of working with no new tech involved at all.
Test
I test it against real use, not assumptions. If it doesn't work, we've learned that cheaply - before anyone's committed a big budget to it.
Scale
If it proves itself, we grow it together. I'd rather be an invested partner than a consultant billing days - I want it to keep working, not the engagement to run long.
So the first conversation isn't a sales pitch. It's the start of figuring out whether - and how - I can actually help.