The platform
One mechanism underneath everything.
Oko has no modules. You define objects, characteristics give them behavior, and every operation a characteristic carries becomes available wherever it’s attached. That one mechanism is the whole platform — and it’s why Oko can be a single source of truth for your entire business, not another point solution for a slice of it.
Why primitives, not features.
Most operational work shares a handful of shapes. Something moves through stages toward a close. Someone owns it. Rules gate it. People and places attach to it. History accrues on it. Build those shapes once, as primitives that already know how business works, and one system can hold any business — a law firm, a factory, a fund — without becoming a different product for each. That’s the design bet, and every part of Oko is built on it.
- deals
- matters
- work orders
- hires
- purchases
- campaigns
- properties
- units
- leases
- shipments
- filings
- crews
- vendors
- people
- sites
Relabeled, not reprogrammed — every one of these is the same primitives wearing a business’s own words, inside one boundary.
Your words, not ours.
Most systems make you adopt their nouns: a hire becomes an “opportunity” the moment you want a pipeline, and the process bends around the tool’s assumptions. Oko doesn’t have that layer. You name the objects, the stages, and the parties in the language your business already speaks — and every behavior still works.
Why this shape wins
Capability compounds.
Operations live on the primitive, not the object. The website primitive knows how to fetch a page’s metadata — so every object that carries a website can do it, and so can Nomi, on every one of those records. Capability doesn’t add up feature by feature. It compounds.
| objects ↓ · primitives → | 10+ more | |||||
|---|---|---|---|---|---|---|
| opportunities | ··· | |||||
| hires | ··· | |||||
| purchases | ··· | |||||
| matters | ··· | |||||
| vendors | ··· |
Nomi inherits 11 operations from these five primitives alone
- deal — advance stages · set offer & final amounts · report the pipeline
- workflow — evaluate rules · gate moves & approvals
- contacts — link people to any record · answer who-questions
- website — fetch metadata · keep links fresh
- address — geocode · map & route
- Every primitive adds its operations to every object that carries it — the grid only grows.
Operations attach to the primitive, not the object. A tool added once is inherited everywhere at once — which is why capability compounds instead of adding up.
Opening soon