Lead management system: requirements document, comparison and vendor selection

What is a lead management system — and why it is not just another CRM

A lead management system is a system that captures every inquiry, records its source, assigns it to the right person, manages the follow-up, and shows what happened up to closing. It is meant for the stage where there is still no customer: the inquiry is new, the information is partial, and the main risk is that no one will get back to it in time.

A CRM is broader. It may also manage existing customers, service, quotes, contracts, and tasks. A good lead management system can be part of a CRM, but it is judged by different questions: did every inquiry come in? Did a representative receive it? Does the business know how much time has passed? Is it possible to explain why a lead became a sale or disappeared?

Instead of starting from a list of features, start from the business failure. Write the sentence that describes it: "Leads arrive to several people, there is no clear ownership, and it is impossible to know what closed." Then define a result that can be checked: every inquiry has a source, an owner, a status, a next action date, and a closing reason.

If you are still debating between a separate system and a CRM, it is worth reading what is CRM? and why it is not just sales software as well. The difference is not in the product name, but in the process the system has to hold.

The lead lifecycle in Israel: from first inquiry to close

The lifecycle starts the moment a person leaves details, sends a WhatsApp message, calls, fills out a form, or gives details to a field agent. It ends with a close, a documented disqualification, or a move to a nurturing process. If any stage happens outside the system, the final report will be partial.

The recommended process map:

• Intake: saving name, phone, channel, source, campaign, inquiry time, and message content.
• Duplicate check: searching by phone number, email, or external identifier. If a record exists, the system should offer an update and not create another lead without explanation.
• Enrichment: adding area of interest, region, budget, urgency, relevant product or service.
• Assignment: attaching an owner by team, region, skill, source, or workload.
• First response: documenting a call, message, email, or an attempt that went unanswered.
• Qualification: determining whether there is a real need, fit, budget, and decision date.
• Follow-up: a task with a date, channel, and next action. A status like "in progress" is not enough.
• Proposal or meeting: saving amount, product, date, version, and probability if probability is used.
• Close: win or loss, with a defined amount and reason.
• After the sale: handover to customer service, service, billing, or operations, without losing the source history.

Define in advance what is allowed for each status. For example, a lead cannot move to "proposal sent" without a send date, an amount, and a contact person. It cannot move to "closed successfully" without a product and an amount. That way reports rest on data and not on gut feeling.

Requirements document for a lead management system: a full template to copy

The following sections are a requirements document you can copy into a working document and fill in with the sales, marketing, and operations managers. Do not start from a vendor demo. Start from this table, and only then check which requirements get an answer.

1. Goals and scope

• The business problem the system needs to solve: ___
• The existing inquiry channels: ___
• The number of teams and users: ___
• Who is responsible for the process: ___
• A desired outcome that can be measured: ___
• What is out of scope in the first stage: ___
• Target date for going live: ___

Acceptance question: how will we know the system works after go-live? Write three testable answers, for example: "no lead without an owner", "every lead has a source", "every open lead includes a next action".

2. Users and permissions

• User roles: manager, representative, marketing manager, operations, management, external vendor.
• Who is allowed to see all leads?
• Who is allowed to transfer ownership?
• Who is allowed to change source or amount?
• Who is allowed to export data?
• Is separation required between teams, regions, or branches?

3. Required fields

• Full name, phone, email and preferred contact method.
• Source, campaign, ad content and landing page.
• Product or service, area, language, budget and estimated purchase date.
• Owner, team, status, next action date and last update date.
• Disqualification or closure reason.
• Consent to receive marketing messages, the date consent was given and the channel through which it was given.

For each field, define the type, whether it is required or optional, who may edit it, and what happens if it is empty. Avoid dozens of fields that have no use in a report or an automation.

4. Statuses and transition rules

• New
• Reviewed
• Assigned
• Contacted
• Meeting scheduled
• Qualified
• Proposal sent
• In negotiation
• Closed won
• Closed lost
• Nurture

Next to each transition, write: who performs it, which fields are required, which task is created and which report is affected.

5. Automations and alerts

• What happens when a new lead is received?
• When is an alert sent to the representative?
• When is an alert sent to the manager?
• What happens if there is no activity?
• Is a follow-up task created after a call, meeting or proposal?
• Which messages are automatic and which require approval?

6. Reports and acceptance

• Leads by source, campaign, representative, area and service.
• Time to first response.
• Transition rate between statuses.
• Cumulative value by stage.
• Loss reasons.
• Actual revenue by source.

7. Integrations, security and budget

• Systems that must be connected: ___
• Import and export formats: ___
• Data retention period: ___
• Login and permission requirements: ___
• Setup budget: ___
• Allowed monthly cost: ___
• Connection, user, message, storage and change costs: ___

