Engineering Firm Software: Build Custom or Buy Deltek Vantagepoint, BQE Core and Unanet?
Two tests decide it. Below roughly $8M in annual fees, single discipline, mostly hourly work against a repeatable deliverable set, buy BQE Core and put the money into business development.
On this page
Two tests decide it. Below roughly $8M in annual fees, single discipline, mostly hourly work against a repeatable deliverable set, buy BQE Core and put the money into business development. Above that, the sharper test is whether you can name the annual figure you lose to jobs discovered late, meaning overruns found at the ninety percent review rather than at forty. If that number is above roughly $300,000, a $60,000 to $130,000 first release pays back inside eighteen months on that alone. If you cannot name it, that is the finding, and it is why the tool you already bought is not helping.
When is off the shelf genuinely the right call here?
Buy if you are single discipline, under roughly $8M in fees, and your work is mostly hourly against a repeatable deliverable set. A build at that size is capital diverted from the thing that actually grows the firm.
The products worth naming, and who should be buying them:
- BQE Core. The right answer for a small to mid sized single discipline practice. It handles time, billing and project financials well, and it will run that firm properly without anyone writing code.
- Deltek Vantagepoint and Ajera. Genuinely good at financial reporting and at carrying your compliance surface. Keep whichever you run as the financial system of record no matter what else you decide. Rebuilding accounting puts billing at risk to solve a problem that lives in resource planning.
- Unanet. Same category, particularly common where government contracting requirements shape the timekeeping. The same advice applies: keep it.
- Procore and Newforma. Right for the construction facing side, requests for information and submittals, and for project correspondence in a design practice. Neither is a design production system and neither claims to be.
- SharePoint, Newforma or Bluebeam for files and markups. Keep them authoritative for documents. A deliverable register should reference files, not store them.
There is one more case where buying, or rather fixing, beats building outright. If your real problem is that nobody files timesheets by Monday, software will not solve it. That is a management problem, and a custom system simply gives it a nicer dashboard.
When does a custom build actually pay off?
Four signals, and they usually turn up together.
You run three or more disciplines and your schedule slips at the coordination between them rather than within them. Structural cannot size roof framing until mechanical issues equipment loads. Nobody owns that dependency, so it becomes an email thread with eight people on it and three quiet weeks disappear.
Somebody in your firm maintains a spreadsheet the business genuinely depends on. It is usually called something ending in v14 final, one person understands it, and that person is a single point of failure. Price the week you would lose if they left tomorrow.
You grew by acquisition and firm wide reporting requires a translation layer. The acquired office numbers projects differently, their phase codes do not map to yours, and the finance director's backlog report needs a manual mapping tab. Multi office firms all have this and all pretend they do not.
You can name the annual figure lost to jobs discovered late and it is material. This is the one that ends the conversation. Measure it for one quarter before deciding anything.
How do they compare on the things that matter in this industry?
Forward capacity against backward utilisation. Accounting systems compute utilisation from posted timesheets, and timesheets post late, so on Wednesday you are looking at last week and last week has already been paid for. The deeper limit is the data model: a person is a labour rate on a cost line, not a capacity with a forward commitment curve. The resource module then asks a busy project manager to type planned hours per person per week, which means the plan is only as current as the last time somebody updated it. Configuration does not change that model.
Evidence behind percent complete. Microsoft Project and Smartsheet accept whatever number you type. There is no evidence layer and nothing connects the figure in the schedule to the state of the sheets in the drawing set. A computed rollup from sheet states and review sign offs, weighted by budgeted hours per sheet, with any override logged and displayed beside the computed value, is a different instrument entirely.
Information dependency against task dependency. A Gantt chart expresses that task B follows task A. Engineering work is gated by data handoffs between disciplines, which no general project tool has a concept for, so firms carry those dependencies in a discipline lead's head.
Reporting across inconsistent conventions. A packaged system gives you one work breakdown structure, and making five offices conform is the migration that keeps getting deferred because it means telling an acquired team that fifteen years of history is wrong. A canonical project spine with per office aliases underneath lets reporting query one layer while users keep their own numbering.
Contract type variety. Lump sum, time and materials, and cost plus fixed fee each compute earned value differently. A firm running all three across several offices is running three models rather than one model with options.
What does total cost of ownership look like at your scale?
A first release covering the forward capacity forecast by discipline and grade, the deliverable register with computed percent complete, and a read integration into your accounting system runs $60,000 to $130,000 over 12 to 16 weeks. A full platform adding interdiscipline handoffs, document extraction on inbound client material, review workflow, a client portal and write back runs $150,000 to $400,000 phased over 6 to 12 months. The deliverable register on its own runs $30,000 to $55,000 over six to eight weeks.
A 150 person firm running four disciplines across three offices, two of which arrived through acquisition with their own numbering, keeping the accounting system with a read only integration, totals about $129,000, at the top of the first release band. Four disciplines and the multi office alias mapping are what put it there. A single office firm with two disciplines lands nearer $75,000. Adding document extraction, review workflow, a client portal and write back takes that same firm to roughly $270,000 to $340,000 across the following year.
Two line items deserve naming. Write back to the accounting system adds roughly $40,000 and six weeks, almost all of it in reconciliation logic for retroactive timesheet edits, because a forecast that already consumed last week's hours has to cope when somebody amends them on Thursday. Interdiscipline handoffs are $19,000 to $35,000 and are usually the highest return feature in the build, because nothing you can buy has a concept for them.
Running cost is unusually light here. Storage is roughly $100 to $300 a month, because the register references documents rather than storing them, which is a good reason to keep it that way. Support and enhancement runs 12 to 18 percent of build cost annually, weighted towards enhancement while additional disciplines and offices are folded in. The standing effort that actually matters is deliverable template maintenance, because if nobody owns it the register drifts and project managers go back to typing percentages.
You are almost certainly keeping your accounting platform, so the renewal is not the comparison. Put three of your own numbers against the build instead: the annual loss to jobs discovered late, the cost of the Monday resource meeting with six principals arguing about an export that was stale when it printed, and the risk carried in that one spreadsheet.
What does the hybrid look like, and when is it the honest answer?
For engineering firms the hybrid is not a compromise, it is the correct architecture, and it is also the cheapest. The accounting system stays authoritative for time and money. Your document management stays authoritative for files. A custom layer above them handles forecasting, deliverables and coordination, reading hours nightly through the interface and never claiming to be the system of record.
Three decisions keep that layer small. Start read only and earn the right to write later, because several firms that shipped the forecast first concluded they never needed write back at all. Model two disciplines first, ideally the two whose coordination causes the most slippage, since the handoff object generalises to the third and fourth cheaply. And skip computer aided design integration in phase one: pulling live sheet state out of Revit or Civil 3D means dealing with model files rather than a clean interface, and a sheet state maintained by a project coordinator is accurate enough to compute percent complete for a fraction of the cost.
The hybrid is especially right if you bill federal, transport authority or defence work. Leaving the audited record in the accounting system and keeping the custom layer read only means your compliance surface stays exactly where it already is. Retrofitting immutable edit history, documented approval chains and segregation of duties into a system that was not designed for them is close to a rewrite, and we have watched a firm pay for that twice.
The narrowest hybrid of all is worth naming for firms that are not ready. Build only the deliverable register. What it produces is the gap between the typed percent complete and the computed one, and a fifteen point gap on a job is a scope conversation waiting to happen. In the firms where we have shipped it, that single figure becomes the most looked at number in the Monday meeting.
Which should you choose, by operator size and stage?
Single discipline, under roughly $8M in fees, hourly work. Buy BQE Core. Nothing here applies to you yet, and revisit when a second discipline starts gating the first.
Two disciplines, one office, growing. Keep your accounting platform and build the deliverable register alone at $30,000 to $55,000. It is the cheapest way to find out whether your percent complete is fiction, and the answer usually funds the next phase.
Three or four disciplines, one or two offices. The first release at $60,000 to $130,000, read only, with interdiscipline handoffs included because that is where your schedule actually slips. Roll out to two disciplines before the rest.
Multi office firm grown by acquisition. The same first release with the canonical project spine as a named line rather than an assumption. Budget three to five weeks for migrating active projects and two to three years of closed history, running in parallel rather than blocking, and keep the old reporting alive until the new layer has reconciled for a full billing cycle.
Federal, transport authority or defence work at any size. Keep the audited record where it is and keep the custom layer read only. Scope the compliance question in writing before the estimate, not after.
Before signing anything, ask a developer to model your domain on a whiteboard. One who has built this asks unprompted whether your phases are fee bearing and whether percent complete rolls up from sheets or from hours. One who has not draws a task list with a status field, and that difference is worth more than any portfolio.
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. 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.
- In the Flexera 2025 State of ITAM report, respondents reported roughly 33% of SaaS spend is wasted, underscoring how paying for off-the-shelf seats and tiers that go unused erodes the supposed cost advantage of generic SaaS. Source: Flexera (2025) →
- Median SaaS spend reached $9,455 per employee, and organizations leave an average of 36% of their SaaS licenses unused. Source: Zylo (2026) →
- OECD research finds that digitalisation offers SMEs opportunities to improve performance, spur innovation, enhance productivity and compete more evenly with larger firms; it reports that increased use of online platforms produced significant multi-factor productivity gains in SME-heavy sectors such as hospitality and retail, while smaller firms lag in adoption due to skills, resource and financing gaps. Source: OECD (2021) →
- One in four US employees report lacking career advancement opportunities; 48% of employees who participated in mentorship programs report high job satisfaction versus 29% of non-participants, and access to advancement opportunities ranges from 33% at organizations under 10 employees to 74% at those with 1,000+. Source: Gallup (2025) →
Frequently asked questions
What does it cost to move off Deltek or Unanet later?
Do not plan to. The accounting system is the piece worth keeping in almost every case, and rebuilding it puts billing and compliance at risk to solve a problem that lives in resource planning.
What building the operational layer does change is your position if you ever do switch. Once the canonical project spine, the deliverable register and the forecast live in your own system, a platform change becomes a read integration rewrite of roughly $18,000 rather than a re implementation of how your firm plans work.
What if our accounting vendor changes seat pricing or licensing tiers?
Model it at full headcount including the people who only need to see a forecast, because that is where seat based pricing bites in this category. Firms often discover they are paying for licences so that discipline leads can look at a dashboard.
A custom layer changes that shape specifically. Read only viewers live in your own system at no per seat cost, while the accounting platform keeps only the users who genuinely touch time and money. That alone closes part of the gap on a build for larger firms.
How long does it take, and how long does migration take?
Twelve to sixteen weeks for a first release. Migration of active projects plus two to three years of closed job history typically takes three to five weeks and runs in parallel rather than blocking the build.
The work is not moving data, it is mapping inconsistent project numbering and phase codes across offices, which is why the right design is a canonical spine with per office aliases rather than making anyone renumber. Keep the old reporting running until the new layer has reconciled for a full billing cycle.
Is BQE Core enough for a two discipline firm?
Often yes, and it is a genuine recommendation rather than a hedge. For hourly work against a repeatable deliverable set it handles time, billing and project financials well, and the money you would spend building belongs elsewhere.
Where any of these platforms strains is forward planning, because their model of a person is a labour rate on a cost line rather than a capacity with a forward commitment curve. If your slippage comes from coordination between two disciplines rather than from billing, that is when the deliverable register and handoff layer start earning their cost.
Why does write back to the accounting system add so much?
Retroactive timesheet edits. A forecast that has already consumed last week's hours has to reconcile when somebody amends those hours on Thursday, and every firm has amendments. In our delivery experience write back adds roughly $40,000 and six weeks over a read only integration.
Start read only, prove the forecast against a quarter of real staffing decisions, then decide. Several firms conclude they never needed it, and ask any developer what they do about retroactive edits before you hire them, because naive integrations break on exactly that.
Can we build just the deliverable register first?
Yes, and it is the cheapest way to prove the case at $30,000 to $55,000 over six to eight weeks. It covers a drawing register with sheets, disciplines, milestone levels and review states, with percent complete computed and weighted by budgeted hours per sheet.
What it produces is the gap between the typed number and the computed number. That gap is where the scope conversations hide, and it usually pays for the next phase without any further business case.
Does federal or transport authority work change the decision?
It pushes you towards the hybrid rather than away from building. Timekeeping controls, immutable edit history, documented approval chains and segregation of duties turn a simple timesheet view into a controlled record, and that is a design decision rather than a feature.
The cheaper route is to leave the audited record in your accounting system and keep the custom layer read only, so your compliance surface stays where it already is. Scope this explicitly in writing before the estimate, because retrofitting an audit trail into a system not designed for one is close to a rewrite.
How do we know the build will actually pay back?
Measure one number for a quarter: the fees lost to jobs discovered late, meaning overruns found at the ninety percent review rather than at forty. Above roughly $300,000 a year, a first release pays back inside eighteen months on that alone, before counting recovered principal time in resource meetings.
If you cannot produce that number, do not build yet. Not being able to measure your own leakage is itself the finding, and it usually means the first thing to fix is the deliverable register rather than the whole platform.
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.
We've outgrown ClickUp. Does that mean we need custom software?
Not automatically. First check whether ClickUp's Business tier at about $12 per user per month plus its API covers the gap, because most complaints about outgrowing ClickUp are really automation limits, not data model limits. The genuine signal for custom is structural: your work does not fit the task-in-a-list model, for example a job that must sit under two clients with separate billing at the same time. If you are paying someone monthly just to maintain workarounds, it is time to price a build.
How big a team does it take to build a project management platform?
A typical Digital Heroes pod is 4 to 5 people: a product designer, two or three engineers, and a shared project manager and QA. Smaller than that and timelines stretch because one person is context-switching across design, backend, and testing; bigger only helps after the MVP, when work splits into parallel streams. Headcount matters less than whether the same pod stays on your project from discovery to launch.
Can we migrate years of data out of our current system into new custom software?
Almost always yes, through CSV exports or the vendor's API, and migration should be scoped as its own workstream with field mapping, a dry run, and a planned cutover window rather than an afterthought. The real time sink is rarely moving the data; it is cleaning it, since years of duplicates, free-text fields, and inconsistent formats surface all at once. Pull a full export from your current vendor before committing to anything new, because some SaaS plans restrict exports on lower tiers.
How much does it cost to build a custom project management tool for my company?
A focused build that replaces one painful workflow runs $60,000 to $90,000, and a full platform with portfolio views, client access, and integrations runs $120,000 to $200,000 or more. Those are Digital Heroes delivery bands across 2,000+ projects, not list prices. Add 15 to 20 percent of the build cost per year for hosting, maintenance, and integration upkeep.
What happens to my software if the agency shuts down or we stop working together?
Nothing dramatic, if the engagement was set up correctly: the code sits in your repository, hosting runs on your cloud account, and a handover document explains how to deploy and operate the system. Any competent replacement team can then take over in days rather than months. If the agency controls the repo, the servers, or the domain, fix that now, because renegotiating access during a dispute is the most expensive place to discover the problem.
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 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 should I have ready before I contact a development agency?
Four things: an export from your current tool, a list of the specific workflows it fails at, screenshots of the spreadsheets you use as workarounds, and your integration list with a budget range. Buyers who arrive with those cut discovery from two or three weeks to days, and that time comes straight off the invoice. You do not need a formal spec document; a good agency writes that with you.
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.
Who can build a custom project management software system?
Digital Heroes builds custom project management 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 project management 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 Layla.
Senior Account Manager · Wellness · Sydney · 1 post on the site
Published · Last updated .
