Case Study
Ecobra: the plot is drawn on the map, and the map is the source of truth
The size comes from the outline itself, two plots cannot occupy the same space and each client sees their own part of the area.
The client
Ecobra Soluções Ambientais works with green areas destined for tree planting and the generation of carbon credits. Companies acquire plots within those areas — and need to know exactly which piece is theirs, how many square metres it has and where it sits. When the product is a piece of land, the record cannot be a spreadsheet row with a hand-typed number.
What the project called for
The product is geographic. The system controlling it has to be geographic too.
An area is not a number, it is an outline
Storing only the size says nothing about where the area is or what shape it has. And a typed size is a size someone can get wrong — or round in their own favour.
Two plots cannot occupy the same space
With spreadsheet control, an overlap only surfaces when two clients claim the same piece. By then the problem is legal, not operational.
The plot has to fit inside the area
A plot drawn beyond the area boundary is a sale that does not exist. Checking it cannot depend on someone looking carefully at a map.
Clients want to see what is theirs
Whoever bought a plot does not want a code: they want to open the map and see their own piece highlighted, with the size they contracted.
What we built
A system where the map does not illustrate the record — the map is the record.
The area is drawn on the map
The manager traces the area outline directly on the map, and the system stores the polygon, not a text with coordinates. What sits in the database is the real shape of the land.
The size comes from the outline
The square metres appear while the outline is being drawn and are recorded from the geometry itself. Nobody types an area, so nobody gets the area wrong.
Subdivision into plots inside the area
Once an area is picked, the plot is drawn inside it — and the drawing is confined to the parent outline, so no plot is born half outside.
Overlaps refused on both sides
The system refuses area over area and plot over plot. The check happens on screen, so the manager sees it instantly, and again on the server, by geometry — because a validation that only exists in the browser is not a validation.
Each client with their own colour
A plot inherits the colour of the client who bought it. Opening the map and understanding whose each piece is became a glance, not a query.
Area occupancy panel
Total, allotted and available square metres, always calculated from what is drawn. The remaining area stops being mental arithmetic.
The plot commercial cycle
Each plot follows a visible path in the system — available, reserved, sold and settled — so the map also shows the commercial situation, not just the geography.
Client area
Buyers sign in with their own access and see their plots on the map, with size and status. No need to ask sales for a screenshot.
Client records and settings
Clients with contact details and colour, users linked to them and the system settings, all administered from the panel.
Ongoing management and security
The system gets permanent oversight: updates applied and fixes shipped as soon as vulnerabilities are disclosed.
What is live
The fronts the system supports today.
What it changes in practice
The effect of letting the map govern the record.
Size stops being an opinion
The number comes from the geometry in the database. There is no divergence between what was sold and what is drawn, because they are the same thing.
The conflict never reaches the client
Overlaps are refused at save time. The error dies on the manager screen, not in a conversation with two buyers of the same piece.
Occupied area counts itself
How much is allotted and how much is left appear in the panel straight from the drawings — with nobody adding plots up in a spreadsheet at month end.
The client checks without a middleman
They open the map, see their plot highlighted in their colour and the size they contracted. Sales stops being the channel for a simple question.
What this project solves is an entire class of error: when the record is the drawing itself, wrong sizes, overlapping plots and sales beyond the boundary stop being possible — not through the discipline of whoever fills the form, but by how the system is built.
The services behind this project
It is the same work we do for other companies.
Custom web systems
The whole system: areas, plots, clients, the buyer area and the geographic control.
Systems and API integration
The map integration and the internal APIs behind the drawing and the validation.
High-performance cloud servers
The infrastructure hosting the system and the database with geographic support.
Does your area control still live in a spreadsheet?
When the record is the drawing itself, sizes stop diverging and overlaps stop existing. Tell us how your operation controls this today.