Casefile · elicitation before software
Your operation already knows what software it needs.
it's written in the workarounds — read those first
Elicio is a software practice that reads the operation first — the spreadsheets, the threads, the memory, the Tuesday-afternoon workarounds — then builds the purpose-built tool the reading calls for, and stays to keep it fitting. The app is the consequence of understanding, not the opening pitch.
Exhibit A · fragmentation
One order. One Tuesday. Five places.
A composite of the operations we're usually shown: a good business, coordinated by memory and five capable tools that have never met. Illustrative, not a client — though most visitors recognize the handwriting.
“the price lives in an inbox”
“institutional memory takes holidays”
“every yes has one door”
“load-bearing stationery”
“Thursday is a rumor”
ONE ORDER · FIVE PLACES · NO OWNER
Each mark above is the same order. None of these tools is broken. Together, they are how good businesses quietly lose their Tuesdays.
The finding · constraint
The tools aren't the problem. The gap between them is.
Follow the five exhibits and they converge on a single point: every yes runs through one inbox. Stock can be counted, the truck can be booked, the client can be called — and still the whole order stands in a queue behind one person's afternoon.
This is the part that never appears in a feature list, and the part we look for first. The constraint is rarely the tool everyone blames. It is usually a person who became a system, or a decision that never got a home.
A business is never slower than its narrowest yes.
The map · understanding
Understanding, drawn — until reality agrees.
Before we write software we draw the operation: lanes, handoffs, the constraint and what it protects. Operators correct the drawing until they nod. The drawing is the first deliverable — if it's wrong, better to be wrong on paper.
DRAWN WITH THE PEOPLE WHO DO THE WORKREVISED UNTIL THEY NODCOMPOSITE · NOT A CLIENT
The software · purpose-built
Then — the software. Every screen has a reason.
Purpose-built means each part of the tool exists because of a finding in the casefile. Three marks from the reading, three parts of the build. Follow the lines.
FINDING 1
“One order, five places.”
So: one record per order. The sheet, the thread and the note stop being copies of the truth — they become views of it.
FINDING 2
“Every yes has one door.”
So: an approval gate with a rule. Small orders approve themselves; big ones show their age and fall back to a second approver before they rot.
FINDING 3
“Memory takes holidays.”
So: an exceptions lane with a named owner. Nothing waits in a head, on glue, or behind an out-of-office reply.
| ORDER | CLIENT | OWNER | STAGE | STATUS |
|---|---|---|---|---|
| 1041 | Ferrer S.L. | Dana | delivered | done |
| 1042 | Braun GmbH | Luis | approval | waiting · 2d |
| 1043 | Atelier N. | Marta | packing | truck Thu |
| 1044 | Ferrer S.L. | Dana | intake | new |
Approvals oldest · 2d
rule: < threshold auto-approves · > 4h old falls back to Ana
Exceptions
every exception has a name on it — nothing lives in heads
The engagement · how we work
Five stages. The app is the fourth.
-
Understand the real operation
We sit with the work — the real one, not the org chart's version. We read the sheets, the threads, the workarounds, and we ask what breaks on the worst week of the quarter.
-
Expose the constraint
We name it out loud, with evidence. Sometimes it's an inbox. Sometimes a person who became a system. It is almost never the tool everyone blames.
-
Map the work around it
We draw how work should move — and revise the drawing with the people who do the work, until it agrees with reality. The map is a deliverable you keep, whatever happens next.
-
Build software that fits
Then, and only then, software: small, fitted, opinionated about what it refuses to do. Built to hold the map — not to impress in a demo.
-
Maintain and improve it
Operations drift; software should drift with them. We stay — watching the fit, adjusting the rules, retiring what stopped earning its place.
When to call
You'll recognize the moment.
The plan lives in five places, and the truest copy is in someone's head. Coordination happens in messages, spreadsheets, approvals and memory — and it mostly works, which is why it's dangerous.
One person became a system. When they're on holiday, a part of the company is on holiday with them. Everyone knows who it is. Nobody says it in meetings.
The weekend tool became load-bearing. Someone capable built a sheet or a small app in a weekend; the business grew around it, and now it has reached the edge of what it was ever meant to hold.
The symptom is visible; the cause isn't. You can point at the late orders or the long Fridays, but not yet at the constraint that produces them. That gap is exactly where we start.
If any of these read like your Tuesday — that's the moment.
The invitation
Bring us one messy week.
We'll bring the red pen. The first conversation is a reading, not a pitch — and the drawing it produces is yours to keep.