Loading
Because each system creates a customer when it first needs one. Support knows them as one spelling, finance as another, and the quarterly account review spends its first ten minutes reconciling the two.
The company record is the customer as an organisation: legal and trading names, addresses, industry, owner, hierarchy position, and every deal, ticket, project and invoice attached to it.
One row, referenced everywhere. Desk tickets, Loop projects and Books invoices point at it rather than restating it, so the account view is a query rather than a compilation.
Kanaka Foods appears once. From that row you can see two open deals, an overdue invoice, an at-risk delivery phase and eleven support tickets — which is the whole of why the renewal conversation needs finance in the room.
It is not a data provider. Enrichment can fill firmographics and shows its source, but Treepie does not assert facts about a company it was not given or told to fetch.
Every other product reads it. Books bills it, Desk routes on it, Loop delivers against it, Growth attributes traffic to it, and reporting rolls up through its hierarchy.
Merge the records. History from both is kept and attributed, and the surviving row keeps every relationship.
Yes. Field-level permissions apply, so finance terms need not be visible to everyone who can see the account.
No practical one. Reporting and search are built to work at the size you actually import.
Fourteen days, every module, no card. Or half an hour with someone who will run it on your own records and tell you where it does not help.