The analysis process

From disputed metric to documented decision

A six-stage engagement that begins with definitions, protects cohort integrity and ends with a decision your whole team can inspect.

Notebook, charts and pencil used to document an analysis process

Six stages, with no black box

The sequence is designed to catch definition and source problems before they become confident recommendations.

  1. Decision framing. We write down the choice the team faces, the date by which it must be made and what evidence would materially change it.
  2. Source inventory. Owners, fields, timestamps, identifiers and known gaps are mapped across store reports, subscription systems and product events.
  3. Definition lock. Trial eligibility, conversion, active entitlement, renewal, cancellation, refund and revenue measures receive explicit rules.
  4. Reconciliation and cohorts. Sources are bridged at an agreed tolerance. Cohorts are frozen by start date and offer before dimensions are compared.
  5. Context review. Your team adds release, campaign, pricing and outage history so coincidence is not mistaken for cause.
  6. Decision readout. Findings, constraints and next actions are delivered in writing and discussed with the people who must act.

What to prepare

Bring the decision, not a polished dataset. A sample schema, current metric definitions, offer catalogue and rough date range are enough for the first call. We will identify which exports are required and which personal fields should be excluded.

Secure, proportionate access

Preferred access is a time-limited warehouse role or encrypted transfer approved by your organisation. Pseudonymous identifiers are sufficient. We do not ask for names, email addresses, card details or message content. Access is removed at engagement close and extracts are retained only for the period agreed in the statement of work.

The deliverables

You receive a written brief, metric dictionary, reconciliation notes, supporting cohort tables and a recorded or live readout according to your policy. Code or query extracts are included where permitted and useful for reproducibility.

Plan the first scoping call.