How to Hire a Permitting and Licensing Software Development Company
Hand every shortlisted firm one page of your adopted fee ordinance with a mid-year amendment and ask them to model it. Anyone who asks about effective dates, GL codes and whether pricing follows submittal or issuance inside ten minutes has built this before.
On this page
Hand every shortlisted firm one page of your adopted fee ordinance with a mid-year amendment and ask them to model it. Anyone who asks about effective dates, GL codes and whether pricing follows submittal or issuance inside ten minutes has built this before. Expect $60,000 to $130,000 for a first release covering intake, the fee engine, review routing and inspections.
Replacing permitting software is like re-decking a bridge while traffic keeps crossing. You cannot close the counter for four months, the statutory review clocks keep running whatever state your systems are in, and the people crossing are contractors who will tell every builder in the county what the experience was like. The failure mode is rarely a crash. It is a permit tech quietly keeping the old spreadsheet because the new fee engine cannot express what the ordinance says.
What makes this category hard to buy is that your fee schedule is a legal document, your review process is a set of statutory obligations, and your portal is public-facing government. Most development firms treat all three as configuration. They are not. A fee rule has an effective date and an ordinance citation. A resubmittal restarts part of a clock and not the rest. And a form-heavy public portal that has never been through a screen reader audit is an enforcement exposure your city attorney will hear about before your IT director does. None of that shows in a demo built on a fictional building department.
What a permitting and licensing development company actually does
The visible build is an application form, a status page and an inspector app. Call that a third of the work.
The rest is where agencies get hurt. They model the fee schedule the way your ordinance does, with each rule carrying an effective from and effective to date, a citation to the section it comes from, and a GL account and fund on every line so cashiering reconciliation becomes a query rather than a monthly argument with Finance. They model plan review as a directed graph rather than a linear workflow, so cycle two reopens only the disciplines that issued comments and preserves the approvals that already cleared. They bind permits to parcels through your Esri ArcGIS layer and handle the case your data will produce in month one, which is a new subdivision lot the assessor has not created an APN for yet. They treat every comment, markup and status change as a public record with a retention schedule, which forces an append only design with no hard deletes. And they build the portal to WCAG 2.1 AA from the first screen rather than retrofitting it.
What it really costs in 2026
| Scope | Cost band | Timeline |
|---|---|---|
| Layer on your existing Accela or EnerGov backend: review routing plus a real public portal | $70,000 to $110,000 | 10 to 14 weeks |
| First release: intake, effective dated fee engine, parallel review routing, inspection scheduling, one department | $60,000 to $130,000 | 12 to 16 weeks |
| Full platform: contractor licensing, code enforcement, business licensing, GIS binding, cashiering, portal | $150,000 to $400,000 | 6 to 12 months |
| Legacy migration as its own workstream | $25,000 to $60,000 | 4 to 8 weeks |
| Annual ordinance updates and support | 15 to 20 percent of build a year | Retainer |
Two line items are almost always absent. The first is accessibility. A public-facing permitting portal is form-heavy, table-heavy and deadline-driven, which is the hardest kind of interface to make conformant, and building to WCAG 2.1 AA from the start costs a fraction of retrofitting it after a complaint. Ask for a real audit report against a form-heavy application before you believe anyone.
The second is records and retention design. Every plan review comment, every markup, every status change and every uploaded sheet is a public record subject to your retention schedule and to public records requests. That means append only storage, attributed corrections instead of edits, and an export path that produces a defensible package. Firms that have only built private-sector software price this as logging. It is a compliance surface. One procurement detail to carry into your evaluation: incumbent platforms price per module and per named user, and the annual figure most agencies quote to their council omits the retained implementation partner needed to keep workflow configuration alive after go live.
Signals of a strong partner
- They ask which schedule applies at submittal versus issuance. That question in the first meeting means they have modelled a real fee ordinance.
- They describe review as a graph with dependency edges. Engineering waiting on Planning, Fire waiting on a deferred sprinkler submittal, and cycle two reopening only the open disciplines.
- They have hit the missing APN problem. Any firm that has shipped permitting knows what happens when a parcel layer is republished and geometries shift underneath live permits.
- They treat comments as structured records. Code section, sheet number, status and a threaded applicant response, rather than a paragraph in a PDF correction letter.
- They can show an accessibility audit report. Run with an actual screen reader against a form-heavy application, not an automated scanner summary.
- They name your financial system. Tyler Munis and CentralSquare Finance both have firm opinions about how a receipt posts, and a firm that has integrated one will say which.
- They propose a parallel running period. Three to four weeks of both systems taking applications before cutover, with the fee engine reconciled line by line.
Red flags
- The fee schedule will be made configurable. That sentence means you will be the one configuring it, and your permit techs will be overriding it by month two, which is how you get an audit finding.
- Workflow demonstrated as a straight line. A sequential approval chain cannot express a resubmittal that reopens two disciplines and preserves three approvals, so your staff will route by email instead.
- No question about records retention or public records requests. A firm that has not asked treats your permanent legal record as application logging.
- Accessibility described as a testing task at the end. Retrofitting conformance onto a finished portal costs several times building to it, and the retrofit rarely reaches the complex screens.
- They retain the code and license it back. You would be recreating exactly the dependency you are trying to leave, with a smaller support team behind it.
Questions to ask on the first call
- Here is a page of our fee ordinance with a mid-year amendment. Model it. Which schedule prices an application submitted June 28 and issued July 3?
- How does a resubmittal reopen only the disciplines that issued comments, and what happens to the statutory review clock?
- How do you bind a permit to a parcel when the assessor has not created an APN for the lot yet?
- What happens to live permits when our Esri parcel layer is republished and geometries move?
- Show me your accessibility audit report for a form-heavy application, run with a screen reader.
- How does a failed inspection generate the reinspection fee and hold the next inspection until it is paid?
- Which cashiering system have you posted receipts into, and how did GL coding per fee line work?
- Every comment and markup is a public record. How does your design handle retention, redaction and a records request?
- Who owns the repository, the schema, the infrastructure definitions and the documentation, and what does your transition package contain?
A simple way to decide
Do not choose from three RFP responses written against three different readings of your ordinance. Buy a paid discovery phase, typically three to five weeks and a small fraction of the build, and require one deliverable: a written specification your agency owns. It should include the fee engine model with effective dating and GL mapping, the review routing graph with dependencies and SLAs per discipline, the parcel binding approach and GIS scope, the migration decision on closed versus open permits, the accessibility standard and how it will be verified, the records retention design, and acceptance criteria another firm could build to. Written that way it becomes a procurement document your purchasing office can put in front of several bidders and get genuinely comparable prices back.
It also protects a decision many agencies should make: fixing the layer that is failing rather than replacing everything. Digital Heroes writes the specification before code as standard, contracts through an India LLP, a US LLC and a UK LTD so intellectual property assigns under your own law, and puts the repository in your accounts from the first commit. More than 2,000 projects, Fiverr Vetted Pro, verifiable through D-U-N-S, Clutch and Trustpilot. The specification is yours whichever way the award goes.
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.
- Senior executives report the highest average compensation among developer roles (e.g., $225K median in the US), and reported salary bands shifted downward year-over-year ($60-75K vs. $70-85K in 2023), underscoring how compensation varies sharply by role and location. Source: Stack Overflow (2024) →
- This analysis cites IDC research that companies lose 20-30% of revenue annually to inefficiencies caused by data silos, Gartner's estimate that poor data quality costs organizations at least $12.9 million per year on average, and a Salesforce benchmark that 80% of IT leaders say data silos hinder digital transformation - illustrating the business case for integrating systems. Source: Cherry Bekaert (citing IDC, Gartner, Salesforce, DATAVERSITY) (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) →
- SMS reminders that stated the specific cost of the appointment to the health system reduced missed appointments in Trial One, with the DNA (did-not-attend) rate falling from 11.1% (control) to 8.4% (specific-costs message) - an odds ratio of 0.74 (95% CI 0.61-0.89), i.e. roughly a 24-26% relative reduction - at no additional cost. (Trial Two replicated this at an 8.2% DNA rate.). Source: PLOS ONE (Hallsworth et al.) (2015) →
Frequently asked questions
How much does it cost to hire a permitting and licensing software development company?
Building custom review routing and a public portal on top of an existing Accela or EnerGov backend runs $70,000 to $110,000. A first release with intake, an effective dated fee engine, parallel review routing and inspection scheduling for one department runs $60,000 to $130,000 over 12 to 16 weeks. A full platform adding contractor licensing, code enforcement, GIS binding and cashiering runs $150,000 to $400,000.
What should we test a vendor with in the first meeting?
Hand them one page of your adopted fee ordinance including a mid-year amendment and ask them to model it out loud. A firm that has built permitting asks about effective dates, GL account codes, and whether pricing follows the submittal date or the issuance date within the first ten minutes. A firm that answers that it will be configurable is telling you your own staff will be maintaining it.
Does a public permitting portal have to meet accessibility standards?
Yes. A public-facing government portal needs to meet WCAG 2.1 AA, and permitting portals are unusually hard because they are form-heavy and table-heavy. Ask any prospective firm for an audit report run with a real screen reader against a comparable application. Building to the standard from the first screen costs a fraction of retrofitting it, and retrofits rarely reach the most complex screens.
How should legacy records from Accela or EnerGov be migrated?
Treat it as its own workstream of four to eight weeks. Migrate closed permits as read-only historical records that staff can search, and bring only open permits into the live workflow. The difficult parts are attachments, incomplete parcel bindings on older records, and permits sitting in workflow states that no longer exist. Splitting closed from open cuts most of the risk without losing anything staff needs.
Should we replace the whole system or fix the part that is broken?
Often just the broken part. Custom plan review routing and a genuine public portal built on top of your existing backend fixes most of the daily pain with no migration risk and no data conversion. Full replacement earns its keep when the fee engine itself is failing and staff override it manually, when you are consolidating jurisdictions, or when the renewal quote approaches the cost of ownership.
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.
Will custom software work with the tools we already use, like QuickBooks and Stripe?
Yes, and this is one of custom software's genuine advantages: QuickBooks, Stripe, Shopify, and most mainstream business tools publish documented APIs built for exactly this. Expect each standard integration to add one to two weeks of build time, and be suspicious of any quote that lists five integrations without asking what data flows in which direction. The hard cases are legacy systems with no API, which is a question to raise in discovery, not in week nine.
Will an app built for 10 users survive growing to 500?
Yes, if it is built on standard cloud infrastructure with a sound data model, because moving from 10 to 500 users is a hosting configuration change, not a rebuild. The scaling decisions that actually hurt are made early and invisibly: how the database is structured, how accounts and permissions are modeled, and whether background work is queued properly. Ask your agency how the system would handle ten times the load; the right answer is boring and specific, and a promise to cross that bridge later means you will pay for the bridge twice.
How much should a small business budget for its first custom app or website?
For a focused first build, most small businesses land between $8,000 and $60,000: roughly $8,000 to $45,000 for a custom website and $25,000 to $60,000 for an internal tool or simple web app, based on Digital Heroes delivery across 2,000+ projects. Customer-facing products with payments, logins, or a mobile app start around $40,000. Quotes far below these bands usually mean a template with your logo on it, not software shaped around your workflow.
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 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.
Our developer disappeared mid-project. Can another team pick up the code?
Yes, this is a routine engagement, provided the code exists somewhere you can access, so your first move is securing the repository, hosting, and domain credentials today. A takeover starts with a one to two week paid code audit that ends in one of three verdicts: continue the build, keep the design but rebuild the weak parts, or start over. Digital Heroes has inherited enough projects to say plainly that sometimes the rebuild is cheaper than the rescue, and an honest agency will tell you which one you have before taking your money.
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.
Does it matter which tech stack the agency wants to use?
Yes, but not in the way most buyers expect: the goal is boring, popular technology such as React, Node.js or Python, and PostgreSQL, because any future team can maintain it and hiring a replacement developer takes days, not months. The red flag is an agency-proprietary framework or an unusual language, which welds you to that one vendor no matter what your contract says about code ownership. A useful test: could you find three freelancers fluent in this stack within a week? If not, push back.
Should we build an MVP first or go straight to the full system?
MVP first, for almost everyone: ship the single workflow that carries the business value in 10 to 16 weeks, learn from real users, then fund phase two from evidence instead of guesses. The caveat is that an MVP is a small version of a well-built system, not a badly built version of a big one; the data model must already support what comes next. An agency that cannot tell you what they deliberately left out of your MVP has not designed one.
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 Ishaan.
Shopify Plus Tech Lead · Delhi · 2 posts on the site
Published · Last updated .
