Yes.
You need a simple CRM — but only for the leads half of what you described.
Why
Leads, claims and collections look similar but are three different processes: leads are a pipeline (stages, conversion), claims are SLA-driven tickets (status, deadlines, compliance trail), collections are recurring chase cycles tied to a policy record. At 50–200 inquiries/month across web form, referrals and WhatsApp with 4–10 people touching them, a sales CRM will pay for itself on the lead side alone — but jamming claims and collections into it is what makes these projects collapse. Those two belong in your policy/admin system or a ticketing tool, not next to your sales pipeline.
What you actually need
- Pipedrive — roughly $15/user/mo entry tier (verify on their pricing page) — one visual pipeline for *new business only*: Inquiry → Qualified → Quoted → Underwriting → Issued. Strong mobile app for field reps, which matters for referral-driven life insurance agents.
- Respond.io (paid monthly — check current pricing) — a shared WhatsApp inbox so 4–10 people can work one number, with conversations pushed into Pipedrive as leads. The free WhatsApp Business app won't work for you: it can't handle auto-replies, qualification flows, or multiple agents on one number.
- Habit: claims and collections stay out of the CRM. Keep them in your policy admin system (or a separate Zoho Desk / Freshdesk-style ticket queue) with their own SLAs. Link by policy number, don't merge.
Do this today
Open a spreadsheet and tag every inquiry from the last 14 days with one of three labels: NEW_LEAD, CLAIM, COLLECTION. Count each pile. That single 30-minute exercise tells you the real ratio and kills the "one system for everything" idea before you spend a cent.
What to ignore
Ignore Salesforce Financial Services Cloud, HubSpot Enterprise, and any "insurance CRM suite" demo that promises leads + policy admin + claims in one screen — those are built for 50+ seat carriers, not a 4–10 person team. Also skip Outreach/Salesloft/Apollo-style outbound tooling — you're inbound and referral-led, not running cold sequences.
What doing nothing costs you
With WhatsApp leads landing on individual phones and no shared pipeline, some percentage of your 50–200/month go cold simply because nobody knows whose turn it is — and in a regulated product, a missed claim SLA is a complaint risk, not just a lost sale.
Where this leaves you
The plan gives you: one place every new-business lead lives, a WhatsApp number your whole team can answer, and a clean separation that stops claims work from polluting your sales reporting. The contrarian bit: the "insurance CRM" your vendor is quoting is almost always a policy admin system with a weak pipeline bolted on — you want the opposite.
When to revisit this
When a single person is handling more than ~80 WhatsApp conversations a week, or when you hire your first dedicated claims handler — that's when the shared inbox and the ticketing split start to strain.