Approach
A product is never finished. It is tended.
The ensō is drawn in a single breath and deliberately left open. That is the closest thing we have to a description of software: complete enough to be useful, never actually closed.
What we believe
Most software problems are not coding problems. They are problems of scope, of sequence, and of nobody being clearly responsible for whether the thing works.
Selling development hours makes that worse. Hours are easy to measure and tell you nothing. A team can be fully booked for a year and leave a product in a worse position than it started.
So the unit of work here is the product, and the first question is always the same one: where is this thing actually, right now? Answer that honestly and the correct next move is usually obvious.
How the work goes
-
Name the situation
Idea, wreck, or working product. Getting this wrong is the most expensive mistake available, because every later decision inherits it.
-
Agree what better means
Before scope, before estimates. If we cannot say what should change in the world, we cannot tell afterwards whether the work mattered.
-
Find the smallest honest version
Small enough to build and release soon, complete enough that the result actually tells you something.
-
Build it properly
Conventional tools, boring choices, code that the next person can read. Cleverness is a cost paid by whoever comes after.
-
Read the result
Measure what happened, including the parts nobody predicted, and let that set the next round rather than the original plan.
Who does the work
You'll be working with the people building it.
EnsouWorks is a founder-led studio. The person who answers your first email is the person who does the work — there is no account manager in between, and nothing gets handed down to someone more junior once the contract is signed.
That shape is deliberate, and it has a cost we accept: we take on a small number of engagements at a time. It also has the benefit you're actually buying — the person making the technical decisions is the person who heard you describe the problem, and who will still be there when the consequences of those decisions arrive.
When an engagement genuinely needs more hands, we bring in senior people we have worked with before, and we say so before they start. We don't quietly grow the team to grow the invoice.
The three practices
One company, three situations.
A product can move between them in any direction, and often does.
The ensō is drawn in one breath and left open on purpose. So is this process: complete enough to be useful, never pretending to be finished.
Start here
Tell us where your product is, and we will tell you what we would do next.
No pitch deck required. A short description of the situation is enough for a useful first conversation.