Loading
A company of fifty people typically runs a CRM, a project tool, an HR system, a helpdesk, an accounting package and a spreadsheet that reconciles them. Each is defensible on its own. Together they produce a customer who exists six times, with six addresses, and a month end that takes a week because most of that week is spent asking people for numbers that already exist.
Treepie’s answer is not integration. Two systems joined by a sync are still two systems, and one of them is always slightly stale. Instead the seven products write to the same record. A deal that closes in Flow does not copy the customer into Loop — Loop was already reading it.
A shared record is harder to build than seven databases and an integration layer, and it makes some things worse: you cannot adopt one product with a completely separate permission model, and a change to the record model touches everything. We think that trade is correct, but it is a trade, and we would rather say so than pretend the design has no downside.
The test is whether a fact ever has to be typed twice. If you find somewhere in Treepie that asks you to re-enter something the system already knows, that is a bug in the premise, not a missing feature — and we would like to hear about it.