Skip to main content
GullySystem

CRM for Leads, Quotations and Territories

CRM software keeps leads, accounts, quotations, orders and territories together. Each enquiry has an owner and a next date, so the pipeline stays with the firm when a salesperson leaves.

Where enquiries go missing

Enquiries arrive from online directories, WhatsApp and the phone. Without one owner per lead, two people ring the same buyer, or nobody does.

  • The same buyer chased by two people in one morning
  • Quotation revisions saved as files named final-2
  • Deals left idle while their owner is on leave
  • A pipeline held only in a salesperson’s diary

The eight CRM modules

Six entries below cover all eight modules. Leads and quotations are where most firms start.

Lead management

Enquiries from every channel arrive with one owner and one next date. Duplicates are caught before two people chase the same buyer.

Contact and account management

The firm and the people inside it are kept apart. Orders, quotations and complaints attach to the account, not to a mobile number.

Opportunity and pipeline management

Each live deal shows what the buyer wants, its value, its stage and the last conversation. A board groups open deals by stage and executive, with ageing that shows what is stuck.

Quote and proposal management

Quotations are built from your own rate list, with every revision kept in order. A discount past your limit is held for approval.

Order management

A confirmed order is followed from the day it is taken until it is delivered and billed. Part deliveries are included.

Forecasting and territory management

The forecast draws on confirmed orders, open deals with a closing date and the same month last year. Territories record who covers which district, route or postal code, with a visit plan.

Connections to WhatsApp and billing

Much of the selling already happens on a phone. The CRM reads from those channels instead of asking for re-entry.

  • Enquiries pulled from online directories and your website form
  • Quotations and confirmations sent on WhatsApp from the record
  • An accepted quotation becoming an order, then an invoice
  • Follow-up reminders reaching the executive by date

What a CRM does not do

A CRM records the calls that happened and shows the ones that did not. It does not make anybody ring a customer. Where sales staff enter nothing, it becomes a second set of books that nobody reads.

A salesperson’s week with the pipeline

A salesperson lives by the next date on each enquiry. The CRM keeps those dates visible and tied to the person responsible. One week of a field salesperson shows how the record changes as the work moves along. Watch the dates.

Monday’s call list

The executive opens the leads due today, sorted by promised follow-up. Each lead shows the last conversation in a line or two. Scrolling is not needed. Old messages stay behind the record until someone wants to read them in full.

A quotation after a site visit

After meeting a buyer, the executive builds a quotation from the record and sends it on a messaging app. The quotation stays attached to the account. A revision replaces nothing. It sits beside the first.

Handing over before leave

Before a week away, the executive reassigns open deals to a colleague. The colleague sees every note and next date. Buyers keep getting replies. The pipeline survives an absence without a scramble, and nobody has to ring the absent person.

Friday’s manager review

The sales manager reviews the pipeline by stage and by territory. Deals with no date set are listed first. The conversation moves from asking what happened to deciding who calls whom on Monday, and which quotations deserve a second look.

Decisions about enquiries before the CRM is set up

A CRM holds whatever the firm decides to record. The choices below come before the first lead is typed. They shape who owns an enquiry, what a stage means and how old records are brought across. Settle them together first.

Who owns a new enquiry

Settle how a new enquiry is assigned, whether by area, by product or in turn. Without a rule, two people chase the same buyer. Reassignment is still allowed. The reason is written beside it, so the move can be understood later.

What each stage means

Agree in plain words what qualifies a lead, what counts as a proposal and what closes a deal. Staff use the same words. Forecasts then mean the same thing to everybody who reads them, from the owner to the newest executive.

Which details are compulsory

Choose what must be entered before a lead is saved, such as source, product and a next date. Fewer compulsory fields make entry quick. Leave out too much and the pipeline turns thin and hard to read when reviews begin.

How existing contacts come across

Contacts live in phones, diaries and spreadsheets. Decide which are imported and who removes duplicates first. A trial load checks the fields. Only then does the full set follow, with each executive confirming their own contacts came across.

Make an informed decision

Agree the evidence before signing off this part.

Use a representative scenario to decide what this part of the system must show and where review is still needed.

The eight CRM modules

Which assumptions stop being valid when the quotation changes?

For “The eight CRM modules”, compare an accepted version with a later revision. Identify changed quantities, exclusions and validity dates before the revised amount is used downstream.

Background reading: ERPNext: quotation terms

Connections to WhatsApp and billing

How does a stop request affect messages already waiting to be sent?

For “Connections to WhatsApp and billing”, check the intended recipient and permission before sending a test message. Agree how staff record a withdrawal and prevent a queued follow-up from going out.

Background reading: WhatsApp: permission and opt-outs

FAQ

Frequently asked questions

Will our sales team actually use the CRM?

It depends on how little the daily entry asks for. The daily screen stays at a handful of fields on a phone, and the manager’s morning list is built from those entries. Adoption is reviewed during implementation.

Can it pull enquiries from online directories and our website?

Yes. Directory enquiries arrive through their feed where one is offered, and website forms post straight into lead management. Each lead keeps the channel it came from.

Do we need CRM software when we already use accounting software?

Yes, for a different job. Your accounting software holds what was billed. It does not hold enquiries that never became a bill, quotations the buyer rejected, or dealers nobody has visited lately.

What if we are unsure a CRM fits our trade?

It depends on the trade, and the first conversation is where that is checked. The team looks at how enquiries reach you, what your quotations look like and where deals are lost, then writes back with what to fix first. Hiring GullySystem afterwards is no part of it.

Talk to us

Tell us what you need.

Tell us what your team does today, where work gets stuck and what you want to change.

What happens after you share your requirements

  1. We review your brief and the systems you already use.
  2. We clarify the workflow, missing information and the work to consider first.
  3. The proposed scope sets out the deliverables, responsibilities and dependencies.
  4. Review the scope and commercial terms before deciding whether to proceed.

Start with your requirements

Describe your current process, the people involved and the change you need. Start with the details you know; we can clarify the rest together.

Share your requirements