martin laws
I help founders figure out what to build next — and then actually ship it.
For design-minded founders whose stack wasn't built for the AI era.
Now booking for Q3 2026.
You need technical leadership with real judgment about the product, not just the code.
You need someone who can sit across from your customers, designers, engineers, and board of directors — and translate between them.
You need someone who can use the latest AI to build real software — not just vibe-coded prototypes.
And you need someone you'd actually want to see on the other end of a Zoom call at the end of a hard day.
Most consultants jump straight to building. I don't. Clarity comes before code — naming the right problem is most of the work.
I work hands-on in the codebase and hands-on with the strategy. Most people sell you one or the other.
My incentives are aligned with yours: I get paid to help you make the smartest moves, even when that means recommending the simpler option.
Understand → decide → it's yours
Understand, diagnose, decide together, plan, show you working proof — and at the close, the whole body of work is yours. Here is what that actually looks like.
I show up already informed.
Before we talk, I've drafted my read of where you are — so we start from a working hypothesis, never a blank page. Your twenty minutes just tell me where I'm warm and where I'm off.
The floor is yours → I listen firstThe real bottleneck(s), named.
The Week-1 diagnosis: not the symptoms, but the thing or two underneath — written as a brief so clear anyone can read it once and finally see the problem plainly.
I have it from here — then your pushbackAn honest pause at the midpoint.
We stop together after Week 1 and look at what we found. Week 1 defines what to prototype; Week 2 builds it. If the diagnosis has earned the build, we keep going — and if it hasn't, you decide before Week 2 and we wrap with the clarity you already have. Either way is a good outcome.
The path out, ordered by leverage.
Every move plotted on effort and impact — my read seeded first, then we calibrate it together until the order is one we both believe.
Don't tell you, show you.
Once we commit, the plan becomes something you can click — real visuals and working code, not another deck. You feel the idea instead of reading about it, and we steer from there.
Everything is yours to keep.
The brief, the roadmap, the visuals, the prototypes, the working code — the whole body of work leaves with you. Not a hand-off document; everything we made, plus an optional walkthrough where I talk through the thinking.
Clarity before code, an honest pause to decide together, proof you can click, and a body of work that's entirely yours — that is the whole way of working.
The menu
Two fixed-scope, two-week sprints to get unstuck — then a longer Build when you're ready to ship. Not sure where to start? Pick the last option and I'll help you find it.
Clarity — a written verdict on what to build, and why.
A demoable, video-ready prototype on a live URL.
Production software, shipped — with me in the codebase.
Not sure which fits?
Tell me what's going on and I'll point you to the right next step — or we'll figure it out together on a call.
From designers, engineers, and leaders I've worked alongside.
Martin is the person you want to work with. He knows design and front-end inside and out, cares deeply about accessibility — and he's a natural leader who gets stuff done.
One of the best technical leaders I've worked with — charismatic and seriously capable. I'd jump at the chance to work with him on anything.
It's rare to find deep development expertise paired with the ability to communicate across disciplines. His humour could cut the tension in any difficult meeting.
I wouldn't be where I am without Martin. He keeps who people are at the centre of the solution — and his confidence is infectious.
Fifteen years across product teams, studios, and my own builds — promoted by outcome, not by logo count.
Stabilized the team and roadmap, rebuilt the tech stack from the ground up, then hired their long-term CTO before stepping back to advisor.
Designed and shipped the complete event presence as one team with Gev Design — site, system, and assets, on a conference date that could not move.
Joined as the technical partner alongside Gev Design and took it from zero to launch — product direction, stack, and ship.