Measurement

How to track a quote pipeline without collecting unnecessary details

Use a small set of consistent stages to understand where enquiries need attention.

By Graphic Core   /   Published
Monthly guide series: April 2023

Four dishes hold decreasing numbers of wooden counters, illustrating stages in an example enquiry pipeline.

Choose the decision before the data

A quote pipeline is a way to see what happens between an initial enquiry and an agreed piece of work. It can show whether requests need a response, whether a quote is outstanding and where a person has asked to pause. Start with a practical decision, such as whether the team has capacity to follow up, rather than collecting a large set of figures because a tool offers them.

The record should support the customer's journey as well as the business. A small service company might need an owner, a next action and a date; a complex project may need additional information. Decide why each field is necessary and who may see it. A spreadsheet can be sufficient if it is secured and maintained appropriately.

Define stages that match real work

Use short labels that your team interprets consistently: received, suitable, quote sent, accepted and closed are possible starting points. A suitable enquiry is not the same as a quote, and a quote is not the same as a confirmed job. Write down the criteria for each stage and how to record a request that needs more information.

Allow a person to change their mind and avoid moving a record forward simply to make a report look better. If two colleagues classify the same request differently, review the definitions together. A small set of stable stages makes a comparison more useful than a complicated pipeline with categories that nobody updates.

Keep the information proportionate

Separate the detail needed to handle a live enquiry from the aggregate information used in a report. Staff may need a contact route and a brief description of requested work; a monthly review usually does not need names, full messages or an address. Use broad categories such as service type and general fit when they are sufficient.

Do not enter sensitive customer details into an analytics tool or an unapproved shared document. Explain data use in accessible privacy information, limit access, and decide when records will be reviewed or removed. A different retention reason may apply to an actual contract or financial record; check the purpose and any relevant obligations before deleting.

Calculate rates carefully

A stage-to-stage rate divides the number reaching the later stage by the number in the earlier stage and multiplies by 100. Define the period and make sure you compare the same group: quotes sent in one month may relate to enquiries received earlier. A rate is a prompt for investigation, not a judgement about a member of staff.

Use counts alongside percentages, especially when there are few requests. A change from one to two accepted quotes can produce a large percentage increase even though the underlying numbers remain small. Record incomplete cases separately and avoid treating an unanswered or delayed decision as an automatic rejection.

A worked illustrative pipeline

Suppose, purely as an example, that a team follows the same group of 20 enquiries. It considers 12 suitable and sends six quotes after receiving enough information. The suitable-enquiry rate is 12 divided by 20, or 60%; the quote rate among suitable enquiries is six divided by 12, or 50%. Those values describe this imagined group only, not an industry benchmark.

The team should check whether the other suitable requests are still awaiting details before drawing a conclusion. A low quote count may reflect delays, lack of availability or a customer's changed plans, not necessarily poor marketing. Investigate with the people doing the work rather than assigning a single cause from the chart.

ILLUSTRATIVE CHART

An example enquiry pipeline

  • Enquiries20 requests
  • Suitable12 requests
  • Quotes sent6 requests
Illustrative example, not measured results. Each later stage is a subset of the same group.

Turn the review into an action

If many enquiries are unsuitable because an area or service is unclear, improve that explanation on the relevant page. If suitable requests are waiting for a reply, agree a manageable ownership process before increasing promotion. If quotes are being sent but decisions are delayed, consider whether the scope and next step are clear; do not assume the price is the only cause.

Pick one change, name an owner and choose when to review it. Keep notes about the action and any changes in capacity or season so that a later comparison has context. This is not a substitute for listening to customers or checking that messages reach the right inbox.

A cohort worksheet you can reuse

Create one row for a defined group of requests and record the date range, number received, number that met the agreed suitability criteria and number sent a quote. Add a separate column for cases still open. If a request arrives at the end of the period and is quoted later, keep it in its original group when calculating how that group progressed.

Write the formula beside the number: suitable requests divided by received requests, multiplied by 100. In the illustrated group, 12 divided by 20 gives 60%. Six quotes divided by 12 suitable requests gives 50%. Neither calculation tells you why a person accepted, declined or has not replied, and neither is meaningful when its denominator is zero.

If a project receives a revised quote, decide whether the report counts projects or quote documents and keep that definition consistent. A duplicate request from the same person may also need investigation. Record an aggregate correction rather than copying the person's private message into the dashboard. Review a few records with the responsible team before sharing the resulting chart.

Agree who closes a stale request and whether the person has been told what will happen next. A paused conversation, declined project and uncontacted enquiry may all need different next actions even if they are grouped together for a simple report.

A practical review checklist

Check that every open record has an appropriate owner, a clear next step and only the information needed for that purpose. Review whether closed requests can be deleted or anonymised under your policy, and check permissions when someone leaves the team. If the system exports reports, make sure those copies are controlled as well.

For each reporting period, record the stage definitions, the dates covered and whether cases are complete. Look for mismatched categories, duplicates and gaps before calculating a rate. Agree one follow-up action and use the next review to see whether it addressed the original problem.

YOUR NEXT MOVE / 01

Ready to make
more of your business?

Tell us about your website, your services and where you want to grow.

START A CONVERSATION