Yes. Each system is read on a schedule, usually overnight and read-only wherever the system allows, into one warehouse in your own account. There, the same customer, product or employee is matched across systems and every key number gets one written definition. Dashboards, scheduled reports and the AI layer all read from that warehouse, so they agree with each other, and nothing changes in the systems your teams use.
Why every system's reports stop at its own edge
Each system reports well on what it holds. The accounting system knows invoices and costs, the CRM knows deals, payroll knows people, the till knows the day's takings. Each has a supplier who knows it well.
The questions a leadership team asks most often sit between them. Is this customer profitable once the cost of serving them is counted? Did last spring's campaign produce invoices or only deals? Does the new branch earn more than its people cost? Each needs two or three systems at once, so each ends up in a spreadsheet someone rebuilds every month.
That space between systems is usually nobody's job. It is the part we take on.
How the systems meet without anyone changing them
Every system is read, not written to. We ask for the least access that lets the warehouse see what the reports need, and your administrator or the system's supplier grants it. The route is whichever the system offers: an interface for other software, a ready-made connector, a read-only copy of the database, or a file the system itself produces on a schedule. The audit confirms which, system by system.
In the warehouse, records are matched across systems, so the customer in the CRM is recognised as the same customer in the ledger. Above that sits a written list of the terms your business uses, revenue, margin, active customer, headcount, each defined once with your team. This layer is what we call a data fabric, and because it works from what each system can export, there is no fixed list of systems it can join.
Loads run overnight. If one fails, it is flagged to a named person, so that a missing figure is caught before anyone reads it as a zero.
Systems with a page of their own
Each page explains how that system holds the data finance needs, how it is read, and what to settle before it meets the rest.
SharePoint
Trackers and lists your teams update every day, read with access limited to the sites you name, and joined to the ledger.
02Excel
Which workbooks to retire, which to keep as inputs with an owner, and what makes a workbook safe to load every night.
03Sage
Which Sage you run decides how its ledger is read. The nominal codes become the lines your directors recognise.
04Odoo
Odoo already joins its own apps. The warehouse adds your other systems, the years before Odoo and each month as it closed.
05HubSpot
Deals followed to the invoice and the cash, with the HubSpot fields finance reads differently explained.
And the rest
Business Central, NetSuite, SAP Business One, Salesforce, Shireburn Indigo, tills, booking engines, e-commerce platforms and software built in-house. If its data can be read, it can join the warehouse; the audit confirms how.
What we need from you before a system is connected
Short, and the same for every system. The audit turns it into a list with names against it.
A named contact for each system
The administrator or supplier who can grant read access and tell us when the system is about to change.
Read access, approved by you
The least access the reports need, granted on your side, which you can withdraw at any time.
The reports you rebuild today
Copies of the packs and workbooks people assemble by hand, so the first view replaces real work.
Someone to agree the definitions
Usually the finance lead, with the heads of the departments whose numbers are involved.
What each kind of system usually holds for reporting, and how it is read
A starting map, not a promise for any one product. The audit confirms the route for the version you run.
| Kind of system | What reporting usually needs from it | How it is usually read |
|---|---|---|
| Accounting or ERP | The ledger, invoices, costs, stock and the chart of accounts | Its interface for other software, a connector, or a read-only database copy |
| CRM | Deals, stages, sources and the companies behind them | Its interface for other software, with read-only permissions |
| Payroll and HR | Pay totals and headcount by department, after each pay run | A file the payroll system produces after each run, as totals wherever possible |
| Tills, bookings, e-commerce | Sales by outlet, product, channel and day | Its interface, or a file it produces on a schedule |
| Spreadsheets and lists | Budgets, targets, mappings and trackers no system holds | The saved file or list, with a named owner |
A distributor with four systems and no single view
A Maltese distributor keeps its books in an accounting system, runs sales in a CRM, pays its people through a payroll bureau and plans in a budget workbook. Each system has its own supplier.
- Revenue comes from the ledger, headcount from payroll, and nobody sees the two side by side.
- Each supplier is asked for reports and can only answer from its own system.
- The budget is compared with actuals once a quarter, by hand.
- All four sources load overnight into a warehouse the company owns.
- Customers are matched between the CRM and the ledger, so revenue per sales team is one agreed figure.
- Budget against actual and revenue per head refresh every morning, with pay detail shown only to the roles cleared for it.
No system was replaced and no supplier lost its role. A question that used to go to three suppliers now goes to one screen.
Which system to connect first
The one that holds the money
Usually the accounting system. Almost every question the board asks ends in revenue, cost or cash, so the ledger is the spine the other systems attach to.
The question leadership asks every month
Then the system that answers the question asked most often and answered most slowly, often the CRM or the till.
The spreadsheet nobody can be away from
A workbook that only one person can run is a risk as well as a cost. Moving its work into the warehouse early removes both.
The system that forgets
Some systems keep only the current state of a record. Loading them early means the warehouse starts keeping their history from that day on.
What we do not do
- We do not sell, license, implement, configure or support any business system. Your suppliers keep doing that.
- We do not wire systems to each other so they exchange transactions. That is system integration, and it stays with your integrator.
- We do not write data back into any system.
- Your IT support keeps its role.
How it works
- A strategy callThirty minutes with Glen, free, with no pitch deck. Bring the systems you run and the question none of them answers on its own. You leave knowing whether joining them is worth doing, and where to start.
- The data auditAbout three hours with your team, mapping where each figure comes from, which system holds it and which steps are done by hand. The audit confirms how each system can be read, and it ends with a quote.
- The buildThree to four weeks from an accepted quote to a live dashboard. Implementation is the first month. Your team agrees the definitions with us; we do the building.
- The fractional teamAn ongoing senior team keeps the loads running, follows changes made to your systems and connects the next source when the business needs it.
Glen Sultana founded 110 Analytics after a career built where the numbers move daily. Our people have run analytics for tier-one companies, S&P 500 firms and high-growth technology businesses. Glen is the person on the first call, and he runs every data audit himself.
- Built in your environment, under your account
- No lock-in: if we part company, it keeps running and stays yours
- Based in Malta
Straight answers
Which systems can you connect?
Any system whose data can be read, by an interface, a connector, a database copy or a file the system produces on a schedule. Five have pages of their own here: SharePoint, Excel, Sage, Odoo and HubSpot. Business Central, NetSuite, SAP Business One, Salesforce, Shireburn Indigo, tills and booking systems are read the same way, and the audit confirms the route for each.
Do we have to replace anything?
No. Every system keeps its job and its supplier. The warehouse reads a copy of what the reports need, so nothing your teams use day to day changes.
Our supplier says they can build the reports inside their system. Why use you?
For questions about that system alone, they often can, and those reports stay useful. The questions that need two or three systems at once are the ones no single supplier can answer, and that is the work we do.
Will you need administrator rights on our systems?
No more than each connection requires. Wherever a system can grant read-only access, that is what we ask for, limited to the data the reports use, and you approve every connection before it goes live.
Who owns the warehouse?
You do. It is built in your own cloud account, under your credentials. If we parted company, it would keep running and stay yours, with no lock-in.
How long before the first system is live?
Three to four weeks from an accepted quote to a live dashboard, starting with the system and the view agreed as the priority in the audit.
What does it cost?
The price comes in the quote that closes the data audit. It depends mainly on how many systems are joined and how much matching each one needs.
Terms on this page
- Data fabric
- The layer that matches records and holds one definition per term across all your systems, so any source that can be read can join it.
- Read-only access
- Permission to see data without being able to change it. We ask for it wherever a system can grant it.
- Overnight load
- A scheduled job that copies each system's latest data into the warehouse, ready for the morning.
- Matching rule
- A written rule, agreed with your team, that says when two records in different systems are the same customer, product or person.