Occupational Licensing Board Software: Build vs Buy for a State Regulator
Buy. A single board with one or two license types, a few thousand licensees and a stable practice act is exactly what Thentia and MyLicense were built for, and their configuration is genuinely deep.
On this page
Buy. A single board with one or two license types, a few thousand licensees and a stable practice act is exactly what Thentia and MyLicense were built for, and their configuration is genuinely deep. Building is the right call for an umbrella agency running boards with different statutes, or where routine legislative changes keep arriving as vendor change orders.
What Thentia, MyLicense, Versa and Tyler do well
Buying is the right call more often than a development firm will tell you, so take that first. If you are a single board with one or two license types, a licensee population in the low thousands, a statute that changes rarely and a disciplinary caseload you could describe in a meeting, buy. Thentia and System Automation MyLicense are built for precisely that shape and configure deeply enough that a rules analyst can work in them without a developer.
Versa Regulation is a reasonable fit for a mid-size regulator that wants a packaged enforcement workflow rather than assembling one. Tyler Technologies deserves serious consideration if your board already sits inside a Tyler estate, because integration cost frequently dominates the total in state government and nobody thanks you for a technically superior system that cannot reconcile to the same cash receipting the rest of the agency uses. GL Solutions has a long history in this market and remains worth a shortlist slot.
These products do the recurring work properly: application intake with document checklists and reviewer queues, renewal cycles with payment, public license lookup, and continuing education tracking. They handle the parts of the job that look the same across professions, and for most boards the parts that look the same are most of the job.
What buying gets you beyond features is a maintenance path you do not staff. A board with four employees and 3,000 licensees should not own a codebase. That is not a compromise, it is the correct allocation of public money.
Where they stop: nine hundred applications in flight when the rule changes
An application to your board is not a form with attachments. It is a decision tree written in statute and rule, with entry pathways that do not share requirements. An applicant by examination needs an approved program transcript, supervised hours signed by a qualifying supervisor, results transmitted from the testing vendor and a criminal history response. An applicant by endorsement needs primary source verification of an active license elsewhere, a discipline check and whatever equivalency your rule allows. A military spouse applying under your expedited statute needs a shorter set with a statutory clock attached. Each has its own definition of complete.
Packaged products model this as a form plus a checklist plus a queue. That holds until the legislature amends the supervised hours rule effective the first of January, and 900 applications are already in flight under the old requirements. A checklist has no honest way to evaluate both populations correctly, so staff either reprocess by hand or the board applies a rule to people it should not have, which surfaces at an appeal.
Three more places the packaged model strains. Renewal hold logic evaluated serially at the moment a licensee clicks, against whatever partner integrations happen to respond, is why your site crawls in the exact week it matters and why a renewal occasionally issues that should have been held. The separation between licensing and investigative records is implemented as role-based permissions on a shared record, which is correct for a sales system and wrong here, because roles drift and a respondent's counsel will one day ask in discovery who viewed the file and when. And compact participation, whether nursing, medicine, psychology, counseling or physical therapy, turns your board into a node in a network with outbound reporting obligations, alongside National Practitioner Data Bank submissions for health professions, which most legacy systems handle as a staff member retyping a signed order.
The arithmetic: cost per active licensee
Price both paths per active licensee per year, over a seven-year horizon rather than five, because agency systems live longer than commercial ones.
Worked example, with your own quote substituted. Say a packaged product is quoted at $5 per active licensee annually across 55,000 licensees, which is $275,000. Add renewal-season overtime, and add the change orders: if you have paid for three statutory amendments in the last three years, average them and put the annual figure in. Call the total $335,000, or about $6.10 per licensee.
The build side: a $450,000 phased platform amortised over seven years is roughly $64,000, plus support at 15 to 20 percent, so about $145,000 a year, which is $2.64 per licensee. The overtime does not vanish, but precomputed hold status removes the reason renewal week collapses.
Under roughly 15,000 active licensees on one or two license types, buy, and the arithmetic is not close. The crossover sits near 35,000 active licensees, or at four or more boards with genuinely different statutes under one umbrella agency, whichever arrives first. Below that, the deciding variable is not size at all. It is the rate at which your practice act changes compared with the rate at which your vendor will move.
What a custom build costs a public agency
From the public sector work Digital Heroes has delivered across more than 2,000 projects: a first release covering one profession end to end, meaning intake with a versioned rules engine, renewal with hold logic, payments and the public lookup, runs $90,000 to $200,000 and ships in 14 to 20 weeks. A full platform adding continuing education with a provider registry, complaint intake, investigation and hearing management, compact and data bank reporting, and legacy conversion runs $250,000 to $600,000 phased across 9 to 18 months.
Legacy data conversion runs 10 to 25 percent of the build and in this environment it reliably lands at the ceiling. Twenty or thirty years of license history carries duplicate person records created before you had a unique identifier, name changes recorded as new licensees, boards that merged, and disciplinary actions stored as free text in a notes field. Budget it as its own workstream with a reconciliation period where the legacy system stays readable, and have staff verify a sample of every high-risk record, meaning anyone with an action, a probation condition or an open case.
Year two runs 15 to 20 percent of build cost annually. In a regulator that pays for something specific: rule versions added each session, WCAG 2.1 AA conformance maintained as pages change, and an owner for the outbound reporting queue. Accessibility is cheap designed in and expensive retrofitted, so decide it at kickoff.
Four conditions that move a regulator to build
- Regulatory fit. Requirements need to be first-class objects with effective dates, so an amendment publishes as a new version and in-flight applications keep evaluating against the version live when they were filed. If your legislature touches your practice act most sessions, this single design decision is the whole argument.
- Scale economics. Past roughly 35,000 active licensees, or four boards with different statutes under one agency, per-licensee licensing plus change orders exceeds an amortised build inside the normal life of a state system.
- A workflow that is your own rather than the market's. Application turnaround is the thing legislators hear complaints about, and the pathways that create the backlog are written in your statute, not in a vendor's product plan. If you cannot change the requirement set without a release cycle, you cannot fix the queue.
- Integration sprawl across three or more systems. A testing vendor exam feed, a state criminal history response through an authorised channeler, a payment gateway that reconciles to treasury cash receipting rather than merely taking a card, a compact coordinated database, the National Practitioner Data Bank, and your state identity provider. Those are six problems with six failure modes.
How to decide in a week, before the next session
Monday, list every amendment to your practice act in the last three legislative sessions. Tuesday, mark each one as staff work or vendor work, and total what the vendor work cost in money and in months. If routine statutory change is arriving as change orders, you have your answer and the rest of the week is confirmation.
Wednesday, run the in-flight test. Ask your current or prospective vendor, in writing, how the system evaluates 900 pending applications when a requirement changes effective on a date, and how it evaluates 40 of those filed under an expedited pathway. A team that has done regulatory work answers with rule versions, evaluation date and replay. A team that has not answers with a configuration screen.
Thursday, ask your counsel one question: if a respondent's attorney demands a list of everyone who viewed an investigative file and when, can we produce it. If the honest answer is a permission matrix rather than an access log, that is a design problem no product setting fixes. Friday, run the per-licensee arithmetic and decide.
Whichever way it goes, start with a paid discovery on one profession and one pathway. The deliverable is a written rules specification your own counsel signs, covering pathways, requirement sets, hold conditions, retention schedules and acceptance criteria. At Digital Heroes no code is written until that document is signed, and the agency keeps it either way, which is what makes competing bids comparable.
We are wrong for you if you need a full enterprise replacement across a dozen boards in one procurement, or if your counsel wants a firm to interpret your statute. We are also wrong for a small single board, and we say so. Where we fit: more than fifty specialists, over 2,000 projects, our own products including ShopScore, HeroCheckout and Section Vault, and India LLP, US LLC and UK LTD entities so intellectual property assigns under your own law rather than a foreign one. You meet the named team before signing, and our record is checkable on Clutch, Trustpilot, Fiverr Vetted Pro and our D-U-N-S listing.
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.
- 48% of private companies cite integration with legacy systems or technical debt as a top obstacle to realizing the full value of their digital and AI investments (behind data quality/availability at 72% and gaps in AI fluency or technology talent/leadership at 53%). Source: Deloitte (2026) →
- Median SaaS spend reached $9,455 per employee, and organizations leave an average of 36% of their SaaS licenses unused. Source: Zylo (2026) →
- McKinsey found that currently demonstrated technologies can fully automate about 42% of finance activities and mostly automate a further 19%, indicating roughly 60% of finance work is technically automatable. Source: McKinsey & Company (2018) →
- 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) →
Frequently asked questions
How much does it cost to replace a licensing board's legacy system?
A first release covering one profession end to end, with a versioned rules engine for intake, renewal with hold logic, payments and the public lookup, runs $90,000 to $200,000 over 14 to 20 weeks in Digital Heroes delivery experience. A full platform adding continuing education, complaints, investigations, hearings, compact reporting and conversion runs $250,000 to $600,000 across 9 to 18 months.
How long does a licensing system build take from contract to first release?
Fourteen to 20 weeks for one profession. The schedule risk is almost never engineering. It is getting your rules written down, because pathways, requirement sets, equivalency provisions and hold conditions usually exist as staff knowledge plus a practice act, and turning that into a specification counsel will sign takes real weeks. Boards that already maintain written procedure manuals move noticeably faster.
Who owns the code if a state agency hires a firm to build its system?
The agency should own the repository, the cloud infrastructure accounts and the unrestricted right to bring in another firm, written into the contract before kickoff. At Digital Heroes the client owns all of it from the first commit. This matters more for a public buyer than a private one, because a procurement that leaves the code with a vendor guarantees a sole-source renewal five years from now.
Can we migrate twenty years of license history without losing disciplinary records?
Yes, but treat conversion as its own project with its own budget. The hard parts are duplicate person records created before you had a unique identifier, name changes recorded as new licensees, merged boards, and actions stored as free text. Plan a reconciliation period where the legacy system stays readable, and verify a sample of every licensee with an action, a probation condition or an open case.
What does interstate compact participation require from our system?
Compacts in nursing, medicine, psychology, counseling and physical therapy make your board part of a network rather than a standalone registry. You must determine and maintain primary state of residence, recognise privilege granted elsewhere, and push adverse actions to the coordinated database quickly. Build those as durable outbound messages with retries and delivery receipts so a partner state's question is answered with a transmission log.
Should continuing education evidence come from licensees or from providers?
From providers, wherever your rule allows it. Give approved providers a portal or an interface to submit completion rosters that post hours directly to a licensee ledger with the approval number and topic categories attached. Compliance then becomes a running balance rather than a year-end investigation, and your audit sample can be the size your rule actually intends rather than the size staff can process.
Can a custom system handle accessibility requirements for public-facing pages?
It should be scoped that way from kickoff. Most state policies now require WCAG 2.1 AA conformance for public-facing services, and it is inexpensive when designed in and expensive when retrofitted after a complaint. Include it in acceptance criteria with named testing, rather than treating it as a late quality assurance pass, and confirm your specific state policy with your agency's accessibility coordinator.
What happens to renewal week if a partner agency integration times out?
In a system that evaluates holds serially at the moment a licensee clicks, the renewal either fails or issues when it should have been held. The fix is to precompute: a nightly job evaluates every active license against hold rules and writes a status with a reason code and timestamp, so renewal reads an answer rather than making six network calls. Intraday changes republish for that licensee only.
Can we keep our current product and build only the rules engine?
Often yes, and it is the cheapest honest path for a board that is otherwise content. Keep renewal, payments and the public lookup where they are, and build eligibility determination as its own service with versioned requirement sets and effective dates. The bridge back into the incumbent carries only a decision and a reason code, which also keeps your investigative separation clean.
What is the difference between configuring a product and owning a rules engine?
Configuration lets you change values inside shapes the vendor anticipated. A rules engine lets your own analyst define a new requirement type, attach an effective date and publish it without a release cycle. The distinction only matters when your legislature writes something the vendor did not anticipate, which is exactly when it matters a great deal and when hand processing quietly begins.
Should I ask for a fixed price or pay the agency hourly?
Fixed price for the first version, hourly or retainer for what comes after launch. A fixed-scope, fixed-price V1 puts the estimation risk on the agency, which is exactly where you want it while trust is unproven; hourly billing on an unscoped greenfield build is a blank check. After launch, flip it, because maintenance and small features arrive unpredictably and fixed-pricing every ticket wastes everyone's time.
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 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 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.
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 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.
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.
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.
How do I work out whether custom software will pay for itself?
Do the arithmetic on hours before anything else: if the system saves three staff eight hours a week at a $35 loaded hourly cost, that is about $43,700 a year against, say, a $70,000 build plus 15 to 20% annual maintenance, a payback around two years. Add revenue effects only if you can name them specifically, like faster quotes or fewer abandoned orders, not as vague growth. In our delivery experience the businesses that see payback inside 24 months are the ones automating a process they already measure.
What should I have ready before I contact a development agency?
Three things, none of them technical: a one-page description of the problem in your own words, a list of the tools and spreadsheets the new system must replace or connect to, and a must-have versus nice-to-have split of features. Add a budget range, even a wide one, because it changes the conversation from fantasy to engineering. You do not need a formal specification; producing that is what a discovery phase is for.
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 Liam.
Senior iOS Engineer · APAC · Sydney · 1 post on the site
Published · Last updated .
