Delivery
See the job.
Write it down.
Hand it over.
Corvux skips invented case studies. This is the path we run: scope, a copy of your data, a human in the loop, a runbook you can keep.
Buyers in Nairobi have been burned by decks. So we skip logos we lack permission to use, and we skip inventing “40% faster” stories. How we work is the product promise: a written scope, a copy of your data, a person who can say no to a bad model output.
01
Show us the job
A file, a queue, a PACS folder, a WhatsApp line. Who does it today. What “done” looks like on a bad day, on a real day, away from demo day.
02
Written scope
In, out, hosting (your machine, any cloud, or Kenya GPUs), and who clicks approve. If it is a two-day script, we say so.
03
Build on a copy
Sample rows, a week of tickets, de-identified images. Production credentials come last.
04
Handover
Runbook, who to call, and the eval you re-run when the input format drifts. See pricing for how that is billed.
Regulated work still starts with where data already leaks. Medical image work is assistive, clinician-reviewed. A hospital, a bank, and a law firm each hold their own licence. We build the software.
Walk us through one messy week
That is enough to tell you if this is a script, a desk, or a private stack.
Start a scope