Start a project
Bring the problem in whatever shape it is currently in. Half-formed is fine — the first job is usually working out what the question actually is.
Before you write
Things people usually ask first.
Straight answers about money, ownership, timing and what happens when things go wrong — so you can decide whether to talk to us before you spend the time.
The first engagement — mapping and recommendation — is fixed price, because its scope is fixed. Build phases are either fixed-scope increments or a monthly embedded team, whichever fits how you work. Every proposal states what is in, what is out, and what would change the number. There are no time-and-materials surprises at the end of the month.
Usually within two weeks of a first conversation. The first phase needs access to the right people and systems more than it needs us, so if you can put us in front of the people who actually run the process, we can move quickly.
Yes, and we prefer it. We work in your repositories, your tools and your rituals rather than asking you to adopt ours. The measure of a good engagement is that your team can run and extend what we built after we leave.
Then that is what you get. The six disciplines exist because real problems rarely stay in one lane — not because every engagement needs all six. If the honest answer is that you need a website and nothing else, we will say so.
Yes. Send yours or use ours. We will never ask you to describe a sensitive problem in depth before one is in place.
You do. Code, designs, documentation, models — everything produced for you is yours on payment, with no licence-back and no dependence on us to operate it. Dependency is not a business model we are interested in.
Whichever fits the task: hosted frontier models, open-weight models you run yourself, or small fine-tuned models where latency, privacy or cost matter more than raw capability. We are not tied to a vendor and we will show you the trade-offs rather than a preference.
Remote-first, working across IST, CET and ET. Most clients never need us in a room. When they do, we travel.
We say so, early. Every engagement has defined checkpoints where either side can stop cleanly. We would rather lose a project than keep billing for something that is not delivering — and we will hand over everything we have done properly either way.