For broader working methods you can use CRM requirements document: the full guide and a work template to copy, but do not copy fields that are not related to your lead journey.

Lead intake from all channels: WhatsApp, phone, forms and agents

The system must create a single record, even when the same person starts on WhatsApp, calls afterwards and leaves a form. Require a unified identifier, duplicate search and a continuous history.

WhatsApp

Check whether the connection uses the official API, how the conversation history is stored, who may reply, and what happens when the representative replies from a private phone. Ask whether it is possible to link a conversation to an existing lead, to record voice messages and files, and to transfer a conversation to a representative without losing context. Ask to see what happens when the message arrives outside the operating hours you have defined.

Phone

Required: incoming number, outgoing number, call duration, representative, call outcome and a link to the recording if the business uses one. An unanswered call should become a task or a lead, and not remain in the call list. Check whether a search by number opens the record before answering.

Forms, landing pages, and advertising platforms

Every form should pass through source, campaign, ad set, ad, and page. Do not settle for a "Facebook" or "Google" field; that way you cannot compare campaigns. Check what happens when a form is submitted twice, when a field is missing, or when an external service is unavailable.

Field agents and import

An agent should be able to create a lead from a mobile device, even without continuous reception if that is part of the work. Add visit date, area, photo or document, and a signature of who entered the data. In an import from a file, define field mapping, duplicate detection, an error report, and the option to cancel the import before it changes existing records.

Routing, assignment, and response times (SLA)

Good assignment is not just equal distribution. It connects each lead to a representative who can handle it, and starts a clear clock from the moment of intake until the first action.

Choose a rule for each lead type:

• Round-robin: cyclical distribution among available representatives.
• Area: by city, district, branch, or address.
• Skill: by language, product, license, or domain of knowledge.
• Source: a channel managed by a specific team.
• Load: assignment to whoever has fewer open leads.
• Existing customer: return to the previous owner, if that is the business policy.

Define what the starting point of the clock is: form submission, receiving a WhatsApp message, ending a call, or entry into the system. Write what counts as a response: a call attempt, an answered call, an automatic message, or a human action. Include exceptions such as weekend, holiday, duplicate lead, representative on vacation, and a lead received outside operating hours.

Demand an escalation mechanism: an alert to the representative, then to the manager, and afterward a change of ownership or an alternative queue. In the demo, ask to show a lead that was not handled, not just an ideal process. That is where escalation rules, duplicates, and actions that were not assigned an owner are revealed.

Scoring, filtering, and automations for lead management

Lead scoring is a tool for prioritization, not a substitute for a conversation. It can weigh fit with the service, urgency, source, activity on the site, and answers in the form, but it must be understandable to the representative and open to examination.

Example scoring rules

• Relevant service: points added.
• Area the business serves: points added.
• Imminent purchase date: points added.
• Number of repeat inquiries: points added, but with a duplicate check.
• Missing phone or invalid details: points deducted or moved to review.
• Request outside the field: disqualification with a reason.

For every score, write an action: who receives the lead, which task is created, and what explanation appears. If a rep cannot understand why a lead received a certain score, the scoring becomes a black box.

Useful automations include creating a follow-up task, a reminder before a meeting, an alert about a proposal that was not answered, a status change after a documented action, and a transfer to a nurturing process. Be careful about sending too many messages. Every message should include a stop condition: a reply, a meeting, an unsubscribe request, or a close.

When a lead becomes a customer, define an explicit handoff: which data is transferred, who takes responsibility, and what happens to open tasks. Good automation replaces manual copying; it does not hide business decisions.

Measurement and attribution: how do you know what actually generates leads

A lead report should connect four points: source, activity, outcome, and revenue. The number of inquiries alone is not a measure of quality.

Ask for at least the following reports:

• Number of leads by source and campaign.
• New leads, in progress, in nurturing, and closed.
• Time to first action by rep and channel.
• Movement between each status.
• Closes and revenue by source.
• Loss reasons by product and rep.
• Leads with no activity or no next action.
• Cost per campaign versus actual revenue, if cost data enters the system.

Define an attribution model before implementation. Is the sale attributed to the first source, the last touch, all touches, or the source that led to the meeting? There is no single correct answer for every business, but an undefined answer will change from report to report.

A management dashboard should answer quickly: how many leads are open, how many are stuck, which sources produce quality leads, who needs help, and what is expected to close. If you are checking several systems, recommended CRM system for an Israeli business - full comparison can help build a comparison framework, but the metrics must be derived from your own process.

Israeli integrations that must appear in the system

An integration is not a trademark on a list of capabilities. It is a defined process: what information goes out, what information comes in, who owns it, and what happens on error.

Check the following connections:

