Compliance-first delivery
Build a custom CRM only when your process is the advantage
Most companies do not need custom CRM development. A good off-the-shelf CRM, configured properly, covers lead capture, pipelines and reports for a typical sales team. We say that first because it is true, and because a CRM you did not need is an expensive system to keep alive.
A custom CRM earns its cost when the way you sell does not fit a standard pipeline: leads arrive mostly on WhatsApp and phone, deals depend on data held in Tally or an ERP, several branches or dealers share one pipeline under strict permissions, or per-seat licences for a large team cost more each year than owning the software. Then a CRM built around your process, connected through our systems integration work and maintained like any other production software, is both cheaper and a better fit.
Our own Insight OS brings every live-chat, WhatsApp and call enquiry into one inbox, and the Appointment Reminder App runs an AI inbox for patient conversations. They are not CRM products, but they are inbox and lead tools we run every day, and they shape how we design CRMs.
Custom CRM development services
Five pieces most custom CRM software development projects need. We build them together, or one at a time alongside the tools you keep.
WhatsApp-first lead inbox
The problem
Enquiries arrive on several WhatsApp numbers and phones, salespeople reply from their own handsets, and the conversation leaves when they do.
How we build it
We connect the WhatsApp Business Platform (Cloud API) to a shared inbox, create or match a contact on the first message, assign by rules, log consent and use approved templates for follow-ups outside the customer service window.
What you get
- Shared WhatsApp inbox with assignment
- Auto-created contacts and leads
- Template library and opt-in records
- Message cost reporting
Telephony & AI call summaries
The problem
Calls are the main sales channel, but nobody logs them, recordings sit in a telephony portal and managers cannot see what was promised.
How we build it
We integrate your cloud telephony provider for click-to-call and call events, attach recordings to the deal, then transcribe and summarise calls with Claude, GPT or open-weight models into notes and next steps that the salesperson confirms.
What you get
- Click-to-call and call logging
- Recordings on the deal timeline
- AI summaries and follow-up tasks
- Recording notice and retention rules
Pipeline, permissions & audit
The problem
Every branch, dealer and manager needs to see different deals, and nobody can tell who changed a price or reassigned a lead.
How we build it
We model your real stages and approval steps, add role, branch and territory permissions enforced on the server, and keep an append-only history of every change to deals, contacts and prices.
What you get
- Custom stages and approval flows
- Role, branch and territory permissions
- Field-level change history
- Manager dashboards
Migration from Zoho, HubSpot or Excel
The problem
Years of contacts, deals and notes sit in an old CRM and a dozen spreadsheets, full of duplicates and inconsistent stages.
How we build it
We export through the vendor’s API or bulk export, map fields and stages, deduplicate on phone and email, run trial imports for your team to check, then cut over with a freeze window and a reconciliation report.
What you get
- Field and stage mapping sheet
- Deduplication and cleansing rules
- Trial imports with sign-off
- Cut-over reconciliation report
Tally, ERP, email & calendar integration
The problem
Sales cannot see whether a customer has paid, quotes are retyped into accounts, and meetings live only in personal calendars.
How we build it
We sync customers, quotes, orders and outstanding balances with Tally or your ERP, log email threads and meetings from Google Workspace or Microsoft 365, and handle sync conflicts explicitly instead of silently overwriting.
What you get
- Two-way customer and order sync
- Outstanding balance on the deal
- Email and calendar logging
- Sync error queue and alerts
What we build custom CRMs with
Mainstream frameworks and vendor APIs, as of October 2026, so your CRM never depends on us to survive.
Laravel 13 + Livewire
The stack behind our Insight OS inbox. Quick to build admin-heavy screens, queues and permissions, and easy to hire for in India.
Node.js or Python
When the CRM sits inside a wider Node.js or Python estate, or leans on real-time features or heavy AI processing.
WhatsApp Business Platform
Meta charges per delivered message. Since 1 October 2026 that includes service replies beyond a free tier of 1,000 a month per business number, so message design affects cost.
Cloud telephony APIs
Exotel, Twilio or your existing provider, for call events, recordings and click-to-call.
Claude, GPT and open-weight models
Call summaries, lead classification and reply drafts, with prompts and outputs logged for review.
PostgreSQL or MariaDB with Redis
Relational data for contacts and deals, full-text search for quick lookups, Redis for queues and live updates.
Tools and APIs we integrate
- Laravel
- Livewire
- Next.js
- PostgreSQL
- MariaDB
- Redis
- WhatsApp Cloud API
- Exotel
- Twilio
- Google Workspace APIs
- Microsoft Graph
- TallyPrime
- Razorpay
- Metabase
Versions and vendor details checked October 2026. We pin versions per project and upgrade on a schedule you approve.
Custom CRM vs HubSpot or Zoho: the 3-year cost formula
Compare the options over three years, which is roughly how long a CRM decision lasts before someone revisits it. Fill in both sides with your own numbers:
Buy = (seats × licence per seat per month × 36) + add-ons + implementation + integration upkeep
Build = initial build + (monthly hosting and support × 36) + three years of change budget
A few things usually decide it. Seat counts grow, and the tiers with custom objects, advanced permissions and higher API limits cost noticeably more than entry plans. Build cost is front-loaded and does not rise with headcount, but the change budget is real: a CRM nobody improves goes stale within a year. Integration upkeep exists on both sides. We fill in the formula with your actual vendor quotes during discovery instead of printing list prices here, because those change and depend on region, currency and discounts.
| Buy (HubSpot, Zoho, Freshsales) | Build custom | Hybrid | |
|---|---|---|---|
| Time to first use | Days to weeks | Weeks to months | Weeks |
| Fit to your process | You adapt to the product | Built around your process | Standard CRM, custom pieces where it hurts |
| Cost shape | Grows with seats and tiers | Front-loaded, flat with seats | Licence plus a smaller build |
| WhatsApp and telephony | Marketplace apps and add-ons | Designed in from the start | Custom inbox feeding the CRM |
| Data and hosting control | Vendor’s cloud | Your cloud | Split between the two |
| Best for | Standard B2B pipelines, small teams | Large teams, unusual pipelines, strict data rules | Many growing companies |
When not to build a CRM
- Your sales process is a standard B2B pipeline and the team is small.
- Nobody will own the product after launch, either internally or through a support agreement.
- The real problem is data quality or adoption, which a new tool will not fix.
- You need it working this month.
In those cases, configure HubSpot, Zoho CRM or Freshsales properly and spend the budget on integrations and training. We will say so on the first call.
WhatsApp-first CRM design for India
For many Indian businesses the real customer record is a WhatsApp conversation with a phone number attached. Designing for that changes the data model:
- Phone number as identity. Normalise numbers to international format on the way in, match on them, and handle one person with two numbers or one number shared by a family business.
- The conversation is the timeline. Messages, media, template sends and delivery status sit on the contact record, not in a separate tool.
- Consent and templates. Record each opt-in with its time and source. Outside the 24-hour customer service window you can send only approved templates.
- Cost-aware flows. Meta charges per delivered message. Since 1 October 2026 that also covers service replies beyond a free tier of 1,000 per business number each month, and utility templates sent inside the service window. A bot that sends three messages where one would do now costs real money.
- Bot-to-human handover. An AI assistant can qualify a lead, but the handover to a named salesperson, with context, is what closes it.
Our guide to WhatsApp AI chatbot rules and costs in India covers the policy side. Consent records also matter under the DPDP Act; see our DPDP rules timeline.
Telephony and AI call summaries
Cloud telephony providers send an event for every call: ringing, answered, missed, recording ready. We attach those to the contact and deal, open a task for every missed call, and add click-to-call so outbound calls are logged without effort. For AI call summaries, recordings are transcribed and condensed by Claude, GPT or an open-weight model into a short note, agreed next steps and a suggested follow-up date. The salesperson confirms or edits the summary before it is saved, because a confident wrong summary in a CRM is worse than none. Tell callers they are being recorded, set a retention period and restrict who can play recordings.
Data migration from Zoho, HubSpot or Excel
- Export everything through the vendor’s API or bulk export, including notes, attachments and record owners.
- Map fields and stages, and decide what not to bring across.
- Deduplicate on normalised phone and email, then review the edge cases with your team.
- Run a trial import into a staging copy and let salespeople check their own accounts.
- Freeze the old system briefly, run the final import, and reconcile record counts and pipeline totals.
Permissions and audit
Enforce permissions on the server, not by hiding buttons. Most teams need role, branch or territory and record-owner rules, plus field-level limits on sensitive values such as margins and discounts. Restrict bulk export, which is how customer lists walk out of the door. Keep an append-only trail of every change to deals, contacts, prices and ownership, so “who changed this?” always has an answer.
Integrations: Tally, ERP, email and calendars
Decide which system owns each piece of data before writing any sync code. Usually the CRM owns leads and deals, while Tally or the ERP owns billing details, invoices and outstanding balances. We sync through TallyPrime’s XML interface or the ERP’s API, show balances and overdue invoices on the deal, and push confirmed orders back. Email and meetings come from Google Workspace or Microsoft 365 through their APIs and are logged against the right contact automatically. Every sync gets an error queue and an alert, because silent sync failures are how a CRM loses its users’ trust.
What drives custom CRM development cost
- The number of pipelines, roles and approval steps.
- Channels: WhatsApp, telephony, email and web forms, and how many numbers or inboxes each has.
- Integrations with Tally, an ERP, payments or industry systems.
- Migration volume and the state of the existing data.
- AI features such as call summaries, lead classification and reply drafting.
- Mobile or offline needs for field teams.
- Support and change requests after launch.
Common mistakes
- Copying every feature of the old CRM instead of the ten things people actually use.
- Letting salespeople keep personal WhatsApp running alongside the new inbox.
- Migrating duplicates and dead leads, then blaming the new system.
- Launching with no named owner for the CRM.
Checklist for choosing a custom CRM development company
- Do they start with build versus buy, and will they recommend buying when it wins?
- Have they worked with the WhatsApp Business Platform and telephony APIs, not just web forms?
- Can they show a migration plan with deduplication and reconciliation?
- Are permissions enforced on the server, and is there an audit trail?
- Will the code, data and cloud accounts be yours?
- Who maintains the CRM after launch, and on what terms?
Inbox and lead tools we run
Not CRM products, but the same core problem: every enquiry in one place, assigned, answered and recorded.
Insight OS
Analytics, live chat & leads in one script Every live-chat, WhatsApp and call enquiry lands in one inbox. Built on Laravel 13 and Livewire. Visit insight.hi4.in
Appointment Reminder App
WhatsApp & SMS reminders that grow into an AI inbox An AI inbox and AI agent, built on the Claude API, for patient conversations alongside WhatsApp and SMS reminders. Visit appointmentreminderapp.comA typical first engagement: CRM discovery and cost model
Three to four weeks, fixed scope. You come away with a decision, not a sales pitch.
Process mapping
We sit with sales, support and accounts, map how a lead becomes revenue today and list every tool and spreadsheet involved.
Build-vs-buy model
The 3-year formula filled in with your seat counts, current quotes and integration needs, plus a recommendation, which may be to buy.
Data & integration audit
A sample export from your current CRM or sheets, a duplicate and quality report, and a check of WhatsApp, telephony and Tally access.
Scope & proposal
If building wins, a phased scope with milestones and a fixed price. If buying wins, a configuration and integration plan.
Guides and related pages
Guides
Questions about CRM projects
It depends on the number of pipelines and roles, the channels you need such as WhatsApp, calls and email, integrations with Tally or an ERP, how much data you are migrating and any AI features. We start with a short discovery, fill in a three-year build-versus-buy comparison with your numbers and then send a written proposal with scope, milestones and a fixed price. No rates are published.
Sometimes. For a small team with a standard pipeline, an off-the-shelf CRM is almost always cheaper. Custom becomes cheaper when you have many users, need higher tiers for custom objects and permissions, or spend heavily on add-ons and workarounds for WhatsApp, telephony or ERP data. The three-year formula on this page shows where your break-even sits.
Yes. We connect the WhatsApp Business Platform to a shared inbox where each conversation is attached to a contact and a deal, with assignment rules, approved templates, opt-in records and delivery tracking. As of October 2026 Meta charges per delivered message, including service replies beyond a monthly free tier, so we design message flows with cost in mind.
Yes. We export contacts, companies, deals, notes and attachments, map fields and stages, deduplicate on phone and email, run a trial import for your team to check and then cut over with a reconciliation report so totals match.
Yes. We deliver remotely to businesses throughout India and in other countries, and on-site workshops can be arranged by agreement. Radiatus is registered in Delaware, USA and as an MSME in India.
You do. The code lives in your repository, the application runs in your cloud account and the data stays in your database. We document the system and can support it under an agreement, but you are free to take it in-house or to another team.
Not sure whether to build or buy a CRM?
Send us your seat count, your sales channels and your current tools. We will run the three-year numbers with you and tell you if buying wins.