From source of truth to tailor-made stakeholder outputs
Conservation organisations don't have a data problem. They have a common-language problem.
I help conservation NPOs decide what counts as truth, route it to the people making decisions, and turn dashboards no one opens into a system the board actually trusts.
The proposition
Most conservation organisations collect more data than they can use.
Telemetry platforms feed dashboards few people open. Donor reports are still assembled by hand each quarter. Board members receive different numbers in different forums — sometimes for the same KPI, in the same week. Field staff feel they are duplicating data entry across systems and getting little back in return.
The reason is rarely the data itself. It is that the source of truth is fragmented, the decisions to be made aren't mapped to the data that exists, and the portals that exist serve the producer of the report, not the person making the decision.
My work is built on two principles. Decision-Ready Information — every metric tied to a specific decision someone needs to make. Exception-Based Management — people are told when something is off, not asked to look.
How I work
I start as your pilot. I finish as your co-pilot. Then you fly on your own.
This is joint work. Your team does not receive a system — it learns to build and adapt it, with AI coding tools, so it keeps fitting your reality long after I leave. Four phases, and you can stop at the end of any of them.
A few days · offered
Prototype
A first version built from what is already public about your organisation. At my cost, yours to keep either way. Reacting to something real takes ten minutes; filling a list of questions takes weeks.
I fly · your team is co-pilot
Pilot
Your real data comes in — real dates, real numbers, real situations. Three or four working sessions, back and forth, until the first working version is accepted. Every session is also a lesson.
Your team flies · I am co-pilot
Co-pilot
Your people make the changes, with AI coding tools and short written guides for each step. I review, correct and step in when needed.
AI tools are co-pilot · 30 days on call
Own flight
The system is yours: the data, the tools and the know-how to adapt it. I stay on call for 30 days, and after that only when you ask.
One condition: name one person in your team who will own the system. Without a co-pilot, there is nobody to hand the controls to.
How the price is set
One fixed price per result, agreed on one page before we start.
No hours, no day rates. The prototype is never charged. You pay for what comes after it: your real data inside, every number checked against its source, and the controls in your team’s hands. Three questions set the number, and they are the same for every organisation, today and in five years.
What we build sets the range — a diagnostic, a technical fix, a full module or a full system.
How your data is today sets where in the range — one clean source, many files and PDFs, or paper and systems with no API.
Who funds the work sets the adjustment — a fund, an organisation with its own budget and a community-based organisation are not priced the same. Any relationship discount shows as its own line.
Payment follows the controls
40%
when the pilot starts
30%
when the first working version is accepted
30%
when the controls are handed over
- ·Nothing is paid before you sign off the phase: you confirm the agreed test is met, and only then is that phase invoiced.
- ·Anything outside the page we signed is not squeezed into the price — it becomes a new one-page scope.
- ·30 days of support are included after handover; beyond that, only when you ask, by the hour.
- ·The ranges behind these questions are reviewed once a year.
Prices are agreed in the one-page scope, never before we have talked about the problem.
Cases
What I've built before.
Three representative platforms below — the flagship plus two operational examples. I have seven products in production today; the full list, with screenshots, lives on the fact-check page.
Flagship · Source-of-Truth → Outputs
Conservation Data Studio
End-to-end pipeline from source of truth to tailor-made stakeholder outputs — dashboards, monthly reports, grant-writing inputs, and donor-facing visualisations, in a self-contained system. The platform that proves the framework.
Public · Community programme
Community portal serving 51 villages
A bilingual public-facing portal for a fenced-farming programme covering 729 households and 265 hectares across rural Mozambique. Replaced manual reporting with live dashboards for donors, partners, and the local board.
Private · Internal operations
Multi-entity HR & operations platform
An internal platform serving 38 staff across 4 legal entities and 6 office locations. Replaced 12 spreadsheets and two SaaS tools with a source of truth for people, contracts, payroll inputs, and policy compliance.
Who I am
João Campoa.
I have spent the last six years as Chief Operating Officer of Mozambique Wildlife Alliance, where I designed and built the data infrastructure that runs the organisation: a multi-pillar operations stack covering wildlife crime, human-wildlife conflict, and veterinary work, with a consolidated operational backbone serving multiple programmes.
I have spoken at international conservation forums in Cape Town, Hanoi, and Victoria Falls. Verify →
Ongoing engagements with INL, GIZ, Sida, and Oak Foundation. References available on request.
I deliver every engagement personally. No subcontracting.
Common questions
Before you book the call.
Get in touch
Tell me about your common-language problem.
Reach out by email. No commitment. If it's a fit, I send a proposal in 5 working days.
consulting@joaocampoa.com