Skip to content
← All articles

Notes for owners · CRM, automation and RevOps

CRM data governance: who may edit what, and why it matters

Who owns a record, which fields cannot stay empty, who may merge or delete, and what a leaver hands over: the rules that keep a small firm's CRM trustworthy.

The GullySales team · Updated 17 Oct 2026 · 6 min read

Editorial illustration for CRM data cleansing, deduplication and governance
On this page
  1. Why a CRM goes bad in a small firm
  2. Decision one: every record has one owner
  3. Decision two: the fields that cannot be empty
  4. Decision three: who holds the keys to merge, delete and export
  5. The week someone gives notice
  6. The Aligarh firm, with the rules in place
  7. Scaling it down
  8. Print the rules before you buy a tool

Picture a lock manufacturer in Aligarh on a Monday morning. The owner opens the CRM and finds the salesperson who resigned on Friday still listed as owner of forty dealer accounts. Eleven dealers appear twice, and nobody can say which entry holds the real credit limit. Data governance is the set of rules that stops this. Each record has one named owner. A few fields cannot be saved empty. Only named people may merge or delete. A leaver hands over before the login closes. It fits on one page.

Why a CRM goes bad in a small firm

It does not go bad through carelessness alone. It goes bad because nobody was told where their power ended. A salesperson who can edit anything will correct a dealer's phone number on a hunch. A coordinator who can delete anything will clear "old" accounts before a quarter-end report. Both mean well, and both destroy history that someone needs later.

Governance is not a security project. For a firm with five to fifteen users, it is four decisions written down and shown to everyone on the same day.

Decision one: every record has one owner

Give each account a single owner who is a person, not a team or "sales". The owner is the one who gets asked when the record is wrong. If two people work on a dealer, one still owns the record and the other is listed as support.

Make the system show the owner in the first line of the record, and treat "unassigned" on a live account as a fault to fix that day.

Ownership also answers the question of who may edit. A simple rule can work for a small team. The owner edits freely. A manager edits with a reason typed in the notes. Nobody else edits, but anyone can add a note. The note is how a colleague says "their number has changed" without rewriting the record.

Decision two: the fields that cannot be empty

Demanding fourteen fields produces full stops typed into twelve of them. Pick the few without which you could not follow up.

  • contact name and mobile number
  • firm name and town
  • lead source, chosen from a fixed list
  • the owner
  • next action and its date

The system should refuse to save without these. A rule that is checked only at month-end is easy to ignore. Add two more fields only when a deal reaches quotation: the value and the person who decides.

Lead source needs a drop-down. When three people type "IndiaMART", "India Mart" and "indiamart enquiry", you cannot count the leads from any of them. Whoever wants a new source asks the admin, who adds it once.

Decision three: who holds the keys to merge, delete and export

These three powers are different, yet small firms give them all to everyone.

Merging two records is delicate because one set of notes survives and the other is folded in. A salesperson who merges alone may keep the record with their own name on it. Send possible duplicates to one admin, who keeps the older record, moves the newer notes across and writes the date of the merge.

Deleting should sit with that same admin, with a log. A deleted dealer takes its call notes and quotations with it. Give salespeople a "flag as wrong" button instead.

Exporting is the one owners forget. Anyone who can download the full dealer list can carry it home. Limit export to the admin and the owner, and let a manager pull only their own team's accounts.

For matching, use the mobile number first because it is the steadiest thing you hold, and firm name plus town second. Run every spreadsheet import, whether from an exhibition card pile or a marketplace download, past the admin before it goes in. One careless import can add hundreds of near-copies in a minute.

The week someone gives notice

Work down this list in order, and start the day notice is given, not the day the person leaves.

  1. Switch off their export rights at once, before any handover talk.
  2. Move every open lead and account to a named person. "Unassigned" is not a person.
  3. Sit with them over their open quotations and write in any verbal promise: a price held, a sample owed, a visit agreed.
  4. Check that each dealer's number for the firm is saved in the CRM under a company contact, not only in a personal phone.
  5. Move any WhatsApp group they ran with dealers to a second admin.
  6. Close the login on the last day and record the date.

Step four is the one that loses dealers. If the dealer only ever had the salesperson's own number, the dealer simply stops hearing from you when that number goes silent.

The Aligarh firm, with the rules in place

For example, take the lock maker again, as an illustration and not a client. It had six salespeople, about ninety dealers across western Uttar Pradesh and a CRM that anyone could export from. One salesperson downloaded the dealer list during their notice. Two dealers soon began quoting a rival brand's rates to the firm's own staff.

The owner did not buy new software. The owner took export rights away from everyone but the admin and the owner, moved lead source to a drop-down, chose mobile number as the match rule, and printed the six-step list. Reassigning a leaver's accounts became a single sitting, with the manager and the admin in the room. A few dealers still took weeks to answer their new owner, and two were lost to the rival anyway.

The limit is plain. No rule stops a determined person from copying numbers into a notebook. Governance makes it harder and more visible, and it means the firm still holds the record. Put a clause about customer data in the employment letter too, and ask your own adviser for the wording.

Scaling it down

With two salespeople and a spreadsheet, skip roles. Keep one owner column, a source drop-down and a copy of the file saved somewhere other than a laptop. Add the rest when a third person starts typing in data or when the first duplicate costs you a call.

A long book of old records needs a clean-up as well as rules, and the rest of our sales work sits under sales.

Write the required fields, the owner rule and the leaver list on one sheet and name your admin. Strike out whatever your current system cannot enforce and see how much is left. CRM data cleansing, deduplication and governance is the service that turns that sheet into a working setup, and tell us what you need is how it starts.

Questions

Questions owners ask.

Do I need data governance if I only have four salespeople?
Yes, a short version. Four people can still create four copies of the same customer and leave with their own contacts. One owner per record, a short list of required fields and a leaver checklist fit on one page and take an afternoon to set up.
Should every salesperson be able to delete records?
No. Deleting should sit with one or two named people, because a deleted record takes its call notes and quotes with it. Give salespeople a way to mark a record as wrong or duplicate, and let the admin decide.
What if my team enters data in WhatsApp and Excel, not the CRM?
Then the rules apply to wherever the master list lives. Pick one place that counts, say so in writing, and treat anything outside it as unofficial until someone moves it in.
Who should be the CRM admin in a small firm?
Someone who is in the office most days and cares about tidy records, often a sales coordinator or accounts person, not the owner. The owner approves the rules; the admin applies them and handles merges.

From the blog

More notes for owners.

Your next practical step

Tell us what you are trying to grow, and we will read it before we call.

Eight short steps, mostly taps. Skip anything you would rather answer on the call.