Personalisation, upsells, catalogue data, site speed and who is liable for the words next to your product.
A quiz knows what a shopper types. A connected tracker knows what their last six months looked like. Which to use, and when a quiz is still the better tool.
Read the guide UpsellsCo-purchase logic recommends what is popular, not what fits. What merchants say works instead, and how to tell whether it did.
Read the guide ClaimsThe FTC can hold a brand responsible for claims made on its behalf. What that means when software writes the words beside your product.
Read the guide Site speedSpeed is the veto most merchants apply before features. What actually loads, how to measure it, and why consolidating apps is not automatically a win.
Read the guide CatalogueAny engine can only match on what your catalogue says. The five fields that carry weight, and a three-question test for finding your thin products.
Read the guideGetting at client data across mixed devices, staying inside your scope, and who holds what.
Clients ask it, the device makers do not answer it, and the enterprise products are built for teams. What a solo practitioner can actually do today.
Read the guide ScopeThe scope documents all talk about blood tests and say nothing about sleep or HRV. What the bodies actually say, and the safe way to use a number with a client.
Read the guide RecordsConsent, your eight-year record-keeping duty, and why holding less of the data than you expect does not put that duty at risk.
Read the guideWhat an employer can and cannot see, why take-up is low, and how to write a business case that survives a CFO.
The ICO’s own worked example says consent at work usually fails. What a scheme can be given instead, and the five questions to put to a supplier.
Read the guide Take-upMost employers report EAP take-up under a quarter. The four reasons people never open the benefit, and what gets opened a second time.
Read the guide Business caseA third of benefit changes are rejected for lack of data, and the best studies say do not promise ROI. What to put in the paper instead.
Read the guideControllership, provider churn and the limits nobody puts on a pricing page.
Aggregator contracts assign controllership to you in a single line. What that pulls in, and the one integration shape that does not.
Read the guide MaintenanceFour provider-side discontinuities in two years. A dated list of what changed, what it cost teams, and what to ask before you build.
Read the guide LimitsPricing pages say "historic data retrieval". The docs say 28 days for some providers. The real numbers, and what they mean for your first session.
Read the guideA short conversation about your catalogue, your clients or your scheme, and whether this is the right fit for it.