Start with the problem
The first conversation is not a sales call. You describe what you're dealing with — the workflow that's breaking down, the system that's fighting you, the thing your team keeps working around — and I ask questions until I understand it. Whether that leads to an engagement is a separate decision we make afterwards, and it's fine if the answer is no.
Ways to Reach Me
Use whichever channel suits you. A few sentences about your situation are enough to start — what the business does, what's going wrong, and roughly what prompted you to look for help now. You don't need a brief, a budget, or a technical vocabulary for it.
What Happens Next
No process theater — just three honest steps between your first message and a decision. Most of it happens in one call.
Understand
I start by learning how your business actually works: the workflow in question, who runs it, what it costs when it goes wrong, and which constraints are fixed. Expect specific questions rather than a pitch — I can't evaluate a problem I don't understand, and neither of us should commit before that.
Evaluate
Then we decide together whether I'm the right fit. That's a real question, not a formality: some problems need a different specialist, some are solved better by an off-the-shelf tool, and some aren't worth solving with software at all. If any of those is true, I'll say so and point you somewhere more useful. A clear "no" early costs us one conversation; a wrong "yes" costs you months.
Plan
If it makes sense to continue, I'll explain how I would approach the work: what I'd do first, what I'd need from your side, and how you'll see progress. You'll have enough detail to judge the plan on its merits — and to take it elsewhere if you'd rather.
Availability
Current availability is below, and it's kept honest — it's the same status shown across this site, updated when it changes rather than left saying "available" forever.
Available for new projects· updated September 2026
You don't need a fully defined problem to reach out. “Something is wrong with how we handle X and I can't tell what” is a perfectly good starting point — turning a vague pain into a precise problem is the first part of the work, not a prerequisite for it.