PipeTrack
Custom CRM and lead management software
Every enquiry followed up, every deal visible.
For sales teams that bought a CRM, stopped updating it, and went back to a spreadsheet. Built around the stages your business actually sells through, with the data entry reduced to what a salesperson will realistically do between calls.
Screens
What it looks like
4 screens from the working demo — the same data you will see if you open it.
The problem
Why this gets built
Leads arrive from the website, IndiaMART, referrals and walk-ins, and land in four different places. The ones that get followed up are the ones somebody happened to remember. Nobody can say which source is worth the spend, because nobody tracked what happened next.
Who it is for
Fit
Sales teams from two to fifty people who are currently running on spreadsheets and memory.
Capabilities
What the system does.
Lead capture & sources
Enquiries recorded with their origin, so spend can be judged against conversions rather than clicks.
Pipeline stages
New, qualified, quoted, negotiation, won or lost — with value and age per deal.
Follow-up scheduling
Next action and owner on every open lead, with what is due today at the front.
Quotations
Quotes raised against a lead and tracked to acceptance rather than emailed and forgotten.
Contacts & companies
History against the organisation, so the next conversation starts from the last one.
Conversion reporting
Win rate by source, by stage and by owner, showing where deals actually die.
See it running
PipeTrack is a clickable demo — open the modules, browse the tables, see how the screens fit together.
Buying decision
Why off-the-shelf falls short here.
Most CRM failures are not feature failures. The software works; the team does not use it. That happens when the pipeline stages are somebody else's, when logging a call takes eight fields, and when the salesperson gets nothing back for the effort. The data decays, the forecast stops being believable, and management goes back to asking people directly.
The second failure is the quote. In many businesses the quotation is the real artefact - it carries the specification, the rates, the terms and the revision history - and it usually lives in Excel, outside the CRM entirely. So the CRM holds a number someone typed, while the document that would justify it sits on a laptop.
A custom build inverts the trade. Stages match how you actually qualify and close. Entry is minimal and mostly derived from things that already happen - a call, a WhatsApp message, a quotation sent. And the quotation is generated inside the system, so the pipeline value is the quoted value.
Comparison
Packaged product vs a custom build.
The differences that decide it, for this sector specifically.
| Aspect | Packaged product | Custom build |
|---|---|---|
| Pipeline stages | A standard funnel you adapt to | Your stages, with the entry and exit criteria your team already applies informally |
| Data entry | Many required fields per activity | Minimal, and largely captured from calls, messages and documents as a side effect |
| Quotations | An attachment | Generated in the system from your rate card, versioned, with the pipeline value derived from it |
| Lead sources | Web form and manual | Website, WhatsApp, IndiaMART, calls and walk-ins landing in one queue with the source preserved |
| Follow-ups | A task list | Scheduled against the deal with reminders where the salesperson will see them |
| Reporting | Generic dashboards | The two or three numbers your management actually decides on, computed the way you compute them |
Integrations
What it connects to.
A system that cannot reach the tools already in use becomes another island. These are the connections this sector normally needs.
Telephony
Click to call and automatic call logging, so activity is recorded without being typed.
WhatsApp Business
Conversations attached to the lead rather than trapped on a personal phone.
Accounting
A won deal becomes an invoice in Tally or Zoho Books without re-entry.
Website and marketplaces
Enquiry forms and marketplace leads routed straight into the queue with the source intact.
Threads attached to the deal, with templates for the messages that get sent repeatedly.
How it runs
From first conversation to cutover.
Indicative for a build of this shape. The parallel run is not optional — nothing is retired until the numbers agree.
- 1 week
Discovery
We sit with two salespeople and map how a deal really moves, which is rarely the documented process.
- 3-5 weeks
Core build
Lead capture, stages and quotations - the parts that carry the team's daily work.
- 2-3 weeks
Team pilot
One team uses it exclusively. If they go back to the spreadsheet, we fix the reason rather than mandate the tool.
- 1-2 weeks
Rollout
Remaining teams, integrations and management reporting switched on.
After rollout
What changes day to day.
- The pipeline is believable because its value comes from issued quotations rather than typed estimates.
- Leads stop being lost between channels, since WhatsApp, calls and web forms arrive in the same queue.
- Follow-up happens on schedule because the reminder reaches the salesperson where they already are.
- Management asks the system instead of asking the team, which is the only real test of a CRM.
Described qualitatively on purpose. We do not publish percentage improvements we cannot attribute to a named client with their agreement.
Questions
Common questions.
Can leads be captured from multiple sources?
Yes. Website, marketplace enquiries, referrals and walk-ins all land in one place with their source recorded, so spend can be judged against conversions.
Does it remind the team to follow up?
Yes. Every open lead carries a next action and an owner, with what is due today shown first.
What reporting does it provide?
Win rate by source, by stage and by owner, which shows where deals actually die rather than only where they are counted.