Customers & data
Todaycustomers_2026.xlsx sits on exactly one person's desktop.
In many companies the customer list exists three times: in accounting, in the mailbox, and in an Excel file that one person maintains. Every discrepancy costs time later, sometimes money. We build one place where the details live and make sure the other programs get them from there.
Where it usually gets stuck
- The same company appears in three systems, spelled three different ways.
- It is unclear which list is the correct one.
- Quotes and invoices contain outdated addresses.
- If one person is away, nobody knows where things are maintained.
A second list is never created on purpose. It appears because one program does not hold a particular detail, someone needs it quickly, and starts a spreadsheet. From then on there are two truths, and which one applies is answered by whoever looked last.
The damage shows up late: in an invoice to an old address, in a quote with the wrong contact, in a report nobody trusts.
What that looks like in the workflow
01 Record
Once, in one place
With fixed fields and clear ownership for keeping them current.
02 Check
Errors show up immediately
Duplicates and implausible entries are flagged as they are typed, not months later.
03 Distribute
The other programs receive them
Accounting, industry software and mailbox all work from the same state.
04 Maintain
Changes stay traceable
Who changed what and when is visible – that alone is usually enough for the data to be looked after.
What gets built
- A data model with clear fields: what is recorded, what is mandatory, who maintains it
- Validation rules that catch duplicates and obvious errors at entry
- Synchronisation with the systems you keep — accounting, industry software, Microsoft 365
- Migration of your existing lists, cleaned up once
What changes
- An address is changed in one place and is current everywhere.
- Duplicates and implausible entries show up at the point of entry instead of later in a report.
- Who maintains what is defined and known.
- Reports rest on data whose origin can be seen.
From applications we have built
What follows are excerpts from applications we have actually built. No mocked-up interfaces and no invented figures.
Questions about Customers & data
Do we have to replace our programs for this?
In most cases no. We define which system leads and connect the others to it.
What happens to our old Excel lists?
They are cleaned up once and migrated. After that nobody needs to maintain them.
How long does such a changeover take?
It depends on the state of the data. After a first review we tell you what to expect.
Also searched ascustomer data · customer list · Excel lists · addresses · contacts · master data · data maintenance