The Same Customer Exists Five Times and No Two Agree
They are in the website form, the CRM, somebody’s inbox, a spreadsheet and a WhatsApp thread. Three spellings of the name, two phone numbers, one email that bounces, and each system has a different idea of what stage they are at. Connecting those tools is not the job. The job is deciding which of those records is the person — and until that is answered, joining them up just copies the confusion faster.
No credit card required · 30-minute call · No obligation to sign up
Six reasons your systems describe different people
None of these is anybody being careless. Each is a normal consequence of tools being adopted one at a time by people solving a problem in front of them.
- They enquired twice, months apartDifferent email · same person
- One system has no phone fieldSo it lives in a note
- Somebody typed the name differentlyOr the company’s trading name
- WhatsApp has a number and nothing elseNo name, no source, no record
- Two people share one businessAnd both contacted you
- The spreadsheet is somebody’s ownAnd it is the accurate one
The last row is the awkward one and it turns up constantly. Somewhere in most businesses there is a spreadsheet kept by one person that is more accurate than the CRM everybody paid for — because it contains the judgements that the CRM has no field for. Integrating without understanding why that spreadsheet exists throws away the most reliable data you have, and the person who kept it will quietly go on keeping it.
Decide what makes two records the same person
This sounds like a technical question and it is a business one. Is it the email address, the phone number, the company, or a human deciding? Every answer is defensible and each produces a different customer list. Email is tidy and misses people who changed jobs. Phone number is reliable and fails when a business has one landline. Company merges two people who should be separate. Somebody has to choose, and it should be somebody who deals with the consequences rather than whoever is building the integration.
Then the matching has to allow for being unsure. Records that clearly match get merged, records that clearly do not stay apart, and the ones in between go to a person — because a merge is very hard to undo and an automated merge that was wrong quietly destroys history. That middle pile is small, it is worth a few minutes a week, and it is the difference between a customer list you trust and one you keep second-guessing.
On direction, the same rule as anywhere: for each field, one system is allowed to be right and the rest read it. Whoever owns the relationship owns the contact details; whoever owns the money owns the money. Where two systems both write the same field, you do not have an integration, you have an argument that runs on a schedule and is settled by whichever ran last.
And the spreadsheet needs a real answer rather than deletion. Usually it exists because it holds something the CRM cannot — a judgement, a note about how somebody likes to be contacted, a reason a deal stalled. Either the CRM gains a field for that, or the spreadsheet stays and is joined properly. Telling that person to stop is how integrations get quietly bypassed.
- ✓Choose the matching key deliberately — Email, phone, company or a human. Each gives a different list.
- ✓Unsure matches go to a person — A wrong automated merge destroys history and is hard to undo.
- ✓One writer per field — Two systems writing the same field is an argument, not an integration.
- ✓Understand the spreadsheet — It usually holds what the CRM has no field for. It is often the accurate one.
- ✓Do not tell them to stop — That is how integrations get bypassed rather than adopted.
Somewhere in most businesses there is one person’s spreadsheet that is more accurate than the CRM everybody paid for.
What the work actually consists of
Six things, and the first two happen before anything is connected.
Define What Makes a Person
Email, phone, company, or a human decision — chosen by somebody who deals with the consequences. It is a business decision that gets encoded, not a technical default.
A Field-by-Field Owner Map
For every field, the one system allowed to write it and the rest that read. Produced before any connection is built, because the connection is an implementation of this document.
A Review Pile for Unsure Matches
Clear matches merge, clear non-matches stay apart, the rest wait for a person. Small, a few minutes a week, and it protects history that a wrong merge would destroy.
Deal With the Spreadsheet
Find out what it holds that the CRM cannot, then either add the field or join it properly. Telling its owner to stop is how the whole integration gets bypassed.
WhatsApp and the Inbox, Included
The two places real enquiries actually live and the two most often left out because they are awkward. A number with no name attached is still a customer.
Something That Notices Failure
When a sync stops, somebody is told the same day. Integrations fail silently and are usually discovered weeks later by a customer asking why nobody called back.
What clients say
Real clients, quoted in their own words — published with their permission.
“Ghalib’s clear guidance has helped improve our website’s SEO performance.”
“We’re very thankful to Ghalib and his team for building a fully-functioning website for our business.”
“It was a pleasure working with Ghalib and his team.”
More of them, in full, on our reviews page.
— Our Proprietary Methodology —
The Visibility Framework™, applied in Systems Integration
The method doesn’t change by market. What it’s pointed at does.
Audit The Hours
Where time actually goes, task by task, scored on volume, repetition and the cost of getting it wrong. Ends in a ranked blueprint with estimated hours saved — yours to keep either way.
Design The Guardrails
Before any building: what the agent may touch, where a human must approve, what happens when it is unsure, and which data is never allowed near a third-party model.
Build & Evaluate
One workflow at a time, in your accounts, scored against real examples from your business before it touches live work. Shipped early so it meets reality while it is still cheap to change.
Run & Improve
Monitored for cost, failures and quality drift. Models change, your business changes, and an automation nobody tends becomes a liability rather than an asset.
Honest, No-Nonsense Commitment
If the audit concludes that a task is not worth automating, we will tell you and refund the difference rather than build it anyway. And if a workflow we built does not hit the outcome we agreed in the blueprint, we keep working on it at no extra cost until it does or we take it out.
AI Automation pricing for Systems Integration, in GBP
Quoted in pounds after the identity question is answered, because an integration priced before that is priced for moving data rather than for making it mean something. This stage is small and it is routinely where a project finds the system nobody mentioned.
Two Systems
Website and CRM, joined properly.
- Matching key chosen deliberately
- Field-by-field owner map
- Failure noticed the same day
The Real Stack
The usual one. Including WhatsApp and the inbox.
- Everything in Two Systems, across four or five
- Review pile for unsure matches
- The spreadsheet understood and handled
- Optional: bundle in SEO or Website Development
Consolidation
Years of overlapping records, sorted.
- Historic de-duplication with human review
- Migration plan with a rollback
- Documented rules kept outside the tooling
- Optional: combine all 4 services for full-funnel growth
Every plan is scoped around your market — start with a free first look and we’ll recommend what fits, priced in GBP.
What you’re actually committing to
Most agencies keep this in a contract you only see after the sales call. We would rather you knew now, because it is the question everyone asks second — right after the price.
- The audit is credited, not sunkPay for the audit, and the full amount comes off the build if you proceed. If you don’t, the blueprint is still yours to hand to anyone else.
- A fixed build price after the auditQuoted once we know what we are building. If it takes longer than we estimated, that is our risk — the price only moves if you change the scope.
- You own everythingAccounts, API keys, workflows, prompts, evaluation sets, logs and documentation — all in your name from day one, and still yours if we never work together again.
- Running costs are yours and visibleAPI usage is billed by the provider directly to you. We never resell tokens or mark up usage, and you see the real number.
- The retainer is month to month30 days’ notice, no exit fee. Stop it and your automations keep running — you are simply maintaining them yourself.
- Human approval is the defaultAnything customer-facing or irreversible needs a person until the evaluation data justifies otherwise, and that decision is yours to make, not ours.
These are the terms as they appear in the agreement itself — nothing here is softened for the website. The full wording lives in our terms and conditions, and you get the agreement to read before anything is signed or invoiced.
Systems Integration AI Automation questions, answered
Related AI Automation pages
Same service, different angle — by market, by service and by industry.
Want the records to mean something?
Free 30-minute call · No obligation · Response within 24 hours
Get in touch with Ghalib Ashrafi HQ
Ghalib Ashrafi takes on work for brands in six markets — the UK, USA, UAE, Saudi Arabia, Australia and Pakistan. Every enquiry gets a reply within 24 hours.