A 5-person sales team is the size where CRM adoption is most critical and most fragile. Small enough that individual habit matters if two of the five do not update their deals, the pipeline is unreliable. Large enough that without a system, enquiries fall through the cracks constantly. This checklist is designed for exactly this team size.
Why a checklist matters for CRM setup
Work through this checklist in order. Each section depends on the one before it.
The 5-person team CRM setup checklist
Section 1: Platform and access (Week 1)
- [ ] CRM platform chosen and account created (Zoho, HubSpot, or Freshsales)
- [ ] All 5 team members added with appropriate permission levels
- [ ] Each team member has confirmed they can log in from both desktop and mobile app
- [ ] Company details, timezone (IST), and currency (INR) configured
Section 2: Pipeline architecture (Week 1)
- [ ] Pipeline stages defined and named to match your actual sales process (not platform defaults)
- [ ] Required fields defined at each stage what data must be present before advancing
- [ ] Deal probability assigned to each stage (used for pipeline value forecasting)
- [ ] Lost reasons defined: at least 5 specific options (price, timing, competitor, no budget, no decision)
Section 3: Lead routing (Week 1)
- [ ] Lead assignment rules configured: who owns which type of lead (by product/service/area)
- [ ] Round-robin assignment set up if all 5 reps handle similar lead types
- [ ] Owner notification configured: rep is notified via email and app when a new lead is assigned
Section 4: Lead source integrations (Week 2)
- [ ] Website contact form connected: new form submissions auto-create CRM contacts
- [ ] WhatsApp chatbot connected: qualified WhatsApp leads auto-enter pipeline
- [ ] Email enquiries: shared enquiry inbox (e.g. info@domain.com) forwards to CRM or triggers manual log
- [ ] Instagram/Facebook lead ads connected via Zapier or native integration
- [ ] Source attribution confirmed: every contact has a "lead source" field populated automatically
Section 5: Automation rules (Week 2)
- [ ] Automation 1: Welcome WhatsApp message fires within 5 minutes of new lead entering pipeline
- [ ] Automation 2: Rep task created at the same time with contact context
- [ ] Automation 3: If no activity in 48 hours on a new lead, reminder task created for rep
- [ ] Automation 4: If deal in "Proposal Sent" for 5 days with no response, automated follow-up WhatsApp fires
- [ ] Automation 5: When deal moves to "Closed Won," onboarding sequence triggers
Section 6: Reporting (Week 2)
- [ ] Weekly pipeline report configured: total leads, stage distribution, top reps
- [ ] Lead source attribution report: which sources generate leads and which generate closed deals
- [ ] Sales velocity report: average time from enquiry to close, by rep and by deal size
- [ ] Lost deal report: monthly view of loss reasons
Section 7: Team training and adoption rules (Week 3)
- [ ] 1-hour team training session completed: pipeline stages, deal logging, mobile app
- [ ] Adoption rule documented and communicated: if a deal is not in the CRM, it does not count for commission reporting
- [ ] Weekly pipeline review scheduled: every Monday, team reviews open deals in the CRM together
- [ ] First 30-day review scheduled: team discusses what is working, what to adjust
Section 8: Post-launch validation (Day 1 7 after go-live)
- [ ] Test lead sent through every source and confirmed in CRM
- [ ] Automation triggers tested: create a test deal and confirm automations fire correctly
- [ ] Mobile app tested by all 5 reps on their own phones
- [ ] First week's data reviewed: any missing sources, any reps not logging activity?
Ready to take the next step?
Let Perceptra scope the right approach for your business.
Book a Free Strategy Session ?Frequently asked questions
For a 5-person team with one lead source and simple automation, 2 3 weeks from start to live. For multiple integrations and complex automation, 4 6 weeks. We can complete this in parallel with your team's normal operations no downtime.
Section 2: Pipeline architecture. A wrong pipeline is much harder to fix after data is in the system than before.
Complete Sections 1 4 before going live. Sections 5 8 can follow in the first two weeks after launch. Do not delay launch waiting for perfect automation imperfect and in use beats perfect and never deployed.