Every business is built from the same few building blocks
A handful of simple but flexible primitives, each answering a question no other can — and everything a business does composes out of them. Coordinator brings those building blocks to you as software, which is why the product feels different to use.
The base case: structured facts — a contract, a spec, an intake, a note. Records persist; they never 'complete'. Everything else has to earn its way out of being a record.
In the product: Typed documents with custom fields, forms that produce them, files that become findable facts.
A contact points at something real that can act — a person or a company. That's what a record can't do, and it's why a contact can pay you, book you, sign for you… or turn out to be a whole business on the network.
In the product: One address book referenced by every invoice, project, booking and thread — and the seam that makes cross-company work possible.
Work exists in order to be completed — it's ephemeral by design, where a record is built to persist. From that one property everything follows: someone must do it (assignment), by when (dates), taking how long (estimates, time).
In the product: A project, a task, a candidate pipeline and a homework batch are one object at different scales — so stages, templates, approvals and mirroring were built once and work everywhere.
A message always has a counterparty — it exists between parties, which a record doesn't. So messages carry participants, read state and delivery, and attach to whatever they're about.
In the product: Chat filed on the work, broadcasts that fan out privately, threads that mirror across company lines with real identity.
Time is where conflict is real: two claims on the same hour genuinely collide. Only people and resources own time — an organization has no body, so it plans over its members' calendars rather than having one.
In the product: One contention engine under meetings, bookings, shifts and rentals — and a personal calendar that spans every organization you belong to.
A resource looks like a record until you notice contention: only one party can have the van at a time. Whatever is contended needs a calendar; whatever holds state (clean/dirty, working/broken) needs behavior.
In the product: Rooms, vehicles and equipment that book clash-free — and whose state changes can spawn the cleanup work automatically.
Money actually moves in the world — and it moves for reasons unconnected to work (a refund, a transfer, a loan). So money is its own primitive, and a business can close its books no matter how its work was organized.
In the product: Real accounting that stands alone — and job costing as a link between work and money, not a merger of them.
The container: people, work, money, records and resources, grouped into a unit that acts. An organization you are is your workspace; one you deal with is a contact; when both are true, the two link — and collaboration crosses the boundary.
In the product: Multi-tenancy, roles and permissions, personal spaces for individuals, and the org-to-org network.
Composition is where the magic you've seen comes from
Every 'wow' moment in Coordinator is two primitives touching. None of them were built as features — they fall out of the model.
Job costing: the work knows its revenue, its costs, its margin.
A booking at an accepted price generates its own invoice.
Forms create clients and kick off templated projects; deliverables gate completion.
A dirty room spawns its own cleaning task, then flips back bookable.
A contact that is another business unlocks mirrored work and invoice→bill.
Conversation files under the thing it's about — findable forever.
And the deepest consequence: because a mirrored project is just an Activity, the entire stack — stages, approvals, deliverables, threads, invoicing — crossed the company boundary for free. That story is here →
Every primitive earns its place — or it's just a record
A resource is contended (so it must have a calendar). An activity completes (so it must be assigned and dated). A message has a counterparty. A transaction moves real value. When a thing has no property a record can't express, it stays a record — that refusal to multiply concepts is why the product stays calm while doing this much.
Feel the model, don't just read it
Free in minutes. Make a project, book a meeting, send an invoice — and notice they already know about each other.
Free. No card. About two minutes to set up.