Connect
the systems, fix
the numbers, forecast
what’s next.
Zansa is a data analytics and data science team for small and mid-sized companies anywhere in the world. We connect the systems you already use, reconcile the numbers that don’t match, and build dashboards and machine-learning forecasts your team can trust. You own everything we build.
Less rebuilding.
More knowing.
We connect the tools you already use: Excel and CSV files, Xero, Sage, Shopify and SQL databases, loaded daily into a warehouse in your own account.
Every business is different, so we quote once we understand your systems. You get a fixed price and timeline in writing before any build starts.
For guidance: Health Checks from R25,000. Builds typically R80,000–R250,000. Support from R12,000/month. (placeholder amounts)
Something not covered? Ask on the call.
In a cloud account owned by your company, usually Google BigQuery. We work with access you grant and can revoke at any time. Nothing is stored in a Zansa account.
Sectors we work in
Retail & e-commerce
Sales, margin and stock across every channel.
Shopify, the till system and the ledger each report a different revenue figure, and stock counts drift between them. Month-end means exporting and stitching spreadsheets.
- Shopify, POS and Xero or Sage connected in one model
- Daily sales, margin and stock-cover dashboard
- Order-to-payment-to-ledger reconciliation
Manufacturing
Yield, downtime and true cost per unit.
Production numbers live in shift spreadsheets, costing sits in the ERP, and nobody agrees on the real cost per unit.
- Shift sheets and ERP joined at batch level
- Yield, downtime and OEE dashboard by line
- Cost-per-unit model your finance team signs off
Logistics
On-time delivery and cost per drop, by route.
Tracking, fuel cards and invoicing are separate systems. Route profitability is a guess, and late deliveries surface only when a client complains.
- Tracking, fuel and billing data in one place
- On-time and cost-per-drop by route and driver
- Daily exceptions list for late or unbilled loads
Healthcare
Utilisation, billing and claims in one view.
Practice management, billing and insurer and medical-aid remittances don’t line up, and patient data has to be handled carefully under privacy law such as POPIA or HIPAA.
- Billing and remittances reconciled automatically
- Utilisation and rejected-claims dashboard
- De-identified reporting layer, access logged
Property
Occupancy, arrears and maintenance across the portfolio.
Lease, billing and maintenance data sit in different tools, so arrears and vacancies are reported weeks late and per building by hand.
- Lease, billing and maintenance systems connected
- Portfolio dashboard by building and tenant
- Weekly arrears and lease-expiry alerts
Hospitality
Occupancy, RevPAR and labour cost, daily.
PMS, POS and rostering each tell part of the story. Managers wait for month-end to see whether a busy week was actually profitable.
- PMS, POS and payroll joined per property
- Morning dashboard with occupancy, RevPAR and labour
- Forecast of covers and rooms for rostering
Professional services
Utilisation, WIP and realisation by team.
Timesheets, billing and the ledger disagree, so partners don’t know which clients and teams are actually profitable until year-end.
- Timesheets, billing and ledger reconciled
- Utilisation, WIP and realisation by team and client
- Monthly client-profitability report
Frequently asked questions
Where does our data live?
In a cloud account owned by your company, usually Google BigQuery. We work with access you grant and can revoke at any time. Nothing is stored in a Zansa account.
Is this compliant with privacy law (POPIA, GDPR)?
We design for privacy law from the start, including POPIA in South Africa and GDPR in the EU and UK: data stays in accounts you control, personal information is minimised or de-identified for reporting, and access is limited and logged. We sign an operator agreement before we touch any data.
Can we use Power BI instead of Metabase?
Yes. Metabase is our default because it has no per-user licence fees, but we build in Power BI if your team already uses it. The data models underneath are the same either way.
What do you need from us?
A sponsor who can make decisions, read access to the relevant systems, and about an hour a week from the people who know where the numbers come from.
Do you use AI tools on our data?
Not without your written approval. Any AI tools we use for writing code never receive personal or client-identifiable data. If you want ML models, they run inside your own account.
What if our data is on paper?
We start with a simple capture process, such as structured templates or forms, so the data becomes digital going forward. The Health Check tells you what is worth digitising and what isn’t.
Who owns what you build?
You do. Code, data models, dashboards and documentation sit in your accounts from day one, and you can keep using them without us.
How long does a build take?
The Health Check takes 1–2 weeks. A Foundation Build typically takes 4–8 weeks, with a fixed timeline agreed in the quote.
Browse 500 answers on analytics, data quality, forecasting and privacy · About Zansa
Contact: hello@zansa.co.za