At BookPrint I set HubSpot up for myself and became an accredited HubSpot marketer. I used the free sales CRM and paid for the marketing automation. I built custom forms in the CRM, and when I tried to feed the form responses into the automation I couldn't, unless I upgraded to the paid CRM, so my own form data left HubSpot through Zapier in order to come back into HubSpot. I don't want to hate on HubSpot; I'm picking on it because I know it. The frustration was never the features. It was the underlying data structure and the business model, and they turned out to be the same thing.
That pattern runs through every legacy all-in-one platform, and it is why the more important conversation about software is never which tool does what. It is where the source of truth lives, and how it is derived.
Two kinds of software
A workflow app is a filing cabinet. Humans type records in, the software keeps them tidy, and when a status changes from Active to Churned the old status is overwritten. The record is accurate in the present moment, and the system has lost the context, the history and the why. HubSpot, the project boards, most of what a business calls its system: structurally, they are still just tables.
A data engine records events and never overwrites. Every change is an entry that cannot be altered, so the business can be replayed as it stood on any date. Ask it what this customer looked like on the fifteenth of March and it can tell you. That history is not a luxury. It is the strict prerequisite for any AI that is going to decide anything, because a model that only sees the present moment is guessing at how it got there.
Humans still need the filing cabinet. Someone has to enter the unstructured thing, make the subjective call, review the record. The difference is that the interaction layer is decoupled: a lightweight control plane that reads from the core and writes to it, rather than being the ultimate database itself.
The all-in-one dilemma
The promise of the all-in-one is seamless integration, because everything is under one roof. As a business gets more complex that stops being true, in three ways.
Data lock-in. When the primary data layer lives inside a vendor's ecosystem, every new interaction and every historical record has to be integrated on their terms, and porting it out becomes cost-prohibitive. The data is yours on paper and theirs in practice.
Forced shapes. A vendor's data model rarely matches how a business runs. An ERP and an MRP need completely different shapes from a CRM, so teams end up running disconnected systems in parallel and fighting to keep them in sync. My form data taking a trip through Zapier was a small version of this.
Pricing leverage. Every new feature, data expansion or AI capability is priced at the native premium rate, because the alternative, plugging a specialised tool into an open architecture, is not available when the architecture is closed.
What it looks like on a Tuesday
A supplier emails that a shipment is delayed. In the filing-cabinet workflow a human opens a spreadsheet or the CRM, updates the delivery date, checks by hand which manufacturing orders are affected, and emails the plant manager. In the data-engine workflow the supplier's system logs a delay event to the core, the core maps the delay to the affected products, recalculates the inventory risk, and alerts the plant manager with recommended schedule changes. Same event, same people, and one of them has happened while the human is still opening the spreadsheet.
You buy a new HR tool. In the filing-cabinet world you pay a developer to build a bridge between it and payroll so they can share employee data, and every tool after that adds another bridge, until the integrations are a spaghetti network of point-to-point connections nobody can draw. In the data-layer world you define once, in the core, what an Employee is. The new tool points at that definition, reads it and writes back to it, and adding or removing software becomes plug and play.
How to get there without a big-bang decision
The move toward an owned core does not start with a platform purchase. It starts smaller.
First, build a simple internal CRUD system whose only job is to digitise and formalise the decision and information workflows the business already runs. Not to improve them yet. To write them down in a form a machine can hold.
Second, improve those workflows iteratively, updating the simple system as you learn what the business actually decides and in what order.
Third, build the modern data layer that the ERP, the MRP, the CRM and every rented tool read from and write to. By now you know the shape of your own entities, because you have watched them for two rounds.
Fourth, automate. Outside expertise or internal resource at any of the four steps.
The simple CRUD stage is the check. It is the small test before the big commitment: it digitises what the business actually does before anything is built on top of it, and it costs a fraction of getting the platform decision wrong.
The privacy angle
Companies holding large datasets are looking at what those datasets are worth to AI providers and as enrichment data, and the all-in-one that holds your core may be one of them. In July 2026 HubSpot told the administrators of accounts using enrichment that, from August, enrichment data such as business contact details, employer information and email deliverability signals may be shared with other customers. The platform read on that change is on this site. Owning the core is not only about what you can do with your data. It is about who else can.
The same shape everywhere
The System Seed is the knowledge half of a business's source of truth: what it knows, how it sounds, what is verified. The core is the data half. A seed sitting on top of a vendor's database is a rented core, and the vendor decides what history you keep and who else reads it. Own both halves. Rent everything else, and rent it as an engine you could replace on a Tuesday, which is the rented edge. If the shape feels familiar, it is the same one The Trust Algorithm draws around attention, proof and reputation: the things you rent never compound, and the thing you own is the only one still working while you sleep.