How to engage
It starts with a slice of your operation. Not with a slide deck.
This market is too technical, and that usually stalls the conversation in the wrong place: the buyer has to understand the model before being able to judge the proposal. This page inverts the order — first how you engage, then what runs underneath.
The rule that holds for every path below: scoping comes before the contract. No proposal is written without a real slice of your operation on the table — the assets, the thresholds, the calendar, and what hurts today.
The path, in four steps
From first contact to an operating contract. Each step has its own deliverable: if the conversation stops halfway, you leave with what was already done.
1
Scoping conversation
A technical meeting, not a sales one. You bring a problem and a real slice of the operation; we tell you what can and cannot be answered with the data that exists today. No charge.
2
Diagnostic and scope
The slice becomes written scope: which assets, which hazards, which thresholds, which integration, which metric defines success. This is where price takes shape — and where most climate risk projects go wrong, on vague scope.
3
Pilot on real data
A short, paid proof of value on your data, against the metric agreed in the previous step — fewer inspections, forecast accuracy, response time. No demo data: a pilot on pretty data proves nothing.
4
Operation
What the pilot proved goes into an operating contract, in whichever format your organisation supports — and it grows by module, not by rebuild. Nobody should change platforms to expand scope.
How you buy it
The same technology arrives in five shapes. Which one fits depends on where your operation already is: whether you have a dashboard, whether you have a data team, whether your contract lets the data leave the building.
SaaS · platform we operate
The full dashboard, with your sector’s views, operated by us in the cloud. The shortest path: it starts running with no infrastructure project on your side.
DaaS · just the data, over API
Forecasting, wildfire risk, hydrology and climate projection delivered over an API, with the variable dictionary generated from the services themselves. For teams that already have a dashboard and want the model, not the interface.
AaaS · the agents inside your systems
The climate risk agents answer from inside what your company already uses: your dashboard, your ERP, your field team’s WhatsApp. You are not giving the team one more interface — you are putting the specialist inside the one they already have.
See detail
Copilot or autopilot, depending on how much the operation wants to delegate. The agent arrives with the sector’s vocabulary and access to our models, without anyone having to open our platform.
PaaS · the foundation you build on
GIS services and Maps as a Service: georeferenced layers, maps and components published for your team to build your own product on top. You build; the geospatial foundation is ours.
On-premise · MapsAI only
When the contract requires the data to stay in the building, MapsAI runs inside the client’s security perimeter. It is the only product that works this way today.
See detail
Risk360 and Climate Edge depend on models and data that run on our side, and promising on-premise for them would be a promise the first technical meeting would undo.
Not every platform fits all five, and on-premise is the most restricted case: today, MapsAI only. The shape is settled during scoping, before the contract, alongside the targets and the sources.
Coupling
Coupled to your assets and your data.
Our platforms do not ask you to switch systems or migrate your base. They plug into what already runs in your operation — and when you only want the clean data, it arrives over an API, inside the dashboard you already have.
Integrates with what already runs
ERP, SCADA, OMS, ArcGIS, Cell Broadcast and alerting systems. Risk shows up where the team already works, not in one more tab open all day.
Data as a Service
Forecasting, wildfire risk, hydrology and long-term climate projection delivered over an API, under a stable contract. Consume the model without buying the platform, and without discovering the schema by trial and error.
See detail
It ships with a variable dictionary generated from the services themselves: field by field, with type, unit and the range measured on real samples.
Agents as a Service
The specialist AI agents answering from inside your systems and your team’s WhatsApp — as a copilot that recommends, or as an autopilot that does the work and hands the decision over ready for someone to sign.
Maps as a Service
Georeferenced layers and maps as a service, ready to feed dashboards, field applications and your own AI agents.
Data in Brazil, and MapsAI inside your perimeter
Everything runs with data hosted in Brazil, LGPD compliance and full traceability of decisions. And when the contract requires the data to stay in the building, MapsAI runs inside your security perimeter.
- ERP
- SCADA
- OMS
- ArcGIS
- Cell Broadcast
- Alerting systems
- API · DaaS
What you need to have — and what you do not
Needed: where your assets are
A list of assets with location. A spreadsheet will do, and it does not have to be perfect — part of the diagnostic work is telling you what is missing from it.
Needed: someone who answers for the operation
A person who knows the real thresholds — what the crew does and does not do in rain, wind or heat. Without that person, the threshold comes from our guess, and a guess does not survive the field.
Not needed: replacing your systems
The platforms couple to what you already use, or deliver only the data over API. A project that starts by demanding a system replacement does not start.
Not needed: starting big
One region, one basin, one line, one farm. The first scope exists to prove value with the least risk for both sides.
How the purchase happens
We have contracted through all three paths, and the shape of the first step changes in each.
Private company
Direct contract, usually starting with the paid pilot. The buyer is typically the operations or O&M director, backed by risk and regulatory teams.
Government and public concession
Public tender, or direct award where the case allows. We help on the technical specification stage — including when the tender is written before a known supplier exists, which is the common case in climate risk.
Project with an international body
Development cooperation and development banks, scoped as a study or an implementation. São Tomás has taken this route before, and the ritual is different: procurement follows the body’s rules, not ours.
What shapes the price
We publish no price list, and the reason is honest: price comes out of the scope, and scope is what the first conversation produces. What can be said upfront is what weighs on the bill.
How many assets, across how many fronts
One region costs differently from a national portfolio, and one sector differently from four — each sector has its own vocabulary, thresholds and calendar.
Which engines come in
High-resolution forecasting, fire, hydrology, long-term projection. Each engine is a calibrated proprietary model, not a catalogue item switched on.
How much integration
Reading a registry from a spreadsheet is one thing; writing a work order inside your ERP and SCADA is another. Integration is usually the part nobody budgeted.
Whether the operation is assisted
A platform delivered and run by your team costs differently from a platform with our team inside your situation room during the event.
One reference that calibrates expectations without a price list: in the power sector, a client who cuts a fraction of its own exposure to outage compensation usually pays for the platform several times over within the same year. Your exposure figure is public, and it goes into the diagnostic.
Bring us your challenge
If it involves climate, territory and data, it is our ground. The conversation starts from a real slice of your operation — not from a deck.