How Working With Me Actually Goes
You get me, directly, and you get a straight answer. That’s the short version. There’s no account manager between us, no junior learning on your budget, no deck where a one-line answer would do. You bring me the decision, the plan, the quote, the thing that doesn’t smell right — and I give you my honest read with the reasoning behind it, including when the honest read is “don’t do this.” If you want to know what working with me feels like before you commit, this is it.
I find the real problem first
The first thing I do on any engagement is ignore the brief long enough to find the actual problem, because the stated one is almost never it. “We need a CRM” is usually “our data is scattered and nobody trusts the numbers.” “The app is slow” is usually three decisions made badly eighteen months ago. “We need to rebuild” is usually “one part is rotten and the rest is fine.” Solving the stated problem is the single most common way I watch people waste money, and a clear diagnosis is worth more than a fast build every time.
So expect me to ask harder questions than you were braced for, and to push back before I agree. That’s not difficulty for its own sake — it’s where the value is. The leverage in software isn’t typing faster; it’s not building the wrong thing in the first place. Get the diagnosis right and the rest gets cheap.
I have opinions, and I’ll tell you why
I don’t hedge. If you ask me what to do, you’ll get an answer, not “it depends” followed by three options and a shrug. But the opinion always comes with the reasoning, because an opinion you can’t interrogate is useless to you — you should be able to push on my logic and watch it hold or change my mind with something I hadn’t weighed.
Where I land is consistent, because it comes from the same few convictions:
- Build, don’t rent, when ownership pays. The default advice in this industry is to spend — buy the platform, rent the SaaS, add the headcount. My default is the opposite question: what’s the smallest thing you could own that solves this, and how fast can you have it? Renting forever to avoid building once is usually the expensive choice dressed up as the safe one.
- Own your data and systems. Everything points back here. Own the core and every later move gets cheaper — you can connect it, automate across it, extend it on your terms instead of paying rent for limited access to your own operation.
- MVP first. Ship the lean version, start earning from it, then compound. A six-month build before you’ve validated a single assumption is how budgets die. Get something real in front of real users fast, and let what you learn pay for what comes next.
- Simplicity over ceremony. The simplest thing that solves the real problem wins. Most of the complexity I’m asked to admire is decoration, and decoration is where projects quietly go over budget.
You’ll see these turn up in every recommendation I make. They’re not a pitch — they’re just how I think, and they’re the reason a fair number of engagements with me end with you spending less than you walked in expecting to.
The shape of it, day to day
In practice the work is conversational and direct. We agree where I’m useful — sometimes a regular rhythm, sometimes a one-off piece of judgement, sometimes hands on the keyboard. Then you bring me the things that matter as they come up, and I turn them around with a real answer rather than a process. I’ll tell you when a proposed build is twice the size it needs to be, when a tool you’re about to rent is something you should own, and when the honest move is to do less than you planned.
When I’m reviewing what your developers or your agency are telling you, I translate it into plain English you can actually act on — no jargon used to sound clever, only where it’s the precise word, and then explained. The point is that you come away understanding the decision, not just nodding along to it. That’s the difference between hiring judgement and hiring hands: a contractor builds what you ask for; I’m paid to tell you whether you should be asking for it.
Who this isn’t for
If you want someone to rubber-stamp a plan you’ve already committed to, or the cheapest hourly rate going, we won’t get on. The value here is in being told the truth about the hard calls — sometimes the truth you didn’t want to hear — and that’s only worth paying for if you intend to act on it. If what you actually need is a standing team to build and run software for years rather than judgement on the calls, that’s my agency Digital Royalty, not me — and because I run it, I’ll tell you honestly which one your problem needs.
Tell me about your problem
If you’ve got a decision riding real money and you’re not sure it’s the right one, that’s exactly what this is for. Tell me about your situation — a short conversation is usually enough for me to tell you what’s actually going on and how I’d approach it. If you want the wider context first, my story explains where this way of working came from, and experience shows the kinds of problems it’s been tested on. (Back to about.)