# Deep in the sectors that move Africa.

> Boltcliq builds vertically integrated AI and data systems for financial services, healthcare, agriculture, energy, government, telecom, logistics, education and commerce.

Canonical URL: https://www.boltcliq.com/industries
Part of: https://www.boltcliq.com/llms.txt

We go vertical. Each engagement starts from the specifics of the industry, its data, its rules and its people.
### Why we go vertical
- Generic tools stall in the real world. A model that works on a clean demo dataset meets a core banking system from the 1990s, a wallet platform with different customer IDs, and a branch that still files paper. The hard part is not the model. It is the meaning of the data, the rules around it and the people who must trust the result.
- So we combine the ontology of a sector with its data, workflows and regulation. A bank, a ministry of health and a port authority each need different objects, different links and different approvals. Each also faces a different mix of laws and regulators. We write these down as a sector pack, test them with people who do the work, and build solutions that fit end to end.
- This is how we think about vertical integration. It does not mean we own the whole chain. It means we know the chain well enough to place the platform in it, work with the right local partners, and avoid promises we cannot keep.
### Nine sectors
**Financial services**
- One governed view of customers, accounts, wallets and agents across core banking and mobile money. Credit, fraud, KYC and regulatory reporting use the same facts.
- Customer
- Account
- Wallet
**Healthcare**
- Patient, facility, medicine and referral data connected across clinics and ministries. Teams see stock, capacity and follow-up gaps before patients are turned away.
- Patient
- Encounter
- Facility
**Agriculture and food**
- Farmers, plots, cooperatives and lots linked from field to export. Lenders, processors and buyers share one record for financing and traceability.
- Farmer
- Household
- Cooperative
**Energy, mining and utilities**
- Assets, work orders, permits and incidents modeled as one graph. Maintenance, safety and ESG reporting draw on the same evidence.
- Site
- Asset
- Sensor
**Government and public sector**
- Sovereign data foundations for identity, revenue, procurement and services. Agencies share facts under strict access control and audit.
- Person
- Business
- Household
**Telecommunications**
- Network, subscriber, wallet and partner data joined for care, fraud and planning. A private runtime lets operators run AI inference near their customers.
- Subscriber
- SIM
- Device
**Logistics and supply chain**
- One shipment record across ports, borders, fleets and warehouses. Carriers, forwarders and agencies get scoped views of the same facts.
- Shipment
- Container
- Consignment
**Education and skills**
- Learners, courses, assessments and skills linked from school to work. Teachers, providers and employers use evidence instead of guesses.
- Learner
- Guardian
- School
**Retail and commerce**
- Merchants, stock, sales and payments in a shared model. Restocking, merchant credit and demand sensing build on real sales records.
- Merchant
- Outlet
- Product
### How we go vertical
- Ontology packs. For each sector we keep a starting set of objects, links and actions in Zeus, with typical data sources and workflows. A pack is a head start, not a finished product. We adapt it to your terms and your systems.
- Regulation. Each pack lists the data protection laws and sector rules we expect to matter, such as Nigeria NDPA 2023, Kenya Data Protection Act 2019, South Africa POPIA, Ghana Data Protection Act 2012, Egypt PDPL 2020 and Rwanda Law 2021. These are examples. Always confirm with counsel what applies to you.
- Local partners. We expect to work with local integrators, cloud and data center providers, and domain experts in each market. They know the regulators, the languages and the systems. Partnerships are discussed per project, and none are announced here.
- Ontology packs per sector, adapted with your teams
- Compliance notes and residency options up front
- Local partners for delivery, hosting and support
### Frequently asked questions
- Why separate pages for each sector?
- Buyers think in sectors. Each sector has its own objects, systems and regulators, so a general page would say too little.
- Do you work outside these nine sectors?
- Possibly. These are where we are building packs first. Talk to us if your sector is different.
- Which countries do you cover?
- We focus on Africa. Laws and systems differ by country, so we scope each engagement by market and confirm requirements with counsel.
- Can data stay in our country?
- That is a design requirement. Argus is portable, with a path from AWS to local data centers and on premises.
- How do engagements start?
- With one use case, one owner and a short discovery. Forward deployed engineers then build with your team and hand the work over.