How Much Does Turnaround Management Software Cost in 2026?
Turnaround and shutdown management software runs $80,000 to $550,000, and the line that moves the estimate most is how deep you go with Primavera P6. Reading an exchange file once a day is straightforward and cheap.
On this page
Turnaround and shutdown management software runs $80,000 to $550,000, and the line that moves the estimate most is how deep you go with Primavera P6. Reading an exchange file once a day is straightforward and cheap. Maintaining a live two directional relationship with a schedule that a scheduler is actively editing, with a defined conflict rule, is a different order of work and it is where these integrations fail when underpriced. Decide that depth before anyone quotes. A first release covering the scope register, work pack readiness and daily field progress is $80,000 to $170,000 over 14 to 20 weeks in our delivery experience.
The bands a turnaround build falls into
The first release band is $80,000 to $170,000 over 14 to 20 weeks. That covers a single scope register with a challenge state machine and duplicate detection, work pack readiness computed from prerequisite records rather than claimed on a spreadsheet, daily field progress captured offline against rules of credit, and one forecast derived from those inputs rather than typed.
The full platform band is $220,000 to $550,000 across 8 to 14 months. That adds cost integration, contractor productivity with labour, equipment and materials reconciliation, materials and tooling readiness, permit and isolation linkage, a scenario planner and post event benchmarking that lets the next turnaround start from your own actual productivity rather than an estimator's memory.
There is a narrower start some sites take before a major event. The scope register with challenge workflow alone, with no field capture and no schedule integration, runs $30,000 to $52,000 over six to eight weeks. It does nothing during execution. It does mean the worklist that goes into the event is one durable register with a named acceptor per item, which is the difference between explaining scope growth and arguing about it.
What drives a turnaround build up
Primavera P6 integration depth is the first driver. Reading an exchange file gives you a snapshot. A live map between scope item, work order and schedule activity that survives a scheduler editing the file is a considerably larger piece of work, and the conflict rule has to be agreed with the scheduler rather than assumed. Ask any prospective developer how they handle a schedule that is open in front of someone, because a vague answer here becomes your worst week.
Maintenance system integration is the second. SAP work order and project system integration is its own workstream with its own transports and its own approval path, and it rarely moves at the pace of the rest of the build.
Contractor timesheet reconciliation is the third. Every contract has different rates, shift premiums, travel rules and minimum call outs, and each is real configuration work rather than a rate field.
Offline mobile capture is the fourth. It roughly doubles the testing burden on the field application, and it is not optional. A system that needs connectivity inside a vessel or under a pipe rack will not be used, and you will end up back on marked up sheets with a more expensive system running in the background.
Site count is the fifth, because multiple sites means reconciling naming, disciplines and rules of credit across organisations that have each done things their own way.
What keeps the number down
Run the first version on a single unit or a single small shutdown, with two contractors rather than fifteen. The model is the same at any scale and the rules extraction is far cheaper when the room contains two contract managers instead of a dozen.
Do not replace P6. It is the right scheduling engine and reproducing it is a poor use of capital. The custom layer owns the scope register, readiness and field data, and maps to the schedule rather than becoming it.
Agree rules of credit before the build, not during it. This is a workshop with your superintendents and contractors, and it is the single most valuable non technical input to the project. Turning percent complete into verifiable steps costs nothing in software and everything in agreement.
Keep artificial intelligence in one narrow place. Reading inspection write ups and free text notifications to classify work type and surface historic similar jobs is genuinely useful and can take a day out of the found to working path. Automated rescheduling is not, and a resequence nobody trusts is how you lose every superintendent on site.
Finally, go live at least one full event cycle before the turnaround that matters. Going live during a major event is the most common way these projects fail, because the people who would normally absorb teething problems are the busiest on site.
A worked example that adds up
A single site running a refinery turnaround of roughly fifty thousand contractor hours, two main contractors, an existing P6 schedule maintained by an in house scheduler, work orders in SAP.
- Scope register with challenge state machine, duplicate detection on equipment tag and work description, named acceptor and deferral target per item: $30,000
- P6 mapping between scope item, work order and schedule activity, read plus controlled write back with an agreed conflict rule: $28,000
- Work pack readiness as a computed state over prerequisite records for permit, isolation, scaffold, material, tooling and procedure, with a rolling 48 hour look ahead of unready jobs sorted by float: $26,000
- Offline mobile field progress capture against agreed rules of credit, recording crew size and hours alongside earned steps: $34,000
- Forecast at completion computed from earned hours, actual hours and contract rates: $18,000
- Discovery on site, rules of credit workshops, testing and a pilot on a small shutdown: $22,000
Total $158,000 over 18 weeks. Adding contractor productivity with labour, equipment and materials reconciliation typically adds $45,000 to $80,000, most of it in contract specific rate rules. Adding materials and tooling readiness with warehouse integration adds $35,000 to $70,000.
How the spend phases
Weeks one to four are discovery on site, and they have to be on site. The objects in this domain, scope item, work order, schedule activity, work pack and readiness prerequisite, are five different things with five different lifecycles, and a developer who has not stood in a turnaround control room will collapse them into tasks and subtasks. Roughly fourteen percent of the budget goes here and it is not negotiable.
Weeks three to nine build the scope register and the P6 mapping. Do the mapping early rather than late, because it is the item most likely to reveal that your work order numbering and your schedule activity coding do not relate to each other as cleanly as everyone assumed.
Weeks seven to fifteen deliver readiness and field capture. Field capture is the largest single line and it is the one that has to be tested in the environment it will be used in. Test it under a pipe rack, not in an office.
Weeks fourteen to twenty cover the forecast and a pilot on a small shutdown. That pilot is the reason the go live date should sit a full event cycle before the turnaround that matters, and compressing it is how these systems get abandoned in week two of an event.
The ongoing costs nobody quotes
Mobile device provisioning and management is the running cost specific to this category. Rugged tablets for the field, a device management tool, and replacements after each event are a real annual line that never appears in a software quote.
Hosting is modest between events and spikes during them, typically $400 to $1,500 a month averaged across the year, because a turnaround generates more traffic in four weeks than the rest of the year combined.
Support during an event is a different product from support between events. You need someone reachable at three in the morning for the duration, and that should be contracted explicitly rather than assumed. Budget it per event rather than annually.
Support and enhancement typically runs 15 to 20 percent of the build cost annually. In this category the enhancement half arrives in bursts before each event, as scope categories, contractors and rules change.
The cost that belongs in the business case rather than the software budget is the discipline of maintaining rules of credit. The system computes progress from them. It does not decide them, and keeping them current as work types change is a planner's standing responsibility.
Comparing a build against your current renewal
Most sites are comparing against P6 plus a cost tool plus a great deal of labour, and the labour is the part that never appears on an invoice.
Start with the licences you hold. Then add the planners and controls staff whose week is spent reconciling the scope register against the schedule and the cost report. That reconciliation is a person, not a task, and your controls manager can tell you how many.
Then price the standing time. Ask what a crew of eight costs per hour at your contractors' rates, then ask your superintendents how many crew hours were lost to a missing permit, an unhung isolation, a scaffold not built or material not staged during your last event. You do not need an industry figure for this. Your own daily reports have it.
Then price the found to working path. If a discovery job takes a day and a half to move from written up to working while the equipment sits open, that delay has a value your operations team can compute from the production loss of a day of overrun.
Finally, look at the next estimate. A build that captures actual productivity by contractor and discipline means your next turnaround is estimated from your own history rather than from memory, which is the argument that usually persuades a maintenance director.
When buying beats building
Buy if your shutdowns are short, largely repeatable and executed by a stable in house crew who know the work. P6 plus a well run worklist and a good coordinator is genuinely sufficient at that scale, and a custom system would be overhead your team resents.
Buy Prometheus Group STO if you are a heavy SAP site whose process is close to the workflow it ships with, and you would rather adapt your process than build one. It is purpose built for shutdowns and tightly bound to SAP, which is a real advantage in exactly that situation. Keep Hexagon EcoSys or Cleopatra Enterprise for cost control and estimating if your cost breakdown is clean, because they forecast well when the structure underneath them is right.
Build when two or more of these are true. Your events exceed roughly forty thousand contractor hours. Discovery work routinely takes more than a day to move from found to working. Your scope register and your schedule are reconciled by a human. You cannot answer, at any moment on any day, how many crews are standing and why. Or you run several sites and want the next event to start from the last event's actual productivity rather than from an estimator's recollection.
The honest test is the day nine question. When a vessel comes open and the inspector finds more than the plan assumed, can you say what it does to start up before the morning meeting. If the answer is a scheduler working overnight, that is the gap the build closes.
If you would rather someone argued with your brief than agreed with it, Digital Heroes contracts through India LLP, US LLC and UK LTD entities, so the agreement and the intellectual property assignment sit under law your own advisers already read. 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.
- Across more than 5,400 IT projects studied by McKinsey and the University of Oxford BT Centre, large IT projects ran on average 45% over budget and 7% over schedule while delivering 56% less value than predicted. Source: McKinsey & Company / University of Oxford (BT Centre for Major Programme Management) (2012) →
- PMI's Pulse of the Profession research found organizations waste an average of roughly 9.9% of every dollar invested in projects due to poor performance - equivalent to about $1 million wasted every 20 seconds collectively worldwide. Source: Project Management Institute (PMI) (2018) →
- Only 22% of firms are 'future ready' having significantly transformed digitally; these companies show average revenue growth 17.3 percentage points and net margins 14.0 percentage points above their industry average. Source: MIT Center for Information Systems Research (MIT Sloan) (2022) →
- Digital Champions expect to achieve about 16% in cost savings and around 15% in revenue gains from digital operations over five years; the study surveyed 1,155 manufacturing executives across 26 countries. Source: PwC / Strategy& (2018) →
Frequently asked questions
What is the total cost of custom turnaround management software?
A first release covering the scope register with challenge workflow, work pack readiness and daily field progress against rules of credit runs $80,000 to $170,000 over 14 to 20 weeks in our delivery experience. A full platform adding cost integration, contractor productivity and reconciliation, materials readiness and scenario comparison runs $220,000 to $550,000 over 8 to 14 months.
Primavera integration depth and contractor timesheet rules are the two things that move the number most.
What does it cost to run each year?
Hosting averages roughly $400 to $1,500 a month across the year, because a turnaround generates more traffic in four weeks than the rest of the year combined. Support and enhancement runs 15 to 20 percent of the build annually and arrives in bursts before each event.
Two lines never appear in software quotes: rugged tablets with device management and replacements after each event, and event support contracted separately, because someone has to be reachable at three in the morning for the duration.
How long before the turnaround should the software go live?
At least one full event cycle earlier, and ideally shaken out on a small shutdown first. A first release ships in 14 to 20 weeks, so work backwards from the event that matters rather than towards it.
Going live during a major event is the single most common way these projects fail, because the people who would normally absorb teething problems are the busiest people on site.
Is Prometheus Group STO cheaper than a custom build?
Almost certainly, on licence cost alone, and if you are a heavy SAP site whose process resembles the workflow it ships with, it is the right purchase and we would say so.
It becomes a constraint when your scope challenge, estimating, contracting and progress capture differ from that workflow, because you end up adapting the event to the tool. The comparison worth running is not licence against build. It is licence plus the process changes it requires, against a build that matches how your site already works.
How much does Primavera P6 integration cost?
In the worked example above it was $28,000 of a $158,000 first release. That covered a map between scope item, work order and schedule activity with read plus controlled write back and an agreed conflict rule.
A read only daily import costs materially less. A live two directional relationship with a schedule a scheduler is actively editing costs more, and the difference is entirely in conflict handling. Fix the depth you need before accepting an estimate, because this is the line where vague scoping hurts most.
What does contractor productivity tracking add?
Typically $45,000 to $80,000, and most of it is contract specific rules rather than screens. Every agreement carries different rates, shift premiums, travel provisions and minimum call outs, and each has to be modelled to reconcile labour, equipment and materials records against your own captured hours.
The return is that reconciliation becomes a comparison of two records you already hold rather than an argument at the end of the event.
Can we start with just the scope register before a major event?
Yes, and for a site six months out from a large turnaround it is often the highest value thing to do. The scope register with challenge workflow, duplicate detection, named acceptors and deferral targets runs $30,000 to $52,000 over six to eight weeks.
It does nothing during execution. It does mean the worklist entering the event is one durable register with an owner per item, so the question of why the event grew is answered by a report rather than by an argument.
Where does artificial intelligence actually save money in a turnaround?
In one narrow place: reading inspection write ups and free text notifications to classify work type and surface historic jobs that resemble it, so a discovery estimate starts from what a comparable repair actually took on your site. That can take a day out of the found to working path, which is worth real money while equipment is open.
Automated rescheduling is not worth building. A resequence that superintendents do not trust gets overridden, and the trust does not come back.
Who owns the code and the productivity data if an agency builds this?
You should own the repository, the cloud accounts and the unrestricted right to hire another firm, written into the contract before kickoff. At Digital Heroes that is the default from the first commit.
The productivity history across events is the most commercially valuable data your maintenance organisation produces, because it is what makes the next estimate defensible. It should never sit in a developer's account or in a format you cannot export in bulk.
I run a 15-person business. Is there a cheaper option than a full custom project management build?
Yes: a custom layer on top of a tool you already pay for. Digital Heroes ships client dashboards, automated reporting, and workflow glue built on the Asana and ClickUp APIs for $8,000 to $20,000, which fixes the specific gap without replacing the whole tool. A full custom platform rarely makes sense below roughly 50 seats unless the software faces your own customers.
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.
What's the most common mistake companies make when building their own PM tool?
Chasing feature parity with Asana or Jira. Across 2,000+ Digital Heroes projects, the builds that blow their budgets are the ones recreating Gantt charts, portfolio dashboards, and mobile apps nobody asked for, while the builds that succeed go deep on the two or three workflows that made the team leave their old tool. You are not competing with Asana's roadmap; you are replacing the 20 percent of it you actually use.
What does it cost to keep custom project management software running each year?
Budget 15 to 20 percent of the original build cost annually, so a $100,000 platform costs $15,000 to $20,000 a year to run. That covers hosting, security patches, dependency upgrades, and the item buyers forget: fixing integrations when Slack, Google, or QuickBooks change their APIs, which happens every year. Skipping the maintenance budget is how a two-year-old tool becomes impossible to upgrade.
What should the first version of a custom project management tool include, and what should wait?
Version one is the painful workflow plus the basics: tasks, projects, permissions, and one integration, shippable in 12 to 16 weeks. Everything that feels essential but is not should wait: Gantt views, custom report builders, native mobile apps, and public API access all belong in version two, once real usage shows what matters. Teams that run the MVP for a quarter before expanding consistently spend less and drop features that looked critical on paper.
We run everything on spreadsheets and Airtable. How do we know it's time for custom software?
The reliable signals are re-typing the same data into multiple tools, one employee acting as human middleware between systems, and errors appearing in handoffs between teams. Hard limits force the issue too: Airtable's Team plan caps at 50,000 records per base, and Business costs $45 per seat per month, so a 20-person team pays about $10,800 a year for a tool it has already outgrown. When workarounds consume more hours than the tools save, the spreadsheet era is over.
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 if the agency that built our project management tool shuts down?
Nothing fatal, if you set things up correctly from day one: code in your own GitHub organization, infrastructure in your own cloud account, and written deployment documentation as a contract deliverable. With those in place, any competent team can take over a standard-stack codebase in one to two weeks. Takeover disasters happen when the vendor hosted everything in accounts they owned, so verify account ownership before the first sprint, not after the relationship sours.
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.
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.
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
Published · Last updated .
