A small team can have a working CRM inside a week if it does one thing a day: decide what to track, clean and import the spreadsheet, set pipeline stages, add a few data rules, build one follow-up, then set up a first report and the team habits that keep it alive. The aim of week one is not a perfect system. It is a system people use on Monday.

Before you start: one owner, one goal

Pick one person to own the setup. Not to do all the work, but to make the calls when two people want different stage names. Then write down the single thing the CRM should fix first, in a sentence: “no enquiry goes a day without a reply”, or “we always know what is in the pipeline”. Every decision this week gets checked against that sentence.

Day 1: decide what you will track

Most failed CRM setups fail here, by tracking too much. Start with the records you already talk about every day:

  • People you sell to or serve, with name, email, phone and who owns them.
  • Companies, if you sell to businesses rather than individuals.
  • Opportunities (deals), with a value, a stage and an expected close date.
  • Tasks, so follow-ups have an owner and a due date.

Write down the handful of fields each one needs. If nobody would notice a field missing from a report, leave it out. You can add fields later in minutes; you cannot easily get a team to fill in thirty of them.

Day 2: clean the spreadsheet, then import it

Your old data is the first thing the team will judge the new system by, so spend the morning cleaning before anything goes in:

  1. Put one record per row and one value per column. Split “Name” into first and last name if the CRM keeps them apart.
  2. Delete rows that are obviously dead: test entries, blank emails, people who asked not to be contacted.
  3. Merge the duplicates you can see. Sort by email, then by company, and look down the list.
  4. Standardise the values people filter on, such as status, source and region.

Then import a small sample first, perhaps twenty rows, and check every field landed where you expected. Fix the column mapping, then import the rest. If the CRM lets you save a mapping, save it, because there is always a second file.

Day 3: set your pipeline stages

A pipeline is the list of stages a deal moves through, from first contact to won or lost. Keep it short and make every stage a fact, not a feeling:

  • Enquiry: they asked.
  • Qualified: they have a need, a budget and a timeline.
  • Proposal sent: there is a price in front of them.
  • Won or Lost.

“Interested” is not a stage, because two people will never agree on it. If you cannot say what has to be true for a deal to move to the next column, merge that stage into its neighbour. Move today’s real deals onto the board before the end of the day, so the team sees its own work, not an empty template.

Day 4: add a few data rules

Rules are what stop the clean import from going stale by the end of the month. Start with three:

  • Required fields: a new lead needs at least an email or a phone number, and an owner.
  • Consistent values: status, source and stage come from a picklist, never free text.
  • Duplicate checks: flag or block a new record whose email matches one you already have.

Each rule should prevent a mistake you have actually seen. A rule nobody understands gets worked around, so explain each one to the team in a sentence.

Day 5: build one follow-up

Pick the single moment where leads go cold most often, usually the first reply after an enquiry, and automate only that. A good first sequence is short: a thank-you message the same day, a wait of two or three days, then a second message only if the lead has not moved on. Write it in your own voice and send it to yourself before anyone else gets it.

Resist building five sequences. One that runs every time is worth more than five that half-work.

Day 6: your first dashboard

Build the one screen you want to look at every Monday. For most small teams it answers four questions: how much did we win, how much new work came in, how many new leads arrived, and are tasks getting done. Check the numbers against what you already know. If the dashboard says you won three deals last week and you remember five, fix the data now, while the team still trusts the report.

Day 7: agree the habits

Software does not keep itself current; habits do. Agree a few, write them down and pin them where the team will see them:

  • Every new enquiry goes into the CRM the day it arrives.
  • Every open deal has a next step with a date.
  • Calls and decisions get a note on the record, not in a private notebook.
  • Ten minutes on Monday to review the board together.

The 30-day review

Put a date in the calendar four weeks out. On that day, look at three things: which fields nobody fills in (remove them), which stage deals get stuck in (split or redefine it), and whether the problem in your one-sentence goal got better. Then pick the next thing to improve. Week one gets you started; the review is what makes the system yours.

How this looks in GuardenerAI

In GuardenerAI CRM, the import maps your spreadsheet columns to fields and lets you save the mapping, and duplicates that slip through are caught by an overnight check and land in a review queue. Validation and duplicate rules run every time a record is saved, follow-up journeys send email, SMS or WhatsApp messages with waits and conditions, and the dashboard starts with Revenue won, Pipeline added, New leads and Tasks completed. Every paid plan has unlimited users, so the whole team can be in it from day one.

The verdict

Do one thing a day, keep every list short, and judge the week by whether people use the CRM on Monday, not by how complete it looks on Friday. The setup that survives is the one that matches how your team already works, with just enough rules to keep the data honest.

Where to go next

Written with these teams in mind: agencies and studios , home services , professional services .