Custom CRM & sales systems
Sales and enquiry pipelines shaped around how a specific business actually sells, not a generic CRM the team refuses to update.
CRM at Nowgray
A custom CRM is a sales system shaped around how one business actually sells, rather than a generic pipeline the team is asked to adapt to. In practice the difference shows up in small places: the stages match what really happens, the required fields are ones the salesperson already knows at that moment, and the follow-up happens on the channel the customer replies on.
Nearly every CRM failure we are called in to fix has the same cause. The software was fine; nobody updated it. Reps kept the real pipeline in their head or in WhatsApp because entering it properly took too long and gave them nothing back. Once the data is incomplete, the reports are wrong, managers stop trusting them, and the system quietly becomes an expensive contact list.
So the design question is not which features to include. It is what the salesperson gets in return for each field they fill. If updating a deal produces their next call list, their reminders and their commission view, it gets updated. If it only produces a report for someone else, it does not.
In India that usually means WhatsApp is not an add-on. It is where the conversation happens, so it belongs inside the record rather than in a separate app nobody logs.
What usually brings people here
The real pipeline lives in WhatsApp
Deals progress in chats and never reach the CRM, so forecasts are guesses and handovers lose context.
Too many required fields
Every extra mandatory box at the wrong moment is a reason to skip the entry entirely.
Stages that do not match reality
Generic stages like Qualified and Negotiation mean nothing in businesses that sell on site visits, quotations or credit approval.
Leads lost between channels
Enquiries arrive by phone, web form, WhatsApp and marketplace, and each lands somewhere different, so some are never worked at all.
What we build
- Pipelines with stages named after your actual sales process
- Lead capture unified across web forms, calls, WhatsApp and marketplaces
- WhatsApp conversations attached to the deal record
- Quotation and proposal generation from the deal, with approvals
- Follow-up reminders and task queues that give reps their day
- Territory, team and role-based visibility rules
- Reporting on conversion by source, stage, rep and product
Detailed CRM case studies are being written up with our clients now. In the meantime, these are the services behind this work.
Common questions.
- For many businesses those are the right answer and we will say so. They are strong products with ecosystems we cannot match. Custom becomes worth it when your sales process is genuinely unusual, when per-seat pricing stops making sense at your headcount, or when you have already had a generic CRM fail adoption. That last one is the most common reason clients come to us.
- Yes, through the official WhatsApp Business API rather than an unofficial workaround. Conversations attach to the deal, templates are approved, and automated follow-ups are sent within policy. Unofficial integrations get numbers banned, so we do not build them.
- Yes. Contacts, companies, deals, history and attachments from Zoho, HubSpot, Salesforce, Excel or a legacy system. Migration includes deduplication, which is usually the part that takes the time.
- By making the system useful to them before it is useful to management. Their call list, their reminders, their numbers. We also keep required fields to the minimum that keeps reporting honest. Adoption is a design problem more than a training problem.
Why not just use Zoho, HubSpot or Salesforce?
Can it integrate with WhatsApp properly?
Can we migrate our existing CRM data?
How do we get the team to actually use it?
Building something in CRM?
Tell us the problem. We'll come back with scope, timeline, and a fixed quote.