Software for agriculture.
We have worked with farming companies since 2023. We know the vocabulary — season, field, task, input, withdrawal order — and what happens when the plan lives in a spreadsheet and the execution in each manager's head.
How this kind of project works
What we build
Season planning by field, records of tasks and inputs, stock and withdrawal orders, harvest, costs and valuation. On the administrative side, accounting and reports for several companies in one system.
Who it is for
Growers and companies that need what was planned and what was done to add up, administrators who keep the books of more than one company, and businesses that already have a product for agriculture and need a team to keep building it.
How we work
Module by module and without interrupting operations, because the season does not wait. Each delivery is tested with the people who use it, and the data model is adjusted with real use.
More than one country
Fieldpartner is used in Argentina and Brazil, in Spanish, Portuguese and English.
What we need from you
Your team's agronomic or accounting knowledge to define cycles, tasks and rules, and feedback from users on every delivery.
How long it takes and how it is priced
It depends on scope. After a 30-minute call we send a proposal with scope, timeline and a fixed price. Work runs in two-week stages with a demo at the end of each one, and you can change direction between stages.
Projects where we did it
Fieldpartner.
A platform for growers in Argentina and Brazil: plan the season, record tasks and inputs by field and close the harvest. We have worked on the product since October 2023.
AgroApex.
A farm accounting system with twenty years on Excel and Access, which we are rebuilding as a web platform for several companies.
Frequently asked questions
Do you work on an existing product?
Yes. We join your team, your tools and your repository. We have worked on Fieldpartner continuously since October 2023, adding modules without slowing users down.
Custom system or off-the-shelf?
If an existing product covers almost everything, use it. Custom makes sense when the way you work does not fit any of them, or when the system is part of what you sell.
Can you migrate what we have in Excel or Access?
Yes. That is what we are doing at AgroApex: data is imported and each module is checked against the numbers of the previous system.
Who owns the code?
You do. It lives in your repository, under your licence, from day one. We never reuse one client's code in another client's project.
What happens after delivery?
We leave documentation and include three months of support. After that we stay on only if you need us.