Professional Certification Board Software: Custom Build vs Certemy
Buy. A board holding fewer than about 2,000 certificants on one eligibility pathway should run Certemy alongside a delivery vendor and spend the difference on accreditation readiness.
On this page
Buy. A board holding fewer than about 2,000 certificants on one eligibility pathway should run Certemy alongside a delivery vendor and spend the difference on accreditation readiness. Building earns its place past roughly 8,000 active certificants, or sooner if you issue several credentials with different pathways, because rule versioning and defensible audit sampling are what no packaged product models.
What the off-the-shelf credentialing products actually do well
Three thousand of your certificants fall due for recertification this quarter, a denial from March is under appeal, and the accreditation site visit is eight months away. Before you scope a build, understand that most boards this describes should buy, and we say that in procurement meetings where it costs us the work.
The products in this category are narrower than their marketing suggests, which is a good thing. Each does one job properly.
- Certemy tracks credentials and expiry across a population and chases the people who have gone quiet. If your core need is monitoring rather than issuing, it is the sensible purchase.
- Kryterion Webassessor, Prometric, PSI and Pearson VUE deliver examinations. Proctoring, test centre networks, security incidents and accommodation logistics are a specialist business, and none of them is a business you want to enter.
- Certiverse covers item development and exam publishing with a modern approach to job task analysis and form assembly.
- iMIS, Fonteva and YourMembership hold the association side: dues, events, communications and the member record most boards already run on.
Buy the exam vendor whatever else you decide. Boards that bring item banking and proctoring in house consistently regret it, and the security obligations alone are a reason to let a specialist carry them.
Where they stop: eligibility pathways and the recertification clock
Certification eligibility is rarely one rule. It is a degree plus supervised practice hours, or a longer experience route without the degree, or an equivalency for an internationally trained applicant, or a transitional route that closed to new entrants three years ago and still applies to people who started before the cutoff. Each pathway carries documentary requirements and each has edge cases that arrive by post on a Tuesday.
Packaged products model this as an application form with uploads and a reviewer checklist. The analysis happens in a human head, and the record shows only the outcome. That works until an applicant appeals and asks the board to explain the determination, or until the same fact pattern reaches a different reviewer who reaches a different answer.
The recertification clock is the second place they stop, and it is arithmetic everybody gets wrong. Cycles are anniversary based or fixed calendar based. First cycles are often prorated. There is a grace period, and a real difference between current, in grace, lapsed, expired and revoked, each with consequences for whether the person may use the credential and whether an employer sees them as verified. Then requirements change, and you have to decide who sits on the old rules and who moves to the new. That transition policy is a board debate that lasts a year, and a product with a single settings screen cannot hold both answers at once.
Underneath all of it sits one requirement no configuration screen satisfies: reproducing a decision made eighteen months ago under a rule set that has since changed. Accreditation through the National Commission for Certifying Agencies, or to ISO/IEC 17024 through a body such as the ANSI National Accreditation Board, rests on showing your processes ran as documented. Confirm the current standards with your accreditor rather than any summary, including this one.
The arithmetic: cost per certificant versus the cost to build
Credentialing platforms price per tracked credential holder, sometimes with a floor. That model is generous at 1,500 certificants and quietly punitive at 20,000, because your cost grows with the exact thing your board exists to grow.
Take your renewal number and add the staff time the product does not remove. In the boards we have worked with, that is 15 to 30 hours a month of coordinator time on audit administration and evidence chasing, plus the hours assembling an appeal file from three email threads, plus somebody reading a screen down a telephone every time a hospital wants to verify a credential before a shift. Fully load those hours. In mid sized boards the second number is regularly larger than the subscription.
The crossover sits near 6,000 to 8,000 active certificants on a single pathway, and it arrives far earlier, often around 3,000, if you issue three or more credentials with different eligibility rules. Below the line, buy and run the product properly. Above it, per certificant pricing compounds while a build does not, and the audit programme you quietly stopped enforcing because the volume defeated you starts costing you accreditation rather than money.
What a custom build actually costs
A first release covering eligibility pathways with versioned rules and structured decisions, application through authorisation to test, recertification cycle state handling, and continuing education submission with defensible audit sampling runs $65,000 to $140,000 and ships in 12 to 16 weeks. A full platform adding exam vendor integration and score reconciliation, appeals and disciplinary case workflow, approved provider catalogues, a public verification registry with an interface for institutional verifiers, and accreditation evidence reporting runs $160,000 to $400,000 phased across 7 to 12 months.
Data migration runs 10 to 25 percent of the build and boards land at the top of it. You hold decades of records in systems that predate anyone currently employed, and the real work is deciding what a historic status actually meant when the rules of that era differ from today's. A certificant recorded as lapsed in 2009 may or may not be lapsed under your current definition, and someone has to rule on that person by person for the ambiguous cases.
Year two onward runs at 15 to 20 percent of the build cost a year. That covers rule changes your board votes through, exam vendor interface changes, and accreditation cycle reporting. Rule changes are not defects. They are the ordinary business of a standards body, and a build that treats them as configuration rather than code keeps that number at the lower end.
The four situations where building wins
- Regulatory fit. If your accreditor has raised a finding on process consistency or records, or you expect one, defensibility is the product you are buying. Sampling executed by the system with a recorded seed and method, rule versions stamped on every evaluation, and notifications logged as delivered obligations turn a scramble into a query.
- Scale economics. Per certificant pricing across a growing population, compounded by several credentials, is the arithmetic above.
- A workflow that is your competitive advantage. For a board that is the pathway itself. If employers choose your credential because your eligibility routes recognise practice that others exclude, those routes are the asset and no vendor roadmap protects them.
- Integration sprawl across three or more systems. An association management system holding the member record, an exam delivery vendor issuing authorisations to test, a payment processor, and a public verification page that employers hit thousands of times a month. Four boundaries, and every failure lives at one of them.
None of these true means buy. One true usually means buy the products and build the single layer that hurts.
How to decide in a week
Run the reproduction drill rather than another vendor demonstration.
- Day one. Pick a denial issued eighteen months ago and reconstruct it: the rule version in force, the evidence considered, the reviewer, and the reasoning. Time how long it takes and note who had to be interrupted.
- Day two. Draw your last continuing education audit sample again and try to prove it was random. If the method lives in an undocumented spreadsheet formula, write that down as a finding before your accreditor does.
- Day three. Count how many distinct eligibility pathways you actually operate today, including closed transitional routes with people still on them.
- Day four. Ask a colleague to verify a credential as an employer would, then measure how many verification calls your office fielded that day.
- Day five. Send day one and day two to each vendor and ask, in writing, how their product answers both.
If both drills finish inside an hour, buy the product and keep your coordinator. If day one took a morning and involved a shared drive folder named final_v2, you have your answer, and so will the site visit.
Then commission a paid discovery phase rather than accepting a free proposal. Digital Heroes runs a paid discovery phase that ends in a signed product requirements document covering the credential lifecycle, rule versioning, permissions and acceptance criteria, and the board keeps that document whether it builds with us or hands it to another firm.
We are wrong for you if you want exam delivery and proctoring built in house, if you need a body physically in your office, or if you hold under 2,000 certificants on one pathway, where the subscription is simply better value. What we are is over 2,000 delivered projects and more than fifty specialists, with the named team introduced to your board before any contract. We run our own products, ShopScore, HeroCheckout and Section Vault, so our architects live with their own decisions, and we hold India LLP, US LLC and UK LTD entities so intellectual property assigns under your own law rather than across a border. Our record is checkable on Clutch, Trustpilot, Fiverr Vetted Pro and D-U-N-S.
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.
- Only about 30% of digital transformations succeed at meeting their objectives, but getting six critical success factors in place (leadership commitment, talent, agile culture, progress monitoring, clear strategy, and a modernized platform) raises the odds of success from 30% to 80%. Source: Boston Consulting Group (BCG) (2020) →
- McKinsey found personalization most often drives 10-15% revenue lift, and companies that grow faster drive roughly 40% more of their revenue from personalization than slower-growing peers. Source: McKinsey & Company (2021) →
- Workers can expect 39% of their existing skill sets to be transformed or become outdated over 2025-2030; 77% of employers plan to upskill their workforce, and 63% identify skill gaps as the biggest barrier to business transformation. Source: World Economic Forum (2025) →
- An analysis of enrollment and completion data for 221 MOOCs (Katy Jordan, published in the International Review of Research in Open and Distributed Learning, IRRODL, 16(3), 2015 - not the Journal of Distance Education) found completion rates ranging from 0.7% to 52.1%, with a median completion rate of 12.6%, and completion negatively correlated with course length (longer courses had lower completion rates) - underscoring how unsupported self-paced online courses struggle to finish learners. Source: Journal of Distance Education (via ERIC / Katharina Jordan) (2015) →
Frequently asked questions
How long does a certification board system take to build?
Twelve to sixteen weeks for a first release covering eligibility, applications, recertification state and continuing education audit. Appeals, disciplinary workflow, exam vendor integration and a public registry add another five to nine months. The schedule slips most often when the board has not settled a transition policy for a rule change, because engineers cannot write logic the board is still debating. Settle policy before kickoff.
Who owns the certificant records if the vendor relationship ends?
Settle it in writing before kickoff: the repository, the cloud accounts in the board's name, and the right to hire another firm. At Digital Heroes the client owns the code from the first commit. This matters more for a board than for most buyers, because you hold permanent records about people's professional standing and a dispute should never put those records beyond your reach.
Can we keep Kryterion or Pearson VUE for exam delivery?
Yes, and you should. Establish eligibility on your side, issue an authorisation to test with the window and attempt count derived from your own policy, transmit it through the vendor interface, and reconcile scores on return. The failures in this category live at that boundary: windows issued wrongly, retakes inside a waiting period, and accommodations approved in one system and never communicated to the other.
What happens to appeals filed under rules that have since changed?
They must be decided under the rules in force when the original determination was made, which is why rule versioning is not a technical nicety. Every evaluation should carry a stamp of the rule set applied, the evidence considered and the reviewer. Without that, your appeals process becomes file archaeology across email, and the reviewer defending it is guessing about a decision somebody else made.
Should we build our own exam item bank and proctoring?
No. Item banking, form assembly, psychometric analysis, proctoring and test centre logistics are a specialist industry with security obligations that dwarf the rest of your operation. Boards that bring it in house regret it, usually after the first security incident. Buy the delivery vendor, integrate cleanly, and put your build budget into the credential lifecycle that no vendor sells you.
What is the difference between an association management system and a certification platform?
An association management system such as iMIS or Fonteva holds membership, dues, events and communications. A certification platform holds eligibility, examination results, recertification cycles, audits and discipline. Many boards run both and let the association system own the person record while the certification side owns the credential. Trying to force one to do the other job is where most unhappy implementations start.
Can software handle certificants grandfathered under older requirements?
It can, and this is the single best test of whether a system was designed by someone who has worked with a standards body. Requirement changes should be versioned with a transition rule that assigns each certificant to a rule set, so you can run the cohort and see exactly who is affected before the board votes. A single settings screen cannot hold two live answers.
Should a board with 1,500 certificants build anything at all?
Almost certainly not a platform. At that size the honest recommendation is a monitoring product, a delivery vendor for the exam, a written and documented audit sampling method, and a coordinator with time to run it. Custom software becomes overhead you notice every year. Revisit the question when you add a second credential or pass roughly 6,000 active holders, not before.
How do we handle international certificants and credential equivalency?
Model equivalency as its own eligibility pathway with its own evidence requirements rather than as an exception a reviewer applies by judgement. Then add the practical constraints early: language of evidence, document authentication, and where personal data may be stored and transferred. Those constraints change architecture, so raise them in discovery. Retrofitting a data residency requirement after launch is expensive and avoidable.
Where does machine assistance genuinely help a credentialing board?
Two places. Extracting provider, date, hours and activity title from uploaded continuing education certificates so a reviewer confirms rather than keys. And anomaly detection, flagging the same certificate submitted by several certificants or hour totals that do not reconcile. Both surface candidates for a human. Neither should ever change a credential status on its own, because an incorrect finding against a professional record is a serious harm.
How do I vet a software development agency before signing a contract?
Ask to speak with two past clients whose projects resemble yours in size and industry, and ask exactly who will write your code, since some agencies sell senior faces and deliver junior or subcontracted hands. Demand a written specification with acceptance criteria before any fixed price, and check that their portfolio links to products that are actually live. An instant quote given without questions about your workflows is the clearest warning sign there is.
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.
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 do I make sure custom software is secure and compliant with rules like HIPAA?
Start with the baseline every business system should have: encryption in transit and at rest, role-based access control, and audit logs. If HIPAA applies, the hosting provider must sign a Business Associate Agreement, which AWS, Azure, and Google Cloud all offer, and access controls have to be designed in from day one, not bolted on. SOC 2 certifies a company's operating practices, not a codebase, so ask vendors what they have shipped in your regulated domain rather than which logos are on their website.
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.
We run everything on spreadsheets and Airtable. How do we know it's time for custom software?
The reliable signals are re-typing the same data into multiple tools, one employee acting as human middleware between systems, and errors appearing in handoffs between teams. Hard limits force the issue too: Airtable's Team plan caps at 50,000 records per base, and Business costs $45 per seat per month, so a 20-person team pays about $10,800 a year for a tool it has already outgrown. When workarounds consume more hours than the tools save, the spreadsheet era is over.
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.
How many people should be working on my software project?
Three to five for a typical focused build: a project lead, one or two engineers, a designer, and part-time QA, which is the standard shape across 2,000+ Digital Heroes projects. Larger platforms justify 6 to 10, but a ten-person team on a small first version usually signals bill padding rather than horsepower. What predicts success is whether a senior engineer is writing your code daily, not the headcount on the proposal.
We run everything on Airtable and spreadsheets. When is it time to go custom?
The switch usually makes sense when you hit one of two walls: Airtable's record caps (125,000 records per base on the Business plan) or logic the tool cannot express, like multi-step approvals with conditional pricing. There is also a simple cost signal: 25 people on Business at roughly $45 per seat per month is about $13,500 a year, forever, for a tool you are already fighting. Custom is worth it when the workflow is core to how you make money; for peripheral processes, staying on Airtable is the right call.
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 Oliver.
Senior Account Director · UK · London · 3 posts on the site
Published · Last updated .
