Ways of working.
Almost none of what decides a project is technical. It is the rhythm, the writing down, and who is in the room when the hard choice gets made.
Five habits.
Kept from the first week, on every project, whatever it turns out to be. None of them are technical.
Async by default.
No standing meeting. A written update on a fixed rhythm, decisions recorded where both sides can find them, questions answered in writing so nobody has to remember a call.
Small and regular.
Small incremental deliverables. Regular small updates and check-ins, not one big release all at once, an invoice, and no further contact. One table a week; between the tables, the work runs on its own.
Integrated.
I work inside your tools, on your board, next to the people who will use the thing. Part of the team from the first week, not a supplier behind a ticket queue.
Finding it together.
I don't always know the right solution for the problem at hand. Often it takes a few attempts to build it, and adjustments after. That's the best part of working together: finding the right solution in the least amount of time.
Ahead of the ask.
If I can see a question coming, the answer is written down before it arrives. Handover notes before anyone has to ask who else could run this. A runbook before the first time it breaks at an inconvenient hour.
Three principles.
The code was never the hard part. Three choices, made early, do most of the work on any project worth taking.
Diagnosis, not delivery.
Most of the work is deciding what the thing actually has to be, for whom, and at what pace. Writing that sentence down takes weeks. Building from it takes days. The sentence is the deliverable; the code is downstream of it.
Architecture as respect.
The choices nobody sees are the ones that decide whether a thing feels calm. Who gets in and how. What happens when someone forgets. Where the data lives, and under whose law. What happens on the day I am not here. Get them right and nobody ever thinks about them again.
Working with what you already trust.
The tools you already use are usually fine. A thin, durable layer over them beats a bespoke system somebody has to be taught: no admin panel to maintain, no staff training, nothing new to forget how to use.
This is the part most agencies would replace with something of their own. Replacing it is usually the wrong answer.
Your time back. Not a dashboard you have to check, not a process you have to keep fed. An afternoon that is yours again, and the work you have been putting off finally getting a turn.
That is not a business outcome. That is a life outcome.
Where you can see it.
Klosterdorf is the one I can show you end to end, because it is my own: a village website rebuilt as a place the village actually owns, run on these habits, on no budget at all. The same care that paid work gets.
Read the Klosterdorf caseHow an engagement runs.
No hourly billing. Every piece of work is quoted as a fixed price before it starts, from a spec you have read.
- First
Diagnosis.
A few weeks, one fixed fee. It ends in a written spec and a first working version. You own both, whether or not we carry on.
- Then
Building.
Quoted from that spec, one delivery at a time, each at a fixed price agreed before it starts.
- After
Keeping it running.
A flat monthly fee against a named scope, so you know what is included and what is a new piece of work.
§ 05 · What this kind of work is
Bring me the thing everyone said couldn't be done. We'll sit with it until it's yours again.
One-to-one at the table to work it out. Everything you pay for goes into your product.
Found by referral, not by RFP.
Talk to Casey