Engineering Document Control Software: Build Custom or Buy Aconex, ProjectWise, Meridian and Newforma?
The dividing line is one project against a programme. If you run one capital project at a time with a stable delivery model and no strong internal document standard, buy, and configure Aconex or ProjectWise properly.
On this page
The dividing line is one project against a programme. If you run one capital project at a time with a stable delivery model and no strong internal document standard, buy, and configure Aconex or ProjectWise properly. The build case belongs almost entirely to owners running a programme of projects where every new one means reconfiguring a packaged system to a different standard again, and where handover reconciliation against the asset tag register is still done by hand. A first release runs $70,000 to $160,000 in 14 to 18 weeks, with a full platform at $200,000 to $500,000 across 8 to 14 months.
When is off the shelf genuinely the right call here?
Buy if you are running one project at a time with a stable delivery model and an owner who has no strong document standard of their own. These are mature products with real deployment expertise available in the market, and a competent configuration by an experienced document control lead will serve you well.
The products worth naming, and who should be buying them:
- Oracle Aconex. Strong on transmittals, correspondence and the audit trail across parties, which is exactly the problem most single projects actually have. If your pain is proving what was sent and received, this is squarely what it does and rebuilding it is poor value.
- Bentley ProjectWise. The natural home when the engineering authoring environment is the centre of gravity and design files need managed access and referencing.
- Accruent Meridian. Common on the contractor and operating plant side, and a reasonable choice where the document set outlives a single project inside one organisation.
- Newforma. Good at correspondence and project information exchange for design practices, and light enough to actually get adopted.
There is a second buy rule that removes the decision entirely. If you are the engineer or the contractor on someone else's project and the owner has already mandated a system, your job is to work inside it rather than beside it. Building a parallel system on a mandated project produces two registers, and two registers is the failure this whole category exists to prevent.
When does a custom build actually pay off?
Five signals, and two or more should be true before you commit.
You are an owner running a programme and every project reconfigures a packaged system to your standard again. That configuration cost recurs, project after project, and it is the clearest recurring number in the comparison.
Handover register reconciliation consumes months. Six weeks before handover somebody opens the register and finds vendor documents that were never received, documents whose numbers map to no tag, and drawings marked as built that were never updated after the last field change. Then the team does archaeology while a payment milestone sits waiting.
Vendor document expediting is done in a spreadsheet by one person. Vendor documents are usually the largest single gap at handover, because the vendor has been paid and has lost interest.
You have paid for rework caused by construction from a superseded revision and could not quickly prove who held what. The argument about who pays is settled by whoever can produce an acknowledgement record.
Your numbering must map into an existing asset management structure the packaged tool cannot represent without compromise. That compromise becomes a workaround, the workaround becomes a spreadsheet, and the spreadsheet is what fails at handover.
How do they compare on the things that matter in this industry?
Whose numbering wins. The owner has a corporate standard baked into their asset management system. The engineer has a project scheme from their own procedures. Each equipment vendor numbers to their factory standard and will not change for your order. The same heat exchanger data sheet exists under four numbers. Packaged systems impose a metadata model, which is a legitimate product decision, and it means fitting your project into their structure. A build can treat identity as a set of aliases against one internal record so any of the four numbers resolves in search.
Status as one field or three dimensions. Revision, issue purpose and review status are separate. A document can be at revision D, issued for construction, with an outstanding comment from one reviewer and a client hold that blocks it regardless. The site needs one derived answer: in this area, what may I build from today.
Reconstructing the past. The question a dispute turns on is what the set of current revisions was on a date eight months ago. That requires append only history rather than a mutable status field, plus an acknowledgement record per recipient. Ask any vendor or developer to produce it before you commit.
Comment consolidation. Aconex and Newforma both handle transmittals and correspondence well. Where teams still fall back to spreadsheets is merging comment sets from marked up files, emails and comment sheets, detecting reviewers who contradict each other on the same location, and closing each comment individually against a reissue.
Authority across organisational boundaries. This is the structural point rather than a feature gap. Every packaged system is built to be authoritative inside one organisation, while document control on a capital project is a reconciliation problem between several organisations that each have valid conventions. A product requiring everyone to adopt one convention gets worked around by whichever party has the most commercial reach.
What does total cost of ownership look like at your scale?
A first release covering the document register with alias based identity, the numbering and revision engine, transmittals with acknowledgement tracking, distribution matrices and the vendor document requirement register runs $70,000 to $160,000 over 14 to 18 weeks. A full platform adding multi party review rounds with comment consolidation and disposition, hold point management, tag register reconciliation, handover completeness reporting and offline site access runs $200,000 to $500,000 phased across 8 to 14 months.
Know the floor and the ceiling. Under $70,000 you get a file share with metadata, which will store documents and will not tell you whether the latest issued revision is acknowledged in the hands of the party building from it. Above $500,000 you are taking on engineering data management rather than document control, and that belongs in its own business case with its own owner.
An owner starting on one project with an engineer, four principal contractors and roughly sixty equipment vendors, with tag register integration deferred, totals about $122,000 and ships in around sixteen weeks. Phase two adding review rounds, hold points, tag reconciliation, handover dashboards and offline access is another $150,000 to $280,000, bringing the programme to roughly $320,000 across the year. Tag register integration alone is commonly $50,000 to $110,000 depending on which system holds the tag structure and how clean it is. The review and comment module is $45,000 to $90,000.
Running cost is 15 to 25 percent of build value a year, roughly $18,000 to $31,000 on that release, plus two obligations that sit outside it. Long term retention, because the record must stay producible for years after handover and sometimes decades. And per project configuration, which should be document control lead time rather than developer time if the numbering engine was built properly. Add ongoing external party onboarding, since every new contractor and vendor needs accounts, training and a distribution matrix entry.
The buy side comparison needs four of your own figures: per project fees plus the configuration days a partner charges to set up each new owner standard, document control staff time spent maintaining cross reference spreadsheets, the cost of your last handover reconciliation, and any rework you have paid for after construction from a superseded revision. The last two usually carry it.
What does the hybrid look like, and when is it the honest answer?
The sharpest version of this is also the cheapest. Keep the mandated or incumbent platform for transmittals, correspondence and the audit trail, which is what it is genuinely good at. Build only the vendor document requirement register: generated per purchase order at award, with due dates relative to order placement or delivery, an overdue report by supplier, and the retention or milestone payment that is conditional on submission attached to it. Link that register to the tag structure so completeness shows per system months before handover rather than weeks.
That slice runs roughly $60,000 to $95,000 including the purchase order feed from your enterprise resource planning (ERP) system that makes the register generate itself, and it targets the largest gap at handover without disturbing anything the project teams already use. Owners fund these builds for this feature more often than for any other, because it converts a contractual right into an operational one.
Two more reductions belong in any hybrid. Take review comments as structured records without building automated extraction in release one, since consolidation is where the value is and extraction only reduces typing. And leave legacy projects where they are: keeping the historical archive searchable in place while running new projects on the new system is a better use of the first year than title block extraction across a scanned drawing library.
The hybrid fails in one place. If the incumbent cannot export an acknowledgement record per recipient, your completeness layer has nothing solid underneath it, and you are inferring receipt rather than proving it. Test that export before you design around it.
Which should you choose, by operator size and stage?
One project, one engineer, a couple of contractors. Configure Aconex or ProjectWise and spend the saved money on an experienced document control lead. That person is worth more than any software difference at this scale.
An engineer or contractor on an owner mandated system. Work inside it. Do not build a parallel register under any circumstances.
An owner on the first project of a programme, where vendor documents are the pain. The $60,000 to $95,000 vendor requirement slice beside the incumbent. It starts producing value at purchase order award, months before review workflow matters.
An owner running a programme across several standards. The first release at $70,000 to $160,000, launched live on one real project rather than validated in workshops. Then treat the second project, with a different owner standard, as the actual proof. Two projects is honest evidence that the numbering engine is configurable by a document control lead. One project is a demonstration.
An owner facing structured handover deliverables and tag reconciliation. The full platform across 8 to 14 months, sequenced by the pain. If handover reconciliation is the problem, build tag integration next. If review turnaround is the problem, build comment consolidation next.
Spend three to four weeks of discovery on numbering and status before anything else. Get the alias model or the three status dimensions wrong and you rebuild the schema in month four, which here also means reissuing a register people had started to trust.
If you would rather someone argued with your brief than agreed with it, 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 keep the specification either way.
The evidence behind this guide
Independent findings on why this investment pays off. Every link goes to the primary source.
- Companies in the top quartile of McKinsey's Developer Velocity Index had 2014-18 revenue growth four to five times faster than bottom-quartile peers, showing that software-building capability is a driver of business performance, not just a support function. Source: McKinsey & Company (2020) →
- An independent Forrester Total Economic Impact study of OutSystems found a 363% three-year ROI with payback in under 6 months, illustrating that faster, lower-labor build approaches can materially shift the payback math. Source: Forrester Consulting (commissioned by OutSystems) (2024) →
- The EY survey of 508 payroll professionals at U.S. companies with 250-10,000 employees quantifies the direct and indirect cost of payroll inaccuracy, reinforcing the ROI case for payroll automation; the study is the original source of the frequently cited $291-per-error figure. Source: BusinessWire / EY (Ernst & Young) (2022) →
- IBM frames first-time fix rate as a core field service KPI, noting the industry average sits around 80% (roughly one in five jobs needs a return visit). Correction: IBM cites best-in-class providers at 89-98%, not '85%+'. Source: IBM (2024) →
Frequently asked questions
What does it cost to move a live project off Aconex or ProjectWise?
Do not, if the project is live and the owner mandated the system. Mid project migration produces two registers during the overlap, and two registers is the exact failure that causes construction from a superseded revision.
Move at a project boundary instead. What you migrate is the numbering scheme, distribution matrices and requirement templates, not the historical correspondence. Closed projects should stay searchable in place for the retention period, because the record has to remain producible for years and forcing it into a new model adds risk without adding value.
What if per project or per user fees change across our programme?
Model configuration days alongside the fees, because in this category the recurring cost that surprises owners is not the licence, it is the partner engagement to set up each new project against a different owner standard. That happens every project, and it is the number to ask for in writing.
The other line to isolate is external party onboarding. Every new contractor and vendor needs accounts and a distribution matrix entry, and how that is priced on a programme with sixty vendors matters more than a headline rate.
How long does a build take, and when do we know it is configurable?
Three to four weeks of discovery on numbering and status, then 14 to 18 weeks to a release that goes live on a real project rather than being validated in a meeting room. The compromise that breaks a numbering engine is one nobody thinks to mention until a real vendor document arrives with a number that does not fit.
The milestone that answers the question is the second project with a different owner standard, configured by your document control lead without a development ticket. Plan the first two projects as one programme.
Is ProjectWise enough if we are the engineer rather than the owner?
Usually yes, and often it is the only sensible answer. ProjectWise sits close to the authoring environment and handles managed access and file referencing well, which is the engineer's actual problem. If the owner has mandated something else, use theirs.
Where an engineering practice does build is on the comment consolidation side, because merging markup, emails and comment sheets into one review round with contradictions surfaced before response drafting is the step teams still do in spreadsheets. That is a $45,000 to $90,000 module, not a platform replacement.
Can we start with just transmittals and vendor document tracking?
Yes, and it is the cut we recommend most often. Vendor documents are the largest gap at handover, and the requirement register starts producing value at purchase order award rather than at review time.
That slice is roughly $60,000 to $95,000 including the purchase order feed that makes the register generate itself. It also delivers the acknowledgement trail that settles a superseded revision dispute, which is the other expensive failure in this category.
Why does tag register integration cost so much?
Because the reconciliation logic is where the value is and the mapping is rarely one to one. Documents cover multiple tags, tags carry documents from several vendors, and the exceptions are exactly the cases that matter at handover.
Budget $50,000 to $110,000 as a phase rather than a line, depending on which system holds the tag structure and how clean it is. Deferring it from release one keeps you in the lower cost band while still fixing transmittals and vendor expediting.
What does migrating legacy scanned drawings cost?
Treat it as a separate workstream with its own budget, because rebuilding a register from scans means title block extraction with a review queue for anything ambiguous, and volumes in this category are large.
Most owners get better value keeping the historical archive searchable in place and running new projects on the new system. If you must migrate, do it after the first project is live so the target model is already proven against real documents.
Who owns the code and the project record?
You should own the repository, the cloud infrastructure accounts and the unrestricted right to bring in another firm, agreed in the contract before kickoff.
This matters more here than in most categories because a document control system outlives the project it was built for. The record it holds is the evidence base for disputes years after handover, and it should not sit inside an account you cannot open or a licence you have to keep renewing to read your own history.
Can a custom internal tool connect to QuickBooks, Salesforce, and the other software we already use?
Yes, and integrations are usually the strongest argument for going custom instead of chaining tools together with Zapier. QuickBooks, Salesforce, Shopify, Stripe, Slack, and Google Workspace all have mature APIs, and each integration typically adds $1,500 to $5,000 to a Digital Heroes build depending on how much two-way syncing you need. The honest caveat is legacy industry software without an API, which may need file-based imports instead of a live connection, so list every system in the first conversation.
What tech stack should an internal tool be built with?
Boring and popular: a React or Next.js frontend, a Node.js or Python backend, and PostgreSQL covers the vast majority of internal tools and keeps future hiring easy. The stack matters far less than whether a different developer can pick the code up in two years, so require documentation as a deliverable and avoid anything exotic. Treat it as a red flag if an agency pushes a proprietary platform only they maintain, because that quietly converts your tool into a subscription to that agency.
Should we build our internal tool in Retool instead of hiring developers?
Retool is the right choice if someone on your team is comfortable with SQL and JavaScript and the audience is a handful of technical users, because a basic CRUD dashboard comes together in days. Hire developers when non-technical staff will use the tool daily, when the logic goes beyond forms sitting on a database, or when per-seat pricing stings, since Retool's Business tier lists at $50 per standard user per month. A pattern Digital Heroes sees often: companies arrive after a year on Retool with a tool nobody can maintain because the one person who built it has left.
How many people should be working on my software project?
Three to five for a typical focused build: a project lead, one or two engineers, a designer, and part-time QA, which is the standard shape across 2,000+ Digital Heroes projects. Larger platforms justify 6 to 10, but a ten-person team on a small first version usually signals bill padding rather than horsepower. What predicts success is whether a senior engineer is writing your code daily, not the headcount on the proposal.
Who owns the code when an agency builds my software?
You should, completely, through a written intellectual property assignment that transfers everything on final payment; without that clause, copyright stays with whoever wrote the code by default. Insist that the repository lives in your own GitHub organization from day one and that hosting, domains, and third-party accounts are registered to you. Also check for licenses to the agency's proprietary frameworks buried in the contract, because those can make switching vendors practically impossible even when you own your own code.
What does it cost to keep an internal tool running after launch, and do we need to hire a developer?
Budget 15 to 20 percent of the build cost per year, so a $25,000 tool runs roughly $300 to $400 a month covering hosting, security patches, dependency updates, and small tweaks, figures drawn from Digital Heroes maintenance contracts. You do not need an in-house developer; a monthly retainer with the agency that built it covers the typical internal tool comfortably. Hosting itself is cheap for internal audiences, often $20 to $100 a month, because you serve dozens of users rather than the open internet.
How many developers does it take to build an internal tool?
Two to four people covers nearly every internal tool: one or two developers, a part-time designer, and a project manager who doubles as your single point of contact. Internal tools rarely need consumer-product polish, so a full-time dedicated designer is usually wasted budget. On Digital Heroes projects, a two-person core team handles the typical 4 to 8 week build, with a specialist pulled in briefly for a tricky integration or a security review.
Can we start on Airtable or Retool now and move to custom software later?
Yes, and it is often the smartest sequence: run the workflow on Airtable or Retool for 6 to 12 months to learn what you actually need, then go custom once the process stabilizes. The no-code version becomes free requirements documentation, and its data exports cleanly into a custom database. The one risk is waiting too long, because teams stack automations and workarounds until migration becomes a project of its own, so set a concrete trigger in advance, such as hitting Airtable's 50,000-record Team plan cap.
Will a custom internal tool scale as our company grows?
Yes, provided it sits on a standard stack with a real database: PostgreSQL comfortably handles millions of records, and adding users costs hosting pennies rather than per-seat fees. The real scaling risks are organizational, not technical: new departments want features, processes change, and the tool needs a budget line to evolve. Set aside a small quarterly improvement budget instead of treating launch as the finish line, and the tool stays useful for a decade rather than getting rebuilt every two years.
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.
Should we build the whole internal tool at once or start with an MVP?
Start with a version that fully replaces one workflow, ship it in 4 to 6 weeks, and let real usage set the roadmap. Internal tools have a captive audience, so you learn within days which features matter, and across Digital Heroes projects roughly a third of initially requested features never get built once staff work with version one. Phasing also spreads the spend: a $40,000 vision becomes a $15,000 phase one that starts paying for itself while phase two is scoped.
Who can build a custom internal tools system?
Digital Heroes builds custom internal tools 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 internal tools 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
Published · Last updated .
