Ag Retail Crop Input Software: Build or Buy, and Why the Ledger Is Not the Question
Buy the accounting, at every size, without exception. Agvance and AGRIS encode decades of ag retail specific accounting for prepay, bookings, blending, split billing and patronage, and Levridge covers the same ground on Microsoft Dynamics 365 for co ops that want it.
On this page
Buy the accounting, at every size, without exception. Agvance and AGRIS encode decades of ag retail specific accounting for prepay, bookings, blending, split billing and patronage, and Levridge covers the same ground on Microsoft Dynamics 365 for co ops that want it. The build question is only about the operations layer around that ledger, and the threshold is whether custom application is dispatched from a whiteboard with tickets keyed from paper afterwards. If it is, an operations layer runs $70,000 to $160,000 over 12 to 18 weeks and usually pays back inside one season. If your dispatcher can see every job from where he stands, buy and stop.
When is off the shelf genuinely the right call here?
Buy Agvance or AGRIS and keep them. We say that against our own interest. Those products carry an enormous amount of industry specific accounting that took decades to accumulate: prepay held as customer money with product level strings attached, bookings at locked prices, blend formulas, split invoicing across landlord and tenant, patronage allocation. Rebuilding that is a multi year programme with a high failure rate and no operational upside in year one. Levridge is the sensible modern alternative if you want the ledger on Dynamics 365 with a co op orientation, and a like for like migration is a shorter and safer path than a rebuild.
Make anyone proposing to replace your accounting system walk you through the prepay accounting model in detail before you believe them. A developer who calls prepay a customer deposit has already told you the project will fail.
Buy and stop entirely if you are a single location retailer with a handful of rigs, your dispatcher can see every job from where he stands, and a grower who rings the counter gets an answer in a minute. At that size the whiteboard is a legitimate system. It is visible, everyone reads it the same way, and it never claimed to be authoritative. Money is better spent on agronomy staff than on software that formalises something already working.
The signal that buying is still right: nobody is retyping. When application tickets go from paper into a system days later, that changed.
When does a custom build actually pay off?
The build case is about the four weeks that decide your year, and it lives entirely outside the general ledger.
- Custom application runs on a whiteboard. Rigs, tenders, field boundaries, product loaded and applicator licence status exist in a dispatcher's head and on magnets. Nothing on that board is in any system, and acres applied arrive on paper after the fact.
- Invoicing lags application by weeks. That gap is working capital sitting in a filing tray, and it exists because a keying step sits between the cab and the invoice.
- Growers and agronomists cannot see prepay without phoning the office. Prepay is normally tied to specific products at specific prices, so a single dollar balance answers nothing. The counter, the agronomist in the field and the grower each need the position per product.
- The blend plant to invoice chain has manual transcriptions in it. Ordered and actual weights always differ, and thin fertiliser margin leaks in that gap in amounts too small to notice individually.
- You are a co op with one grower across several divisions. Agronomy credit, grain positions, feed and energy net into a real exposure that nobody can see, so April credit decisions are made against a partial picture.
- Margin is provisional all season because manufacturer rebate accrual lives in a spreadsheet on the finance director's laptop.
Each of those has an operational payback and none of them requires touching the ledger. That is the whole point.
How do they compare on the things that matter in this industry?
On prepay and booking accounting, buying wins outright and permanently. The ledger treatment your auditor expects is not a place to be inventive.
On fleet dispatch, a build wins because the packaged products were never designed for it. This is field service work with agronomy layered on top: work orders carrying field boundary, product and rate, generated from the agronomist's recommendation rather than retyped, and a board that knows rig capability, product loaded, tender position and applicator licence status.
On the cab, a build wins if and only if it is built properly. Offline capture that keeps working in a field with no coverage, records start and finish, pulls actual acres from the machine controller where it is exposed, and produces the restricted use pesticide application record you must retain. Certified applicators face a federal minimum retention of two years with many states requiring longer, so confirm your own state's rules with the state lead agency rather than with any vendor.
On grower facing visibility, a build wins on presentation rather than data. The position already exists in the ledger. Reading it reliably and showing drawdown per product on a phone is the work, and it needs no write access at all.
On integration burden, buying wins. Every read you build against Agvance or AGRIS is yours to maintain when the vendor updates, and writing transactions into a live ledger during April is a different risk class from reading positions.
On portability, own the operations layer and the field data. The application records and field boundaries are yours, and for a business with a four week peak the ability to hire a second team quickly is a risk control rather than a contract detail.
What does total cost of ownership look like at your scale?
The operations layer runs $70,000 to $160,000 over 12 to 18 weeks in Digital Heroes delivery experience: work orders, dispatch board, offline in cab capture, blend and delivery reconciliation, a grower portal showing prepay per product, and consolidated credit exposure. Adding rebate accrual with programme terms modelled as rules, live margin including accrual, agronomist recommendation intake and multi division consolidation takes it to $180,000 to $400,000 over 9 to 15 months. Full replacement of bookings, prepay accounting, inventory and billing is $300,000 to $800,000 over 12 to 24 months, and we list it because retailers ask, not because we recommend it.
Within the operations band, dispatch plus mobile capture alone is roughly $60,000 to $85,000 depending on fleet size and location count. Modelling your largest manufacturer programmes sits at $35,000 to $60,000 inside the extended platform.
The drivers are location count and whether locations actually operate the same way, which they usually do not, blend plant integration where the controller may be older than the rest of your stack, and accounting integration depth. Reading positions is manageable. Writing transactions back needs a testing regime that can cost more than the integration.
Running costs are $350 to $1,000 a month of infrastructure, driven by mobile sync and cab photographs rather than compute, plus 15 to 20 percent of build annually for support and enhancement. That percentage is higher than most categories because a fault during the application window is not an inconvenience. Add device management for rugged tablets that get broken, lost and reassigned, and an annual task to enter each season's programme terms before the early order window.
What does the hybrid look like, and when is it the honest answer?
In this category the hybrid is not one option among several, it is the recommendation. Keep the ledger, build the layer, and read rather than write in the first release.
That single decision, read only integration, removes the largest risk item from a project that has to survive April. A grower portal showing an accurate prepay position needs no write access to Agvance at all. Sequence write back into a later phase once the layer has been through a season.
Start with dispatch and the mobile ticket. It is the operational bottleneck, it produces the billing data, and it is the part no product you already own is doing. Build the cab first: an application that works in the office and fails in a field with no signal is worse than the whiteboard, because the whiteboard never pretended.
Use scale tickets rather than plant control integration where the plant is old. You lose some precision and save weeks. Integrate the modern plant, prove the reconciliation, then decide whether the older one earns the work.
Ship the grower portal late and deliberately. It is the piece growers see, and a portal showing a wrong prepay balance costs more credibility than no portal at all.
Which should you choose, by operator size and stage?
Single location, a few rigs, one blend plant: buy the accounting, keep the whiteboard, spend on agronomists. Revisit when you add a second location or the dispatcher stops being able to see the yard.
Two locations, modest fleet, invoicing lagging application: build the smallest credible version at around $70,000, meaning work orders, a dispatch board, offline in cab capture and a basic grower view of prepay and bookings. Read only against the ledger.
Three to five locations, two blend plants, growers ringing the counter about prepay: the full operations layer at $70,000 to $160,000 is the right project, and it should pay back within one season through same week invoicing alone.
Co ops serving one grower across agronomy, grain, feed and energy, or anyone whose margin stays provisional until rebates settle: extend to $180,000 to $400,000, and do the grower entity resolution with your controller before kickoff. That is unpaid preparation that removes paid discovery, and it is a governance decision the development team should not be making.
Whoever you hire, ask them to explain prepay drawdown back to you before you explain it twice, and ask what they have shipped that dispatches a fleet with offline mobile capture. Plan the cutover well outside the spring window. Nobody should be learning a dispatch board in the second week of April.
When you are ready to turn this into a specification, Digital Heroes has delivered more than 2,000 projects with a named team you can speak to before you sign, rather than a bench you meet in month two. Nothing about that commits you to the build.
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) →
- Gallup reports global employee engagement fell to 20% in 2025 (its lowest since 2020, down from a 2022-2023 peak of 23%), and estimates low engagement costs the world economy an estimated $10 trillion in lost productivity, or 9% of global GDP. (Note: this figure appears in Gallup's evergreen State of the Global Workplace page, currently reflecting the 2026 edition reporting on 2025 data.). Source: Gallup (2025) →
- Brandon Hall Group research on onboarding reports that done well, structured onboarding drives measurable gains in new-hire productivity, employee engagement, and retention; the page notes 41% of organizations experience greater than 5% turnover among new hires. Source: Brandon Hall Group (2024) →
Frequently asked questions
What does it cost to switch from Agvance to AGRIS or Levridge?
Treat it as a full accounting migration rather than a software swap, because the data that moves is prepay balances, open bookings at locked prices, blend formulas, patronage history and split billing arrangements. Retailers who have done it plan a year and a parallel season.
That is exactly why we recommend building the operations layer against whichever ledger you have rather than around a migration. If the ledger changes later, the layer's read integration is re pointed, and your field data and application records never move.
What happens if our accounting vendor changes pricing or its module strategy?
Your exposure depends on how much of your operation lives inside their product. If dispatch, field records and grower facing views are yours, a price change is a negotiation about the ledger only, which is a smaller conversation.
Budget a few days a year regardless for integration maintenance. The vendor updates on their schedule, and while reads are usually stable, a version change can require attention before your spring window rather than during it.
How long does the operations layer take to build?
Twelve to 18 weeks, with dispatch and the in cab ticket carrying roughly 40 percent of the schedule. The extended platform with rebate accrual and multi division consolidation runs 9 to 15 months in total.
The two items that most often stretch the timeline are integrating an older blend plant controller and establishing reliable reads from your accounting package. Plan the cutover outside the application window and run one spring in parallel with the whiteboard.
Is Levridge a better answer than building anything at all?
If your genuine constraint is the accounting system, evaluate Levridge before you evaluate a build. Sitting on Dynamics 365 with a co op orientation, it addresses the ledger problem directly and a like for like migration is shorter and safer than a rebuild.
It does not change the operations question. Fleet dispatch, offline in cab capture and same week invoicing from actual applied acres are still the gap, and that gap is where the payback is regardless of which ledger you run.
Can we start with dispatch only and add the grower portal later?
Yes, and that is the sequence we recommend. Dispatch plus offline mobile capture is roughly $60,000 to $85,000 depending on fleet size and location count, it removes the keying step between cab and invoice, and the payback shows inside one season.
The portal is better built once the data behind it is proven. A portal showing a wrong prepay balance costs more credibility than having no portal at all.
Why is the in cab application such a large share of the budget?
Because it has to work with no signal and still be correct. Offline capture means conflict handling when two devices sync, device provisioning and replacement, pulling actual acres from the machine controller where it is exposed, and producing the restricted use pesticide record you are required to retain.
Be sceptical of any quote that treats the cab as a form. That is the expensive half of this category, and a quote that underprices it has not been in a rig.
Should the system write transactions back into our ledger?
Eventually, and not in the first release. Reading prepay positions, balances and product master data is manageable and carries limited risk. Writing invoices and adjustments into a live ledger during the four weeks that decide your year is a different risk class and needs a testing regime that can cost more than the integration itself.
Get through one season reading only, then sequence write back with a full parallel run behind it.
How do we justify this when the accounting system already works?
Do not compare it against the accounting renewal, because you are keeping that. Compare it against the operations you currently run without software: hours keying tickets from paper, the delay between application and invoice, counter time answering prepay questions, and the reconciliation between blend tickets and invoices.
Then weigh the exposure rather than the efficiency. Prepay is customer money you hold and seasonal credit is real risk against income that arrives after harvest. Managing that from memory during your peak is the stronger argument.
What happens to my ERP if the agency shuts down or we part ways?
If ownership was set up correctly, nothing breaks: you hold the source code, the system runs in cloud accounts you own, and handover documentation lets a new team take over. Insist on repository access from day one, admin ownership of all hosting and third-party accounts, and documentation as a contract deliverable rather than a favor. This is the single most important clause to check before signing an ERP contract.
Will a custom ERP scale as we grow from 50 to 500 employees?
Yes, if it is designed for that from the start, which mostly means clean database design, permissions that handle new departments, and modules that stay separable. Adding users to software you own costs nothing in licenses, the opposite of the per-seat scaling penalty on NetSuite or Dynamics. What does need budget as you grow is new modules and integrations, so keep a small standing development arrangement rather than restarting a vendor search every two years.
How many SaaS seats do we need before building custom becomes cheaper?
The crossover usually shows up between 20 and 50 seats on premium tiers. Salesforce Enterprise lists at $165 per user per month, so 40 users cost about $79,000 a year in subscriptions, which is real money against a custom system you would own outright. Run the comparison over three years: if subscription spend beats the build cost plus 15-20% annual maintenance, custom wins on price before you even count workflow fit.
What are the biggest mistakes first-time software buyers make?
Choosing the lowest bid, paying more than 30-40% upfront instead of on milestones, skipping a written specification, and having no maintenance plan for after launch. The most expensive of the four in Digital Heroes rescue projects is the missing spec: without written acceptance criteria, done becomes an argument instead of a checklist, and every disagreement resolves in the vendor's favor. Fix those four and you have avoided most of the ways these projects fail.
Can a custom ERP integrate with the tools we already use, like QuickBooks or Shopify?
Yes, and keeping tools that already work well is usually the right call. The integrations we build most often are QuickBooks or Xero for accounting, Shopify or WooCommerce for orders, ShipStation for fulfillment, and Salesforce or HubSpot for CRM. A typical integration adds $5,000 to $15,000 to the build depending on how much two-way syncing the workflow needs.
Can I start with one ERP module instead of the full system?
Yes, and it is how most successful custom ERP projects at Digital Heroes begin. We build the single module causing the worst pain first, typically inventory or order management, get it live in 10 to 14 weeks, and let it prove ROI before the next phase gets funded. Starting with one module also derisks data migration because you move one dataset at a time.
Is SAP overkill for a mid-sized company?
For most companies under about 500 employees, yes. SAP S/4HANA is built for multi-entity, multi-country enterprises with implementations measured in years and seven figures, while SAP Business One, the mid-market product, still forces your processes into its mold. If your competitive edge lives in how you operate, a custom ERP scoped to your actual workflows ships faster and costs a fraction of an SAP program.
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.
Can a freelancer build an ERP, or do I need an agency?
An ERP is too wide for one person: it needs backend, frontend, database design, integrations, QA, and someone mapping your business processes. A solo freelancer can extend an existing ERP or ship one small internal tool, but full ERP builds by single developers are the most common rescue scenario Digital Heroes takes on. If budget is tight, shrink the scope to one module rather than shrinking the team below three or four people.
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.
Should I hire a freelancer or an agency for my software project?
A skilled freelancer is the right call for a single-discipline scope under roughly $15,000, like a website, a plugin, or one integration. Above that, projects need design, backend, testing, and project management at once, and a solo builder becomes the single point of failure: if they get sick or take a bigger client, your project simply stops. Agencies bill 20-40% more per hour but carry continuity, code review, and someone to escalate to, which is what you are actually buying.
How do I vet an agency for an ERP project?
Ask to speak with two clients who have been running an ERP the agency built for at least two years, because ERP quality shows up in year two, not at launch. Then ask for their data migration plan, their module rollout sequence, and the named senior engineers who will be on your project. An agency that leads with screen designs instead of process mapping is a red flag for ERP work.
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 Sophie.
Account Manager · UK Retail & Fashion · London · 4 posts on the site
Published · Last updated .
