Contact
Tell me where it breaks.
No forms and no funnel — one address that I read. Describe the process and the friction, and you will get a direct answer about whether technology helps.
Useful to include
- What the process looks like today, step by step
- Where it slows down, or where mistakes get in
- Who it affects, and how often it happens
- Any constraint that rules options out — IT policy, budget, timeline
What happens next
- 01
You describe the problem
In whatever form you have it. A paragraph is enough to start.
- 02
I ask about the workflow
Usually a short exchange to understand where the time and errors actually go.
- 03
You get a straight answer
What I would build, roughly what it takes — or that software is not the right fix here.
I don't only write code. I understand the problem, map the workflow, and build the technology that removes the friction.