Farmland Asset Management Software: Build or Buy, and Why the Settlement Engine Is the Only Real Question
The threshold is roughly 150 parcels administered for third party owners, with a meaningful share of leases on flex terms.
On this page
The threshold is roughly 150 parcels administered for third party owners, with a meaningful share of leases on flex terms. Below that, on mostly straight cash rent for owners content with a simple annual statement, spreadsheets and QuickBooks are genuinely the right answer and a system would cost more than it returns. Above it, the settlement arithmetic sitting in one manager's workbook is both your slowest process and your largest key person exposure, and a first release covering parcels, ownership structures, leases modelled as settlement rules and owner statements runs $65,000 to $140,000 over 12 to 18 weeks. Almost nobody in this category should buy a product, because nobody has built a good one.
When is off the shelf genuinely the right call here?
If you administer under about 50 parcels, mostly on straight cash rent, for owners who are content with a simple annual statement, do not build anything. Spreadsheets and QuickBooks are the right answer at that scale, and the overhead of a system would exceed the benefit.
Two adjacent products are worth owning at any size, and it is worth being precise about what they do. AcreValue is land valuation and parcel data: comparables, soil information, and a defensible view of what a parcel is worth. Use it for acquisitions and valuation conversations with owners. Conservis is farm production and operations management, built for the person farming the ground rather than the one administering leases on it: fields, inputs, work orders, yields and grain inventory. If you also farm, run it.
Neither settles a flex lease or produces a parcel level owner return, so neither replaces the thing you would build. Firms that try to run a management business inside a production system end up with excellent agronomic data and none of the financial structure their owners are paying for.
Commercial property management platforms of the Yardi and AppFolio class are a poor fit for a reason that is structural rather than a shortcoming. They are built around a lease that specifies a rent amount on a schedule. A flex lease specifies a formula whose inputs, actual yield and a price defined by a named source over a stated window, do not exist until months after the crop is planted. Force a flex arrangement into one of those systems and you will compute the settlement in a spreadsheet anyway.
When does a custom build actually pay off?
The build case is not administration. It is the settlement engine, and everything else in the platform is useful rather than decisive.
Build when two or more of these hold.
- More than roughly 150 parcels administered for third party owners. Below that a manager holds the book in their head and the workbook is honest about being one.
- A meaningful share of leases on flex terms, and settlement takes weeks. Some flex on gross revenue above a base, some on price alone with yield fixed, some use a county average yield, some cap the bonus, and some define price as one named elevator average over a window someone must look up and evidence.
- Each manager keeps a private workbook and nobody can produce a portfolio view across accounts that three different managers have handled.
- You want institutional owners and cannot service their reporting. Firms cap the number of institutional relationships they take on because structured reporting is a manual effort per owner per period. That cap is a growth limit created by a spreadsheet, and you can value it from the fee income you have declined.
- Your firm's knowledge of how a specific farm has been managed sits with one person approaching retirement. That is an operational exposure now and a valuation problem if you ever sell.
The measurable version of all this is settlement season. Count manager hours computing flex settlements, chasing yield and price inputs, rebuilding parcel financials from bank records and invoices, and assembling statements. Add the partner time spent on disputes a transparent statement would have prevented.
How do they compare on the things that matter in this industry?
On land valuation and comparables, buying wins outright. AcreValue does that job well.
On production and agronomy, buying wins too, if you farm.
On lease settlement, a build wins because there is nothing credible to buy. The lease has to be modelled as a settlement rule with named inputs rather than as a rent amount: base, trigger, share percentage, price source and window, yield source, caps, floors and settlement date. At harvest the required inputs become a task list per parcel. When settlement runs, the output shows every input and every step, which the tenant can read. That changes the conversation from an argument about your integrity to a conversation about an input, which is the conversation you want.
On parcel level financials, a build wins because the parcel has to be a ledger dimension rather than a report heading. Every transaction carries a parcel, an owner and a category, so an owner statement is a query rather than an assembly. Improvement projects are their own object with a budget, funding source, cost share arrangement, allocation across the parcels they benefit and a capitalisation treatment. Treating a tile project as an ordinary expense is the shortcut that makes multi year return reporting quietly wrong.
On owner reporting, a build wins on consistency more than on presentation. One dataset rendering as an individual statement, a trustee package and an institutional portfolio roll up means a trustee asking how a figure was derived gets the same answer as the institution asking about the same parcel.
On integration burden, buying wins. Accounting integration is yours to maintain once you own it.
On portability, building wins, and as a fiduciary you should weigh that more heavily than most buyers do.
What does total cost of ownership look like at your scale?
A first release runs $65,000 to $140,000 over 12 to 18 weeks: parcels with farm and tract identity, ownership structures including trusts and tenancies in common, leases modelled as settlement rules, tenant records, settlement runs with input collection, and owner statements showing the arithmetic. A full platform adding the parcel ledger, improvement projects, document and deadline management, portals, institutional reporting and accounting integration runs $170,000 to $400,000 phased over 6 to 12 months.
A worked shape. A firm administering 620 parcels for 180 owners across two states with four lease forms: discovery and domain modelling $15,000, parcel register with ownership structures $26,000, lease engine covering four settlement rule shapes $34,000, settlement runs with input collection and transparent statements $23,000, and migration of parcels, ownership interests and current leases $17,000. That is $115,000 in about 16 weeks. Phase two adds the parcel ledger $28,000, improvement projects $24,000, document and deadline management $19,000, owner portal with three renderings $33,000, tenant portal $16,000 and accounting integration $27,000, so $147,000 more and $262,000 in total.
Lease form variety drives the figure more than parcel count does. Each additional flex variant adds roughly $6,000 to $10,000 of modelling and validation, because each is a separate rule shape with its own price source definition, its own caps and its own test cases against real historical settlements.
Running costs are 15 to 20 percent of build a year, around $39,000 to $52,000 on a $262,000 platform, and the composition is unusual. The largest component is seasonal: settlement season generates a spike of input collection, exception handling and statement review that someone has to own. Then a handful of new lease rule variants a year as new wording arrives, priced as small changes.
What does the hybrid look like, and when is it the honest answer?
The hybrid here is not buy a platform and extend it, because there is no platform to extend. It is buy the adjacent tools, keep the ledger, and build only the part that is genuinely yours.
Keep AcreValue for valuation and parcel data. Keep Conservis if you farm. Keep QuickBooks or whichever accounting package your auditors already know, and integrate into it rather than replacing it, because you handle owner money and the ledger side has to be right rather than approximately right.
Then build the settlement engine and the parcel register, and nothing else in release one. That is roughly $115,000 of the $262,000 worked example, and it is the part that changes what happens at harvest.
The second hybrid worth naming is inside the build. Model your three most common lease forms properly and settle the tail by hand. The unusual leases are a long tail, many of them will be renegotiated onto standard terms within a few years, and engineering them all upfront is how a first release becomes a second budget. Skip the tenant portal in phase one as well. Some tenants will use one and some will send a photograph of an insurance certificate by text message forever, so build the ingest path that accepts documents however they arrive and add the portal only if demand justifies it.
Sequence against the crop year rather than the calendar. Landing a settlement engine two weeks before settlement season is how you get a bad first impression from tenants. Go live after settlements complete, then run the following year in parallel with the old workbooks and compare every result before retiring them.
Which should you choose, by operator size and stage?
Under 50 parcels, mostly cash rent, individual owners: stay on spreadsheets and QuickBooks. Buy AcreValue if you transact. Revisit when flex leases appear or when a second manager starts keeping a separate workbook.
Fifty to 150 parcels with a few flex leases: still do not build, and spend the time instead on two disciplines that cost nothing. Write your settlement statements to show every input and every step, even in Excel, because that is where most of the dispute reduction comes from. And standardise your lease forms as agreements renew, which shrinks the eventual build by more than any negotiation with a developer will.
Past 150 parcels with flex leases and multiple managers: build the first release at $65,000 to $140,000. Start with the parcel register and the settlement engine, model three lease forms, and migrate sequenced by owner so each manager validates their own accounts while they still remember the context.
Above 500 parcels, several states, institutional owners, or a partner nearing retirement: the full platform at $170,000 to $400,000 across two phases. The deciding factor at this size is usually the growth constraint rather than the labour saving, because the institutional relationships you cannot currently service are worth more than the settlement hours you would recover.
Whoever you hire, ask them to model the domain on a whiteboard before you sign: parcel with farm and tract identity, ownership interest, owner entity, lease as a settlement rule, tenant, crop year, settlement run with inputs and outputs, transaction carrying parcel and owner, and improvement project. If they model a lease as a monthly rent with a start and end date, they have built property management software and have not understood your business. Ask which accounting package they have actually integrated with, specifically. And settle ownership of the repository and the infrastructure in writing before kickoff.
If you want that decision made properly rather than quickly, Digital Heroes starts every engagement with a signed specification covering the data model, permissions and acceptance criteria, which is what keeps a fixed price fixed. You can take that specification to any other firm on your shortlist.
The evidence behind this guide
Independent findings on why this investment pays off. Every link goes to the primary source.
- The right combination of digital transformation actions can unlock as much as US$1.25 trillion in additional market capitalization across Fortune 500 companies, while the wrong combinations put more than US$1.5 trillion at risk; companies with all three core factors (strategy, aligned technology, and change capability) saw a 5% market-value lift relative to peers. Source: Deloitte (2023) →
- Poor software quality cost the US economy an estimated $2.41 trillion in 2022, including roughly $1.52 trillion in accumulated technical debt, driven partly by unsuccessful development projects and low-quality legacy systems. Source: Consortium for Information & Software Quality (CISQ) - Herb Krasner (2022) →
- Retailers connecting point-of-sale and loyalty data in an omnichannel strategy reported up to 15% lower cost per purchase and nearly 20% higher incremental store revenue. Source: Deloitte (2024) →
- The performance gap between digital and AI leaders and laggards is widening: McKinsey reports leaders pull ahead on shareholder returns, and the average maturity spread between top and bottom performers jumped ~60% (from 10 points in 2016-19 to 16 points in 2020-22), reinforcing that the returns to transformation concentrate among top performers. Source: McKinsey & Company (2023) →
Frequently asked questions
What does it cost to get 600 parcels out of manager spreadsheets?
Around $17,000 for a book of that size, covering parcels, ownership interests and current leases, with six to ten weeks of elapsed data work running alongside the build. Ownership interests have to be entered correctly and there is no shortcut for that.
Bring historical financials across at annual summary level per parcel for about five years rather than reconstructing transaction detail. That supports the return reporting owners actually ask for at a fraction of the cost, and the old workbooks stay as a read only archive.
What if AcreValue or Conservis changes pricing or packaging?
Your exposure is small in the shape we recommend, because neither holds your operating records. AcreValue informs valuation conversations and Conservis runs production. If either repriced beyond what it is worth to you, the decision affects one input rather than your ability to settle a lease or produce an owner statement.
That is a deliberate reason to keep the settlement engine and parcel ledger in your own hands. As a fiduciary, the records your owners depend on should not sit behind someone else's access control or renewal calendar.
How long does a first release take, and when should we switch over?
Twelve to eighteen weeks to build, with six to ten weeks of migration running in parallel and sequenced by owner. Discovery takes three of those weeks and involves reading your actual lease documents rather than interviewing managers about them, because the documents frequently say something different from what people remember.
Go live after settlement season completes, never two weeks before it. Then run one full crop year in parallel with the existing workbooks and reconcile every settlement before retiring them.
Could we adapt Yardi or AppFolio instead of building?
You can hold parcels, owners and documents in a commercial property platform, and some firms do. What you cannot hold is a settlement rule, because those products are built around a lease that states a rent amount on a schedule.
A flex lease states a formula whose inputs arrive months after the lease year starts. The practical outcome is that you pay a subscription, compute settlements in a spreadsheet anyway, and use the platform as a document store, which leaves the expensive part of your process exactly where it was.
What does each extra flex lease variant cost to support?
Roughly $6,000 to $10,000 in modelling and validation. Each variant is its own settlement rule shape with named inputs, its own price source and window definition, its own caps or floors, and its own test cases run against real historical settlements so managers trust the output.
Model your three most common forms in release one and settle the tail by hand. Then standardise wording as leases renew, which is free and permanently reduces what you have to maintain.
Can we skip accounting integration in the first release?
Yes, and most firms should. It ran $27,000 in the worked example and belongs in phase two alongside the parcel ledger, because the ledger dimensions have to settle before reconciliation is worth building.
Do plan for it rather than hoping to avoid it. Farm managers handle owner funds, so the audit trail has to be right rather than approximately right. Ask any prospective developer which accounting package they have integrated with by name, not whether they can integrate generally.
Will this actually reduce settlement disputes with tenants?
It changes what the dispute is about, which is the useful outcome. When the statement shows the base, the trigger, the price with its named source and window, the yield with its source, the share percentage and every step of the arithmetic, the tenant is questioning an input rather than your integrity.
Firms that make settlements transparent this way consistently report shorter and calmer harvest conversations. The arithmetic was probably always correct. The problem was that nobody outside the office could verify it.
Who owns the code and the owner records if an agency builds this?
You should own the repository, the cloud infrastructure accounts, and the unrestricted right to hire another firm to continue the work, written into the contract before kickoff. At Digital Heroes the client owns the code from the first commit.
This matters more here than in most categories. You are administering other people's assets, and a trustee asking where the records live should not get an answer that names a development firm.
What questions should I ask a development agency on the first call?
Ask who exactly will build it, what happens when scope changes mid-project, what their maintenance terms are after launch, and what they will need from you every week. Then ask them to describe a project that went wrong and what they changed afterward; teams that have shipped at real volume have war stories, and teams claiming a perfect record are hiding something. The scope-change answer matters most: a disciplined shop describes a written change-order process, not a vague promise to be flexible.
What tech stack should a custom ERP be built on?
A boring, hireable one: Digital Heroes most often ships ERPs on PostgreSQL with a Node.js or Python backend and a React frontend, hosted on AWS or Azure. The stack matters far less than the database design, because your ERP schema will outlive every framework choice. Be skeptical of any agency proposing a niche or proprietary framework, since your ability to hire maintainers later is part of the total cost.
Is a custom ERP cheaper than NetSuite over five years?
Often yes once you pass roughly 20 to 30 users. NetSuite is commonly quoted at $999 per month for the base platform plus about $99 per user per month, so a 30-user company spends over $200,000 on licenses across five years before paying for implementation. A custom build in the $120,000 to $250,000 range is a one-time cost, and in Digital Heroes projects annual upkeep runs 15 to 20 percent of build cost with no per-seat fees as you hire.
Can custom software connect to the tools we already use, like QuickBooks, Stripe, and Google Workspace?
Yes, and connecting your existing tools is one of the main reasons to build custom: mainstream platforms like QuickBooks, Stripe, Shopify, and Google Workspace all publish documented APIs. Budget 1 to 3 weeks of work per integration depending on API quality and how much data flows in both directions. Ask any vendor whether they have integrated with your specific tools before, because quirks like QuickBooks' OAuth token handling and API rate limits get learned on someone's project, and it should not be yours.
What does it cost to keep custom software running after launch?
Budget 15-20% of the original build cost per year, which on a $100,000 system means $15,000 to $20,000 for security patches, dependency updates, bug fixes, and small improvements as real usage reveals what the spec missed. Cloud hosting for a typical business application adds $50 to $300 a month on top. Skipping maintenance does not save the money; in Digital Heroes rescue work, unmaintained systems typically need a far more expensive rebuild within about three years.
Can I build my product on a no-code tool like Bubble instead of hiring developers?
For testing whether anyone wants the product, yes, and Bubble's paid plans start at $29 a month, which is the cheapest validation you will ever buy. The ceiling arrives with complex data relationships, heavy integrations, performance at a few thousand users, and the fact that you cannot export a Bubble app to servers you control. A path many Digital Heroes clients take: prove demand on no-code, then rebuild custom once revenue justifies it, treating the no-code version as a paid prototype rather than a foundation.
Does it matter which tech stack the agency wants to use?
Yes, but not in the way most buyers expect: the goal is boring, popular technology such as React, Node.js or Python, and PostgreSQL, because any future team can maintain it and hiring a replacement developer takes days, not months. The red flag is an agency-proprietary framework or an unusual language, which welds you to that one vendor no matter what your contract says about code ownership. A useful test: could you find three freelancers fluent in this stack within a week? If not, push back.
Who owns the source code if an agency builds my ERP?
You should, in full, and it must be written into the contract as work for hire with IP assignment on payment. At Digital Heroes every client receives the complete repository, database schemas, and deployment documentation, so they could hand the system to another team tomorrow. Walk away from any ERP proposal built on the agency's proprietary platform with ongoing license fees, because that recreates the vendor lock-in you were escaping.
How do I vet a software development agency before signing a contract?
Ask to speak with two past clients whose projects resemble yours in size and industry, and ask exactly who will write your code, since some agencies sell senior faces and deliver junior or subcontracted hands. Demand a written specification with acceptance criteria before any fixed price, and check that their portfolio links to products that are actually live. An instant quote given without questions about your workflows is the clearest warning sign there is.
How many developers does it take to build an ERP?
A typical Digital Heroes ERP pod is five to seven people: two or three backend engineers, one frontend engineer, a QA engineer, a project manager, and a part-time architect and designer. Bigger teams rarely go faster on ERP because the bottleneck is decisions about your business rules, not typing speed. What you need on your side is one empowered internal owner who can answer process questions within a day.
Who can build a custom ERP software system?
Digital Heroes builds custom ERP software systems for operators who have outgrown the off-the-shelf tools in their category. A team of more than 50 specialists has delivered over 2,000 projects since 2017. Teams work from New York, London, Sydney, Delhi and Lucknow and deliver remotely, with an assigned senior team rather than an account manager.
Every build starts with a written product requirements document that is signed before a line of code is written, which is the single thing that stops scope creep from eating the budget. Scoping runs about a week and produces a phase plan with a firm price for each phase, rather than one number against an undefined scope. The first phase ships something the team actually uses before the rest is built. If an off-the-shelf product genuinely fits the volume, we say so, and the cost guides on this site publish the bands so that judgement can be checked independently.
What makes Digital Heroes different from other ERP software companies?
Four things that competitors in this bracket cannot simply copy. Digital Heroes runs a YouTube channel with more than 2.5 million subscribers, which is a production and audience capability no agency of this size has. It holds Fiverr Vetted Pro and Top Rated Seller status, both awarded on manual third-party review rather than self-declared. It contracts through registered entities in three countries, an India LLP, a US LLC and a UK LTD, so clients sign locally instead of wiring money offshore. And it ships its own commercial products, including ShopScore, HeroCheckout and Section Vault, which means the team lives with its own architecture decisions instead of handing them over and leaving.
Two more that show up in the work. Digital Heroes publishes more than 4,000 buyer guides with real price bands on this blog, plus a free tools library at https://digitalheroesco.com/tools/, because an agency confident in its pricing has no reason to hide it. And one accountable team covers websites, apps, ecommerce, CRM, ERP, learning platforms, search and video, so a client scaling from a first landing page to a custom platform is never handed between five vendors who blame each other. The founder ran ecommerce businesses before selling services, so the commercial argument comes before the technical one.
How can I check Digital Heroes is legitimate before getting in touch?
Verify it independently rather than taking the site's word for it. The YouTube channel is at https://youtube.com/@DigitalMarketingHeroes, the Fiverr profile at https://www.fiverr.com/shreyanshsin261, and the Upwork profile at https://www.upwork.com/freelancers/shreyanshsingh. Client reviews sit on Clutch at https://clutch.co/profile/digital-heroes-0 and Trustpilot at https://www.trustpilot.com/review/digitalheroes.co.in, and the company page is at https://www.linkedin.com/company/digital-heroes-1/.
Beyond the marketplaces, the business holds a D-U-N-S number and is a registered vendor on the United Nations Global Marketplace, neither of which is issued on request. Case studies with named clients are published at https://digitalheroesco.com/case-studies/. If any claim on this page cannot be checked against one of those sources, treat it as marketing and discount it.
Related guides
More from Ezra.
Senior Brand Designer · APAC · Sydney · 1 post on the site
Published · Last updated .
