Any software firm will tell you it is the best. It is a cheap claim to make and impossible to verify, which is why it is worth nothing to somebody trying to decide.
This article does something else. It sets out what we have built for Angola, says exactly what state it is in — including what it does not yet have — and explains how you can confirm every claim without taking our word for any of it.
We build and operate our own energy ERP
Most firms that say "we have oil and gas experience" are describing projects they delivered for other people. We are describing a product we built, operate and maintain: Enerxia, an oil and gas ERP designed for Angola.
In figures verifiable against the codebase, as of 21 September 2026:
| --- | --- |
|---|---|
| Business domains | 33 |
| Data models | 258 |
| Test suites | 167 |
| Screens in production | 134 |
| Applied database migrations | 60 |
The thirty-three domains group into six blocks: corporate (finance, tax, HR, expenses, documents), supply chain (procurement, suppliers, contracts, inventory, MRO, logistics), assets and operations (assets, maintenance, quality, fleet), oil and gas (upstream, well cost, production, projects), safety and environment (HSE, incidents, local content) and platform (identity, RBAC, workflow, audit, reporting).
They are not separately sold modules: they share one approvals engine, one numbering service, one unit-of-measure conversion and one audit log.
The real state of adoption, said plainly
Enerxia is in production, in pilot, with two companies and thirty-six users, and the audit log has passed sixty-six thousand events.
We are not going to present this as a system the Angolan sector has adopted, because it has not. We could put an invented number on this page and probably nobody would check — and that would be exactly the kind of decision that makes everything else here suspect.
What is true is more useful than an inflated number: the system exists, it runs, we maintain it, and it can be opened and walked through module by module. If you want to see production accounting, the approvals engine or the SAF-T export working against real data, give us an hour and we will show it rather than describe it.
The engineering rules that make this defensible
An industrial ERP is read for ten years and written for two. Six rules decide what is allowed into the system — and they are also the best way to assess any supplier, us included:
1. Regulatory rules are effective-dated configuration, never code. VAT, local content and approval thresholds carry effective_from and effective_to. An invoice issued in March is calculated with March's rule, permanently, even after the rule changes in June. Reissuing an old document does not recalculate it under today's law.
2. Nothing transactional is deleted. It is cancelled, voided, reversed or versioned. DELETE is not an available operation.
3. Every mutation is audited. Append-only, immutable to ordinary users, with a correlation id threading a whole workflow. The application account holds no UPDATE or DELETE permission on audit tables — the separation is enforced at the database role, not by the good intentions of the code.
4. Technical equivalence is an engineer's decision. The system never automatically infers that two parts are interchangeable.
5. Nothing is complete without test evidence. The 167 suites cover unit, integration, permission, negative and end-to-end cases.
6. No regulatory fact is invented. A rule we do not know with certainty stays configurable, empty and blocked — never a plausible-looking default.
Angolan regulatory engineering
This is where an imported ERP fails in Angola. The rules that matter are not those of Lisbon or Houston:
- VAT and AGT — VAT, withholding and a tax chart of accounts, assessed through dated rules rather than percentages fixed in code.
- Local content and the ANPG — local-content regime and supplier scoring as their own domain, so qualification is calculated and auditable rather than argued in a meeting.
- SAF-T — the standard file exported from the same entries that feed internal reporting. One source, not two.
- Production sharing contracts (PSC) — cost recovery and profit oil modelled in the upstream domain, tied to production accounting and well cost.
- Kwanza and multi-currency — decimal amounts carrying transaction currency, base currency, rate, rate source and rate date on every movement. Never floating point.
How to verify all of this
Do not be asked to believe. Ask to see:
1. The product page — wise-hustlers.com/enerxia describes the architecture layer by layer, with the figures above.
2. The engineering case study — wise-hustlers.com/case-studies/enerxia.
3. The technical cluster — more than twenty Portuguese articles on the concrete problems in this domain: SAF-T, electronic invoicing, local content and the ANPG, joint interest billing, RBAC and audit, offline-first sync for FPSOs. A supplier who understands a subject can write about it; read it and judge.
4. A demonstration against real data — not a slide deck.
What we are not
In fairness to you, since you are assessing options:
- We are not an Angolan company. Firms such as Jupiter (Luanda, since 2001) or Globosoft (since 2008) have local presence and a history in the market that we do not. If your priority is a supplier with an office in Luanda and a decade of local relationships, that is a rational choice and you should weigh it seriously.
- We do not have dozens of Angolan clients in production. We have two pilots. We said so above and repeat it here because it is the most important fact on this page.
- We are not the cheapest option for a brochure site or a simple application. The method described above is expensive, and it is wasted on problems that do not need it.
What we bring is specific depth in a specific problem: industrial and regulated systems, where provenance, effective-dated rules and auditability decide whether the record holds up.
If that is your problem, let's talk. If it is not, some of the names above will serve you better — and saying so costs us less than a badly matched project.