How Much Does Permitting and Licensing Software Cost in 2026?
Custom permitting and licensing software runs $60,000 to $400,000, and the decision that moves the number most is whether you replace the system of record or build only the layer that is failing.
On this page
Custom permitting and licensing software runs $60,000 to $400,000, and the decision that moves the number most is whether you replace the system of record or build only the layer that is failing. A full replacement carries the fee engine, the licensing module, cashiering integration, migration of fifteen years of records and a cutover that every department has to survive. A targeted build, meaning plan review routing and a real public portal sitting on top of the Accela or EnerGov backend you already pay for, fixes most of the daily pain for roughly $70,000 to $110,000 with no migration risk at all. Most agencies should price both before choosing.
The bands a permitting build falls into
A focused first release covering intake, an effective dated fee engine, parallel plan review routing and inspection scheduling for one department runs $60,000 to $130,000 and ships in 12 to 16 weeks in Digital Heroes delivery experience. A full platform adding contractor licensing, code enforcement cases, business licensing, geographic information system parcel integration, cashiering and the public portal takes the total to $150,000 to $400,000 phased across 6 to 12 months.
Sitting between those is the option most agencies never price: a partial build at roughly $70,000 to $110,000 that leaves your existing system as the system of record and replaces only the review routing and the public portal. That is the cheapest genuine fix in this category, it carries no migration risk, and it is what we recommend more often than full replacement. It is worth quoting even if you intend to replace eventually, because it tells you what the expensive parts of a replacement actually are.
What drives a permitting build up
Permit type count and fee formula complexity is the first driver. Twelve permit types with flat fees is a different project from forty types with valuation tables, square footage tiers, per fixture plumbing counts, technology surcharges and state surcharges routing to a different fund. Each formula is a rule with an effective date and an ordinance citation, and someone from your side has to confirm each one against the adopted schedule.
Geographic information system depth is second. Binding a permit to a parcel is straightforward. Binding it to a parcel with overlay districts, flood zones, historic overlays and annexation history through an Esri ArcGIS REST service, and handling what happens when the parcel layer is republished and geometries move, is a project inside the project.
Cashiering and financial integration is third, because Tyler Munis and CentralSquare Finance both have firm opinions about how a receipt posts and neither is negotiable from your side.
Legacy migration is fourth and is reliably underestimated. Fifteen years of records with attachments, incomplete parcel bindings and permits sitting in workflow states that no longer exist is four to eight weeks as its own workstream.
State reporting mandates are fifth, they vary widely by jurisdiction, and they are not optional.
What keeps the number down
The strongest lever is scoping to one department for the first release. Building intake, fees, routing and inspections for Building alone, then extending to Planning and Fire once the patterns are proved, costs far less than designing for all four disciplines at once, and it lets you learn the routing model on a real workload.
The second is migrating closed permits as read only searchable archive and bringing only open permits into the live workflow. Staff need to find old records, not to reopen them, and this single decision usually removes half the migration budget.
The third is deferring route optimisation. Publish fixed morning and afternoon windows for the first season and add drive time sequencing once you have your own historical duration data by inspection type, which is the input that makes optimisation worth anything.
The fourth is keeping payment handling out of your application entirely. Use a hosted payment page so card data never touches your systems, which keeps your scope small and removes an entire compliance conversation from the project.
A worked example that adds up
Take a city of about 90,000 people issuing roughly 6,000 permits a year across 22 permit types, with four review disciplines, currently running an ageing configured product plus a shared fee spreadsheet.
- Discovery, fee schedule modelling and workflow mapping with permit techs, plans examiners and inspectors: $10,000
- Application intake with permit type configuration, submittal checklists and document handling: $18,000
- Effective dated fee engine with valuation tables, ordinance citations, per line general ledger codes and a rendered calculation the counter can show an applicant: $26,000
- Plan review routing as a dependency graph with structured comments, re entrant cycles and statutory clock handling: $28,000
- Inspection scheduling with certification matching, same inspector continuity and an offline capable field app: $24,000
- Public portal showing cycle status, open comments and balance owed, built to WCAG 2.1 AA: $16,000
- Migration of open permits into live workflow plus closed permits as read only archive: $12,000
That totals $134,000, marginally above the first release band because four disciplines and 22 fee formulas are both at the heavy end. Publish fixed inspection windows for the first season instead of sequencing routes, saving $9,000, and archive only three years of closed permits rather than fifteen, saving $5,000, and the same project lands at $120,000.
How the spend phases
The first two to three weeks are fee schedule and workflow modelling, about a tenth of the budget, and the output is a written specification rather than screens. Bring a page of your adopted ordinance with a valuation table and a mid year amendment to the first session. A developer who has done this asks about effective dates, general ledger codes and which schedule applies at submittal versus issuance within the first ten minutes.
The middle stretch delivers intake, the fee engine and the routing model. The fee engine should be provable early: run last quarter's issued permits through it and compare every calculated fee against what was actually charged. Differences at that point are the most useful thing the project produces, because each one is either a defect in the new engine or a fee your staff got wrong under the old spreadsheet.
The last stretch is inspections, the portal and migration. Plan three to four weeks of parallel running where both systems accept applications. Inspectors adopt fastest because the field app removes work from their day. Permit techs take longer, because their muscle memory is the workaround, so training should target the fee engine and the routing where the behaviour actually changes.
The ongoing costs nobody quotes
Fee schedule maintenance is the standing item and it is the reason to own the engine. Your council will amend the schedule, and if a supervisor can enter a new version with its effective date and see which in flight applications are affected, the annual cost is staff time. If it needs a developer, every amendment is a change request.
Parcel layer drift is second. Your county assessor republishes, geometries shift, new subdivision lots exist before their parcel numbers do, and something has to reconcile that rather than silently failing.
Accessibility regression is third and is specific to public sector work. A portal built to WCAG 2.1 AA does not stay conformant through two years of small changes without periodic auditing, and this is enforcement risk rather than good practice.
Records retention is fourth. Every comment, markup and status change in this system is a public record with a retention schedule, and public records request handling has an operational cost regardless of the software.
Then hosting and support at 15 to 20 percent of build cost per year, which for most agencies is still a fraction of the subscription being replaced.
Comparing a build against your current renewal
Start with the renewal invoice, not the list price. Add whatever you pay an implementation partner on retainer to keep workflow configuration alive, because that retainer is part of the true cost of the product and agencies routinely leave it out of comparisons. Add module fees for anything you were told was included and later were not.
Then price the labour the product is not doing. Count the permit techs retyping applicant data between systems and value it at loaded salary. Count the inspection supervisor rebuilding routes by hand every afternoon. Count the front counter calls asking where a permit is, which is the single largest call category at every counter we have measured with clients, and value the tech time answering them.
Then add the number that gets a city manager's attention, which is fee correction and refunds. Pull last year's manual fee overrides and refunds from your finance system. If your multipliers have drifted from the adopted ordinance, that is money you gave back or money you failed to collect, and it is directly attributable to the fee schedule living in a spreadsheet.
If your renewal alone is approaching the annualised cost of ownership over five years, you are financing someone else's roadmap. If it is comfortably under and the product covers your workflows, stay.
When buying beats building
Buy if you issue under about 1,500 permits a year, run one or two review disciplines and your fee schedule fits on a page. OpenGov Permitting and Licensing or CityView will serve you properly at that scale, and the money is better spent scanning your file room and getting your records searchable. We give that answer regularly and we mean it.
Buy if your problem is staffing rather than software. A department that cannot keep a second plans examiner will not be rescued by a new system, and a build will consume the staff attention you do not have.
Buy if your current product works and only the portal is hated. In that case do not replace anything, build the portal layer on top and keep the backend.
Build when the signals stack: you pay a partner a retainer purely to keep configuration alive, your fee schedule needs effective dated versioning and staff override fees by hand, you run more than four review disciplines with genuine dependencies, you are annexing or merging departments or running shared services across jurisdictions that off the shelf products treat as separate tenants, or your renewal has reached a number where three years of it buys the platform outright. Two or more of those, and a build earns its place. One of them, and you should be pricing the partial build instead.
When you are ready to turn this into a specification, Digital Heroes builds and runs its own products, so the people choosing your architecture live with those decisions on their own revenue. 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.
- 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) →
- An independent Forrester Total Economic Impact study of OutSystems found a 363% three-year ROI with payback in under 6 months, illustrating that faster, lower-labor build approaches can materially shift the payback math. Source: Forrester Consulting (commissioned by OutSystems) (2024) →
- A study (led by Prof. Pak-Lok Poon, published in Frontiers of Computer Science, 2024) reviewing decades of spreadsheet-quality research found that about 94% of spreadsheets used in business decision-making contain errors, illustrating the hidden risk of manual spreadsheet workarounds that custom software is built to replace. Source: Central Queensland University / phys.org (Prof. Pak-Lok Poon et al.) (2024) →
- In an RCT, text-message reminders (11.7% missed) were non-inferior to telephone reminders (10.2% missed; difference not significant, within the 2% non-inferiority margin) but far cheaper - total cost EUR 230 for SMS versus EUR 8,910 for telephone over 6 months - making SMS more cost-effective. Source: BMC Health Services Research / PubMed Central (Junod Perron et al.) (2013) →
Frequently asked questions
What does custom permitting software cost for a mid sized city?
A focused first release covering intake, an effective dated fee engine, plan review routing and inspection scheduling runs $60,000 to $130,000 over 12 to 16 weeks in Digital Heroes delivery experience. A full platform adding contractor licensing, parcel integration, cashiering and the public portal takes the total to $150,000 to $400,000 over 6 to 12 months.
Permit type count and fee formula complexity drive the number more than permit volume does. Twenty two types with valuation tables costs more than 6,000 permits across twelve flat fee types.
What are the annual running costs?
Budget 15 to 20 percent of build cost per year for hosting, support and enhancement, which for most agencies is still well under the subscription being replaced. The recurring items specific to permitting are fee schedule maintenance, parcel layer reconciliation when your county republishes, and periodic accessibility auditing of the public portal.
Accessibility is the one agencies forget. A portal built to WCAG 2.1 AA does not stay conformant through two years of small changes without checking, and that is enforcement risk.
How long until inspectors and permit techs are off the old system?
A focused first release ships in 12 to 16 weeks, then plan three to four weeks of parallel running where both systems accept applications. Inspectors adopt fastest because the field app removes work from their day.
Permit techs take longer because their muscle memory is the workaround, so aim training at the fee engine and the review routing, which are the two places their behaviour actually has to change.
Is building cheaper than our Accela or EnerGov renewal over five years?
It depends entirely on your renewal number, so use the invoice rather than the list price, and add the implementation partner retainer that keeps your workflow configuration alive. Agencies routinely omit that retainer from comparisons and it is part of the real cost of the product.
If your annual subscription is under roughly $40,000 and the product covers your workflows, staying is the right financial call. If you are paying six figures a year and still routing paper between departments, three years of that spend typically exceeds a full custom platform you would then own.
Can we just replace the broken part instead of the whole system?
Yes, and this is our most common recommendation. Building custom plan review routing and a real public portal on top of an existing Accela or EnerGov backend runs roughly $70,000 to $110,000, fixes most of the daily pain and carries no migration risk.
Price it even if you intend to replace eventually, because the exercise tells you which parts of a full replacement are genuinely expensive and which you were assuming were expensive.
Why is legacy data migration such a large line item?
Because fifteen years of permits arrive with attachments, incomplete parcel bindings on older records and permits sitting in workflow states that no longer exist. In the worked example, migrating open permits into live workflow plus closed permits as archive came to $12,000, and cutting the archive to three years saved $5,000.
The saving comes from migrating closed permits as read only searchable records rather than reconstructing them. Staff need to find old permits, not reopen them.
What does an effective dated fee engine cost and is it worth it?
In the worked example the fee engine with valuation tables, ordinance citations, per line general ledger codes and a rendered calculation came to $26,000, the second largest item after review routing. It is worth it because your fee schedule is a legal document, not a configuration setting.
Each fee rule carries an effective from and effective to date and a citation, and every permit stores which schedule version priced it. An application submitted before a mid year amendment then prices under the old schedule permanently, without anyone overriding anything by hand.
How much does GIS parcel integration add?
Basic parcel binding is modest. The cost appears when you need overlay districts, flood zones and historic overlays through an Esri ArcGIS REST service, and when you have to handle the parcel layer being republished with shifted geometries.
Ask any prospective developer how they bind a permit to a new subdivision lot the assessor has not yet issued a parcel number for. If they have not hit that case, they have not shipped permitting software.
Do we own the code if we commission a permitting build?
You should own the repository, the database schema, the infrastructure configuration and the documentation, with no runtime licence back to the developer, and it should be explicit in the contract before kickoff. At Digital Heroes the client owns the code from the first commit.
Insist on a transition clause stating another firm can take over the codebase, and ask what the handover package contains before signing. A vendor who retains the code and licenses it back has recreated the dependency you are leaving.
How many people should be working on my software project?
A typical $40,000 to $150,000 build runs on three to five people: a technical lead, one or two developers, a designer, and someone owning QA and project communication, often as overlapping part-time roles. More bodies do not make software arrive faster; past a point they slow it down with coordination overhead. The question that matters more than headcount is whether one named senior engineer is accountable for the outcome.
How long does it take from first call to software my team can actually use?
Plan for four to six months: two to three weeks of discovery, two to four weeks of design, then a 10 to 16 week build with testing. In Digital Heroes delivery experience the schedule killer is not engineering speed but decision lag; a client who takes two weeks to approve wireframes adds two weeks to launch. Book a weekly 30-minute decision slot before kickoff and most of that risk disappears.
What is a discovery phase, and is it worth paying for separately?
Pay for it, and treat the output as yours. A discovery phase runs two to three weeks, typically 5 to 10% of the eventual build budget, and produces a written scope, wireframes, and a fixed quote you can take to any vendor, including a competitor of the agency that wrote it. Skipping it is how projects end up quoted from a two-paragraph email and delivered at twice the price.
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.
Is it cheaper to customize Salesforce than to build a custom CRM from scratch?
If you use less than a third of what Salesforce does, a custom CRM is often cheaper by year three. Salesforce Enterprise lists at $165 per user per month, so 25 seats cost about $49,500 a year before admin and consultant fees, while a focused custom CRM runs $60,000 to $100,000 once plus 15 to 20% a year in maintenance. If you genuinely need Salesforce's ecosystem, reporting, and app marketplace, customizing it beats rebuilding it; the mistake is paying enterprise prices to use it as a glorified contact list.
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.
Is a solo freelancer enough for my project, or do I really need an agency?
A solo freelancer is a fine choice for a well-defined build under roughly $15,000 to $20,000 with a limited lifespan: an internal calculator, a scripted integration, a prototype. Above $50,000, or for any system your business will depend on for years, you are buying continuity as much as code: enforced code review, cover when someone is ill, and support that outlasts one person's career plans. Price the risk of a single point of failure, not just the hourly rate.
Can custom software connect to the tools we already use, like QuickBooks, Stripe, and Google Workspace?
Yes, and connecting your existing tools is one of the main reasons to build custom: mainstream platforms like QuickBooks, Stripe, Shopify, and Google Workspace all publish documented APIs. Budget 1 to 3 weeks of work per integration depending on API quality and how much data flows in both directions. Ask any vendor whether they have integrated with your specific tools before, because quirks like QuickBooks' OAuth token handling and API rate limits get learned on someone's project, and it should not be yours.
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 software system?
Digital Heroes builds custom 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 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 .
