When a CRM build looks cheap until getting your own data back out of it costs more than the build did

A cautionary pattern worth knowing before hiring anyone to build out a CRM stack: a small partnership hires a consultant to build a full pipeline system, property tracking, capital conversation tracking, document request sequences, a shared calendar, an inbound tracking number, delivered well and on budget. The problem that shows up later is ownership structure, not execution quality. It's common practice for a consultant to build the client as a sub-account under the consultant's own agency plan. That's not inherently a red flag, but it means the billing relationship, the admin seat, the registered tracking number, and any integrations authorized through API keys can all sit under the consultant's personal login rather than the client's own account. The client ends up as a user inside a system it doesn't actually own. If that consultant becomes unavailable, whether through a job change or simply stopping the engagement, a sub-account often has to be migrated to a new, independently owned account before it goes read-only. Migration typically means re-importing contacts and notes, rebuilding automations that don't carry over cleanly, re-authorizing integrations, and re-registering any phone number, and undocumented automations that lived only in the original builder's head are often lost outright, along with whatever follow-up sequence was mid-flight when the transition happened. The fix is straightforward and worth insisting on from day one on any future build: the platform account should be opened by the client, under the client's own card and email as owner, with the consultant invited in rather than the reverse. Any tracking or texting number should be registered to the client's entity from the start, with the carrier registration paperwork kept on file. Every integration should run through a service login the client controls, not a personal one. Documentation of each automation, its trigger and what it sends, should be a named deliverable with a dollar figure attached, with a portion of the fee held until it's delivered. And the engagement letter should spell out what happens on the day the consultant stops working, agreed before any deposit is paid. None of this is exotic, it's the same diligence instinct applied to a title commitment, just as easily skipped on a software invoice.