Shortlist (0) ELDE
Home / For business

Better phone decisions. For your business.

Bring support horizons, repairability and part-price evidence into the way you buy, sell and manage devices.

Discuss a projectExplore the open dataset

Three projects with a clear starting scope

Choose a starting point. We confirm the available evidence, exact deliverables, timing and price before you decide whether to proceed.

Catalogue evidence audit

For a shop, marketplace or product team that needs trustworthy phone information in its catalogue.

Deliverables to agree

  • A model-matching sheet for the agreed catalogue.
  • Source-linked support and repairability fields, with observation dates where available.
  • A gap report distinguishing missing, uncertain and reusable information.
What you provide
  • A list of model names and variants, without customer records.
  • Target countries, required fields and intended use.

What shapes the quote: Model count, matching quality, requested fields, source permissions and whether a refresh is needed.

Scope a catalogue audit

Fleet decision brief

For a team deciding which phones to retain, repair or replace before its next purchase.

Deliverables to agree

  • A comparison sheet for the agreed keep, repair and replace scenarios.
  • Explicit purchase-price, repair-quote and ownership-period assumptions.
  • A decision brief explaining trade-offs, evidence gaps and sensitivity to the assumptions.
What you provide
  • Aggregated device counts by model and condition, without staff or customer identifiers.
  • Actual purchase or repair quotes and the planned period of use.

What shapes the quote: Fleet size, number of scenarios, countries, available quotes and the depth of analysis.

Scope a fleet brief

Integration discovery and prototype

For a product or operations team that wants a defined route from sourced data to an existing workflow.

Deliverables to agree

  • An agreed field map, source-attribution requirements and sample output.
  • A data-flow and maintenance plan with limitations made explicit.
  • If agreed in the quote, a bounded prototype for the specified workflow.
What you provide
  • A redacted example schema or field list, without credentials or live customer data.
  • The destination system, required format and intended use.

What shapes the quote: System constraints, source rights, prototype boundaries and ongoing responsibilities, if any.

Scope an integration

Start with the data. Agree the work.

The published dataset remains available under its stated licence. Custom research, implementation and ongoing services are separate work, scoped and priced by agreement. Coverage and source permissions vary by field.

Read the data specification and licenceSee our methodology

From a question to a scoped project

  1. Describe the decision

    Tell us who will use the result and what they need to decide.

  2. Check the evidence

    We discuss coverage, source permissions, gaps and feasibility.

  3. Agree the scope

    Confirm deliverables, timing, cost and responsibilities before work begins.

Give us a useful starting point

Prepare a brief in your browser, review it, then send it through your own email app. Nothing is submitted by this form.

Prefer a direct conversation? [email protected]