How an organisation tells customers what data it holds, what it does with it, and what control they have — designed into the customer experience rather than disclosed in collection notices, T&Cs and privacy policies alone. Communication and consent treated as design problems that carry commercial consequences, with privacy, legal and regulation as inputs to the requirements rather than a review gate at the end.

• Ideal for: Organisations holding customer data at scale, consolidating customer records, or preparing for privacy reform.

• What you’ll get: Discovery documentation mapping internal, regulatory and competitor landscapes. Data classified by purpose, with primary collectors and downstream beneficiaries mapped. A consent model — qualities of consent and the mechanisms that collect them. A communication model: tone, channel and notification rules, governance and templates. All grounded in the regulation that applies in the locale you operate.

Automation held to the same standard as human decision-making. The institutional guardrails get built first and the agent is automated against them, so there is a defensible basis for what it decides and a record of why.

• Ideal for: Organisations moving toward agentic implementation, or running agents already without documented standards. Anyone facing automated decision-making disclosure obligations.

• What you’ll get: Agent OS templates mapping orchestrator to sub-agent relationships. Human-in-the-loop checkpoints. Change and version control standards. Risk classification with a phased path from manual to automated. Playbooks and training scoped as organisation-wide standards rather than a single deployment.

Diagnosis before strategy. Finding the step where errors originate and cascade, then separating what already works from what needs replacing. The findings define the new standard, built from how the service actually runs rather than how it's documented.

• Ideal for: Teams or services operating on tribal knowledge, long lead times, and no standard documented processes, who need something repeatable.

• What you’ll get: An end-to-end service map across every stakeholder touchpoint. Playbooks and SOPs. Facilitated workshops for adoption and upskilling.

Advisory to design leadership, across two connected things: how a design system should be structured, governed, and contributed to, and how the function around it runs — career progression ladders, daily operations, and making the case for strategic design input in commercial terms rather than at the end of the line.

• Ideal for: Design leaders scaling a function, inheriting a system nobody contributes to, or fighting to be in the conversation earlier than delivery.

• What you’ll get: A design system structure — token architecture, component governance, contribution model and documentation standards. Workflow audits. Operating frameworks for the function: levelling, rituals, planning and reporting.