Six weeks to a working Customer 360: what actually takes the time

Published 20 January 2026 · LoxiLabs

The three problems

Identity: the same customer with four keys in five systems. Ownership: nobody responsible for the customer entity once the project ends. Activation: a beautiful view that no campaign or contact-centre system can reach.

Everything else — connectors, storage, features — is engineering, and engineering goes quickly once those three are sorted.

Week by week

Week one connects the priority sources and runs identity resolution with rules tuned to consumer or B2B customers, producing a single key with a confidence score. Weeks two and three build the governed entity with owners and refresh SLAs. Weeks four and five compute segments, propensity, and value features and wire the first use case into an activation channel. Week six is handover: runbooks, cost model, and the client's data team in charge.

What we stopped doing

Building a canonical model of every attribute anyone might want. The accelerator builds what the first use case needs and is designed to be extended by the client. Scope discipline is most of the reason it fits in six weeks; the rest is having done it before.

Measuring it

The accelerator is judged on the first activated use case against a control — usually next best offer or retention — in the units the business reports. The view is an asset; the outcome is the point.