Strategy and experimentation for organizations that need to test before they commit.
On the house
Free space — you already found this page, which is most of the battle. Book a call and let's talk about the rest.
First step
Is this idea worth pursuing? Before you build, hire, or commit — find out. Most ideas don't fail because they were bad — they fail because nobody stress-tested them before the money was spent. Typical output: a written assessment with options, rough effort/cost estimates, and a recommendation. Usually two to four weeks.
Tangible output
Microsoftware, custom tools, and experiment apps — built with the people who'll use them, not at them. Off-the-shelf tools are built for the average case; yours probably isn't. Works for internal tools, academic experiment apps, and working prototypes. Built to be handed over and maintained without depending on me.
Long view
New markets, new models, sharper positioning — strategy that accounts for how the business actually works, not how the deck says it does. Typically starts with a systems check and leads to a roadmap with prioritised initiatives.
Course correction
For projects that launched and stalled. The early energy is gone and nobody's sure whether to restart, pivot, or let it die. Recovery starts with an honest read of where things actually are, and ends with a clear decision. Fast. Uncomfortable. Useful.
Fair warning
I'll use them exactly once, to prove I know what they mean, and then translate everything back into plain English for the rest of the engagement.
Also fine
Some problems need a workshop. Some just need someone willing to open the spreadsheet nobody else wants to touch. Happy to do either.
Guilty as charged
I'll say it if it's true, roll my eyes if it isn't, and never once put it on a slide unironically.
Managed, mostly
I'll figure out who actually needs to be in the room, and do my best to protect you from the ones who don't.
Caught early
The number one killer of good projects. I'll name it the moment it shows up, not three months in when it's already too late.
How we can work together
One-off
A workshop, thinking day, or intensive sprint. A defined problem, a defined output, a defined end. Good for getting unstuck or pressure-testing a specific question.
Fractional
A set number of hours per month, working on a running problem. Good when the work is continuous but doesn't justify a full-time hire. Think sparring partner with implementation capacity.
Embed
Three to six months, full or half time, inside the organisation. For complex transformations where the work can't happen at arm's length. Leaves with documentation and no dependency.
Ready to start?
Not sure which of these fits? That's what the first conversation is for.
Most engagements start with a scoping call. No prep needed — just bring the problem.