Integrations & data
Business system integrations and data
The expensive part of having six tools is not the licences. It is the person who copies data from one to the other, and the day they copy it wrong.
Built and running at Lawang Estate, a property developer selling villas and land. The figures below are theirs.
01 · What it is
An integration is worth building when a human is acting as the cable between two systems. A lead arrives in the ad platform and someone pastes it into the CRM; a payment lands and someone ticks a box; a booking is made and someone adds it to the calendar. Each of those is a place where data goes missing without anyone noticing.
More detail
The rule we build to is that every fact has one owner. When two systems both hold the price, the date or the customer’s name, the integration decides which one is the source and the other only reads. Copying both ways is how two systems end up disagreeing, and nobody can tell which is right.
And an integration must fail loudly. The worst ones are those that stop working on a Tuesday and nobody finds out until the end of the month. Ours record what they moved, and when a call fails they say so to a person, not to a log nobody reads.
02 · Seen working
Lawang Estate — nothing typed twice
Sample data in the shape of the real tool. No names, no amounts.
Where each piece of data comes from, where it goes and whether the last run worked. Red needs a person.
| Source | Destination | What | Last run | Status |
|---|---|---|---|---|
| Meta Lead Ads | CRM | New form leads | 08:00 | OK |
| GoHighLevel | CRM | Lead traceability | 07:45 | OK |
| Bank CSV | Banks | Statement lines | Yesterday | 3 to match |
| Intranet | Website | Plot sizes | Live | OK |
| Telegram | Database | Owner approvals | — | 1 waiting |
IN PRODUCTION
Meta lead forms and GoHighLevel feed the developer’s CRM with their source attached. Bank statements come in as CSV, mapped per account, with a fingerprint that stops the same line being imported twice, and reconciliation happens only inside the database. The public website reads plot sizes live from the intranet, and approvals travel to the owner on Telegram.
MODULES · 9
- Meta Lead Ads
- GoHighLevel
- Bank statements, mapped per account
- Duplicate fingerprint
- Telegram approvals
- E-signature
- Email delivery
- Website ← intranet
- File storage
03 · How it flows
- 01SourceWhere the data is born.
- 02MappingIts fields, translated once.
- 03OwnerOne system decides; the rest read.
- 04DatabaseStored once, with its origin.
- 05AlarmA failed run reaches a person.
04 · What’s included
| # | Component | What it means |
|---|---|---|
| 01 | Map | What lives where today, and who owns each fact from now on. |
| 02 | Leads | Ad platforms and web forms feeding the CRM, with the source attached. |
| 03 | Payments | Stripe, local providers and bank exports reconciled against the record. |
| 04 | Calendars | Bookings written into a real calendar, not a list someone copies. |
| 05 | Spreadsheets | Read where the team still keeps them, instead of forcing a migration on day one. |
| 06 | Messaging | WhatsApp and Telegram as the channel a human already reads. |
| 07 | Failure | Every run recorded; a failed call reaches a person. |
05 · Questions
Can you connect a tool that has no API?
Is this the same as Zapier?
Do we have to move everything to a new system?
Who owns the credentials?
What does it cost?
Start a project
Have something worth building well?
Tell us what you are working on. We reply in English or Spanish, usually within a day.