How Much Does Permit to Work Software Cost in 2026?
Electronic permit to work software costs $70,000 to $450,000 to build.
On this page
Electronic permit to work software costs $70,000 to $450,000 to build. A first release covering permit issue and close, the electronic isolation register, gas test capture and area based conflict checks runs $70,000 to $150,000 over 12 to 18 weeks, while a full control of work platform adding contractor competency, turnaround surge handling, offline field devices and a work order link into SAP PM or IBM Maximo reaches $180,000 to $450,000 phased over 6 to 12 months, based on Digital Heroes delivery experience. The cost driver almost nobody budgets for is the site model, meaning the tag to system to area hierarchy plus the drain, flare and firewater relationships that make conflict detection possible: if your process and instrumentation diagrams and equipment register are messy, that is discovery work of $15,000 to $40,000 that has to happen before a single conflict rule can be written.
The bands a control of work build falls into
A first release runs $70,000 to $150,000 over 12 to 18 weeks. That covers your permit types with your fields, signature stages and escalation rules expressed as data rather than code; the electronic isolation register where isolation points are objects carrying energy source, method, applied by, verified by, tag number, drawing reference and photo, grouped into certificates that permits hang on; gas test capture with validity windows; area and system based conflict detection evaluated at the moment of issue; and a field view. It is a system the permit office runs on from day one, not a pilot.
A full platform runs $180,000 to $450,000 phased over 6 to 12 months. It adds contractor competency and induction checking, turnaround surge features including pre approved permit packs and group issue, offline field applications on intrinsically safe devices, work order integration and the analytics a shift superintendent needs to see live permit count by area.
Your position inside those bands is set by permit type count and by the state of your equipment data, not by the size of the plant. Each permit type is effectively its own form, its own rule set and its own approval path. And every conflict rule you want depends on a site model that has to be built from your drawings, which is the work that gets left out of every estimate we are asked to review.
What drives a permit to work build up
- Permit type count, $8,000 to $18,000 each beyond the first two. Hot work, confined space entry, excavation, electrical, working at height and radiography have genuinely different fields, prerequisites and signature stages. Reusing a form and hiding fields is how sites end up running a shadow paper process for the exceptions.
- The site model, $15,000 to $40,000. Tags rolling up into systems and areas, with shared drains, common flare sub headers, vent stacks, scaffold relationships and firewater ring main sections represented as data. Without it, conflict detection is a report rather than a control.
- Hazardous area rated hardware and offline sync, $35,000 to $70,000. Intrinsically safe tablets have smaller screens and slower processors than a developer laptop, and units have no reliable coverage at the far end. Field effort roughly doubles compared with a normal tablet application.
- SAP PM or Maximo integration, $20,000 to $45,000. Work order and functional location reference in, permit status out. Treat it as its own workstream if your functional location data is inconsistent, because cleaning that is the hidden work.
- Turnaround surge features, $25,000 to $45,000. Pre approval of routine permit packs, group issue for repeat jobs, gate kiosk mode and live area headcount. Anything merely acceptable at 40 permits a day fails at 500, usually at the queue rather than in the software.
- Multi site rollout, $4,000 to $8,000 per additional site. Sites will insist their standard differs and they are usually right, so the rules layer has to be genuinely site scoped rather than retrofitted.
What keeps the number down
- One unit, two permit types, and the isolation register. That is where the risk concentrates and where the learning is. Everything else is a rollout question rather than a design question once those work.
- Use the site model you already have. If your equipment register and functional location hierarchy are clean, the most expensive discovery line in the project shrinks to almost nothing. Find out which it is before you approve a budget.
- Normal tablets outside the classified area. The permit office, the gate and the contractor compound do not need intrinsically safe hardware. Scope the rated devices to where the classification actually requires them.
- Defer the maintenance system integration. A permit that references a work order number typed by the issuer is imperfect but workable for one release, and it buys you time to sort out functional location data properly.
- Skip analytics in phase one. Live permit count by area is genuinely useful during a turnaround. It is not what makes the first release safe.
- Reuse rules across sites rather than forking them. Site scoped does not mean site specific code. If each plant gets its own codebase you have bought several projects instead of one.
A worked example that adds up
A mid size refinery issuing around 40 permits a day in normal operation and several hundred during a major turnaround, with several area authorities issuing in parallel, six permit types, SAP PM for maintenance, and a paper isolation register carrying long term isolations older than a year.
- Discovery and site model build from process drawings across two units: $19,000
- Permit types, fields, signature stages and escalation rules as data: $44,000
- Electronic isolation register with points, certificates and boundaries: $52,000
- Gas test capture with validity windows and device recording: $16,000
- Area and system based conflict detection at point of issue: $48,000
- Offline field application on intrinsically safe devices: $57,000
- Contractor competency and induction checking: $26,000
- Turnaround surge features including pre approval packs and gate kiosk: $31,000
- SAP PM work order and functional location integration: $29,000
- Append only event log and investigation export: $18,000
That totals $340,000. Add a 15 percent contingency rather than the usual 12, because site model discovery reliably finds equipment relationships that exist in the plant and not on any current drawing, and the committed number is $391,000 across roughly eleven months.
How the spend phases
- Weeks 1 to 6, about $19,000. Site model construction with process engineering and the area authorities. This runs longer than a normal discovery because it is drawing work, not workshop work, and it gates everything downstream.
- Weeks 4 to 18, about $112,000. The first release: permit types, the isolation register and gas test capture. At the end of this, the question of what is isolated in a given unit right now takes two seconds instead of a walk to the permit office.
- Weeks 14 to 26, about $48,000. Conflict detection, once the site model and the permit data both exist to evaluate against. Building it earlier means writing rules against a model that is still changing.
- Weeks 20 to 36, about $57,000. The offline field application on rated devices. Start hardware procurement and area classification sign off in parallel from week 20, because that approval is not on your schedule.
- Weeks 30 to 44, about $86,000. Contractor competency, turnaround surge features and SAP PM integration, sequenced to land before your next planned turnaround rather than during it.
- Weeks 40 to 48, about $18,000. The event log export for investigations, built last because it is only meaningful once there is a real history of permits, isolations and gas tests to reconstruct.
The ongoing costs nobody quotes
- Support and maintenance, 18 to 25 percent of build. On a $391,000 platform that is roughly $70,000 to $98,000 a year. A permit office runs at 05:40 and the support arrangement has to match that, which is a contract term rather than a hope.
- Site model maintenance, $12,000 to $30,000 a year. Plants change. New tie ins, decommissioned equipment and modified drain routing all alter conflict relationships, and a stale model produces false confidence, which is worse than no model.
- Rule changes after incidents and audits, $10,000 to $25,000 a year. The whole reason to own this is being able to change a rule the week after an incident. Fund that capacity rather than treating each change as a project.
- Intrinsically safe device fleet. Rated hardware costs several times a consumer tablet, lives in a hard environment and needs a replacement cycle plus spares held for turnarounds when the fleet size temporarily triples.
- Turnaround surge support, $15,000 to $40,000 per major turnaround. Extra devices, extra accounts, pre approval loading and on site cover during the first shifts. Budget it against the turnaround, not against the software line.
- Maintenance system upgrades, $8,000 to $20,000 per major upgrade. SAP PM and Maximo upgrades move interfaces, and a broken work order link is silent until a planner notices permits are missing references.
- Hosting and record retention, $10,000 to $28,000 a year. The event log is safety evidence with retention obligations attached, and the storage decision should be made against those obligations rather than against convenience.
Comparing a build against your current renewal
Compare against four numbers, not the licence line on your control of work platform.
First, the licence and support you already pay, from invoices, plus the professional services days consumed each year on configuration requests. Second, the shadow process. If any permit type runs on paper because the configured system cannot express it, count those permits and put a cost on an incomplete electronic record, which is what an investigator will find. Third, the permit office queue. Measure how long crews wait at the window on a normal morning and during a turnaround, multiply by contractor crew cost, and you have the daily figure a pre approval workflow removes. Fourth, the investigation cost: total the hours spent in the last two years reconstructing what was live on a piece of equipment at a given hour, and add the findings that landed because the reconstruction was a guess.
In our delivery experience the second and fourth lines are the ones that persuade a site director, and neither appears on a renewal quote. The first line rarely justifies a build on its own, and we would not argue that it does.
When buying beats building
Buy if you are a single plant issuing under about ten permits a day with one permit issuer and no turnaround larger than a few dozen contractors. Damstra and the entry tiers of the larger platforms will digitise your form, and a custom build would be an expensive way to get a better PDF. At that volume the money is better spent on competency and supervision.
Buy also if you are a group site being told to standardise on the corporate Enablon or Sphera Control of Work instance. Fighting that is a political project rather than a software one. Both are credible platforms and if your site fits inside their permit model, use them.
Build when two or more of these are true. Your simultaneous operations control depends on a person remembering how systems connect. Your isolation register is paper or a spreadsheet and you carry long term isolations older than a year. You have implemented a commercial package and run a shadow paper process for the permit types it could not express. Your turnaround permit office is the bottleneck delaying the 07:00 start every morning. Or you operate multiple sites with genuinely different standards and one vendor configuration is being forced on all of them. The threshold is not permit volume by itself. It is whether the coordination logic between permits, isolations and areas has become the actual safety control on your site, because once it has, that logic belongs somewhere you can change it the week after an incident rather than in a vendor backlog.
If you would rather scope this before committing budget, 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.
- Median SaaS spend reached $9,455 per employee, and organizations leave an average of 36% of their SaaS licenses unused. Source: Zylo (2026) →
- Technical debt is the number-one frustration at work for professional developers, cited by about 63% of respondents - roughly twice the rate of the next-most-common frustration (complexity of tech stack, ~33%). Source: Stack Overflow (2024) →
- The global point-of-sale terminal market is projected to reach approximately $181.47 billion by 2030, growing at an 8.1% CAGR from 2025 to 2030, driven by digital payment adoption and demand across retail, restaurant, and hospitality sectors. Source: Grand View Research (2025) →
- 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) →
Frequently asked questions
How much does a custom electronic permit to work system cost?
A first release covering permit issue and close, the electronic isolation register, gas test capture and area based conflict checks runs $70,000 to $150,000 over 12 to 18 weeks in Digital Heroes delivery experience. A full control of work platform with contractor competency, offline field devices, turnaround features and SAP PM or Maximo integration runs $180,000 to $450,000 over 6 to 12 months.
Permit type count and the state of your equipment register drive the number more than plant size does.
Why is building the site model such a large cost line?
Because conflict detection is impossible without it. Tags have to roll up into systems and areas, and the relationships that actually cause harm, such as a shared sump, a common flare sub header, work directly above another live job or a depressurised firewater section, have to exist as data rather than in someone's memory.
Budget $15,000 to $40,000 and expect it to run six weeks of calendar time, because it is drawing work rather than workshop work. If your process drawings and equipment register are clean, it shrinks considerably, so find out which you have before approving a budget.
What does the offline field application on rated devices add?
Between $35,000 and $70,000, roughly double what the same application would cost on ordinary tablets. Devices taken inside a process unit must suit the area classification, which means smaller screens, slower processors and a constrained set of hardware options.
The application also has to work fully offline and reconcile on reconnection, with explicit rules about what is permitted offline. Recording a gas test result offline is reasonable. Collecting an authorising signature for hot work offline is not.
What does a control of work platform cost to run each year?
Plan on 18 to 25 percent of build for support and maintenance, roughly $70,000 to $98,000 a year on a $391,000 platform, and make the support hours match a permit office that opens before 06:00.
Add $12,000 to $30,000 for site model maintenance as the plant changes, $10,000 to $25,000 for rule changes after incidents and audits, $10,000 to $28,000 for hosting and record retention, plus the rated device fleet replacement cycle and $15,000 to $40,000 per major turnaround for surge support.
How long does it take to roll out across several sites?
Plan 12 to 18 weeks for the first site, then 4 to 8 weeks and $4,000 to $8,000 per additional site, most of which is site model building and standard reconciliation rather than engineering.
Sites will insist their permit standard differs and they are usually right, so the rules layer needs to be site scoped from the start. Attempting a single corporate configuration across genuinely different plants is the most common way these programmes stall.
Is Enablon or Sphera Control of Work cheaper than building?
On licence cost, yes, and if your site fits inside their permit model you should use them. They are credible platforms with real deployments behind them.
The honest comparison is not licence against build. It is licence plus annual configuration services plus the cost of the shadow paper process you run for the permit types the configuration cannot express, plus the hours spent reconstructing records during investigations. Those last two are what persuade a site director, and neither appears on a renewal quote.
What is in the worked example total of $391,000?
Site model discovery at $19,000, permit types and workflow at $44,000, the isolation register at $52,000, gas test capture at $16,000, conflict detection at $48,000, the offline field application at $57,000, contractor competency at $26,000, turnaround features at $31,000, SAP PM integration at $29,000 and the event log export at $18,000, totalling $340,000.
A 15 percent contingency, higher than usual because site model discovery finds relationships that appear on no current drawing, takes it to $391,000 across roughly eleven months.
Can we start with just the isolation register?
Yes, and it is often the right first move. Isolation points as objects with owner, method, verification, drawing reference, photo and review date, grouped into certificates that permits hang on, is around $52,000 and delivers the single biggest audit improvement in the whole programme.
It also forces the partial de isolation question into the open, which crews perform whether or not your software supports it. Pair it with two permit types on one unit and you have a defensible first release well inside the lower band.
We issue about a dozen permits a day. Is a build worth it?
Probably not, and we would say so. At that volume with one issuer and no large turnarounds, Damstra or a commercial control of work product is proportionate, and even a disciplined paper system with a proper isolation register can be defensible.
The build case begins when several area authorities issue in parallel, when conflicts depend on someone remembering how systems connect, or when a turnaround takes you to several hundred permits a day. Until then, spend the money on competency and supervision.
What does an internal tool cost for a small business with 20 to 50 employees?
Plan on $5,000 to $15,000 for a focused tool that replaces one painful spreadsheet workflow, such as job scheduling, quoting, or PTO tracking. In Digital Heroes projects at this size, the sweet spot is one core workflow, two or three user roles, and a single integration, usually QuickBooks or Google Workspace. Quotes far below $5,000 usually mean a template with your logo on it rather than software built around your process.
Is a freelancer or an agency better for building an internal tool?
A solid freelancer works for a single-workflow tool under roughly $10,000, if you accept that one person holds all the knowledge. An agency earns its premium once the tool spans departments or integrations, because you get a developer, a designer, and a project manager plus continuity when someone leaves or gets sick. The hidden freelancer cost appears 18 months later when you need changes and the original builder has moved on, a rescue situation Digital Heroes is hired for regularly.
How much does a custom internal tool cost to build?
Most custom internal tools cost $8,000 to $40,000 to build, based on Digital Heroes delivery data across 2,000+ client projects. A single-purpose tool like an approval dashboard or inventory tracker sits at the low end, while a multi-department platform with role-based access and several integrations pushes past $40,000. The three biggest cost drivers are the number of user roles, the number of systems the tool must connect to, and custom reporting requirements.
How do I vet a development agency for an internal tools project?
Ask to see two or three internal tools they have shipped and whether those clients still use them daily, because internal tools fail on adoption, not code quality. Good signs: they ask to see your current spreadsheet or process before quoting, they propose a phased build instead of one big launch, and they spell out who handles training and post-launch changes. Walk away from anyone who gives a fixed price before seeing your actual workflow, since internal tools live or die on process details.
Can I build my product on a no-code tool like Bubble instead of hiring developers?
For testing whether anyone wants the product, yes, and Bubble's paid plans start at $29 a month, which is the cheapest validation you will ever buy. The ceiling arrives with complex data relationships, heavy integrations, performance at a few thousand users, and the fact that you cannot export a Bubble app to servers you control. A path many Digital Heroes clients take: prove demand on no-code, then rebuild custom once revenue justifies it, treating the no-code version as a paid prototype rather than a foundation.
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.
What should I prepare before contacting an agency about an internal tool?
Bring the spreadsheet or document you run the process on today, a list of everyone who touches the workflow and what each person does, and one sentence describing the outcome you want. You do not need wireframes or a technical spec; a 30-minute screen-share of the current process beats a 20-page requirements document. Decide your rough budget band and name a single internal decision-maker, because projects without one take noticeably longer in Digital Heroes experience.
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.
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 .
