systemFree audit
Run the audit on your site

Would you rather talk it through? Direct contact

Language of this page: ITEN

GROW / CRO & analytics

Measure. Learn. Improve.

We turn data into decisions about journeys, content and growth priorities.

Run the audit on your siteLet’s talk about CRO & analytics

The problem to solve.

A report full of visits can leave the main question open: where do customers stop? We build a reading of the journey that lets you choose which obstacle to face.

The outcome

What you receive.

What you are left with

A plan of events
The important actions defined, separating clicks, enquiries and confirmed results.
A reading of the funnel
Steps and segments with sufficient data, including technical errors.
Experiments with hypotheses
Hypothesis, change and evaluation criteria agreed before the test.
Documented decisions
Reports with evidence, limits and a next action.

The usual order

01 · Definition
What counts as a result: a qualified enquiry, a confirmed purchase, a completed activity.
02 · Data quality
Completeness and reliability of the tracking before reading any number.
03 · Reading
Steps, segments and obstacles with the data available.
04 · Test or research
An experiment when volumes and time are enough; otherwise qualitative research and usability tests.

What we start from

Access
To the measurement tools.
Definitions
What counts as a conversion.
Commercial data
Orders, enquiries and outcomes: without them the funnel is half the story.
If there is no tracking
We define the events and we implement them: without measurement the work stays a partial reading.

The phases describe the usual order in which these elements are approached, not a calendar. “What we start from” lists what is needed on your side: where a piece does not exist yet — a page, a content, a flow, a tool — producing it enters the scope of the work. Times and costs are defined in the brief: there is no price on this page. To see what the structure of your site says today, the free audit reads any public URL: no payment, no account.

The scope

What we build.

01

A plan of events

Definition of the important actions and the separation between clicks, enquiries and confirmed results.

02

Reading the funnel

Analysis of the steps and segments with sufficient data, including technical errors.

03

Experiments

Hypothesis, change, evaluation criteria and constraints agreed before the test.

04

Documented decisions

Reports with evidence, limits and a next action, instead of a set of metrics without context.

Where it fits.

In GROW you measure what the other three parts produce. You start from the plan: which event actually describes a result — a qualified enquiry, a confirmed purchase, a completed activity — and which data records it reliably. Then the analysis of the journey, then the interventions, then the comparison between consistent periods. If the data is not reliable, the first thing to repair is the data: an experiment run on a wrong measurement only produces a wrong decision with more confidence. It is the work that makes it possible to say, afterwards, whether something changed.

What it covers.

  • Measurement plan
  • Funnel analysis
  • Experiments with clear hypotheses
  • Reports and continuous optimisation
Contexts

Where it applies.

The problem that brings you here.

The site does not produce useful enquiries.

Does the visitor understand what you offer, and find a clear next step? Start from the journey: message, service pages, form and confirmation. If the tracking is reliable, it shows where people stop.

These are the situations described in Where to start, in the same shape in which you choose them: not a classification of sectors, but the point where you begin.

Before starting

What we need from you.

Access to the measurement tools, conversion definitions and the commercial data available. We verify the quality and completeness of the tracking first; if it is not implemented yet, we implement it.

Delivery criteria

How we verify it.

We compare the events against test actions. Experiments require adequate volumes and time: when those are missing, we use qualitative research and usability tests.

What it is not.

Not always A/B tests: with little traffic a test may not give an answer, and the method is chosen on the data available — sometimes qualitative research or a usability test. It is not reporting: a report that produces no decision has measured nothing. It does not bring traffic (that is FIND) and it does not build the pages (that is BUILD). And this site does not publish its own numbers: it does not use analytics on its content, as it states on the cookies page — the measurement we propose is on your system, not an industry average.

Questions

Do you always run A/B tests?

No. With little traffic a test may not give a reliable answer; we choose the method on the data available.

Which metric should we look at first?

The one that describes the result of the journey: a qualified enquiry, a confirmed purchase or a completed activity.

Related steps

The system continues.