# Data and Integrations

> A scoped AI Pod that connects the systems running your business, so the same record stops being typed into three tools. 80 to 250 story points.

Source: https://www.koombea.com/ai-pods/catalog/data-and-integrations/

---

So someone types the same record into three tools, the numbers disagree by Friday, and every report starts with an argument about which system is right. This Pod ends that.


## The problem

Integration debt does not announce itself. It arrives as a job that is half copy and paste. As a monthly reconciliation nobody can explain. As a leadership team that quietly stopped trusting its own dashboard.

Nobody counts the cost, because it never appears as a line item. It shows up as a slow month-end close. As a report that starts with an argument. As decisions made against numbers that were wrong for a fortnight before anyone checked.

We connect the systems, decide which one owns each record, and make the failures loud. Most integration disasters are not caused by a sync breaking. They are caused by a sync breaking quietly.

- One system owns each record, and the others read it
- Every failure raises an alert with the payload attached
- Reprocessing is a documented action, not an engineer with database access

## What this Pod ships

- **Integrations that survive**: Retries, backoff, idempotency and dead-letter handling, so a third party being briefly down is not a data loss event.
- **Pipelines and sync**: Scheduled and event-driven movement between your systems, with the transformation logic in one reviewable place.
- **A record ownership map**: Which system is authoritative for each entity, written down, which is the decision that actually resolves the disagreements.
- **Observability**: Dashboards for volume, lag and failure rate, plus alerts that name the record that did not make it.

## Three systems, one record


## The part people skip

Deciding which system owns the customer record is not a technical question. It is the one that makes or breaks the work. When two systems both believe they are authoritative, you get a record that flips between two values every fifteen minutes.

So we force that decision early, in writing, with whoever owns the process. Skipping it is why the last attempt did not hold.


## What it costs

80 to 250 story points. The drivers are how many systems are in scope and how well documented their APIs are. A modern API is routine work. A nightly file drop is not.

We scope each connection on its own. Start with the two that hurt most and add the rest later, without re-planning anything.

- Points: 80 to 250, committed before work begins
- Scoped per connection, so the program can start small
- Salesforce, HubSpot, NetSuite, SAP, Shopify, Stripe and the rest
- 30 day warranty from written acceptance