Permit to Work Software: Custom Build vs Off the Shelf
Buy. For most sites Enablon, Sphera or Damstra will digitise the permit, hold the isolation register and satisfy your auditor for far less than a build costs.
On this page
Buy. For most sites Enablon, Sphera or Damstra will digitise the permit, hold the isolation register and satisfy your auditor for far less than a build costs. The decision changes when your simultaneous operations control depends on someone remembering how two systems connect, or when a turnaround takes you from forty permits a day to six hundred. Then the conflict logic is worth owning.
What the off-the-shelf products actually do well
Twenty two contractor supervisors at the permit office window at 05:40. The isolation register is a red binder one person controls. The area authority is signing his fourth hot work permit while a pipefitter waits to ask whether a spade off the debutaniser is still in or was pulled last Thursday. That is the scene most sites are trying to fix, and the commercial platforms fix a good deal of it.
Enablon Control of Work and Sphera Control of Work are credible systems used at large operators, and both bring something a build does not: a permit model that has survived contact with dozens of sites and auditors, plus a vendor who maintains it. Damstra is strong on contractor management and site access, which is often the sharper pain at a single plant. Hexagon Permit Vision has real history in this space. Intelex and Cority cover the wider health and safety estate if your problem is broader than control of work. If your site standard fits inside any of those models, use them and spend your capital on competency and supervision instead.
Most plants should buy, and we say so before quoting. A single site issuing under ten permits a day with one permit issuer and no turnaround larger than a few dozen contractors does not need custom software. Neither does a group site being told to standardise on a corporate instance, because fighting that is a political project rather than a software one, and you will lose it slowly.
Where they stop
The break is conflict detection, and it is where people actually get hurt. Incident investigations at plants like yours rarely find a missing rule. OSHA 29 CFR 1910.147 covers energy isolation, 1910.146 covers permit required confined spaces, 1910.119 covers process safety management, and your site procedure already says the right things. What investigations find is two permits, each individually correct, issued by different area authorities, for two jobs that shared one drain header.
A permit references an equipment tag. That is where most electronic systems stop. Real simultaneous operations conflicts are relationship against relationship, not tag against tag. The jobs that hurt people share a common sump, a common flare sub header, a vent stack, a scaffold platform above another live job, a crane radius over an operating unit, or a firewater ring main that one of the permits has depressurised. The commercial packages model a permit to asset link and then a manual review meeting, which is a human reading a printed list at 06:00. That is exactly the control that failed.
The second break is your approval matrix. Every site has grown its own standard, usually after an incident. Hot work in a classified area needs the area authority plus a named fire watch plus a gas test inside the last thirty minutes. Confined space entry needs a rescue plan and a standby person named on the permit. Night shift extension is cold work only and only by the shift superintendent. Configurable workflow engines get you close, then force a compromise on the last twenty percent, and the compromise always runs toward the vendor model. Sites then keep a shadow paper process for the exceptions, which leaves the electronic record incomplete, which is the worst possible position during an investigation.
The third break is the register itself. Long term isolations applied in March are still live in September, the original applicant has left the contractor, the tag number has been reused, and no product we have seen treats partial de isolation as a first class operation with its own approval. Crews do it anyway.
The arithmetic on cost to build versus per user licensing
Price this per named user and per permit, because both grow and they grow at different times.
Suppose your quote is $95,000 a year for 250 named users, and a turnaround adds 400 contractor supervisors for eight weeks at a surge rate. Add the implementation partner retainer most sites end up paying to keep configuration alive, say $30,000, and the annual figure is nearer $140,000 in a turnaround year. At 40 permits a day and roughly 12,000 permits a year, that is about $11 a permit.
Against a build: our first release band is $70,000 to $150,000, with year two support at 15 to 20 percent of build cost annually. Three years at the midpoint is roughly $110,000 plus two years of support, so call it $150,000, against $350,000 or more for three years of licence plus retainer.
The crossover sits between 40 and 70 live permits a day, or above roughly 600 named users once contractor accounts are counted. Below 15 permits a day with one issuer, the product wins on every arrangement of these numbers, and a build would be an expensive way to replace a printed form.
The number that belongs in neither column is the 07:00 start. If your turnaround permit office delays the start of shift by forty minutes across 300 contractors, price that against the day rate you are already paying and compare it with everything above. On most turnarounds it is the largest figure on the page.
What a custom build actually costs
The figures below are Digital Heroes delivery bands. They are what we have charged, not a survey of the sector. A first release covering permit types and workflow, the electronic isolation register, gas test capture, area and system based conflict detection and a field view runs $70,000 to $150,000 and ships in 12 to 18 weeks. That is a system the permit office runs on from day one rather than a pilot. A full control of work platform adding contractor competency and induction checks, turnaround surge handling, offline field devices, work order integration and analytics runs $180,000 to $450,000 phased over 6 to 12 months.
Data migration is 10 to 25 percent of the first release, and here the migration is mostly the site model rather than old permits. Building the tag to system to area hierarchy, plus the drain, flare and firewater relationships that drive conflict rules, is discovery work read off your process and instrumentation diagrams, and if your equipment register is inconsistent it lands at the top of the range. Year two is 15 to 20 percent of build cost annually, covering hosting, rule changes your health and safety lead makes after an incident, and support through turnaround weeks.
What pushes it up specifically: the number of distinct permit types, since each is its own form and rule set; SAP Plant Maintenance or IBM Maximo integration when work order and functional location data is inconsistent; hazardous area rated hardware, because devices carried inside a process unit must suit the area classification under ATEX or IECEx, which roughly doubles field application effort against a normal tablet; and multi site rollout where each site genuinely does have a different standard.
The four situations where building wins
One of these on its own is an argument for better configuration. Two of them is a safety case.
- Regulatory and standard fit. Your site procedure, written after an incident and accepted by your regulator, contains permit types or signature stages the product cannot express, so you run a shadow paper process. Under a process safety management regime, or a COMAH or Seveso site in the United Kingdom and Europe, an incomplete electronic record is a finding waiting to happen.
- Scale economics. You are past the permits per day crossover above, or turnaround surge licensing has become a line item somebody has to defend.
- Conflict logic that is your actual safety control. When the coordination between permits, isolations and areas is the control keeping two crews apart, that logic belongs somewhere you can change the week after an incident rather than in a vendor backlog.
- Integration sprawl across three or more systems. Work orders in SAP Plant Maintenance or Maximo, gas detector fleet data, badge and access control at the gate, and a contractor competency register. Once three or more are reconciled by hand, the reconciliation is already a system nobody owns.
How to decide in a week
Run a clash test on real history rather than watching a demonstration.
Monday, pull every permit issued in one busy week last month, ideally during a shutdown. Tuesday, put a process engineer and an area authority in a room with the process and instrumentation diagrams and ask them to find every pair that shared a drain, a flare sub header, a firewater section or a vertical work relationship. Record how long it takes and how many pairs they find. Wednesday, ask your current system to find the same pairs and see how many it surfaces without a human. Thursday, take the three permit types your standard treats most strictly and check whether each one is issued entirely inside the system or partly on paper. Friday, run the per permit arithmetic above.
If the system found the pairs and nothing runs on paper, buy, configure the remaining gaps and stop. That is the outcome for a good number of sites. If two people with drawings found clashes the system could not see, and two of your permit types live partly on paper, you have proven the case in four days and can put real evidence in front of your steering committee.
Buy a specification before you buy a system. Two to four weeks, fixed fee, ending in a written product requirements document covering the site model, the conflict rule set drawn from your own simultaneous operations matrix, permit types and signature stages, isolation and partial de isolation handling, offline field behaviour and acceptance criteria. You keep the document either way, and it makes competing quotes comparable for the first time.
Where Digital Heroes is wrong for you: small single plants under ten permits a day, sites mandated onto a corporate platform, and anyone wanting a supplier to operate a safety critical system rather than own it. We start with one unit and two permit types rather than a site wide launch. We will not start code without a signed specification. India LLP, US LLC and UK LTD entities mean intellectual property assigns under your own law, and you can verify us on Clutch, Trustpilot, Fiverr Vetted Pro and D-U-N-S. More than fifty specialists and over 2,000 projects behind us, with the engineers who will build it introduced before you sign.
Book a 30-minute call with Digital Heroes and get a written plan and a fixed quote within 48 hours.
The evidence behind this guide
Independent findings on why this investment pays off. Every link goes to the primary source.
- 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 average developer spends more than 17 hours a week dealing with maintenance issues such as debugging and refactoring, and about four of those hours on 'bad code' - waste that equates to nearly $85 billion annually worldwide in opportunity cost. Source: Stripe (2018) →
- 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) →
- Mordor Intelligence sizes the field service management market at USD 6.26 billion in 2026, forecasting USD 9.87 billion by 2031 at a 9.54% CAGR, confirming sustained double-digit-adjacent demand for FSM software. Source: Mordor Intelligence (2026) →
Frequently asked questions
How long does it take to roll out electronic permit to work across several sites?
Plan a first site in 12 to 18 weeks, then four to eight weeks 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 genuinely site scoped from the start. Forcing one corporate configuration across genuinely different plants is the most common way these programmes stall.
Who owns the code and the site model if a developer builds it?
You should own the repository, the infrastructure accounts, the rule configuration and the unrestricted right to hire another firm, agreed in writing before kickoff. At Digital Heroes the client owns the code from the first commit. On a safety critical system you should walk away from any developer who hedges on this, because you may need a change made in the week after an incident.
What happens to our permit records during an incident investigation?
That is the strongest argument for an append only event log. Every issue, extension, suspension, gas test, isolation application and close is stored as an immutable timestamped event, and corrections are new events rather than edits. An investigator can then reconstruct what was live on a given piece of equipment at a given hour in minutes, including concurrent work, and can see that the record was not tidied afterwards.
Can we build only the isolation register and keep our current permit system?
Often the right first move, and cheaper than a full platform. The register is where the highest consequence data sits: which valves are shut, which spades are in, which breakers are racked out, who is hung on each boundary and which isolations have outlived their review date. Building that alone gives you a queryable answer to what is isolated in unit four right now, without touching permit issue.
We issue about a dozen permits a day. Should we build anything?
No. At that volume with one issuer and no large turnarounds, a commercial control of work product, or even a disciplined paper system with a proper isolation register, is proportionate. Spend the money on competency, supervision and getting your equipment register accurate, since that work is needed either way. Revisit when several area authorities start issuing in parallel.
What is the difference between permit to work software and a maintenance system?
A maintenance system such as SAP Plant Maintenance or Maximo plans and records work on assets. Permit to work software authorises that work to proceed safely at a moment in time, against isolations, gas tests and other live jobs. Trying to run permits inside the maintenance system fails because the approval and isolation logic does not fit there, and the two need to exchange data rather than merge.
Will a permit system work in the field with no signal and hazardous area restrictions?
It has to. Devices taken inside a process unit must suit the area classification, which usually means intrinsically safe hardware certified under ATEX or IECEx, with smaller screens and slower processors than a developer laptop. The application must run fully offline and reconcile on reconnection, with explicit rules on what is permitted offline. Recording a gas test result offline is reasonable. Collecting a hot work authorisation offline is not.
How much does integration with SAP or Maximo add?
Treat it as its own workstream rather than a line inside another phase, because the cost is driven by your data quality rather than by the interface. The realistic scope is work order and functional location reference in, permit status out, so a maintenance planner can see whether a job is permit ready. If functional location data is inconsistent, cleaning it is the hidden work and it belongs in the plan.
Can contractor competency checks block a permit automatically?
Yes, and it is one of the better reasons to build. Hold competencies, inductions and medical clearances as records with expiry dates, then make an expired qualification a hard block on being named on a permit rather than a warning somebody clicks past. The failure worth designing against is discovering during an investigation that a confined space standby person's training had lapsed.
Is it worth building if we already have a commercial platform in place?
Only if you can name the specific permit types or rules it cannot express, and only if you are running paper for them today. If the platform covers your standard and the complaint is the interface, the cheaper fix is configuration and training. If two of your permit types live partly on paper because the configuration would not bend, the electronic record is already incomplete and that is a different conversation.
What questions should I ask a development agency on the first call?
Ask who exactly will build it, what happens when scope changes mid-project, what their maintenance terms are after launch, and what they will need from you every week. Then ask them to describe a project that went wrong and what they changed afterward; teams that have shipped at real volume have war stories, and teams claiming a perfect record are hiding something. The scope-change answer matters most: a disciplined shop describes a written change-order process, not a vague promise to be flexible.
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 calculate the ROI of a custom internal tool?
Count hours first: multiply the weekly hours staff spend on the manual process by their loaded hourly cost, then add the cost of errors such as mispriced quotes or missed renewals. A tool saving a 10-person team 5 hours each per week recovers about 2,500 hours a year, which repays a $20,000 to $30,000 build well inside a year at typical wages. Most internal tools Digital Heroes delivers reach payback in 6 to 18 months, with quoting and billing tools at the fast end because they plug revenue leaks, not just time.
How do I vet a software development agency before signing a contract?
Ask to speak with two past clients whose projects resemble yours in size and industry, and ask exactly who will write your code, since some agencies sell senior faces and deliver junior or subcontracted hands. Demand a written specification with acceptance criteria before any fixed price, and check that their portfolio links to products that are actually live. An instant quote given without questions about your workflows is the clearest warning sign there is.
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.
How do I calculate whether custom software will pay for itself?
Divide the build cost by the monthly benefit, where benefit is hours saved times loaded hourly cost, plus subscription fees replaced, plus any revenue the software unlocks. Three staff saving 10 hours a week each at a $40 loaded rate is about $62,000 a year, which pays back a $60,000 build in roughly 12 months. Across Digital Heroes internal-tool projects, 12 to 24 months is the normal payback range, and anything projecting under 6 months usually means the spreadsheet is hiding costs.
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.
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.
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 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
More from Ben.
Senior SEO Strategist · New-york · 5 posts on the site
Published · Last updated .
