FiscalRural: a rural land tax SaaS built from scratch
Our own product · Chrome extension · national land-value database · technical SEO
Brazilian rural land tax is an annual, low-ticket, high-volume filing. Rural accounting firms were spending qualified hours on repetitive calculation and on hunting down land values municipality by municipality. It is the kind of task nobody wants to do and everybody has to file.
fiscalrural.comThe challenge
Land-value data is fragmented
Each municipality publishes its own table, in different formats, and it changes every fiscal year.
The final filing happens in the tax authority's own software
The calculation can happen elsewhere, but the declaration has to be entered into the official program — and retyping is where errors happen.
Your own product has to be found
With no inherited client base, the product depends on organic acquisition from day one.
How we solved it
- 01
A land-value database shipped with the product
More than 2,700 municipalities consolidated inside the system. Nobody has to look up the year's value — it's already there when the property is registered.
- 02
Utilization rate and tax computed automatically
The firm registers the property and the taxpayer; the system does the maths that used to live in a spreadsheet.
- 03
A Chrome extension for the last mile
Data moves from the system into the tax authority's program with no retyping — the step where time saved also becomes error avoided.
- 04
Technical SEO from the start
Heading structure, structured data, audience-segment pages and image optimization. Organic acquisition treated as part of the product, not as a later campaign.
The outcome
- A filing that required qualified hours now takes minutes
- A 2,700+ municipality land-value database available inside the workflow
- Zero retyping when filing to the official program
- Our own product live, with organic acquisition structured from day one
What this project teaches
The most valuable part wasn't the calculation — it was removing the retyping at the last mile. Automation that stops before the final step leaves exactly where human error costs the most. It's worth asking, on every project, where the process actually ends.
Stack
- Next.js
- Vercel
- n8n
- PostgreSQL
- Chrome Extension
- Technical SEO
Facing something similar?
Tell us the process you want to automate. You leave the conversation with a technical path — no commercial proposal in between.