Start with the thing people touch
I prototype the interface first. It is the fastest way to find out whether an idea holds up, and it surfaces the hard questions while they are still cheap to answer.
Interface first, schema second.
I design and build the software I want to exist.
Independent product engineer. I take ideas from a rough sketch to something people actually use.
What I'm building
Three products, each one started because I ran into the problem myself.
Visionary Technology
A software studio. Product strategy, architecture and delivery for teams putting something new into the world.
visionary.technology →
DopeTech
Tooling for people who build with AI, shaped by how the work actually goes.
dopetech.ai →
Dealt
Field service operations, rebuilt around the people doing the work rather than the paperwork.
dealt.io →
How I work
Two habits that decide most of the outcome before the first line of production code.
Ship in small, reversible pieces
Every release should be small enough to hold in your head and easy to roll back. Momentum comes from shipping, not from the plan to ship.
Small diffs, short feedback loops.
Writing
Read everything at jesh.io →
2026
The prototype is the spec
Why a clickable draft settles arguments that a document never will.
Read → 2026Small teams, short loops
What changes when the person deciding is also the person building.
Read → 2025Building tools you will use tomorrow
The shortest path to a product worth keeping is needing it yourself.
Read → 2025Notes on shipping alone
Scope, energy and the parts of the job nobody warns you about.
Read →Most software fails long before the code does.
It fails at the point where someone decided what to build. That decision is the part of the job I care about most, and the part I want to be in the room for.
Have something you want built?
Tell me what you are trying to make and where it is stuck. I read every message.
mail@jesh.io