Service / Corporate data

One version of every record. Kept in sync.

We connect the systems that hold your customers, products and orders, name the one that owns each field, and sync the rest.

Describe your project →See an example
Each field
one owning system
Sync
logged and retried
Conflicts
to a review queue
Access
by role, reviewed

01 / What you get

Six deliverables. A data model that stays true.

Data map

Which system holds which data, and who is responsible for it.

data-map.md

Ownership rules

One system of record per field, written down.

ownership.yml

Integrations

Sync between CRM, ERP, webshop and spreadsheets, logged and retried.

sync/

Duplicate review

Matching rules for customers and products, with a queue a person clears.

matches.csv

Access by role

Who can see and change what, reviewed on a schedule.

roles.yml

Reporting base

One database your reports read from, instead of hand-made exports.

reporting db

02 / How it runs

Five steps. Rules first, then code.

  1. Map

    systems and owners

  2. Decide

    one owner per field

  3. Connect

    sync, with logs

  4. Clean

    duplicates reviewed

  5. Run

    alerts and access reviews

03 / Example

One customer, three systems. One owner per field.

Illustrative. Systems and field names are invented.

Example · invented data

ownership.yml
# ownership.yml (illustration, invented systems)customer:  name:         crm      # sales edits it here  email:        crm  vat_id:       erp      # invoicing is the reference  credit_limit: erp  newsletter:   webshopsync:  every: 15m  on_conflict: owner_wins  unresolved: review_queue  log: sync.log

04 / What to send us

  1. 01The systems that hold customer, product or order data
  2. 02The reports you build by hand today
  3. 03Where the same data disagrees between systems
  4. 04Who should see and change what

05 / Related

06 / FAQ

Do we need a data warehouse?

Not always. If reports need two or three systems, a sync may be enough. A reporting database pays off once reports slow the systems or need history.

Will you replace our CRM or ERP?

Not as part of this. We connect the systems you have and decide which one owns each field. Replacing one is a separate project.

What happens when two systems disagree?

The ownership rules decide: the system of record wins, and the change is logged. Cases the rules cannot settle go to a review queue for a person.

How is personal data handled?

Access by role, a log of who changed what, and a data processing agreement wherever we handle personal data for you (GDPR Article 28).

Describe your data

Which systems hold it, and where they disagree.

  • Fixed-scope quote — no obligation
  • Reply within 1 business day

By sending this, you agree that we may contact you about this inquiry.