Professional Licensing Board Software: Custom Build vs Thentia and MyLicense

What the packaged licensing products actually do well

Six weeks before the biennial deadline, your registrar's team is clearing renewals while an investigator two floors away finalises a consent order. The licensee under that order renewed online last Tuesday without friction, because the renewal system has never heard of the case. That gap is the defining defect of board technology, and it is worth saying up front that most boards should still buy rather than build.

The market is small and the products in it are real.

• Thentia is the credible cloud entrant, and for a board wanting off an ageing on premise system without running a build it is the honest first call.
• MyLicense and the older state maintained databases underneath many boards do hold the licensee record, the renewal cycle and the fee accounting, and they have survived twenty years of statute because somebody kept configuring them.
• Accela is genuinely good software solving a real problem, and that problem is municipal permitting and inspections rather than professional discipline. Boards get pitched it regularly.
• Salesforce based implementations from public sector integrators can work where your requirement is largely case tracking with forms and payment.

What you get by buying is jurisdiction agnostic plumbing already written: online applications, payment gateway integration, renewal notices, fee schedules, and a support contract with somebody whose job is your uptime. Writing that from nothing to hit a statutory renewal deadline is a bad trade.

Where they stop: the licensure pathway is statute, not a dropdown

Take one applicant. They graduated from a programme that lost accreditation for two years, part of which overlaps their enrolment. They passed the national examination on the third attempt in another state. They completed 1,340 of the required supervised hours under a supervisor whose own licence lapsed for three months in the middle. They are applying by endorsement.

Every one of those facts triggers a rule in your statute or administrative rules, and the rules interact. A packaged product models this as an application form with document uploads and a reviewer checklist, which means the analysis happens in a human head and the record shows only the outcome. That holds until the applicant appeals and asks the board to explain the determination, or until the same pattern reaches a different analyst who reaches a different answer. Inconsistent determinations are how boards end up in court.

The second stopping point is enforcement. Complaints arrive from the public, employers, hospitals, other regulators and anonymous sources. They run through intake screening, investigation, expert review, probable cause, settlement and hearing, generating material that must never be visible to a licensing analyst. Boards conclude that separation requires separate systems. It does not. It requires field level access control on one record, enforced and logged, with an automatic hold that blocks renewal or new licensure while a matter is open. Two databases give you the problem you already have. A permissions checkbox gives you a breach.

Then there are the dated obligations nobody configures: adverse action reports to the National Practitioner Data Bank, nursing verification through Nursys, compact privilege data published to and consumed from other member states. These fire from a discipline outcome, and today they fire from a coordinator's calendar reminder.

The arithmetic: cost per licensee versus the cost to build

Modern licensing platforms price per licensee per year, sometimes bundled into a transaction fee added to the renewal. That second structure is worth pulling apart in procurement, because a fee charged to the licensee still shows up in your legislative hearings as the cost of your programme.

Put five years on the clock. On the buy side, add the annual platform cost across your licensee count, the implementation, and the change request queue. That queue is the line boards underestimate: every statutory change is a ticket, priced by the vendor, scheduled against other customers, and in an odd numbered year when your legislature moves you have no say over the date. Add the supplementary spreadsheets and small databases your staff keep alongside the product, because those are the honest measure of fit.

The crossover sits near 25,000 to 40,000 licensees for a single profession, and it arrives far earlier when you regulate several professions with different statutory pathways, sometimes at 8,000. Multi board agencies cross it first, because each additional profession multiplies rule complexity while the per licensee price only adds. Below the line, buy and configure carefully. Above it, you are paying subscription and change requests to approximate a statute you already own.

What a custom build actually costs

A focused first release covering the licensee record, online application and renewal with payment, and the continuing education audit workflow runs $80,000 to $180,000 and ships in 16 to 24 weeks. A full platform adding complaint intake, investigation case management with confidentiality controls, hearing and discipline workflow, public verification with a documented interface and databank reporting runs $250,000 to $600,000 phased across 9 to 18 months.

Data migration runs 10 to 25 percent of the build and regulators land at the top, sometimes above it. A legacy licensing database nobody has audited in fifteen years is always worse than the estimate: duplicate people, disciplinary actions recorded as free text, licence numbers reused after a purge in the 1990s. Budget for a records decision maker inside the agency who can rule on ambiguous history, because a developer cannot decide whether two records are the same nurse.

Budget 15 to 20 percent of the build cost every year from the second year. Statutory change is the recurring line, and a system where an administrator can version and effective date a rule without a code deployment keeps that number low. So does accessibility maintenance, since a public government service page has to meet the accessibility standard your jurisdiction imposes and retrofitting it later costs more than building it in.

The four situations where building wins

• Regulatory fit. Your licence types, equivalency routes, examination attempt limits, supervised hour requirements, endorsement and reciprocity rules and disciplinary procedure are set in law. When the configuration model cannot express them, you fund localisation, and localisation delivered as configuration stays fragile through every legislative session.
• Scale economics. Per licensee pricing across tens of thousands of people, multiplied by professions, is the arithmetic above.
• A workflow that is your competitive advantage. A regulator does not compete, so read this as public protection instead. If you want to ask whether complaints cluster around a supervisor, a facility or a training programme, that question prevents harm rather than punishing it, and no product ships it because no product holds your data that way.
• Integration sprawl across three or more systems. A state payment gateway, an identity provider, a fingerprint vendor channelling to the state repository, a records retention system and a national databank. Five boundaries, each with its own procurement timeline as well as its own interface.

None of these true means buy. One true usually means buy the licensing side and build only the enforcement layer.

How to decide in a week

Run the renewal hold drill rather than another demonstration.

• Day one. Take a licensee with an open matter and try to renew them in your current system. If nothing stops you, write down what would have stopped you and who that person is.
• Day two. Ask what your public verification page showed on a specific date six months ago. If the answer depends on an overnight export, you have a public safety defect rather than an inconvenience.
• Day three. Pull the last three statutory changes and price what each cost you in vendor change requests and staff workarounds.
• Day four. Take one hard endorsement application and write the determination as a reviewer would have to defend it at a hearing. Count the sources consulted.
• Day five. Send day one and day four to every vendor on your list and ask, in writing, how their product handles both.

If a vendor answers both in configuration and shows you the audit log, buy. If the answer is two systems or a checkbox, you already know.

Then fund a paid discovery phase rather than accepting a free proposal. Digital Heroes ends discovery with a signed product requirements document covering the licensee data model, confidentiality controls, rule versioning and acceptance criteria, and the agency owns it whether it builds with us or attaches it to a solicitation for other firms to bid against.

We are wrong for you if you need a team physically in your offices, if your procurement requires an existing statewide term contract we do not hold, or if you regulate one profession with a few thousand licensees, where a product is simply better value. What we are is more than fifty specialists, over 2,000 projects delivered, and a named team the agency meets before award rather than in month two. We run our own products, ShopScore, HeroCheckout and Section Vault, and our India LLP, US LLC and UK LTD entities mean the intellectual property assigns under your own jurisdiction rather than across a border. Check the record on Clutch, Trustpilot, Fiverr Vetted Pro and D-U-N-S before shortlisting us.

Book a 30-minute call with Digital Heroes and get a written plan and a fixed quote within 48 hours.