The same people
Interface, logic and the build do not travel between departments. They stay in the hands that drew the button.
how we work
The simplest thing that works comes first. Then a problem shows up. Then the next layer. Not the other way round: an architecture invented up front usually describes an idea of the system rather than the system.
If a spreadsheet solves it, we will say that a spreadsheet solves it. A database earns its place the moment the spreadsheet starts getting in the way — and not a minute earlier.
We do not take on a project whose workings we do not understand. That is cheaper for everyone: a problem nobody understood surfaces anyway, only later and at a worse price.
what we do ourselves
- interface layout, type, speed
- logic flows, state, agents, knowledge bases
- connections forms, requests, other people’s APIs, spreadsheets, Telegram
- operations servers, deploys, domains, redirects, logs
The designer, the developer and whoever fixes the server at night are not three emails and two approvals. Usually they are one conversation.
lemma — a small statement proved on the way to proving a larger one.