Oversize Overweight Permit Software: Build vs Buy
Buy, or use a permit service. A few routine oversize moves a month across two states will never recover a build, and services exist to absorb exactly that administrative load.
On this page
Buy, or use a permit service. A few routine oversize moves a month across two states will never recover a build, and services exist to absorb exactly that administrative load. Building starts to pay past roughly 1,500 permits a year, or five jurisdictions worked regularly with engineered configurations whose axle spread changes from move to move.
What the off-the-shelf products actually do well
A handful of routine oversize moves a month across two states with repeatable dimensions: use a permit service and stop reading. You will never recover a build, and the administrative load is precisely what those services exist to absorb.
The tools are good at what they were built for. ProMiles offers strong mileage and routing alongside permit ordering. Bestpass handles permits next to tolling as a managed service, removing two administrative burdens through one relationship. TransCore is deeply embedded in state permitting and in several states is effectively the machinery issuing the paper. Trimble PC MILER routes commercial vehicles properly, with restriction data maintained by people whose entire job that is. JJ Keller and the other permit services take applications off your desk completely.
If most of your work sits in annual permit territory, where the same trailer runs the same corridors inside standing limits, the coordination complexity that justifies a build is largely absent and a service is the right answer.
They also carry things you would otherwise own forever. Someone else tracks state fee changes. Someone else notices when a portal changes its form. Someone else keeps road network data current, which is a subscription and a maintenance obligation rather than a purchase.
So buy first, or use a service. What follows is the point at which the coordination problem outgrows both.
Where they stop: the truck in the profile is not your truck
Routing software carries a vehicle profile. Height, weight, length, sometimes axle count. For general freight that is sufficient, because published restrictions are written against those figures.
Heavy haul is governed by something else: the axle configuration. How many axles, in what groups, at what spacings, carrying what individual and group weights. Two combinations at identical gross weight give different answers on the same structure, because capacity responds to distribution rather than total. The federal bridge formula makes the same point in law rather than engineering. What you may carry across a given axle spacing depends on the spread, not the sum.
So if you run a nine axle expandable with a jeep and a booster and change the spread for a particular move, your permitted weights change with it. No service bureau tool holds your trailer catalogue as engineering data, so dimensions get typed from a drawing into a form, and transcription errors become permits issued for a configuration you are not actually running.
The second gap is the one that strands crews. Each state issues its own permit with its own route, worked sequentially. Then state three returns an amended route avoiding a bridge, which adds sixty miles, which crosses a county with a curfew the original did not have, and which no longer matches the entry point on the state two permit. Three permits are now inconsistent, the escort company is booked to the old schedule, and nothing anywhere represents the complete movement. The tools are organised around permit issuance, which is inherently per jurisdiction, so no product owns the whole line. Your permit manager does, in their head.
The arithmetic: per permit service fees versus a build
Permit services charge a fee per permit on top of the state fee, and the state fee is not avoidable by any route or any software. So model only the part software can move: the service fee, and the labour on your own permit desk.
Count permits rather than moves. A four state move with two county permits is six. Multiply your annual permit count by the service fee you pay, then add the fully loaded cost of coordinator hours spent on applications, amendments and rebooking. At 300 permits a year across two states, that total sits well below a build and a service is plainly correct.
The crossover lands around 1,500 permits a year, or five or more jurisdictions worked regularly, whichever you reach first. Jurisdiction count usually decides it before volume does, because coordination cost grows with the number of interacting rule sets rather than with the number of forms.
Then add the failure costs, which nobody puts in a spreadsheet. Take the last twelve months and count escort companies who invoiced for a move that was rescheduled, crane windows missed because a bridge review ran long, moves that sat while a permit expired waiting on another state, and any citation or turnaround at a scale. Those are your own numbers and they are usually larger than the service fees.
One caution. A build does not reduce state fees, does not shorten a bridge review and does not make a state issue faster. Anyone implying otherwise is selling.
What a custom build actually costs
Bands. A focused first release covering your equipment configuration catalogue with real axle groups and spacings, move objects holding permits and route segments, restriction and escort rules as maintained data, and permit application assembly runs $70,000 to $140,000 and ships in 12 to 16 weeks. A full platform adding routing evaluated against actual configurations, curfew and restriction checking along the route, escort and resource scheduling, portal integration where states support it, and a crew packet with movement capture runs $170,000 to $400,000 phased across 6 to 12 months.
Data migration adds 10 to 25 percent, and here the migration is knowledge capture. Your curfews, escort thresholds, jurisdiction quirks and the routings that worked last time have never been written down. Structured sessions with your permit manager are the migration, and every captured rule needs a source and a review date, or the data rots quietly and people go back to trusting memory.
Year two runs 15 to 20 percent of build cost annually, plus the road network data licence, which is recurring and belongs in the model from day one rather than surfacing in month seven.
What pushes the number up: jurisdiction count, since each state has its own rules, forms and portal behaviour and several expose nothing at all. Canadian provinces if you run cross border. Superload work, where structural review is a state engineering process you participate in and the system tracks as a workflow rather than a calculation it performs. And transportation management system integration if you want moves, billing and settlement joined.
What keeps it down: your top five jurisdictions by permit count, one equipment class, and manual submission in phase one.
The four situations where building wins
- Regulatory fit. The federal bridge formula and the interstate axle limits set the floor, then every state layers its own permit thresholds, escort requirements and superload definitions on top with no uniformity between them. Certified pilot car operator requirements differ, some dimensions call for police escort, and holiday and metropolitan curfews are set locally. Encoding all of that as data with a source and a review date makes compliance maintainable. Holding it in one person's memory means it is correct right up until they retire.
- Scale economics. Per permit service fees across five or more jurisdictions at volume, where the fee scales with the exact activity you are trying to grow and buys you no coordination in return.
- A workflow that is your competitive advantage. If you win project work because you commit to a delivery window on a superload while competitors will not, that confidence comes from knowing which of your configurations clears which corridor. Encoding the configuration catalogue and your past routings turns that from a person into an asset, and it answers the quoting question you currently cannot answer quickly.
- Integration sprawl across three or more systems. State portals, a routing tool, an escort scheduling spreadsheet, the transportation management system carrying the load and the invoice, and a folder of permit documents. The move file is the object none of them own, and it is exactly what your insurer asks for if a structure is ever struck.
Two of those true is a build. One of them is a better conversation with your service provider.
How to decide in a week
Audit twenty moves. Not the difficult ones you remember, the last twenty multi state moves in order.
Monday: for each, record the number of permits, the number of amendments after first issue, and the days between first application and wheels turning.
Tuesday: for every amendment, write down what triggered it and what it broke downstream. A bridge avoided. A route that no longer connected at the state line. A curfew nobody checked. Then note whether an escort, a crane or a utility crew had to be rebooked because of it.
Wednesday: price the rebookings and the idle days at your own rates. Include escorts who invoiced for a move that did not happen, because that line is real and it is rarely counted.
Thursday: ask your permit manager one question and record the answer verbatim. Which of our configurations can make this move with the fewest permits. If it takes more than an hour, or if the answer depends entirely on that person being at their desk, you have located the bottleneck this project addresses.
Friday: compare the total against the bands above, and consider the middle path before the full one. Keep a permit service for issuance where they are efficient, and build only the coordination layer: configurations, moves, restrictions, resources and the file of record. That is where the losses and the key person risk sit, and it is the part no vendor sells, because it reflects how your company runs projects rather than how a state issues paper.
What follows is a paid discovery phase rather than a proposal. Two to three weeks, fixed fee, producing a signed product requirements document covering the configuration model, the move object with segment connection checks, the restriction rule set with sources and review dates, and acceptance criteria. You own that specification whoever builds it.
Who we are wrong for: two state carriers running routine dimensions, anyone shopping purely on hourly rate, and anyone who wants portal automation in phase one. Digital Heroes writes that requirements document before any code, with more than fifty specialists and India LLP, US LLC and UK LTD entities so intellectual property assigns under your own law. ShopScore, HeroCheckout and Section Vault are our own products, over 2,000 projects sit behind us, and you meet the named team before signing. We are listed on Clutch, Trustpilot, Fiverr Vetted Pro and D-U-N-S.
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.
- McKinsey's Developer Velocity research finds best-in-class tools are the top contributor to software business success, yet only about 5% of executives ranked tools among their top-three software enablers, signaling underinvestment in developer tools (this finding originates in McKinsey's Developer Velocity study rather than the linked generative-AI article). Source: McKinsey & Company (2023) →
- Technology 'Leaders' grow revenue at more than twice the rate of 'Laggards'; laggards surrendered 15% in foregone annual revenue in 2018 and stood to miss out on as much as 46% in revenue gains by 2023 if they did not change their enterprise technology approach. Based on a survey of more than 8,300 organizations across 20 industries and 20 countries. Source: Accenture (2019) →
- In the Flexera 2025 State of ITAM report, respondents reported roughly 33% of SaaS spend is wasted, underscoring how paying for off-the-shelf seats and tiers that go unused erodes the supposed cost advantage of generic SaaS. Source: Flexera (2025) →
- Acquiring a new customer is five to 25 times more expensive than retaining an existing one, and research by Frederick Reichheld of Bain & Company found that increasing customer retention rates by 5% increases profits by 25% to 95% - underscoring the ROI of support that keeps customers. Source: Harvard Business Review / Bain & Company (2014) →
Frequently asked questions
How long before a custom permit system is usable on real moves?
Twelve to sixteen weeks for a first release covering configurations, move files and permit assembly, then six to twelve months for the full platform. The schedule risk sits on your side rather than the developer side, because rule capture depends on structured time with the one or two people who hold the curfew, escort and jurisdiction knowledge nobody has ever written down.
Who owns the code and the permit archive if an agency builds this?
You should own the repository, the infrastructure accounts and the right to hire another firm, agreed before kickoff. Treat the move file archive as a separate clause, because it holds permits, amendments, routes as issued and crew acknowledgements, and it is your evidence if a structure is struck or a citation is issued. Evidence you cannot reach without a supplier cooperating is not evidence you control.
Should we automate submission to state permit portals?
Phase two at the earliest. States differ enormously in what they expose, several offer no interface at all, and the automated ones change without notice, which makes portal integration the least stable part of the entire build. Automate submission only where a state offers a documented interface and your volume there justifies the ongoing maintenance it will demand.
Can we keep our permit service and still build something?
Yes, and for most carriers that hybrid is the right answer. Leave issuance with the service in jurisdictions where they are efficient, and build the coordination layer that no service sells: your configuration catalogue, the move file, restriction rules, escort and crane scheduling, and the archive. That is where the losses and the key person risk actually sit.
What is the difference between a routing tool and a permit system?
A routing tool finds a legal path for a vehicle profile and tells you the miles. A permit system manages the commercial and regulatory process around a specific movement: applications per jurisdiction, amendments, escort and curfew rules, resource bookings and the evidence file. Carriers frequently buy the first, discover the second was the actual problem, and end up coordinating from a spreadsheet regardless.
Do we have to license road network data, or can it be built?
License it. Commercial road network data with structure attributes carries an ongoing cost that belongs in your budget from the start, and assembling your own network creates a maintenance obligation with no competitive value whatsoever. Your engineering effort belongs in the configuration logic and the restriction rules that sit on top of it, which is the part specific to how your equipment moves.
What happens if our permit manager retires during the build?
It becomes considerably more expensive, which is an argument for starting sooner rather than for waiting. Sequence rule capture first, record the sessions, and put a second coordinator in every one of them. If that knowledge leaves undocumented, the next hire spends roughly a year rebuilding it through mistakes that happen on live moves rather than in a meeting room.
Can software perform bridge analysis for superloads?
Not in the sense of replacing it. For superloads the structural review is a state engineering process you participate in, not a calculation you run in house. What software does well is model your axle configuration accurately so the submitted data is correct first time, and track the review as a workflow with an expected duration so downstream escort and crane bookings reflect reality rather than optimism.
Can the same system handle Canadian provinces?
Yes, and it should if you run cross border, but price it as separate scope rather than as an extension. Provincial rules, forms, escort requirements and seasonal load restrictions differ from state practice, and spring thaw restrictions in particular have no clean equivalent south of the border. Adding provinces after launch is normal and costs a rule set each.
Will this reduce the number of permits we need?
Sometimes, and that is the underrated benefit. When your configuration catalogue is modelled properly, a planner can compare builds and find one that stays inside a threshold in a given state, which removes a permit or drops a superload into ordinary oversize territory. It will not remove state fees or invent a route that does not exist, so treat any saving as a bonus rather than as part of the business case.
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.
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.
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.
What should I prepare before contacting a software development agency?
A one-page brief beats a 40-page requirements document: the business problem in plain words, who will use the system, the 5 to 10 workflows it must handle, the tools it must connect to, and your budget range and deadline driver. You do not need wireframes, a specification, or technical vocabulary; producing those is the agency's job during discovery. Stating a budget range up front is the single best move, because it gets you honest scoping instead of a quote engineered to win the meeting.
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.
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.
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.
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 Vivaan.
Senior Backend Engineer · Node · Delhi · 2 posts on the site
Published · Last updated .
