Permitting and Licensing Software: Build vs Buy
Buy. Under about 1,500 permits a year with one or two review disciplines, OpenGov or CityView will serve your agency and a build would be money better spent digitising your file room.
On this page
Buy. Under about 1,500 permits a year with one or two review disciplines, OpenGov or CityView will serve your agency and a build would be money better spent digitising your file room. The decision turns at roughly 4,000 applications a year across three or more disciplines, or the day your fee schedule needs effective dated versioning and your staff start overriding fees by hand.
What the off-the-shelf products actually do well
A contractor submits a residential addition at 4:47 on a Friday. Your permit technician opens it Monday, finds the site plan missing a setback dimension, and emails him. He replies Wednesday. The review clock started Monday, so a ten day statutory window is now seven days and nobody told the plans examiner. That story repeats in every building department, and it is worth saying plainly that the products in this market did not cause it.
Accela Civic Platform is the deepest system here and has been configured to run genuinely complicated agencies. Tyler Technologies EnerGov integrates with the financial system a great many cities already run, which removes a whole category of reconciliation argument. CentralSquare Community Development covers the same ground for public safety oriented agencies. OpenGov Permitting and Licensing and CityView are well built, opinionated and priced for departments that do not want a two year implementation, and Cloudpermit and Clariti are credible newer options. All of them handle intake, fees, inspections and a public portal out of the box, with state reporting formats maintained for you.
Most agencies should buy. If you issue under 1,500 permits a year, run one or two review disciplines and your fee schedule fits on a page, custom software is the wrong purchase and we will say so before quoting. The money does more scanning your file room and cleaning your parcel data, which you need either way.
Where they stop
The break is that your fee schedule is a legal document, and the products model it as current configuration. Your schedule is adopted by ordinance or council resolution, with effective dates, valuation tables, square footage tiers, per fixture plumbing counts, technology surcharges and state surcharges that pass through to a different fund. In Accela you configure fees through expression scripts. In EnerGov you build formulas in the admin console. Both work until your council adopts a mid year amendment effective 1 July and your ordinance says an application submitted 28 June but issued 3 July prices under the old schedule.
Because a fee is stored as configuration rather than as a versioned rule with a validity window, changing it changes it for everyone, including in flight applications. The workaround is a technician who knows to override manually, and the override becomes the audit finding. Ask any finance director who has had to explain a refund run how much they enjoyed it.
The second break is routing. A commercial permit needs Building, Planning, Fire, Engineering and sometimes Health and the water district. Some of those reviews are genuinely parallel and some carry real dependencies, and a resubmittal after a correction letter should reopen only the disciplines that issued comments while preserving approvals from those that cleared it. Configuring conditional parallel routing with dependency edges in the incumbent tools produces a workflow diagram nobody on your staff can maintain once the implementation consultant leaves. That is why so many departments quietly route by email and keep a paper slip. We have counted eleven hand-offs on one commercial tenant improvement in a city of 90,000.
The third break has a clock on it. Under the Federal Communications Commission shot clocks at 47 CFR 1.6003, a small wireless facility application carries a sixty day review window and a new build carries ninety, with a deemed granted consequence for missing it. A system that cannot show which discipline is holding a clock, per application, in real time, is not a reporting inconvenience.
The arithmetic on cost to build versus per permit licensing
Price this per application, because that is the unit your council understands.
Suppose your renewal is $180,000 a year and you retain an implementation partner for $45,000 to keep workflow configuration alive. Add hosted portal charges and the annual figure is around $235,000. At 6,000 applications a year that is roughly $39 an application, before any staff time.
Against a build: our first release band is $60,000 to $130,000 and the full platform $150,000 to $400,000, with year two at 15 to 20 percent of build cost annually. Three years of a $275,000 platform with support is roughly $360,000, against $705,000 for three years of the current arrangement.
The crossover sits between 3,000 and 5,000 applications a year once you have three or more review disciplines with real dependencies. Below 1,500 applications the subscription wins on every set of numbers, and it wins by enough that the second best use of a build budget still beats the build.
Two staff numbers belong beside those figures and usually decide it. First, retyping. Permit technicians who spend ninety minutes a day moving applicant data between three systems cost roughly $9,000 a year each in time nobody has as a line item. Second, windshield time. Inspection routes built by hand in a mapping app burn about forty five minutes a day per inspector, which across six inspectors is more than a full position of pure driving.
What a custom build actually costs
These are Digital Heroes delivery figures from work of this shape, not published sector averages. A focused first release covering intake, a fee engine with effective dated rules, parallel plan review routing with dependency conditions and inspection scheduling for one department runs $60,000 to $130,000 and ships in 12 to 16 weeks. A full platform adding contractor licensing, code enforcement cases, business licensing, geographic information system parcel binding, cashiering and the public portal runs $150,000 to $400,000 phased over 6 to 12 months.
Data migration is 10 to 25 percent of the build. Fifteen years of records with attachments, incomplete parcel bindings on older files and permits stuck in workflow states that no longer exist is four to eight weeks of its own. The pattern that works is migrating closed permits as read only history and bringing only open permits into the live workflow. Year two is 15 to 20 percent of build cost annually, covering hosting, the fee schedule amendment your council passes each year, and state reporting format changes.
What drives it up in this category: the number of distinct permit types and their fee formulas, since forty types with real valuation tables is materially more than twelve; parcel integration depth, because binding to an Esri ArcGIS layer with overlay districts, flood zones and historic overlays is a project inside the project; cashiering integration, since Tyler Munis and CentralSquare Finance both have opinions about how a receipt posts; and state reporting mandates, which vary widely and are not negotiable.
The four situations where building wins
One item here is a configuration argument you can take to your vendor. Two items is a council memo.
- Regulatory fit. Your fee schedule needs effective dated versioning with a citation to the ordinance section on every line, your portal must meet WCAG 2.1 AA under the Department of Justice web accessibility rule for state and local government, and every comment and status change is a public record with a retention schedule. Products that treat any of those as optional create exposure rather than convenience.
- Scale economics. You are past the applications per year crossover, or your renewal quote came back at a number that would buy the platform in three years while you are still routing paper.
- A model that is genuinely yours. You are annexing, merging departments, or running shared services across multiple jurisdictions. Every off the shelf product prices that as separate tenants and treats the jurisdictions as strangers, which is the opposite of what you are trying to build.
- Integration sprawl across three or more systems. The parcel layer, the finance system, a document repository such as Laserfiche, plan markup in Bluebeam Revu and the state contractor licence board. Once three or more are reconciled by hand, the reconciliation is already a system nobody owns.
How to decide in a week
Run a fee and routing test on live files rather than sitting through a demonstration.
Monday, take one page of your adopted ordinance containing a valuation table and a mid year amendment, and ask your permit technicians to price three real applications straddling the effective date. Time it, and note how many required a manual override. Tuesday, pull the five most recent commercial applications and count the hand-offs from intake to issuance, including every email and paper slip. Wednesday, take three resubmittals and check whether the second review cycle reopened only the disciplines that had issued comments. Thursday, pick ten permits at random and see whether the system can show which discipline is holding the clock right now. Friday, run the per application arithmetic above with your real renewal figure.
If the fees priced correctly without overrides and the routing held, buy and configure. That is the outcome for most departments. If overrides were needed and the hand-off count ran into double figures, you have your business case in writing and it took four days.
Before spending on a full replacement, price the partial. Custom plan review routing and a real public portal on top of your existing Accela or EnerGov backend is often a $70,000 to $110,000 project that removes most of the daily pain with no migration risk. We recommend that shape more often than a rewrite, and it is the smaller invoice.
If replacement is right, procure a specification first and the software second. Two to four weeks, fixed fee, ending in a written product requirements document covering the fee rule model with ordinance citations, the review graph with dependencies and clocks, parcel binding, records retention, accessibility conformance and acceptance criteria. You keep it either way, and it makes competing quotes comparable.
Where Digital Heroes is wrong for you: agencies under 1,500 permits a year, anyone wanting a vendor to host and operate the system indefinitely, and departments that cannot name one decision owner for fee interpretation. Development starts only after a product requirements document is signed. We contract through India LLP, US LLC and UK LTD entities so intellectual property assigns under your own jurisdiction, and our record is open on Clutch, Trustpilot, Fiverr Vetted Pro and D-U-N-S. Over fifty specialists, more than 2,000 projects, and the assigned team meets you before signing.
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.
- Per the Standish Group CHAOS 2020 report (reviewed at this URL), across tens of thousands of software projects roughly 31% end successfully, about 50% are 'challenged', and roughly 19% fail outright; small projects succeed far more often than large ones, and Agile approaches succeed at markedly higher rates than Waterfall. Source: The Standish Group (2020) →
- Standish's 2015 CHAOS research found roughly a third of software projects (about 36% by the Modern definition) fully succeed on time, on budget, and on scope, with top success drivers including executive support, user involvement, and clear requirements/business objectives. Source: Standish Group (CHAOS Report) (2015) →
- 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) →
- SaaS spend averaged $4,830 per employee (up 21.9% year over year), with large enterprises (10,000+ employees) spending roughly $284M annually and running about 660 apps, while organizations wasted an average of $21M annually on unused licenses. Source: Zylo (2025) →
Frequently asked questions
How long before inspectors and permit technicians 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 before cutover. Inspectors adopt fastest because the field application removes work from their day. Technicians take longer, since their muscle memory is the workaround, so aim training at the fee engine and the review routing where behaviour actually changes.
Who owns the code and the schema if we commission a custom system?
You should own the repository, the database schema, the infrastructure configuration and the documentation, with no runtime licence back to the developer, plus a transition clause saying another firm can take over. At Digital Heroes the client owns the code from the first commit. If a vendor retains the code and licences it back, you have recreated the dependency you were trying to escape.
What happens if our council amends the fee schedule mid year?
On a custom fee engine, nothing breaks. Each rule carries an effective from and effective to date and a citation to the ordinance section, and every application records the schedule version it was priced under, so a submittal from before the amendment prices under the old schedule permanently even if it issues months later. That is precisely the case most configured fee tools force staff to handle by manual override.
Can we migrate fifteen years of Accela records?
Yes, and budget four to eight weeks as its own workstream. The hard parts are attachments, incomplete parcel bindings on older records, and permits stranded in workflow states that no longer exist. Migrating closed permits as read only historical records and bringing only open permits into the live workflow cuts risk substantially without losing anything staff needs to search.
Should a small town issuing 900 permits a year build anything?
No. At that volume a subscription product plus good process will beat anything custom, and the vendor maintains your state reporting formats for you. Spend the money on scanning the file room and correcting parcel data, since both are prerequisites for any future system. Revisit if you consolidate services with a neighbouring jurisdiction, which is where off the shelf pricing starts to hurt.
Does a public permitting portal have to meet accessibility requirements?
Yes. A public facing government portal is expected to meet WCAG 2.1 AA, and this is an enforcement and litigation risk rather than a preference. Ask any developer whether they have run an audit with a real screen reader on a form heavy application and ask to see the report. Retrofitting accessibility onto a finished portal costs several times what building to it does.
What is the difference between permitting software and a licensing system?
Permitting is transactional and expires with the work: an application, review cycles, inspections, issuance and final. Licensing is a status held by a person or business over time, with renewals, continuing education, insurance certificates and disciplinary history. Products bundle them, which is convenient, but a licensing record that does not gate permit issuance in real time is the failure that reaches your city attorney.
Can we fix only plan review and the portal without replacing the whole system?
Often the best value, and we recommend it more often than a rewrite. Custom routing plus a real public portal on top of an existing backend is typically a $70,000 to $110,000 project with no migration risk, and it addresses the two things contractors and staff complain about most. Full replacement earns its cost when the fee engine itself is failing or you are consolidating jurisdictions.
Where does AI genuinely help, and where is it a liability?
It helps at intake, reading a plan set to flag missing sheets or unstamped drawings within minutes of upload, and reading insurance certificates and licence documents to populate records with low confidence extractions routed to a human. It should never interpret code, approve a plan or issue a permit. Any vendor offering automated plan review approval is selling you an appeal you will lose.
What happens if we cannot bind a permit to a parcel because the number does not exist yet?
It happens constantly on new subdivision lots the assessor has not created a parcel number for, and it is the question that separates developers who have shipped permitting from those who have not. The system needs a provisional parcel record tied to the plat, reconciled when the real number is issued. Ask specifically about this, and about what happens when the parcel layer is republished and geometries shift.
Who owns the code when an agency builds my software?
You should, completely, through a written intellectual property assignment that transfers everything on final payment; without that clause, copyright stays with whoever wrote the code by default. Insist that the repository lives in your own GitHub organization from day one and that hosting, domains, and third-party accounts are registered to you. Also check for licenses to the agency's proprietary frameworks buried in the contract, because those can make switching vendors practically impossible even when you own your own code.
What does a $50,000 custom software budget actually buy?
One core workflow done properly: 10 to 15 screens, two or three user roles, a couple of integrations, an admin panel, and automated tests, delivered in roughly 12 to 14 weeks. What it does not buy is that workflow plus a mobile app plus AI features plus five more integrations. The discipline of picking the one workflow that matters is what separates $50,000 projects that ship from $50,000 projects that stall at 70% complete.
How much should a small business expect to pay for custom software?
Across 2,000+ Digital Heroes projects, a small business system that replaces spreadsheets or one core workflow typically lands between $40,000 and $80,000, with more complex first versions running up to $150,000. The two levers that move the number most are integrations and user roles, not the team's hourly rate. Any quote under $15,000 for a full production system means the vendor has not understood your scope yet.
What happens if I stop paying for maintenance after launch?
Nothing breaks on day one, which is what makes it dangerous. Within 6 to 18 months, unpatched dependencies accumulate known vulnerabilities, an integrated API like Stripe ships a breaking change, and the first fix requires a developer to relearn a stale codebase at full price. Budget 15 to 20% of the build cost per year for upkeep; it is the difference between a $500 patch and a $15,000 emergency.
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 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.
What happens to my software if the agency shuts down or we stop working together?
Nothing dramatic, if the engagement was set up correctly: the code sits in your repository, hosting runs on your cloud account, and a handover document explains how to deploy and operate the system. Any competent replacement team can then take over in days rather than months. If the agency controls the repo, the servers, or the domain, fix that now, because renegotiating access during a dispute is the most expensive place to discover the problem.
Couldn't I just build my app in Bubble or another no-code tool instead of hiring an agency?
For validating an idea with real users, yes, and we tell clients that honestly. The walls come later: Bubble apps cannot be exported as code to run anywhere else, performance drops on complex data operations, and usage-based pricing climbs as you grow. A meaningful share of Digital Heroes custom builds are rebuilds of no-code MVPs that proved the business worked, which is the system operating as intended: validate cheap, then build the version that scales.
Does the tech stack matter, and which one should I ask for?
It matters less than agencies imply, provided it is boring. A mainstream stack, something like React or Next.js on the front end, Node.js or Python behind it, and PostgreSQL for data, means thousands of developers can maintain your system if you ever change vendors. Apply one test: ask how hard it would be to hire a replacement developer for the proposed stack, and walk away from anything built on an agency's in-house framework.
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
More from Mason.
Product Designer · Sydney · 1 post on the site
Published · Last updated .
