Measuring a website when the sale is months away

For considered purchases, the enquiry arrives in spring and the contract is signed in autumn. That gap makes every monthly report either premature or out of date, unless you measure differently.

Talk to us about your site

With long cycles, split the measurement in two: track enquiries per month as the fast signal, since it responds to site changes quickly, and track what enquiries eventually become worth as a slow figure updated a few times a year. Judging a site on closed revenue alone means always looking at the results of changes made half a year ago.

The reporting problem in one sentence

If your sales take six months, then the revenue you see this month reflects a website that existed half a year ago. Every improvement you make appears in a report long after you made it, and by then several other things have changed too.

So a single number cannot serve both purposes. You need a fast signal for steering and a slow one for judging, and confusing the two is the source of most of the frustration.

The fast signal: enquiries

Enquiries respond immediately to changes on the site, because they depend on the visitor deciding to act rather than on your sales process concluding.

Track them monthly, connected to the pages that produced them. This is the number that tells you whether a rewritten service page, a shorter form or a clearer price signal worked.

The slow signal: what enquiries become

Separately, follow enquiries through to their conclusion, and update the figure a few times a year rather than monthly. What share become customers, how long it takes, and what they are worth.

This changes slowly, so measuring it constantly adds noise rather than insight. Twice a year is usually enough to notice a genuine shift.

  • Share of enquiries that become customers.
  • Typical time from enquiry to signed work.
  • Typical value per enquiry, including the ones that went nowhere.
  • Whether any of these are drifting over a year.

Watch enquiry quality, not just count

With a long cycle, a drop in quality takes months to appear in revenue, by which point the cause is hard to identify. So watch for early signs in the enquiries themselves.

Are they asking the right questions? Do they resemble the customers you want? Did they mention a page or a search that suggests genuine intent? A pattern of vaguer enquiries is worth investigating before the revenue arrives to confirm it.

Two errors to avoid

The first is judging a change too early, concluding it failed, and reversing it before the effect could possibly have appeared. The second is the opposite: waiting so long for certainty that nothing is ever concluded and the site drifts untended for years.

The way through is to agree in advance what you will judge and when. Enquiries after two months, closed work after a year, written down before the change is made.

Keep the record long enough to be useful

Long cycles make record-keeping more valuable, not less, because memory cannot span the gap. Keep enquiries, their dates, their sources, and what eventually happened to them in one place.

After two years that record answers questions no analytics tool can: which pages bring the customers who actually sign, and how long it usually takes them to decide.

How Licheo reports for long cycles

We report enquiries monthly as the responsive signal and revisit the conversion and value figures a few times a year rather than pretending they change month to month.

Where a figure is still maturing, we say so instead of implying a conclusion the data cannot yet support.

Part of a larger guide

This page is one part of Revenue per visitor. The other parts:

Questions people ask

How do I measure a website when sales take months?
Split it: track enquiries monthly as the fast signal that responds to site changes, and track what enquiries eventually become worth as a slow figure updated a few times a year.
How long should I wait before judging a change?
Judge enquiries after a couple of months and closed work after a year, and decide those horizons before making the change so nobody moves the goalposts afterwards.
How do I spot a drop in enquiry quality early?
Read the enquiries themselves. Vaguer questions, less resemblance to your usual customers, and no mention of anything specific from the site all appear months before the revenue confirms them.
Should I stop reporting monthly?
No, but report the right thing monthly. Enquiries and calls respond quickly and are worth watching. Closed revenue reported monthly in a long-cycle business mostly describes decisions made half a year ago.
What record should I keep?
Every enquiry with its date, source, the page it came from, and what eventually happened. After a couple of years that record answers questions no analytics tool can, particularly which pages bring customers who actually sign.

Measure at the right speed

Fast signals monthly, slow ones a few times a year, and nothing presented as concluded before it is.

Talk to us about your site Read the full guide