The thinking behind Coordinator
Four convictions, held stubbornly. Everything else on this site is a consequence of them.
Any business can be built from a few flexible building blocks
Every business tool you've used is a pile of features: invoices here, tasks there, calendars somewhere else, each bolted on as the roadmap demanded. Coordinator started from a different question: what are the building blocks every business is built from?
The answer is a short list of primitives — what's true (records), who you deal with (contacts), what gets done (activities), what's said (messages), when it happens (schedules), what you use (resources), what value moves (transactions), and the organization that contains them. Model those primitives correctly and most 'features' become combinations you get for free: job costing is just work linked to money; a booking that invoices itself is just a schedule linked to a transaction. Coordinator brings those building blocks to you as software.
That's why the pieces here fit — they were never separate pieces.
The full ontology, explainedThe biggest unsolved problem is between companies, not inside them
Almost all business software helps people collaborate inside one company. But look at where a small firm's week actually leaks: chasing the client for approval, re-typing the vendor's invoice, writing status emails to someone at another business. The coordination tax between companies is larger than the one inside them — and almost nobody has attacked it.
Coordinator is built for it from the ground up. A contact can be another business on the platform. Your invoice becomes their bill. Your shared project mirrors into their workspace with a hard boundary around what crosses. Approval is a click that unlocks billing, not a sentence in an inbox.
This is also why it's free and why the tagline is 'Better Together': every business that joins makes the network more useful to the businesses it works with. A paywall would strangle the very thing that makes the product valuable.
How cross-company collaboration worksDon't build a module unless it beats the specialist
All-in-one suites earn their bad reputation: six mediocre tools in a trench coat, each worse than the standalone product it imitates. We hold the opposite rule — a module doesn't ship unless it's genuinely better than what you'd buy separately, at least for the businesses we serve.
So the accounting has journals, period locks, multi-entity books and a cash-flow forecast competitors sell as an upsell. The scheduling has waitlists, session packages and shift-pooled round-robin that the booking apps don't. The project management measures waiting time and gates completion on client sign-off. If a module were merely 'included', it would be a liability — included and better is the bar.
Judge each module yourselfSoftware that touches your money will eventually charge like it
When a platform processes your payments, holds your balance or meters your seats, its incentives drift toward its cut, not your outcome. Coordinator's rule: everything that costs money runs on accounts you already own — your Stripe, PayPal or Wise; your Zoom or Meet; your Google or Microsoft calendar; your AI key. We orchestrate; we never intermediate.
That keeps the product free without a catch, keeps your customer relationships yours, and keeps our incentives pointed at exactly one thing: being worth running your business on.
The honest answers about freeIdeas are cheap. The product is the argument.
Free, in minutes — see whether the four ideas above survive contact with your actual Tuesday.
Free. No card. About two minutes to set up.