Your First 90 Days as a CRM Admin: What to Build, Clean, and Automate
You have inherited the CRM. Maybe the previous owner left. Maybe you volunteered. Maybe the job appeared in a meeting with the words “someone needs to own this”. Whatever the reason, you are now the person who gets asked why the email never went out, why the report is wrong, and why nobody can find the contact from last Thursday.
The good news is that a small business CRM does not need heroics. It needs a three month plan, run in the right order, owned by one person. This is what that plan looks like.
If you are not yet sure what the CRM itself is for, or how it was set up, start with our step by step CRM setup guide and come back.
Before You Start: Get the Brief Right
Spend an hour with whoever handed you the role. Write down the answers to four questions.
- Who uses the CRM today, and how much do they actually use it? Opinions will differ from the login logs. Both matter.
- What are the top three things leadership wants the CRM to tell them? Usually this is pipeline value, conversion rate, and overdue follow ups. Sometimes it is stranger.
- What are the top three complaints about the CRM? These are the problems you will be judged on in three months.
- What is off limits? Some fields, automations, or integrations exist for reasons that are not obvious and have owners you do not yet know.
If you cannot answer these, you are guessing for 90 days. The brief is not optional.
Month One: Audit Everything, Change Nothing
The temptation is to log in, see a mess, and start tidying. Resist it. In month one you are a detective, not a builder.
Week 1: Map the Estate
Make a one page list of what exists.
- Number of contacts, companies, deals, and tasks.
- Number of active users and who logged in last week.
- Every pipeline and every stage in each.
- Every custom field on contacts, deals, and companies.
- Every automation and what it does.
- Every integration (email, calendar, accounting, forms, phone).
- Every saved report and who it is sent to.
Print the list. Stick it on the wall. Anything that surprises you goes in a “investigate” column.
Week 2: Interview the Users
Thirty minutes each with three types of person: a heavy daily user, a light user who logs in weekly, and the person who avoids it. Ask open questions.
- What do you use the CRM for on a typical day?
- What do you do outside the CRM that you wish the CRM did?
- What has slowed you down this week?
- What would you delete tomorrow if you could?
The heavy user tells you what is working. The light user tells you what is close to working. The avoider tells you what is broken. You need all three.
Week 3: Audit the Data
Export everything to a spreadsheet. You are looking for shape, not detail.
| Check | What to Record |
|---|---|
| Duplicates | How many contacts share the same email or phone |
| Missing owner | How many active deals have no assigned owner |
| Dead records | How many contacts have no activity in 18+ months |
| Empty required fields | Whether “required” fields are actually populated |
| Stage time | How long deals sit in each pipeline stage on average |
| Source blank | Percentage of leads with no lead source recorded |
| Departed users | Records owned by people who have left the business |
These seven numbers tell you where the rot is. You will use them in month two.
For the mechanics of actually cleaning duplicates and stale records, cleaning up your CRM data is the companion piece.
Week 4: Write the Baseline Report
One page. Top of the page: three things working well, three things broken, three things you will fix in the next two months. Share it with whoever gave you the brief. Get alignment before you touch anything.
This report is also the single most useful thing to have on file in month six, when someone asks whether things have improved. Without a baseline you have opinions. With one you have numbers.
Month Two: Clean, Segment, and Simplify
Now you have permission to change things. The order matters: clean first, then configure, never the other way round.
Deduplicate Contacts
Most CRMs have a built in merge tool. Use it. For small businesses with under 5,000 contacts, an afternoon of merging is usually enough to clear the worst of it. Work from the export in week three. The easy wins are records with identical emails. Phone number matches come next. Name only matches need a human eye.
Set a rule for new records going forward: no new contact without an email or phone number. Enforce it in the form or the import settings.
Fix the Pipeline Stages
Every stage in the pipeline should have a clear definition of what it means for a deal to be there, and a clear trigger for what moves it to the next stage. If your team cannot agree on what “qualified” means, no amount of reporting will be useful.
A common mistake is too many stages. Six or seven is usually enough for a small business pipeline. If you have fifteen, most of them are subdivisions that would be better expressed as a tag.
Cut the Custom Field Graveyard
Go through every custom field. For each one, ask: what percentage of records have this populated, and what decision is made based on it? If either answer is “not much”, delete it. Empty fields create clutter and teach the team that fields are optional.
Keep the fields that drive segmentation, pricing, or service delivery. Everything else goes.
Reassign Orphans
Records owned by users who have left should be reassigned, not deleted. Create a “to be reassigned” owner, bulk transfer everything from ex-staff to it, and then sort out who really owns each segment with the relevant manager. Active deals go first; dormant contacts can wait.
Tighten Tags and Custom Fields That Stay
The fields you keep deserve better hygiene than the ones you deleted. Consistent values, a closed list where possible, and sensible defaults. How to use CRM tags and custom fields effectively covers the patterns that stop tag sprawl from returning.
End of Month Two: Clean Data, Fewer Fields, Clear Pipeline
By day 60 the CRM should feel lighter. Fewer fields, fewer duplicates, clearer stages. The team will notice. You have also earned the right to start automating, because now the data is worth automating against.
Month Three: Automate and Report
Automation and reporting are what the CRM was sold on. They are also where new admins start, and why half of them fail. Month three is where they belong.
Start With Exactly Three Automations
Pick the three that save the most time across the team. The usual shortlist:
- New lead notification and follow up task. A new contact from the website form creates a task on the right owner for the same working day. This alone prevents dozens of leads going cold.
- Post meeting follow up reminder. When a meeting is logged, a follow up task is created for two working days later, assigned to the owner.
- At risk client flag. Clients with no activity logged for a defined period (90 days for retainers, 30 days for active accounts) are flagged for a personal check in.
That is it for month three. Three automations, each solving a specific pain. If you build eight, you will not understand which one is firing when something goes wrong. For the next tier once these are bedded in, look at five CRM workflows that save hours every week.
Build Three Dashboards
Same principle: three, not fifteen. Tailor them to the three things leadership asked for in the brief.
- Pipeline dashboard. Value by stage, deals overdue at each stage, top 10 by value.
- Activity dashboard. Meetings logged, emails sent, tasks overdue, split by owner.
- Conversion dashboard. Leads in by source, conversion rate to customer by source, average sales cycle.
Each dashboard should answer one question. If a dashboard does not answer a question, it does not belong on the screen. For a sharper view on which numbers matter, CRM metrics that actually matter for growing businesses covers the short list worth watching.
Build a Weekly Admin Routine
Your own weekly rhythm is the thing that keeps the CRM from decaying.
- Monday: Check the overnight new leads have owners and tasks.
- Tuesday: Review stuck deals, the ones that have not moved for longer than their stage average.
- Wednesday: Run the duplicate check on new records from last week.
- Thursday: Check automation logs for any that failed silently.
- Friday: Scan the dashboards, flag anything unexpected.
Thirty minutes a day. How to run a weekly CRM review in 15 minutes runs through the quicker version for less complex set ups.
Train the Team on What Changed
At the end of month three, get the team together for thirty minutes. Show them:
- What you cleaned up (the numbers from the baseline report).
- What is now different (pipeline stages, custom fields, the three automations).
- What you expect of them (which fields are now required, which tags to use).
Training is not optional. A CRM that the admin understands and the team does not is a CRM that rots in month four. How to train your team on a new CRM covers formats that tend to stick with busy small business teams.
Common Traps in the First 90 Days
These appear every time.
- Automating before cleaning. Bad data plus automation equals accelerated bad data. Clean first, always.
- Adding custom fields to solve communication problems. If a sales rep keeps forgetting to tell delivery something, the answer is a process, not a new field.
- Copying a complicated setup from a previous employer. Your new business is not your old one. Build what this team needs, not what the last team had.
- Trying to make the CRM do everything. It does not need to be your accounting, email marketing, and ticketing platform. Integrate where the data belongs.
- Not saving an export before big changes. Before any mass delete, merge, or reassignment, export. Every time. Reversibility is what separates a careful admin from an ex-admin.
After 90 Days
By day 91 you should have:
- A clean, deduplicated contact list with consistent fields.
- A pipeline the team can describe without looking at it.
- Three reliable automations that are saving measurable time.
- Three dashboards that answer the leadership questions.
- A weekly routine that stops the rot from setting in.
- A trained team that knows what is required of them.
That is the foundation. Month four and beyond is about extending it: more integrations, more precise segmentation, more automations built on a base that can now be trusted. If the foundation is right, everything after it is cheaper and faster. If the foundation is wrong, everything after it is an argument.
Ninety days of audit, clean, and automate in that order is not exciting. It is the thing that works. The admins who rush the order end up doing it again six months later; the ones who respect it are the ones the business still trusts in year two.
Ready to build a smoother CRM admin routine? Start with our guide on how to get your team to actually use your CRM, and bring the habits in this plan into your weekly rhythm.
Frequently asked questions
What does a CRM admin actually do?
A CRM admin owns the day to day health of the CRM: the data quality, the pipeline stages, the custom fields, the automations, the user permissions, and the reports. In a small business they usually wear two hats, running the CRM and doing a sales or operations job alongside. The role is one part housekeeping, one part translator between the team and the tool, and one part internal trainer.
What should a new CRM admin do first?
Do not change anything in week one. Log in, read, and make a list. Export the contact list, open every pipeline, click through every automation, run every saved report, and write down what you see. You cannot improve a system you do not understand, and the last person to assume they understood usually built the mess you just inherited.
How long does it take to fix a messy CRM?
For a small business CRM with under 10,000 records, a structured 90 day plan is usually enough to get from messy to manageable. Month one is audit, month two is cleaning and segmenting, month three is automation and reporting. After that the work is maintenance, not rescue. If you try to do all three in parallel you will finish none of them.
Who should own the CRM in a small business?
One person. CRM ownership by committee ends with nobody deciding anything and everybody blaming the tool. The CRM admin does not need to be technical, but they do need the authority to say no to random custom fields and yes to cleaning up duplicates. In most businesses the role sits with operations, office management, or a senior sales person.
What is the biggest mistake new CRM admins make?
Building new automations before cleaning the data. An automation that fires against bad data accelerates chaos. It sends follow up emails to leads who already became clients, assigns tasks to owners who left last year, and segments the database by a field that is blank on half the records. Clean first, automate second. This order is not optional.
Enjoyed this article? Get more CRM tips straight to your inbox.
Comments
Join the conversation. Share your experience or ask a question below.
No comments yet. Be the first to share your thoughts.