CRM Hygiene for Startup Founders
A CRM at seed is usually either empty or a junk drawer. Both fail the only tests I care about. A useful three-part check, circulated in a sales-tech discussion, is: are the accounts you sell to marked as such, are the contacts current, and does your CRM know who has already been spoken to? If those three are false, every "AI SDR," every sequencer, and every new hire will make the same mistakes at a higher speed. Petra Hajal, commenting on a large job-posting analysis, put a sharper warning on the hire: that is where a junior GTM engineer can do the most damage.
Pramod Kumar, co-founder of Kingdom of Kumar. On X
·
Hygiene is not a winter project. It is a weekly standard, small enough that a founder will keep it. List quality is in How to build a B2B list without paying for bad data. Routing depends on it: Inbound lead routing. Reporting depends on it: Pipeline reporting at seed. The work is also on GTM engineer and GTM engineering. If you should not be selling yet, take the App Launch Score and do not tidy a funnel that should not exist.
"Are the accounts you sell to marked as such, are the contacts current, and does your CRM know who has already been spoken to"
Those three questions are the hygiene bar.
Accounts you sell to. Customers, open opportunities, and serious conversations should be obvious in the record. If a customer can receive a cold "we help companies like yours" email, the system failed, even if the copy was pretty.
Contacts current. Names, roles, and emails that you would still use today, with a date of last check. A contact who left six months ago should not be "the" person on the account.
Already spoken to. Last touch, last reply, last meeting, owner, and whether they asked to be left alone. If two teammates can both "discover" the same person, you do not have a CRM. You have two memories that sometimes share a login.
If you cannot answer yes to all three on a sample of twenty records, stop adding automation. Clean the sample, write the standard, then continue.
"That's where a junior GTM engineer can do the most damage"
I would take that comment seriously, whether the person is junior or simply new to your file. A motivated hire with export access and a mandate to "build outbound" can upload a list that overwrites current customers, duplicate open deals, or reset owners. The damage is not only embarrassing mail. It is a reporting system you will not trust for a quarter.
So the first week of any GTM hire, contractor, or tool should include: read-only until they can explain the object model, a written list of fields they may write to, and a rule that bulk imports get a checked sample first. If that slows them down, good.
Founders do this damage too, usually on a Sunday, with a CSV and optimism.
A hygiene standard you can keep
I would require, at minimum:
- One owner on each open conversation and each customer account
- A status that a stranger on the team would understand: customer, open, closed-lost, never-contact, or not yet contacted
- Last activity date that is true, not a default
- Email and role with a last-verified date, for anyone you might message
- A unique way to recognise the company (domain is the usual)
- No duplicate of the same person under three spellings
- Unsubscribes and "do not contact" that actually block sending
That is already a lot. It is also enough. You do not need forty custom fields to be clean. You need those to be true.
A Friday thirty-minute pass
- Look at everything marked open. Is it actually open?
- Look at this week's sends and replies. Did they write activity on the right record?
- Search for the company you signed, and the person who said no last month. Are they marked correctly?
- Scan a handful of new imports for duplicates and personal emails you have no policy for.
- Note one fix for next week, not a rewrite of the CRM.
If the pass keeps finding the same class of error, fix the import or the routing, not only the row.
Tools, sheets, and when to move
A sheet can be a CRM for a very small motion if it has the fields above and one owner of the truth. Move to a proper CRM when two people need to work it, when inbound and outbound collide, or when the sheet is starting to lie. When you move, migrate the standard, not only the rows. An empty Salesforce with a messy import is a downgrade.
Do not buy a data-cleaning product as a substitute for the Friday pass. Tools can help. They will not care more than you do.
A starter object model, in plain language
You need, at most, a few objects a founder can explain without a diagram:
- Company (or account): the organisation, keyed by domain when you can
- Person (or contact): a human at that company, with email and role
- Conversation or deal: the live commercial thread, with an owner and a stage
- Activity: what was sent, received, or said, and when
If your CRM also has "leads" as a third kind of person, decide today whether you will use that or not. Many small teams do better with person-plus-status than with a lead object that later has to be "converted," badly. I will not start a religious war about this. I will say: pick one model, write it in five lines, and do not let a new tool introduce a second model quietly.
When an import arrives, it should land as companies and people, and it should *not* create deals by itself. Deals are for conversations that are actually happening.
Permissions that prevent Sunday damage
Company-owned logins, not a personal Gmail connected to the CRM. A rule about who may import. A rule about who may export, especially if there is personal data in the file. And a backup or export you can actually find, once a month, in case a bulk edit goes wrong. This is dull, and it is cheaper than rebuilding the week after an API sync loops.
If a freelancer needs access, they get the least permission that still allows the work, for a dated period, and the password is not a shared "team" login in a chat archive.
FAQ
How clean is clean enough?
Clean enough that a new teammate, or a sequencer, cannot easily email a customer or a person who asked to be left alone, and that you can tell who was already spoken to. Perfect historical data is a trap. Start with the records you might touch this month.
Should I freeze outbound until the CRM is perfect?
Freeze bulk sends if the three questions fail on a sample. You can still have careful, hand-checked conversations while you tidy.
Can you do hygiene as part of the $500 offer?
Kingdom of Kumar builds and runs a scoped system on Grok and Claude for $500 a month, three-month minimum. You own it, and you approve what goes out. We will treat hygiene as part of that system, not as optional polish. We will not drop a junior-style import into your file to show activity. You still need a founder owner of the standard. This is not a $135,000 RevOps hire.