Welcome to Blogs
Discover actionable insights, in-depth research, and expert perspectives, all in one place.Custom Software Development 7 min read
Choosing a Development Partner for a Custom Licensing Portal: A Vendor Evaluation Guide for US City and County Revenue Department Leaders
| This article is part of our series on Custom Business License Portal Development for US Cities and Counties: Building an Application, Zoning Verification and Renewal Platform |
Introduction: Ask About the Spreadsheet
The most revealing question in a licensing portal vendor evaluation is what happens when a staff member exports a report to a spreadsheet.
A partner who understands this domain will distinguish what the public side may contain from what the confidential side may not, explain that the separation lives in the data model rather than a permission, and note that an export is exactly where a permissions-based design fails.
A partner who answers that permissions govern access has described a system in which a confidential figure reaches a spreadsheet, and the person who ran the report carries exposure that in several states is personal.
That five-minute question sorts a shortlist faster than anything else in a licensing portal vendor evaluation. Four more establish whether a partner understands the rest: the volume question, the referral problem, the verification question and the legacy data question. All five work on product vendors too.
Partner selection is the decision layer of the full custom software development guide to licensing portal development, whose surfaces are business and staff portals.
The Volume Question and the Referral Question
Ask what proportion of transactions in a typical licensing jurisdiction are renewals rather than new applications. A partner who has worked in this domain knows the answer is most of them and will say the two flows should be designed separately. One who describes a single application workflow with a renewal variant has not seen a filing deadline.
The follow-up: how should the system behave in the two weeks around a renewal deadline? A partner who raises load concentration unprompted is thinking about the right year.
Then ask how a referral to the fire department works when the fire department has no system that can receive one. The right answer accepts every mode, including an email and a printed packet, and focuses on the platform knowing what was sent and what came back rather than on an elegant interface.
A partner who proposes that all departments adopt the new system has described a project the revenue department has no authority to deliver.
And the question behind both: who has talked to those departments, and when.
What the Evaluation Should Establish
The Confidentiality Architecture
Not whether the partner can describe permissions, but how the public register, reporting and export are constructed so that confidential information cannot reach the public side.
Reviewed with the jurisdiction’s attorney, since the obligation is statutory and in several states personal. The obligations a partner must demonstrate they understand are set out in Taxpayer Confidentiality Statutes, Gross Receipts and Local Tax Remittance Rules, Secretary of State Entity Verification and Identity Proofing Duties.
Legacy Data Reality
Sample two hundred current records. Count duplicates, addresses that will not resolve to a parcel, classifications that no longer match the ordinance, and receivables nobody believes.
This sizes the largest item in the project and it can be done before any vendor conversation.
Referral Network Readiness
Which departments must participate, what each can actually receive, who has agreed to, and what the current waiting times are. The schedule driver, and an answer that requires other departments to commit.
The Tax Framework Position
The jurisdiction’s authority, its current rates and classifications, whether practice matches ordinance, and what appeal and assessment processes exist. Frequently surfaces divergence worth correcting regardless of procurement.
The Access Position
Current accessibility of the applicant experience, language coverage against the business community, and what happens today when verification fails. Obligations and failures that exist now.
Running the Evaluation in a Public Procurement
A municipal evaluation is governed by procurement rules, which shapes what is possible and what is wise.
A paid discovery or requirements engagement conducted separately, where procurement rules allow and with attention to whether it affects eligibility to bid, so that the specification is written by somebody who examined the legacy data rather than guessed at it. The estimate a partner should be able to defend is detailed in A 2026 Cost Model.
Evaluation criteria that follow from the requirements rather than from a generic template, with weight on domain understanding rather than on feature counts.
Demonstrations run against the jurisdiction’s own scenarios: a restaurant with four referrals, a sole proprietor with no entity record, a multi-location renewal, and a records request.
Reference conversations with other revenue departments, asking specifically about migration, about whether other departments actually participated, and about what the first renewal cycle was like.
Product vendors evaluated on the same criteria as build proposals, since the comparison is the point.
Contract terms covering ownership, source code access, documentation, continuity and data export. And an evaluation record sufficient to withstand a protest, which is a real consideration in this sector.
Reading the Recommendation
Adopt a product when it expresses your tax structure and handles the confidentiality separation properly, which for most jurisdictions it will, and particularly where a suite covering permitting and code enforcement would place the referral departments in one system and remove the hardest problem entirely.
Adopt a product and build the integration layer when the gap is connection to the jurisdiction’s own geographic, finance or identity systems rather than licensing functionality.
Build when the tax structure is genuinely unusual, when licensing is a major revenue function with a real audit operation, or when the jurisdiction administers for several ordinances at once.
Fix the data without new software when the record sample shows the current system is adequate and the problem is twenty years of accumulated inaccuracy, which happens and is the cheapest outcome.
One consideration whichever path is chosen: the legacy data findings, any ordinance divergence and any accessibility gap are live now and worth addressing this year.
A partner who recommends a product and documents why has given a director what they need for a council and a procurement file.
The Remaining Domain Questions
Two questions remain and both are about people rather than technology.
Ask what happens when an applicant is a sole proprietor with no state entity record and no credit file. The right answer is that automated verification is a convenience and a documented human alternative exists. A partner who treats a verification failure as a fraud signal will build a system that turns away exactly the small businesses the department spends effort trying to register.
Ask what the zoning lookup does when the answer is unclear. The right answer is that it presents information with its limits and routes the determination to planning. A partner who describes an approve or deny outcome has proposed that software make another department’s decision using data that cannot support it.
And one last signal worth weighting: ask when they last sat at a business license counter. The answer tells you whether they have watched somebody try to comply.
Red Flags
A fixed price before the legacy data is sampled. Migration priced as a line rather than a workstream. No conversation with the referral departments. Confidentiality described as a permission model. Accessibility scheduled as a testing phase. No product comparison. Annual operating cost absent from the figures.
And the ones that should end the conversation: a zoning lookup that approves or denies; a verification failure treated as a fraud indicator with no alternative path; predictive scoring of businesses for enforcement attention; any feature targeting by neighborhood or owner characteristic; automated liability determination; and any suggestion that the license confirms other approvals were obtained.
The strongest positive signal is a partner who asks to see a sample of your current records before quoting anything.
Conclusion
Ask about the spreadsheet first, since the answer separates partners who understand the confidentiality obligation from those who have only read about permissions.
Sample your legacy records before any vendor conversation, because that is the largest item and you can size it yourself. Talk to the referral departments early, since their participation is the schedule. And evaluate the suites seriously, because one covering permitting removes the hardest problem in this project.
That is a fair standard for any licensing portal vendor evaluation, and for the software companies in the United States on your shortlist.
If you are selecting a partner, asking each one what happens when a staff member exports a report to a spreadsheet is the five minutes that will sort your shortlist.
Frequently Asked Questions
Why is the spreadsheet question so revealing?
Because an export is exactly where a permissions-based design fails. A partner who answers that permissions govern access has described a system in which a confidential figure can reach a spreadsheet.
What should a partner say about renewal volume?
That most transactions in a typical jurisdiction are renewals and the two flows should be designed separately. One who describes a single workflow with a renewal variant has not seen a filing deadline.
What is the right answer on referrals?
Accept every mode, including an email and a printed packet, and focus on the platform knowing what was sent and what came back. Proposing that all departments adopt the new system describes a project revenue cannot deliver.
How do you size the legacy data problem yourself?
Sample two hundred current records and count duplicates, addresses that will not resolve to a parcel, classifications no longer matching the ordinance, and receivables nobody believes. No vendor needed.
What should a demonstration be run against?
The jurisdiction’s own scenarios: a restaurant with four referrals, a sole proprietor with no entity record, a multi-location renewal and a records request.
When is the cheapest outcome available?
When the record sample shows the current system is adequate and the real problem is twenty years of accumulated inaccuracy. That is a data project rather than a software one.
What should happen when verification fails?
A documented human alternative. A partner treating a verification failure as a fraud signal will build a system that turns away exactly the small businesses the department wants registered.
Which answers should end the conversation?
A zoning lookup that approves or denies, a verification failure treated as fraud with no alternative, predictive scoring of businesses, targeting by neighborhood or owner characteristic, automated liability determination, and any claim the license confirms other approvals.
Core Development
Keep exploring the custom services.
AI Software Development
Custom AI Software Development
Build intelligent, production-ready software from machine-learning models to AI-driven automation designed around your business goals.
Learn moreMobile App Development
Custom Mobile Application Development
Native and cross-platform mobile apps that are fast, secure, and built to scale across iOS and Android.
Learn moreWeb App Development
Custom Web Application Development
Scalable, secure web applications, from customer portals to complex dashboards, tailored to how your business actually works.
Learn more