Who owns your CRM? Data, security, AI and what to settle before anyone builds it
Most CRM problems we get called in to fix aren't technical. They're about ownership.
The story is almost always the same. A business pays an agency to build its CRM. It works well enough for a couple of years. Then the owner wants to switch tools, or just change a single follow-up message, and finds out the account sits under the agency's login. The phone numbers are registered to the agency. So is the domain the emails send from.
Nobody did anything wrong on purpose. It was easier to build everything in one place and sort out ownership later. "Later" never came, and now the business depends on a system it can't fully control.
Ownership covers more than a login. It covers your data, who can get into it, what the AI inside it can see, and whether anyone other than the person who built it can maintain it. This article goes through each of those, and ends with what to settle in writing before anyone builds anything.
Data: contacts are the part everyone checks
When people think about owning their CRM, they think about their contacts. It's a reasonable instinct, because the customer list is an asset. It's also the easy part. Almost any CRM can export contacts, notes, deals and custom fields as a file in an afternoon.
That's why ownership problems stay hidden for so long. An owner asks, "Can I get my data out?", the answer is yes, and the question feels settled.
It isn't, because export only answers part of the question. Three more are worth asking:
- Where does the data live, and who else touches it? Your CRM holds names, phone numbers, emails, messages and sometimes health or payment details. Every tool connected to it, and every service that processes it, is another place that data goes. You should be able to get a list.
- How long is it kept? Old leads, call recordings and message history pile up. Decide what you keep and for how long, rather than keeping everything by default.
- Is it clean? Duplicates, missing fields and inconsistent tags make every report and automation less reliable. A CRM that's full of duplicate contacts will send the same person the same text twice.
Messaging has its own rules about consent and opting out, and they differ by country. Whoever builds your follow-up should be able to tell you how a "stop" reply is handled and where consent is recorded.
The logic is the part that stays behind
Think about what's actually inside a working CRM:
- The automations that reply to a new lead, send reminders and chase an unanswered quote
- The pipeline rules that decide when a lead moves from one stage to the next
- The timing of every follow-up: what goes out on day one, day three, day ten
- The routing that decides who gets alerted, and how
- The connections to your website forms, phone system, calendar and accounting tools
Taken together, that's how your business handles a lead. It's years of decisions about how quickly to respond, what to say and when to give up. It's worth far more than a list of names.
And it's the part that usually can't be exported. Automations built in one CRM don't copy across to another. They have to be understood, documented and rebuilt by hand in the new system. If nobody wrote down how it works, you're reverse-engineering your own business from screenshots.
We recently moved a dental practice off a CRM an agency had built for them. It was full of duplicate contacts and automations that no longer worked, and the practice didn't own the account. The full case study is here. The migration finished with zero data lost and zero downtime. The contacts were the easy part. The automations had to be rebuilt, which meant working out what each one was supposed to do and whether it still made sense.
Security: who has the keys
Ownership and security are the same question from two sides. If you can't see who has access, you can't say who's protecting your customers' data.
The basics are not complicated, and they're easy to skip when a build is rushed:
- One login per person. Shared passwords mean you can't tell who did what, and you can't remove one person without disrupting everyone.
- Two-step sign-in turned on for every user, starting with the owner.
- Only the access each role needs. The person who answers enquiries doesn't need to delete contacts or change billing.
- The owner account in your name, with a login you control.
- Access removed the same day someone leaves your team or the agency.
Then there's the part owners rarely hear about: the connections. Every tool linked to your CRM, such as a form, a calendar or a phone system, usually works through a key or a token. Those keys should sit in your account, be listed somewhere you can see, and be replaceable. If the only copy lives in a freelancer's personal notes, you have a dependency nobody can see, and you have a security risk if that person ever loses their laptop.
One more question worth asking: how do you recover? If someone deletes a pipeline by mistake, or a bad automation overwrites a field, can you get back to yesterday's state? Ask what's backed up, how often, and who can restore it.
AI: what it can see and who controls it
More CRMs now have AI built in or added on: assistants that answer enquiries, qualify leads, book calls and write replies. That can save real time, and it adds questions that didn't exist a few years ago.
Before an AI tool goes anywhere near your CRM, ask:
- What can it see? An AI that answers new enquiries doesn't need your full customer history, billing details or private notes. Give it only what the job needs.
- Where does the data go? Most AI tools send text to an outside provider to generate a reply. Ask which provider, and whether it keeps the conversations or uses them to train its models. Get the answer in writing.
- Who owns the instructions? The prompts, the answers you've approved and the knowledge base it draws on are work you or your team have put in. They should live in your account and be exportable, not locked inside the builder's setup.
- Is every conversation logged? You should be able to read what the AI said to a customer, so you can correct it and so you can answer a complaint.
- Does it hand off to a person? There should be a clear point where it stops and a human takes over, and your team should get an alert when it happens.
- Can you turn it off? If you pause the AI, the rest of your follow-up should carry on working. If switching it off breaks the system, it's too tangled in.
AI doesn't change the basic rule. The data is yours, the access is yours, and the setup should be something you can see and change.
Easy to build, hard to maintain
This is the part that surprises people most. A CRM can be quick and cheap to build, and then slow and expensive to live with.
When a build is rushed, the same problems tend to show up a year later:
- Overlapping automations. Two workflows both trigger on a new enquiry, so the customer gets two texts.
- Names nobody understands. An automation called "Workflow 7 (copy)" tells you nothing about what it does or whether it's safe to change.
- Hidden dependencies. One automation relies on a tag that another automation sets. Delete the tag to tidy up, and a follow-up quietly stops.
- Connections only one person understands. The form posts to a tool that updates a sheet that triggers a text. It works, until one piece changes and nobody knows where to look.
- No test, no record. Changes go straight into the live system, and nobody can say what changed or when.
None of this shows on day one. The system works, leads come in and replies go out. The cost arrives later, when you want to change something and nobody can do it safely.
A build that's easy to maintain looks different:
- Small, single-purpose automations with names that say what they do
- A short document per automation: what triggers it, what it does and why
- A change log, so you can see what was altered and when
- Test leads run through every change before it goes live
- Alerts when something fails, so a broken form or a stopped follow-up gets noticed in hours, not weeks
- Ownership of every piece written down: the account, the numbers, the domain and the connections
It takes a little longer to build this way. It takes far less time to run, change and hand over, and it means you aren't dependent on one person remembering how it works.
Numbers and domains: the quiet dependency
There's one more thing that tends to sit in the wrong name: the infrastructure around your messages.
Your business phone number, the number your texts come from and the domain your emails send from all have registrations behind them. If an agency set those up under its own account, moving them later can range from awkward to impossible. In the meantime, your texts and emails may simply stop arriving when the relationship ends.
It's the piece owners are least likely to think of, because it works silently until the day it doesn't.
Five answers to get in writing
Before anyone builds or takes over a CRM for you, get clear answers to these. In writing, not on a call.
1. Whose account is it?
It should be in your name, with you as the owner and an admin login of your own. The same goes for the phone numbers, the sending domain and any message registrations. If the agency builds in its own account at first, there should be an agreed date and process for moving it to yours.
A quick test: can you, today, add a user, change the billing and see every setting without asking anyone? If not, you're a guest in your own system.
2. Can everything be exported, including the automations?
Don't stop at "yes, you can export your contacts." Ask what happens to the automations, the pipeline setup and the follow-up timing. The honest answer is that they can't be copied to another tool, so the useful question is: will there be documentation clear enough that someone else could rebuild them?
Good documentation doesn't need to be long. A page per automation covering what triggers it, what it does and why is enough.
3. Who has access, and how is it protected?
Ask for the list of users, the access each one has, and confirmation that two-step sign-in is on. Ask where the connection keys are stored and how they'd be replaced.
4. What can the AI see, and where does the data go?
If AI is part of the build, get the provider, what data it receives, whether that data is kept or used for training, and how to switch it off, all in writing.
5. What happens if we part ways?
Every working relationship ends eventually, often on good terms. Agree in advance what you receive: which files, in which format, and by when. Add a handover call if you can.
It feels awkward to raise this before the work starts. It's much more awkward to raise it afterwards.
What good looks like
A partner who's confident in their work will answer all five without hesitating. They'll tell you the account is yours from day one, show you where the documentation lives and how access is managed, and have a simple exit plan ready.
If you get a long, vague answer, or a suggestion that it's "all taken care of", that's worth knowing before you've built your follow-up process on top of it.
None of this is about distrust. It's the same reason you keep your own keys to your own premises. Your CRM holds every customer you've ever had, and the process that turns enquiries into bookings. It should belong to you.
Check your own setup in ten minutes
If you already have a CRM someone else built, you can check today:
- Log in and find out who holds the owner or admin role.
- Look at the billing: whose card or account pays for it?
- Count the users, and check that two-step sign-in is on.
- Find out where your phone numbers and sending domain are registered.
- Ask whether there's any written record of what the automations do.
If any of those come back unclear, that's the first thing to fix, before adding anything new.
Not sure where your setup stands? Our free Booked-Jobs Call traces a lead through your CRM, forms and follow-up and shows where it slips away. You get a written plan within 48 hours. If you're thinking about changing systems, see how we handle integrations and migrations, or start with CRM setup and automation.