The deal primitive
Sales calls it a deal. HR calls it a hire. Procurement calls it a PO.
Think about them from first principles and they’re the same shape: two parties, an offer amount and a final amount, contract start and end, stages that progress toward a close, and a pipeline you report on. Oko ships that shape once, as a primitive — and every pipeline in your business gets it.
The same shape, three businesses
Sales
Acme relaunch
Acme Co
Juniper expansion
Juniper Ltd
Meridian rollout
Meridian Co
Halcyon renewal
Halcyon Inc
Foundry pilot
Foundry Bros
Baseline retainer
Baseline LLC
Hiring
Staff engineer
R. Osei
Ops manager
T. Laurent
Account exec
M. Reyes
Design lead
K. Tanaka
Support lead
A. Novak
Data analyst
J. Whitfield
Procurement
Data warehouse
Northwind Data
Fleet leasing
Arrow Fleet
Payroll platform
Ledgerline
Security audit
Bastion Sec
Office fit-out
Formwork Co
Support tooling
Deskbound
One primitive, three businesses. Each board is the same object with the same deal characteristic attached. Only the names change.
The anatomy of a deal.
Attach the deal characteristic to any object you define and it carries the full shape. None of it is hardwired to sales — a hire has an offer too; a purchase has contract terms too. The primitive knows that.
- partiestwo — yours and theirs, relabeled per object
- amountsoffer · final
- contractstart · end
- stagesyours, with automation and gates
- closedate · outcome
- reportingpipeline, by stage and value
You run more deals than you call deals.
An opportunity pipeline is a deal. An employment pipeline is a deal. Buying software is a deal in a procurement setting. So are renewals, partnerships, and fundraising — two parties, a value, stages toward a close. Once the shape is a primitive, every one of them gets pipeline reporting, stage automation, and an operator that can work it.
Deals are one primitive in the vocabulary — people, places, channels, structure, and memory work the same way.
See all the primitivesOpening soon