Loading
A company record represents a customer as an organisation rather than a person. In Treepie Flow it holds the company’s details, the people who work there and their roles, and everything every team has attached to it: deals, projects, support tickets, quotes and invoices. Because every product files against the same row, the company record is the one place the whole account can be read.
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.
| Separate tools | CRM with integrations | Treepie Flow | |
|---|---|---|---|
| Where the account lives | A different version in each tool | In the CRM, copied elsewhere | One row every product writes to |
| Support and billing | Exported for reviews | Synced, often late | Attached directly |
| Subsidiaries | Unrelated rows | Sometimes a parent field | Linked hierarchy with roll-ups |
| Duplicates | Common | Caught on some imports | Matched on entry, import and sync |
| Account review prep | Hours of exports | Less, with gaps | Open the record |
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.
Name, domain, registration number, address, size, industry, account team and any custom fields you add. Size and industry can be filled by enrichment.
There is one owner plus an account team — people in sales, delivery, support and finance who work the account, each visible to the others.
Desk matches incoming email by domain and Books invoices the company directly, so both land on the company without anyone linking them.
Yes. Lifetime revenue, open pipeline and outstanding balance are on the record, and roll up to a parent group if you use hierarchies.
Link them under a new parent, or merge the records if they are now one entity. Merging keeps both histories.
Yes. Record permissions can limit a company to its account team, a region or a role.
No, but most do. A contact can also belong to more than one company, with a role at each.
Yes. Companies are imported first and matched by domain and registration number, then contacts and history are attached.
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.