Every system connected, one set of definitions, in your own cloud.
Which systems, which entities and which definitions matter in your company is what the diagnostic finds out. The modules are the same; their contents are yours.
Two to three weeks: what disagrees, and what fixing it costs.
Inventory of systems, owners and update cycles. Where definitions conflict. One month's key numbers reconciled across sources. Event and integration checks. AI readiness. A gap list with fixed-price quotes.
Deliverable: a report with a one-page conclusion. Fixed fee.
Every system connected read-only, on schedule, with lineage.
APIs where they exist, scheduled exports where they don't. Incremental loads. Lineage from source to table, documented.
Deliverable: connectors and their documentation. Fixed price.
One record per customer, product or supplier across systems.
Matching by rule on the identifiers each system holds. Survivorship rules for conflicting values. Merged records written back to the operating tools that need them.
Deliverable: master tables and write-back channels. Fixed price.
Revenue, margin and customers defined once, in writing.
Definitions agreed with finance and operations. Edge cases decided and documented: returns and refunds, currencies, cost allocation, de-duplication across systems. The same number in every report.
Deliverable: a definitions document and the metrics layer that implements it. Fixed price.
One model, one fact table per process, history kept.
Dimensions shared across the company; a fact table for each business process the diagnostic identifies. Business keys, hash keys and change history. Daily reconciliation against every source, with alerts.
Deliverable: the model, reconciliation reports, code and documentation. Ships with projects.
Kept correct as systems change. Monthly.
Interface-change tracking, a monthly data-health report, new sources and definitions, incident handling.
Then: reporting · automation · AI applications
API where there is one; scheduled exports where there isn't. The support and marketing AI you already run stays — it reads from here. Which systems come first is decided in the diagnostic.
| Platform-native reporting | SaaS analytics tools | Agencies | Consultancies & SIs | Unvessel | |
|---|---|---|---|---|---|
| Where the data lives | The platform | The vendor's database | The agency | The client | Your own cloud account |
| Systems in view | Its own | One slice each | What the agency runs | Depends | All of them |
| Pricing basis | Bundled or usage | Volume or seats | Fee plus commission | Person-days | Fixed price, milestone acceptance |
| Who keeps it correct | The platform | You | The agency | Ends with the project | Managed operations, monthly |
| Way in | Low | Low | Medium | High | A two-to-three-week diagnostic |
In your own cloud account. We hold access during the project and hand it over at the end, deleting our copies.
No. Your systems of record stay; the warehouse sits beside them. API where there is one, scheduled exports where there is not.
Keep them. They read from the warehouse afterwards, so every dashboard shows the same numbers.
Diagnostic at a fixed fee; projects at a fixed price with milestone acceptance; managed operations monthly. Never by data volume or revenue.
Past work is on the case studies page.
Tell us which systems you run. We'll reply with the scope and the fee — or tell you honestly if we're not the right firm.
info@unvessel.ai