Skip to content

Gridsmith

Automation & Intelligence

Data, Reporting & Analytics Infrastructure

Every report is rebuilt by hand and no two of them agree.

Reporting pipelines and the analytics infrastructure underneath them: collecting data from the systems that hold it, defining the measures once, and producing reports that reconcile because they come from the same definitions.

Analytics implementation here means your measurement — tags, events, consent handling and the data layer on your properties. It is client work, and it is unrelated to the separate decision about whether this website runs analytics of its own.

Where measurement involves personal data or consent, we implement the arrangement your policy sets; we do not decide it for you.

What this covers

  • Data/reporting systems
  • Analytics infrastructure

What you get

Measure definitions
Included
Agreed once, so reports reconcile.
Data pipeline
Included
Collection and transformation from the source systems.
Reports or dashboards
Included
The outputs in the agreed scope.
Consent-aware tracking implementation
Included
Built to your published policy and consent arrangement.

What you do not get

Data protection advice
Not included
Lawful basis, policy wording and records of processing are yours and your adviser’s.

How it runs, and what it asks of you

The six stages are the same on every Gridsmith engagement. Where your own time is listed, it is the part of a project that is worth knowing before it starts.

Consultation
We look at the current system, who maintains it, where it is hosted and what actually needs to change.
Planning & Scope
Scope is written as what the system will do, what it will not do, and who owns each account and environment at the end.
Approval & Start
Work starts once scope is agreed. Repository, environment and access arrangements are settled first, on the terms the written agreement sets out.
Design, Development & Updates
Built in reviewable increments on an environment you can see, rather than revealed at the end.
Delivery
Handover covers the running system, written documentation of how it is deployed, and the source-code and account arrangements the written agreement sets out.
Support (if applicable)
Maintenance, monitoring and further development are scoped separately rather than assumed — as further work or as an ongoing engagement.