• WhatsApp: messages, files, assignment to a conversation, consent, and handoff to a representative.
• Telephony: incoming and outgoing calls, recordings, outcomes, and missed calls.
• Forms and advertising: source, campaign, ad, page, external ID, and intake time.
• Email and calendar: documentation of correspondence, meetings, cancellations, and participants.
• Invoices and payments: customer, document, amount, payment status, and matching to a deal.
• BI: export or connection to reports without creating conflicting versions of the data.
• Import and export: an orderly file, field mapping, duplicates, errors, and a full export of the business data.

For every connection ask: who maintains it? What happens when the API changes? Is there a message or user limit? What is written to the log? Can a record that was partially ingested be restored? A system that does not answer these questions may work in a demo and fail in routine.

Information security, permissions, and regulation

Start with permissions by role and not by personal trust. A representative should see their own leads, a manager should see the team, and management should receive reports without necessarily having the ability to change every record. Define permissions for viewing, editing, exporting, deleting, and changing ownership separately.

Require secure login, a full activity log that shows who did what, when, and from which address, and documentation of permission changes. Also check backup, recovery, closing a user who left, vendor management, and support staff access.

Build a consent process: what was agreed, when, on which channel, for what purpose, and how an opt-out request is handled. Set a data retention policy by record type, and not just a general "delete" button. Separate lead data, correspondence, recordings, and documents.

A system can be built to support the business's obligations under the Privacy Protection Law (Amendment 13) and under the GDPR. This is not legal advice. Ask the vendor to describe where the information is stored, who accesses it, which sub-processors are involved, how data is exported, and what happens at the end of the engagement.

Choosing a vendor and a lead management system: questions, matrix, and total cost

Compare vendors on the basis of the same process, the same fields, and the same failure scenarios. Present five sample leads to each vendor: a duplicate, one without a response, one outside the area, a lead that returns after a month, and a lead that moved between two channels.

Evaluation matrix to copy

• Fit to the lifecycle: 25% — Are every stage, field and transition rule supported?
• Channel intake: 15% — Do WhatsApp, phone, forms and agents actually connect?
• Routing and response: 15% — Are there assignment, clock and escalation rules?
• Reports and attribution: 15% — Can you get from source to revenue?
• Integrations: 10% — Do the two-way connections fit the process?
• Permissions and security: 10% — Can you control access and log actions?
• Usability and adoption: 5% — Will reps enter data without bypassing the system?
• Total cost and flexibility: 5% — What will you actually pay and what changes in the future?

Replace the weights if your business is different, but do not let a vendor replace the score with general promises. Next to each score, write evidence: a demonstration, a document, a test process or a contractual commitment.

Questions you must ask in a demo

• Show a duplicate lead received from two channels. What does the system do?
• Show a lead that was not handled on time. Who gets an alert and what is recorded?
• Can a manager see a change of ownership, status and amount?
• How do you export all the business data and the activity history?
• Which capabilities are part of the plan and which are billed separately?
• What is the cost of an additional user, message, connection, storage, change and development?
• Who defines the fields, the automations and the reports?
• What happens when an integration fails?
• How are opt-out, deletion or export requests handled?
• What does the process of moving to another system look like if you need it?

Total cost, not just subscription price

Calculate TCO over the entire planned period of use: user licensing, setup, requirements document, data cleaning, channel connection, messages, telephony, storage, support, training, developments, reports, integration maintenance and data export. Ask that every component appear separately, including change terms.

Also examine the cost of failure: rep time on double entry, lost leads, manual reports, third-party connections and dependence on a single person who knows the system. On the other hand, do not buy a large system just to tick off capabilities. Choose the flow you can operate, measure and improve.

If you want to examine automations beyond lead management, read about automation for businesses: when a connection between tools stops being enough. When there are several channels, permissions and reports, sometimes you need one process layer rather than another point connection.

At alcyone14 we build and operate for businesses a tailored system that connects CRM, inquiry channels, automations, a dashboard and operations; for details on automation and AI inside one system.

Frequently asked questions

Does a lead management system have to also be a CRM?

No. A lead system can handle intake, assignment, follow-up, and closing, while a broad CRM also includes customers, service, and billing. Choose according to the process you need to run, not according to the category name.

How do you prevent duplicate leads from being created?

You define matching by phone number, email, or an external identifier, and decide what happens when an existing record is found. The system should display the record, save the new source, and document the merge or update.

What is an SLA in lead management?

It is a rule that defines within how much time and by what action a lead must be handled, from a defined starting point. It is worth defining exceptions as well, escalation, a substitute rep, and what counts as a real response.

Is it worth adding scoring to every lead?

Only if the score leads to a clear action and can be explained. Start with a small number of business conditions, check the results, and update the weights according to closing data.

What must be checked before signing with a vendor?

Ask for a demonstration of duplication, an untreated lead, an integration failure, data export, and permissions by role. In addition, demand a breakdown of all licensing, setup, connections, messages, changes, and maintenance costs.