Data pillar — Data 360, Tableau & MuleSoft
Your data, ready for decisions and ready for AI
Dashboards have multiplied, and so have the discrepancies: two departments open the same KPI and read two different numbers. An agent does not ask for arbitration: it takes whatever definition it finds and answers with confidence. Our conviction: value comes from a governed KPI catalogue and governed access to systems — everything else follows.
Unify
A governed customer data foundation
Get clarity
What is used, what contradicts itself
Set the definitions
One KPI, one governed definition
Distribute
The right metric in front of the right person
Open up your systems
Systems accessible, in a governed way
Data 360
The foundation that feeds everything else: without unified customer data, there is no reliable semantic layer and no viable Tableau Next roadmap.
Data 360 implementation — customer data foundations
A unified, governed customer data foundation that feeds the semantic layer (D2) and any Tableau Next roadmap (D4).
What we do
- Connecting sources (Salesforce CRM, Marketing Cloud, third-party systems) into Data 360
- Harmonisation and identity resolution: unifying a customer's profiles scattered across systems
- Data foundation modelling, aligned with your business model
- Federated data access without duplication (Zero Copy) where the source allows it
- Defining access governance for the foundation: who can read, write and activate what
Deliverables
- Data 360 foundation configured and continuously fed
- Unified, deduplicated customer profiles
- Documented data model
- Governance plan for data access and quality
Tableau
Analytics estate audit
Know what is really used, and what contradicts you.
What we do
- Inventory of workbooks, views and sources, measurement of actual usage
- Detection of duplicates and contradictory KPIs
- Technical debt analysis (obsolete sources, duplicated calculations)
- Review of access and exports
Deliverables
- Usage map of the analytics estate
- Prioritised decommissioning list
- First version of the target KPI catalogue
Semantic layer & KPI catalogue
One KPI, one definition — including for your agents.
What we do
- Definition workshops with business leaders
- Modelling in the semantic layer (metrics, dimensions, rules)
- Flattening Salesforce hierarchies for drill-down
- Governance: approval cycle for a new KPI
Deliverables
- Semantic model deployed and documented
- KPI dictionary (owner + definition)
- Change governance procedure
Tableau Pulse rollout
The right metric in front of the right person, without them having to look for it.
What we do
- Selection of metrics to push to each audience
- Configuration of subscriptions, thresholds, frequency
- Refocusing existing dashboards on investigation
Deliverables
- Metric set configured and distributed
- Subscription plan by audience
- User training and reading guide
Tableau Next roadmap
Decide what to migrate, what to rebuild, what to retire.
What we do
- Gap between the current state and the target architecture (Data 360 + Semantics)
- Estate classification: migrate / rebuild / retire
- Proof of concept on a representative domain
Deliverables
- Impact assessment and documented decision
- Working POC on one domain
- Costed, sequenced roadmap
MuleSoft
95% of CIOs cite integration as the main obstacle to effective AI. An agent is only as good as the systems it can access.
Integration mapping & API exposure
Know which flows deserve to be governed — useful even without changing tools.
What we do
- Inventory of existing flows, including home-grown exchanges
- Criticality and fragility analysis
- Defining the exposure target (which APIs, which contract)
Deliverables
- Flow map and criticality analysis
- Target API catalogue with interface contracts
- Costed implementation roadmap
Agent-ready APIs (MCP / Topic Center)
Open your systems to agents — without throwing them open.
What we do
- Turning existing APIs into agent-usable assets (MCP)
- Publication in a governed catalogue (access, security, compliance)
- Documentation and handover to integration teams
Deliverables
- 3 to 5 exposed, governed APIs
- Security policies and access control configured
- Compliance tracking dashboard
Scope, duration and budget are defined together based on your context — let's talk. Excludes Tableau, Data 360 and integration platform licences.
D0 is a recommended technical prerequisite for D2 and D4 if your Data 360 is not yet in place; D1 and D3 can build on your existing Tableau estate without waiting for D0. D3 also assumes a KPI catalogue (built beforehand or via D2).
The product features mentioned evolve quickly: our commitments cover the method and the deliverables.
An agent without governed definitions gives answers that are plausible — but wrong
Let's lay the foundations that make your data reliable — for your teams and for your agents.