Thentia Alternatives for Licensing Boards and Regulators: When to Switch, When to Stay, When to Build

Why regulators start shopping for a Thentia alternative

Searches for a Thentia alternative usually start in one of three places: a renewal quote, a statute that will not fit, or a board member asking for a number the system cannot produce. Regulators are not impulsive buyers. Replacing a licensing system touches every licensee you oversee and every public record you publish, so nobody does it for entertainment. They do it because the last legislative session changed the fee schedule in a way the configuration cannot express, because the annual cost has climbed alongside the licensee population and someone has to defend it in a public meeting, or because a new programme was created by law with a compliance date and the honest answer from the roadmap was a future release.

There is a fourth reason people rarely say out loud. The system was implemented under a previous executive director, the configuration decisions were made in a hurry, and nobody currently on staff can explain why the licence types are structured the way they are. That is not a vendor problem, and switching vendors will not fix it. Work out which of the four you actually have, because three of them have different answers.

What Thentia genuinely does well

Thentia Cloud is built around the regulatory model rather than bolted onto a generic case tool, and that matters more than it sounds. Licence types, statuses, renewal cycles, continuing education requirements, complaints, investigations, discipline, and a public register are first class concepts rather than custom objects somebody added later. For a board with two or three IT staff and tens of thousands of licensees, starting from software that already understands what a renewal cycle is removes months of specification work you would otherwise pay for twice.

It is also a hosted product, which quietly solves the things small regulators are worst at: patching, backups, staying up during renewal season, and keeping a public register available when a hospital credentialing office needs it at midnight. If you are moving off a homegrown database that was maintained by one analyst who has since retired, a supported product with documented configuration is a real gain in resilience whatever else you conclude below.

Where a configured platform actually strains

The pressure point in every licensing platform, this one included, is that your enabling statute is unique and the product is shared. Configuration covers the common ninety percent: application intake, exam and education verification, renewals, late fees, CE audit, complaint intake, discipline outcomes. The last ten percent is where regulators live. Unusual reciprocity and endorsement rules, fee proration that follows a statutory formula, joint boards that share one licensee but not one process, tiered or provisional licences that expire on a rule rather than a date. Every one of those is expressible somewhere, and each one costs configuration effort, professional services, or a workaround that a future staff member will not understand.

Reporting is the second strain, and it is universal in this category. Boards need packets, legislatures need counts, and public records requests arrive with deadlines. Standard reports answer the standard questions. The one cross-cutting query the board chair wants, licensees by discipline status by county over five years, tends to be the one that needs an export and a spreadsheet. Third is integration burden. Exam vendors, background check providers, state payment and treasury rails, statewide identity and single sign on, and national verification services all need to be wired up, and each connector is a project with its own owner and its own failure mode.

Your realistic options, competitors included

The off the shelf field for occupational and professional licensing is small and well known. Tyler Technologies sells into this market, System Automation's MyLicense has a long history with state boards, GL Solutions serves regulators with a configurable platform, and a meaningful share of agencies now run licensing on Salesforce public sector or Microsoft Dynamics through a systems integrator. Each of those is a real option and each carries the same underlying trade. You inherit somebody else's regulatory model, you pay on their pricing basis, and your statute still has to bend at the edges.

The platform route deserves a specific warning. A Salesforce or Dynamics licensing implementation feels like custom because an integrator writes it for you, but you keep paying per user forever and you inherit platform limits and upgrade cycles you do not control. It is a legitimate middle path, not a free one. Price it over ten years, not three.

When staying put is the right call

Stay if your pain is implementation quality rather than product ceiling. A reconfiguration project with a competent partner is far cheaper and far less risky than a migration, and it fixes the most common complaint, which is that licence types and workflows were modelled badly at go live. Stay if you regulate a few thousand licensees, because at that size almost no build amortises. Stay if your procurement rules effectively require an established vendor with references from peer agencies, which is common for state boards. And stay if your renewal season already runs smoothly, since a licensing system that survives peak load without drama has earned more credit than most buyers give it.

When a custom build actually pays back

Build when the statute is the product. Umbrella agencies that regulate a dozen professions under different acts, boards with unusual multi-jurisdiction structures, and regulators whose compliance and discipline process is prescribed in law rather than chosen tend to spend years fighting a shared product. Build when you already operate a state identity platform, a payment rail, and a data warehouse that everything else must reuse, because then integration is your primary requirement and the licensing engine is secondary. Build when the reporting obligation, not the workflow, is the recurring pain, since owning the database turns a purchase order into a query.

There is a smarter middle option most agencies overlook. Keep the licensing system of record and build only the layer that hurts: a modern public register and verification API, a licensee portal that matches how your applicants actually behave, and a reporting warehouse fed from exports. That is the cheapest meaningful improvement available to most boards.

Migration reality for a licensing register

Licence history is a legal record, not a convenience. Plan the export before you plan the build: licence numbers and their full status history, discipline orders and their publication status, CE records, application documents, examination results, and payment history. Confirm what you get in machine readable form and what only exists as a report, because that gap is where migrations die. Then run parallel through one complete renewal cycle. Renewals are seasonal, they are when the system is stressed, and a system that behaves in February proves nothing about November.

Budget for retraining twice: your staff, and your licensees. Licensee facing change generates call volume, and call volume during renewal season is what turns a technically successful migration into a public failure. Keep the old public register reachable in read only form until the new one has been verified against it record by record.

Budget for a security and hosting review whichever path you take. State agencies increasingly expect evidence of independent assessment, and that expectation now applies to systems you build as well as systems you buy. It is a manageable cost when it is planned into the project from the start and a genuinely disruptive one when it surfaces two weeks before an intended go live date.

What each path costs

Configured products in this market are quoted, not published, usually on a basis that tracks licensee population plus implementation services. Assume the annual number grows as the professions you regulate grow. On the custom side, from Digital Heroes delivery experience: a focused build covering the public register, verification API, licensee portal, and reporting layer over an existing system of record runs roughly $45k to $110k in 8 to 14 weeks. A full licensing platform for a mid-size regulator, covering intake through renewal, CE, complaints, discipline, and integrations, runs roughly $150k to $350k over six to ten months. Add hosting, security accreditation work, and an internal owner in every year after that.

The honest recommendation

For most boards, the right answer is neither switch nor build. It is to fix the configuration you have, buy the reporting you are missing, and put a modern portal and register in front of it. Switch when the product ceiling is genuinely structural and a peer agency with your statute has already proven the alternative works. Build when your regulatory structure is unusual enough that every shared product will charge you to bend, when you have an internal owner who will still be there in three years, and when you can carry a full renewal cycle of parallel running without breaking your staff.