In this guide 6 sections
Ask six things. Where do leads come from? How are duplicates caught? Who gets each lead, and how fast? How are follow ups reminded? How does a lead become a quote? What do the reports show? Insist on seeing each answer run on your own sample data, including a messy spreadsheet of real enquiries, since slides prove nothing.
Where do leads come from and how do they arrive?
List every place enquiries land today: website forms, a phone line, WhatsApp, an email inbox, classified portal listings, walk-ins and trade shows. Make the vendor show each flowing in. Some need a connector, others need typing. Retyping signals a poor fit.
Ask what is stored with each lead: you want the source, the UTM campaign tag, the timestamp, the original message and the landing page it came from. A bare name and mobile number cannot show which advertisement paid for the enquiry, so the campaign budget ends up judged on guesses instead of counts.
Judge by the demo. A good answer names the integration and runs a live test, while a weak one promises a developer later and moves to the next slide. Also ask what happens to a form entry when the lead tool is down for an hour, since lost enquiries are the costliest bug of all.
- Which channels connect without custom work
- Whether the original message is saved
- How a bulk import from a spreadsheet is mapped
- What happens when a form submission fails
How are duplicates and bad records handled?
One buyer, two channels. Ask how the tool spots a repeat by phone number, email or company, and whether it merges the records or merely warns the user. A shared phone number for a family business makes naive matching merge two different buyers, so ask how the vendor treats it.
Load twenty rows from your own sheet with a few deliberate repeats and spelling variations, then watch what comes out and check the result sheet line by line. Do not trust a summary screen.
The right answer is a match rule you can change, a merge that keeps the history of both records and a log of what was merged.
Who gets the lead, and what happens if nobody calls?
Routing sets the speed of response. Ask whether routing works by city, product, language or round robin, and whether a manager can reassign a whole list in bulk when a salesperson resigns. Territories should be yours to edit. Round robin sounds fair, yet it fails when one salesperson speaks the buyer’s language and the others do not, so the buyer reaches a colleague who cannot help.
Then test the follow up. Can a salesperson set a next step with a date, does the tool remind them, and does it tell their manager when a lead sits idle too long?
A reminder shown only as a dashboard number gets ignored by everyone, so you want an overdue list and an escalation rule. Ask whether a missed call or an unanswered WhatsApp message creates an overdue task by itself, because people forget the quiet ones. Quiet failures hurt most.
- Round robin, territory and product based routing
- Reassignment when a salesperson is on leave
- Reminder channel: app, email or WhatsApp
- Escalation to a manager after a set idle time
How does a lead turn into a quote?
Many tools capture leads well, then stall. Ask what happens when the buyer agrees to a proposal: does the contact with its requirement carry into a quotation, or does someone retype both into a spreadsheet template?
Check the price list link, because a quote should pick up the product, rate and discount limit from one place, with approval needed above a set discount. Ask who sets each salesperson’s ceiling.
Walk one lead through, live. Count the clicks. Retyping is the tell. Note each place where the buyer’s phone number or requirement is typed twice, because every repeat is a future mismatch between the quotation and what the buyer asked for.
What do the reports show, and who owns the data?
Request the reports you will actually read, namely leads by source, first response time, conversion by salesperson and lost reasons, and have them built live from your sample leads. Lost leads need a reason code. Otherwise that report stays empty. A dashboard that needs a consultant for each new chart is a warning sign about the ongoing cost of owning the tool.
Then ask about ownership: can you export leads, notes and call logs as CSV, and what happens to the data if you leave the vendor? Get the answer in writing.
Finish with a two week trial using real leads, scoring the vendor on these questions and deciding from that sheet rather than from whichever demo looked best. No sheet, no decision.
- Source, response time and conversion reports
- Mandatory lost reason list
- Full export of leads, notes and activity
- Roles that limit who sees which leads
Vendor question sheet
A table with six rows, one for each topic above, covers sources, duplicates, assignment, follow up, quote handoff and reporting, each row tied to one pass test. Columns hold the question, the answer you should expect, what the vendor said or showed, a pass or fail mark and a notes box. A total score sits at the foot.
Open a blank worksheet to printQuestions owners ask
How many leads do we need before lead software is worth it?
Count matters less than loss. If enquiries arrive across channels, follow ups rest on memory and nobody can say how many went cold last week, a tool pays off even at low volume.
Should lead management and the quotation tool be the same system?
Separate tools are fine. The handoff is what matters, so the contact and the requirement must reach the quotation without anyone retyping them or pasting them from an email. If the tools are separate, ask how they connect.
What should a trial period test?
Use real leads from two channels and push through one duplicate, one assignment, one overdue reminder and one quote, with the actual users doing the work.
What is the most common reason a lead tool fails?
Salespeople stop updating it once it adds work. Keep screens short, make reminders genuinely useful, and let managers run their reviews from the same records so nobody keeps a private copy in a spreadsheet.
