One process, and it lives in someone's head.
The thing your team works around. The spreadsheet only one person understands. The approval that happens in a chat thread. Write it down once, and get software that runs on it.
The problem
Nobody wrote it down, because nobody had time to.
Every department has one. The process that works because Dana knows the exceptions, and stops working the week Dana is out. It is not that the rules do not exist — it is that they exist in three places, and none of them is a system.
The spreadsheet
Twelve tabs. Formulas nobody dares touch. It is the system of record for something that matters, and it has no permissions, no history, and no way to tell who changed what.
The chat thread
Where the actual approvals happen. Searchable in theory. In practice, the decision from March is forty scrolls up and half of it was in a call.
The person
Who knows the exceptions. Who is the reason it works. Who would like, very much, to not be the reason it works.
How it works
You describe it. We write it down. Software follows.
The rulebook is the process, written once, in plain English and in a form a machine can read. You check it before anything is built. Then the database, the screens, the permissions and the docs all come from it.
Walk us through it
One conversation. We build the rulebook as you talk, so by the end you are reacting to something real rather than describing from memory.
Read it back
Every rule, every role, every exception, in words your team can read. If it is wrong, you say so, and the change is one edit.
Run on it
Screens built for the actual jobs people do. Roles that match how the department works. A record of who changed what, and when.
Most departments land on Internal App.
Each package includes everything above it, so you can start with just the model and move down later without redoing anything. Fixed price, most projects need no deposit, pay only if you like it.
Rulebook
$0
Every rule in your business, modelled and yours to inspect. Nothing to install.
Backend
$1k
A real database and API your developers own, generated from those rules.
Internal App
$5k
Working software with sign-in, roles and screens -- enough to run a department on.
Production App
$10k
The version people depend on daily: task screens, tests, docs, deployed.
What changes
Dana can take a vacation.
The exceptions live in the rulebook now, not in a person. New people learn the process by reading it. When the process changes, the system changes with it — the same day, not next quarter.
Bring the process. We bring the system.
A doc, a spreadsheet, a whiteboard photo. Whatever you already have is enough to start. You see it working before you pay anything.