CRM

The First CRM Setup for a Small Team

A day-one setup for a team of 3 to 10 people, and what to leave switched off.

You have chosen a CRM. The risk now is spending three weeks configuring it and another three trying to convince people to use it. For a team of 3 to 10 people, a good first setup takes an afternoon and touches five things. Everything else can wait until the tool has earned its place in the working day.

A small architecture practice signing up is a useful picture to hold. A couple of directors, a few architects who each handle their own client enquiries, and an office manager fielding the phone and the website contact form. They do not need workflow automation. They need to stop losing enquiries between the inbox, a notebook and someone's memory. Keep that goal in view and most setup decisions answer themselves.

Step one: add your people

Create a login for everyone who will touch a lead, including the person who only answers the phone. A shared login looks simpler and costs you the single most useful fact in a CRM: who did what. When each person has their own account, every note, status change and follow-up is attributed, and you can see whose enquiries are actually moving.

Set roles while you are here, but keep it light. Most small teams need two levels: people who work leads, and one or two who can also change settings and see every report. Do not build an elaborate permission scheme for ten people who sit in the same room.

Step two: pick four to six pipeline stages

The default stages in any CRM are a guess. Replace them with the steps your enquiries genuinely go through. For the architecture practice that might be: new enquiry, first call done, brief and budget understood, proposal sent, won, lost. Six stages, each a real moment you could point to.

Keep it in that range. Four stages is the floor for the pipeline to mean anything; six is about the ceiling before people stop agreeing which stage a lead is on. You can rename or split them later, once you have watched real leads move through. Resist adding a stage for a situation that has come up only once.

Step three: connect one website form

Pick the single form that matters most, usually the main contact or enquiry form on your website, and connect that one. In AliveCRM you build the form and add it to your site with one script tag, and from then on every submission arrives as a lead with the page it came from recorded.

One form done properly is worth more than five half-connected ones. Once enquiries from that form are landing cleanly and the team trusts them, add the next. The extras, conversion tracking fields for your ad campaigns, forms pointed at a specific service, a second form on a landing page, are all worth doing once the basic capture is a habit, not before.

Step four: decide how leads get assigned

Every lead needs one owner from the moment it arrives, or it belongs to everyone and therefore to no one. You have two simple options, and you should pick one now rather than leaving it to habit.

  • Automatic rotation: new web leads are shared across the team in turn, so each enquiry has an owner within seconds and the load stays even
  • One triage person: the office manager sees every new lead first and hands it to the right architect based on who is free or who fits the project

For most teams this size, automatic rotation for web leads plus the option to reassign by hand covers it. The rotation means nothing sits unowned; the manual reassignment handles the cases where a specific person should clearly take the enquiry.

Step five: agree one follow-up rule

Pick a single rule everyone follows and write it somewhere visible. Something like: every open lead must have a next action with a date, and a first response goes out the same working day. That is the whole rule. One rule that is actually kept beats a detailed cadence nobody remembers under pressure.

The point of the rule is that it makes "has this been followed up" a checkable question rather than a matter of trust. If a lead has no scheduled next step, it is breaking the rule, and anyone glancing at the list can see that.

Bring across only the leads that are live

The temptation on day one is to import the entire history: every row from the old spreadsheet, every business card, every name from a three-year-old email thread. Do not. A CRM full of dead records on the first morning teaches the team that the data is not to be trusted.

Bring in only the enquiries that are genuinely open, the ones with a next step you could name today. Everything else can be archived in the old file and imported later if it ever becomes relevant. Starting with fifty live leads that all mean something beats starting with two thousand where nobody knows which twelve matter.

What to ignore at first

The features that look important in a demo are usually the ones a small team should leave alone for the first month.

  • Custom fields beyond the basics: name, contact, source, and what they want is enough to start
  • Reports, other than a weekly glance at new leads and what is stuck
  • Extra pipelines for different services; one shared pipeline is fine until it visibly is not
  • Catalog entries for every product or project you have ever done; add them as live enquiries call for them
  • Integrations and the mobile app until the core habit has stuck at a desk

None of this is wasted work later. It is just work that makes more sense once you know how your team really uses the tool, rather than guessing on day one and unpicking it in week three.

Start everyone on the same day

A CRM half the team uses is worse than a spreadsheet everyone uses, because now the picture is split across two places. Pick a start date, spend twenty minutes together walking through where a lead is created, how it gets an owner, and where the next action goes, and agree that from that morning the old spreadsheet is closed.

Agree the small language too: what you call a lead that has gone cold, when something counts as won, who closes a lead as lost. These sound trivial and they are exactly the disagreements that make shared data messy a month in.

The first two weeks

For the first fortnight, the only measure of success is whether leads are landing in the CRM and getting an owner and a next step. Do a five-minute check each morning: any new leads unassigned, any open leads with no next action. Fix those two things and the habit forms on its own.

After a month you will have real questions. Which source brings the best enquiries. Why proposals stall. Whether one person is overloaded. That is the moment to turn on a report or add a field, because now you are answering a question instead of decorating a setup. In AliveCRM the pieces for that first setup, individual logins, customisable stages, a web-to-lead form and rotation assignment, are the parts you configure first, and the reporting is there waiting when you have a reason to open it.

See it in AliveCRM

Get a small team onto a CRM in an afternoon

AliveCRM covers the day-one setup for a team of 3 to 10 people: individual logins, stages you can rename, one website form and automatic lead rotation.

  • Individual logins with simple roles
  • Customisable pipeline stages
  • Web-to-lead form plus round-robin assignment
Explore CRM for Small Business
RS

Rahul Sharma

Example Technologies

Qualified
SourceWebsite Form
StatusIn Progress
OwnerSales Team
Next Follow-upTomorrow, 11:30 AM
Lead Captured
Assigned to Sales Team
Called, was interested
Follow-up Scheduled

Stop Losing Leads. Start Managing Them.

Capture every opportunity, give your team the right information and follow up at the right time.