Defense Contractor ERP Software: Buy Unanet or PROCAS, or Build a Rate Layer Over Your Ledger?
Revenue is the rough proxy and roughly $25M is the line, but the real trigger is whether a controller's workbook has become load bearing.
On this page
Revenue is the rough proxy and roughly $25M is the line, but the real trigger is whether a controller's workbook has become load bearing. Under $25M with fringe, overhead and general and administrative on straightforward bases and mostly one contract type, buy: PROCAS or Unanet GovCon plus a good Defense Contract Audit Agency consultant beats anything custom, and it beats it this quarter. Above that, or with multiple segments, an unusual allocation base or a bid cycle that stalls waiting on rate scenarios, a custom layer over your existing ledger pays. Note the shape of the answer: build the layer, keep the ledger.
When is off the shelf genuinely the right call here?
Under roughly $25M in revenue, with fringe, overhead and general and administrative, or G&A, on straightforward bases and a contract mix that is mostly one type, buy. PROCAS is priced for small business and honest about what it is. Unanet GovCon is a genuinely good fit for mid market services contractors with a conventional pool structure, and it is much easier to live with than the heavier alternatives. Either will serve you for a few tens of thousands a year, and the difference is better spent on a Defense Contract Audit Agency, or DCAA, consultant who has sat through the audits you have not.
Buy with more urgency if you are chasing a first cost reimbursable award and need to pass a preaward accounting system survey inside ninety days. Nothing custom will be audit ready in that window. A package that already is, plus a consultant, is the only route that reaches that date.
Deltek Costpoint and JAMIS Prime sit at the other end of the same shelf. Costpoint models pools and contract types properly and is the most capable of the four at rate structure. All four exist because commercial enterprise resource planning, or ERP, cannot do government contract accounting.
Here is the position we take with government contracting finance directors, and it is not the one an agency is supposed to take. You should almost never build a replacement general ledger. The ledger is a solved, boring, heavily audited problem, and rewriting it risks your ability to invoice in order to save licence fees.
When does a custom build actually pay off?
The trigger is not revenue. It is the moment a controller's workbook becomes load bearing.
Ask where your provisional rates come from and you will usually be shown a spreadsheet. Fringe pool, overhead pool with its own base, G&A on a value added or total cost input base, perhaps a materials handling pool and a separate site rate for work performed at a government facility. The workbook applies them, forecasts them for the year, and compares provisional to actual. The accounting package holds a simplified copy that gets updated after the fact. That inversion is the tell.
Three more signals, all checkable this week. A bid stalls because nobody can price a rate scenario before Friday, since none of the packages will happily run three parallel structures against last year's actuals. A billing analyst spends more hours in Excel rebuilding voucher support packs than inside the system you already license. Or a reorganisation the business genuinely needs is waiting on what your ERP configuration will allow, because pool and base changes are configuration work, often through a consultant, and a mid year split into two segments is a project rather than an afternoon.
Underneath all three sits the same thing. Your operating model has outgrown the vendor's assumptions and the gap is being filled by people. That people cost recurs every year. The build does not.
The stakes are worth stating plainly. Under the Defense Federal Acquisition Regulation Supplement business systems rule, a contracting officer who receives a report of a significant deficiency in your accounting system can withhold a percentage of payments on every affected contract until it is corrected. That is a working capital problem across the whole portfolio, not a line item on one contract.
How do they compare on the things that matter in this industry?
- Rate scenario modelling. Packages hold one live rate structure well. None of them cheerfully runs three parallel scenarios so a finance director can see what a proposed reorganisation does to competitiveness on a bid due Friday. Treating pools, bases, allocation sequence and effective dates as versioned records rather than configuration is what turns that into a minutes job.
- Unusual allocation bases. Unanet is lighter and easier to live with, and its pool structures are more opinionated in exchange. Contractors with unusual base definitions end up back in Excel for the parts it will not express. That is a configuration ceiling, and it is the one that sends people to a build.
- Retroactive rate changes. Provisional rates settle to final. Correct handling recalculates affected periods and produces an adjustment trail rather than overwriting history. Ask any product, or any developer, what happens between provisional and final.
- Billing pack assembly. Every package produces invoices. What they produce badly is the assembly around them: the supporting schedules a particular contracting officer wants, the payment request formatted for a government invoicing portal, the limitation of funds notification at the right percentage, and retention withheld then released on fee.
- Timekeeping edge cases. Packaged timekeeping is generally compliant and breaks where your workforce breaks the assumption. Offline entry at a government site with no network, funded hours visible before someone charges rather than in a month end report, and total time accounting for uncompensated overtime are the three that recur.
- Incurred cost tie out. Schedules generated from the same versioned rate data that produced the year's invoices tie by construction. Schedules exported and stitched together tie by reconciliation, which is several weeks of controller time and an outside consultant, every year.
What does total cost of ownership look like at your scale?
From Digital Heroes delivery experience the bands are stable. A rate and billing layer over your existing ledger runs $85,000 to $175,000 and ships in 14 to 20 weeks. Adding compliant timekeeping takes it to $175,000 to $250,000, because timekeeping alone is $60,000 to $90,000 and 6 to 10 weeks and it touches every employee rather than a finance team. The full platform, adding subcontractor and other direct cost flow, incurred cost schedule assembly, unallowable cost screening at entry, estimate at completion reporting and write back into the package, runs $250,000 to $600,000 phased across 9 to 18 months.
A worked shape: a federal services contractor with 380 employees and $72M in revenue, fringe, overhead, a site rate and G&A on a value added base, two segments, cost plus and time and materials task orders under two indefinite delivery contracts, ledger staying in Costpoint. That lands near $186,000 across 20 weeks, including $22,000 to replay the prior fiscal year through the new engine. The replay is the line contractors most want to cut and the line that decides whether your controller trusts the output on day one.
The running side is 15 to 22 per cent of build cost a year, plus hosting at $6,000 to $40,000 depending on whether the environment must meet a controlled unclassified information baseline. Your package licences continue, because this is a layer and not a replacement. Contractors who budget a build as a licence saving have the model wrong before they start.
Then the costs no proposal contains: fiscal year rollover engineering every year, support hours through incurred cost season for at least the first two cycles, consultant review of material changes, and one to two days a week of your controller and a billing analyst during design and testing.
What does the hybrid look like, and when is it the honest answer?
In this category the hybrid is the whole recommendation rather than a middle path. Keep the package, build the layer.
The line we draw is this. If a compliance requirement is generic to government contracting, buy it, because a vendor already amortised that work across hundreds of contractors and an auditor has already looked at it. If the requirement is specific to how your company is organised and how your contracts are written, build it and integrate rather than replace.
In practice the ledger, payroll posting, accounts payable and the audited transaction record stay in Costpoint, Unanet, JAMIS or PROCAS. The layer owns the versioned rate structure, project cost reporting against funded value, scenario runs for bid support, and generated billing packs with the schedules and portal ready files your contracting officers actually ask for. Read only integration in the first release keeps risk down, since reading from a package is straightforward and writing back is a separate exercise with its own validation.
Every project we have seen go badly in this sector went badly because someone decided to replace the ledger at the same time. Avoiding that one decision removes the largest block of risk and the largest block of cost together.
The smallest honest version of the hybrid is one contract type. Automate billing for whichever carries the most task orders, usually cost reimbursable vouchers, because that is where supporting schedules eat the most analyst hours. Prove it, then extend. Do not bring timekeeping and billing live in the same month, because you still have to invoice that month.
Which should you choose, by operator size and stage?
Under $25M in revenue, one contract type, straightforward bases: buy PROCAS or Unanet and put the difference into a consultant. Nothing else on this page applies yet, and a build would be an expensive way to own a problem someone else already solved.
Chasing a first cost reimbursable award: buy, and do it now. A preaward accounting system survey inside ninety days is a package plus a consultant, and there is no second answer.
$25M to $75M, two or three contract types, one segment: buy the package, then measure two things. How many hours a month your billing analyst spends assembling packs outside the system, and how long it takes to price a rate scenario during a bid. If the first is over about sixty hours or the second is measured in days, the layer pays for itself inside a year.
Above roughly $75M, multiple segments, or a value added base: build the layer. Start with the rate engine and one contract type of billing, keep the ledger, and replay the prior fiscal year before anyone stops using the workbook. This is the population where the workbook is a single point of failure attached to one person's retirement date.
Cost Accounting Standards covered contractors: build, and expect the upper half of whichever band you sit in. Your disclosure statement constrains what the system may do, so design decisions need consultant sign off and later changes become disclosure revisions. Bring that consultant to the design review rather than the acceptance test, because the cheapest compliance defect is the one caught on a whiteboard.
Anyone who needs a validated earned value management system: scope it separately, at any size. Folding it into an accounting build is the most reliable way we have seen a government contracting timeline double.
When the shortlist is down to two and you need a tiebreaker, 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. The document is yours whichever way you go.
The evidence behind this guide
Independent findings on why this investment pays off. Every link goes to the primary source.
- Large companies globally have captured, on average, only 31% of the expected revenue lift and 25% of the expected cost savings from their digital and AI transformations - a significant gap between expected and realized value. Source: McKinsey & Company (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) →
- Only 16% of respondents said their organizations' digital transformations had successfully improved performance and equipped them to sustain gains over the long term; even in digitally savvy industries such as high tech, media, and telecom, self-reported success rates did not exceed 26%. Source: McKinsey & Company (2018) →
- Per the Standish Group CHAOS 2020 report (reviewed at this URL), across tens of thousands of software projects roughly 31% end successfully, about 50% are 'challenged', and roughly 19% fail outright; small projects succeed far more often than large ones, and Agile approaches succeed at markedly higher rates than Waterfall. Source: The Standish Group (2020) →
Frequently asked questions
If we build a layer on Costpoint, how hard is it to change ERP later?
Easier than it is today, which surprises people. The layer holds its own versioned rate structure, its own project cost history and its own billing pack archive, and it reads the ledger rather than living inside it. Swap the package underneath and you rewrite one integration, not your rate logic.
The genuinely expensive part of an ERP change in this sector is the audited transaction record and the year of parallel running around it. That cost exists whether or not you built a layer, and the layer at least means your rate model and your invoice history survive the move intact.
What happens if our ERP vendor raises prices or changes its licensing model?
The subscription does not disappear, because you are keeping the ledger deliberately. What changes is that a repricing becomes a commercial negotiation rather than a forced march, since the pieces most specific to your company no longer live inside the product.
The stronger effect is on the services line. Contractors who own their rate layer stop paying for a configuration change every time a pool moves or a segment splits, and in our experience that line grows faster than the licence does.
How long until a custom rate and billing layer is actually in production?
Fourteen to 20 weeks for the layer, in our delivery experience. Timekeeping adds 6 to 10 weeks on top, because it touches every employee badge number in the company and needs a parallel run before anyone stops filling in the old sheet. The full platform phases over 9 to 18 months.
Time the cutover against your fiscal year rather than the project plan. Starting a new rate engine mid year means carrying two sets of numbers until year end, which is exactly the reconciliation exercise you paid to remove.
Is Unanet GovCon good enough, or do we need something custom?
Unanet is a real fit for mid market services contractors with a conventional fringe, overhead and G&A structure, and it is materially easier to live with than heavier alternatives. Plenty of contractors should stay on it and stop reading here.
It becomes constraining when your allocation bases are unusual, when you need parallel rate scenarios inside a bid cycle, or when a reorganisation into segments changes the pool structure. The tell is simple and it is the same tell for every package in the category: if your controller maintains the real rates in Excel and the system holds a copy, you have outgrown the configuration rather than the product.
Should we replace Deltek Costpoint with a custom system instead?
Almost never wholesale, and we say that as the firm that would be paid to do it. Costpoint models pools and contract types properly, and rebuilding a compliant general ledger risks your ability to invoice in order to save licence fees.
The productive move is to keep the ledger and build around it: scenario rate modelling, funded value visibility at the point of time entry, billing pack assembly and incurred cost schedules. Those are the places controllers currently run spreadsheets nobody has ever audited, which is where the actual exposure sits.
We are a $30M contractor with two contract types. Build or buy?
Buy for now, then measure. At that size a well configured package plus a consultant usually holds, and the build case has to be earned rather than assumed.
The two numbers to measure are billing analyst hours spent outside the system each month, and days elapsed to price a rate scenario during a bid. Sixty analyst hours a month is roughly a third of a role, and a bid scenario that takes days rather than hours is costing you work you never see. When either crosses, revisit the layer, starting with the rate engine only.
Does building custom make us more exposed at audit, or less?
Less, if the audit trail is designed in on day one. The architectural decision that matters is an append only event store rather than editable tables, so no role in the system can silently change a time or cost record. That costs nothing extra at design time and is very expensive to retrofit once an auditor has asked.
What increases exposure is the situation you are probably in already: the real rate logic sitting in a workbook that has never been audited, maintained by one person, with no version history and no way to show which rate applied to which invoice.
Should earned value management be part of the same build?
No, scope and price it on its own. A validated earned value management system carries its own criteria and its own surveillance, and folding it into an accounting programme is the fastest way we know to double a timeline.
Internal estimate at completion reporting for programme managers is a different and much cheaper thing, and it is what most contractors actually need. Decide which one a contract genuinely requires before anyone scopes it, because the two are often conflated in the same sentence.
How do I calculate the ROI on a custom ERP?
Add up three lines: hours of manual work removed at loaded labor cost, subscription licenses you cancel, and error costs like mispicks and double entry that disappear. In Digital Heroes delivery experience, mid-market ERP builds typically reach payback in 18 to 30 months, faster when they replace a per-seat platform at 30 or more users. Run the math over five years, because that is where a one-time build beats recurring licenses decisively.
Is customizing Odoo cheaper than building an ERP from scratch?
Usually yes in year one, and often no by year three if your workflows sit far from Odoo's assumptions. Odoo's published pricing starts around $25 per user per month and the Community edition is free, but heavy customization means every version upgrade can break your modules and needs paid rework. If you expect to rewrite more than about a third of the core flows, a scratch build with clean ownership tends to cost less over the life of the system.
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.
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.
Can a custom ERP meet compliance requirements like SOC 2 or GDPR?
Yes, and often more cleanly than a shared SaaS platform because you control exactly where data lives and who touches it. The build includes role-based access control, full audit logs, encryption at rest and in transit, and data residency in whatever region your regulator requires. If you need SOC 2 attestation, tell the agency before development starts, since audit logging is far cheaper to design in than to bolt on.
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.
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.
Can we keep our current ERP and just build custom modules around it?
Often yes, and it is frequently the smartest first move. Digital Heroes regularly builds custom scheduling, quoting, or warehouse tools that sit on top of SAP, NetSuite, or Odoo through their APIs, which fixes the painful 20 percent without a risky replacement. The hybrid route costs a fraction of a full rebuild and tells you within months whether a bigger migration is even necessary.
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.
Should I pick Microsoft Dynamics 365 Business Central or build a custom ERP?
Pick Business Central if you already live in the Microsoft stack, your processes are close to standard, and around $80 per user per month for Business Central Essentials stays affordable at your headcount. Build custom when your revenue-driving workflow, such as custom manufacturing steps or unusual pricing logic, would need heavy extension work anyway. In our experience, once Dynamics customization quotes pass about $100,000 the custom option deserves a serious side-by-side.
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 we migrate years of data from our old system without losing anything?
Through a staged migration with a parallel run, never a single cutover weekend. The data gets extracted and cleaned early, loaded into the new ERP while the old system stays live, and both run side by side for two to four weeks so your team can verify counts, balances, and open orders match. In Digital Heroes ERP projects, data cleaning consistently takes longer than the technical transfer, so it starts in week one, not at the end.
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 Zayn.
Director of Strategy · UK · London · 2 posts on the site
Published · Last updated .
