How to Shortlist ERP Vendors for a City or County in 2026 (Step-by-Step)
An 8-step guide to shortlisting ERP vendors for a city or county: requirements, knockout criteria, weighted scoring, scripted demos, references and TCO.
On this page
- How to shortlist ERP vendors for a city or county (quick answer)
- What is a government ERP vendor shortlist?
- Step 1: Confirm readiness and map your current processes
- Step 2: Build a cross-department selection team
- Step 3: Write requirements that actually separate vendors
- Step 4: Build your long list from the full public-sector ERP market
- Step 5: Choose your procurement path (RFP, cooperative contract, or piggyback)
- Step 6: Apply knockout criteria and a weighted scoring matrix
- Step 7: Run scripted demos built on your real pain points
- Step 8: Validate with independent references and total cost of ownership
- City vs. county: how shortlist criteria differ
- How long does municipal ERP vendor selection take in 2026?
- Government ERP vendor shortlist mistakes to avoid
- FAQ
- Start with the work before the RFP
To shortlist ERP vendors for a city or county, map your current processes, write government-specific requirements, and scan the full public-sector market. Then pick a procurement path, cut the long list with pass/fail gates and weighted scores, and test two or three finalists with scripted demos, reference calls, and total cost of ownership.
KCT advises cities and counties on ERP selection from a vendor-neutral seat. Below are the eight steps for 2026, each with an example pulled from a real city or county’s public records, including Cochise County, Siskiyou County, Linn County, and Los Altos.
How to shortlist ERP vendors for a city or county (quick answer)
Confirm you actually need a new ERP and map your current processes before talking to any vendor.
Form a cross-department selection team with clear decision rights, all the way up to council or the board.
Write prioritized, government-specific requirements and decide what’s in and out of scope.
Build a long list that covers both lanes of the public-sector ERP market.
Choose your procurement path: a formal RFP, a cooperative contract, or a piggyback.
Cut to a shortlist of three to five using pass/fail gates and a weighted scoring matrix.
Run scripted demos built on your own scenarios and pain points.
Validate finalists with independent reference calls and a multi-year total cost of ownership.
Each step gets its own section below, with what to do and a real city or county that did it.
What is a government ERP vendor shortlist?
Government ERP vendor shortlists are the small group of vendors, usually three to five, that a city, county, or other government organization invites into the deepest stage of evaluation: scripted demos, reference checks, and negotiation. Any vendor left off it is out of the running, which makes the shortlist the most consequential cut in the whole process.
Generic ERP guides land in the same range. LeverX recommends three to five vendors at the shortlist stage, while RFP.wiki’s government ERP guide suggests starting with four to seven and only inviting those that fit your must-haves and budget.
Some governments go even tighter at the finalist stage. Cochise County, Arizona received five RFP responses and used the scores to narrow the field to two finalists, Tyler Enterprise ERP and Workday. A city advised by Panorama Consulting ended up with three vendors giving customized ERP demos.
Swipe to see all columns →
| Stage | Typical number of vendors | What happens at this stage | Benchmark |
|---|---|---|---|
| Long list | Every vendor that fits your size and scope | Market scan, optional RFI, check against must-haves | GFOA: at least a dozen major vendors serve this market |
| Shortlist | 3 to 5 | Full proposals scored against weighted criteria | LeverX: 3 to 5; RFP.wiki: start with 4 to 7 |
| Finalists | 2 or 3 | Scripted demos, reference calls, total cost of ownership | Cochise County: 5 responses to 2 finalists; Panorama-advised city: 3 demos |
| Selected vendor | 1 | Negotiation, contract, council or board approval | Recommendation goes to council or the board in a public meeting |
Two finalists can work when the scores clearly separate, though three keeps more pricing leverage on your side into negotiation. Whatever numbers you pick for each stage, write them into your project charter so the list doesn’t creep up later.
Step 1: Confirm readiness and map your current processes
Don’t open the market until you’ve written down how work actually gets done today. Skip that, and vendor demos end up writing your requirements for you.
The Government Finance Officers Association (GFOA) is blunt about this. Its view is that letting software vendors define your future-state processes means buying software before you know your needs, and that vendors tend to rebuild your existing bad processes inside the new system.
Governments that do this well treat assessment and selection as separate phases. Catawba County, North Carolina finished an ERP needs assessment of its current processes before moving into a structured selection to replace Oracle PeopleSoft.
Process mapping also gives you a baseline to judge vendors against. Cochise County’s current-state review found five systems that couldn’t integrate and 60% of process steps still done manually, which handed its evaluators a concrete list of problems every finalist had to solve.
Before you talk to any vendor:
List your core processes: budgeting, general ledger, accounts payable, purchasing, payroll, HR, grants, capital projects, and utility billing or tax collection if you run them.
For each one, mark manual steps, spreadsheet dependencies, approval bottlenecks, and duplicate data entry.
Write one sentence per process on what “better” means, in measurable terms.
If you want a structured way to run this, KCT’s Public-Sector ERP Readiness Workbook walks through the full assessment.
Step 2: Build a cross-department selection team
Shortlist decisions stick when the people who’ll use the system every day helped make them, so finance and IT shouldn’t pick alone.
A workable team usually includes the finance director as sponsor, plus leads from HR and payroll, purchasing, IT, utility billing or revenue, and one or two department heads who’ll approve transactions every day. Add the clerk or records manager if retention rules matter in your state.
Siskiyou County, California ran its selection with a team of county staff who evaluated proposals, scheduled demos, and checked references before taking a recommendation to the Board.
Cochise County, Arizona scored with seven “super users” (two from IT, two from HR, three from Finance), with Procurement facilitating and an outside advisor keeping the scoring data-driven. It also invited observers from the Courts, Sheriff’s Office, Treasurer’s Office, and Budget Office to review the demo script and sit in on demos, giving feedback without scoring.
Your action here is a one-page charter. Name the members, the scoring rules, the conflict-of-interest attestation everyone signs, and exactly who approves the shortlist versus the final award.
Step 3: Write requirements that actually separate vendors
Requirements are what make vendors look different on paper. Generic ones (“system shall produce reports”) let every vendor answer yes, and then your scores tell you nothing.
Government ERP requirements should hit the things commercial ERPs handle badly:
Fund accounting across many funds, with interfund transfers
Encumbrance accounting tied to purchase orders and contracts
GASB-compliant financial statements and ACFR support
Grant tracking, including reimbursement and compliance reporting
Position control and personnel budgeting
Project and capital accounting across fiscal years
Scope is a requirement too. Linn County, Iowa pulled payroll, timekeeping, and HRIS out of its ERP selection, then picked GovSense running on NetSuite for the rest. Splitting scope like that changes which vendors even belong on your long list.
Write your top requirements as scenarios, not features. “Show a grant-funded purchase order creating an encumbrance and hitting the grant report” separates vendors. “Supports encumbrances” doesn’t.
Rank everything as must-have, important, or nice-to-have. Only must-haves become pass/fail gates in Step 6.
Step 4: Build your long list from the full public-sector ERP market
Start wider than feels comfortable. The public-sector ERP market runs in two lanes, and it’s easy to only look at one.
Swipe to see all columns →
| Lane | Example vendors | Usually strong at | Check carefully |
|---|---|---|---|
| Government-native ERP | Tyler Technologies (Enterprise ERP/Munis), CentralSquare, Caselle, Springbrook, OpenGov | Fund accounting, encumbrances, GASB reporting, and government modules such as utility billing, permitting, and tax | Depth of HR and payroll, user experience, and how much of the product is truly one platform versus acquired modules |
| Enterprise ERP with public-sector editions | Workday, Oracle Fusion Cloud ERP, SAP S/4HANA, Microsoft Dynamics 365, NetSuite through public-sector partners such as GovSense | HR, payroll, analytics, and platform scale | Whether fund accounting, encumbrances, and grants are native or delivered by a partner add-on, and the implementation partner’s government track record |
GFOA notes there are at least a dozen major vendors in this market, each with different strengths, and the best system for one government isn’t the best for all of them. The Panorama-advised city above deliberately invited commercial-market vendors alongside public-sector ones so it could compare a broader set of capabilities.
Cochise County’s finalists show both lanes in action: Tyler Enterprise ERP from the government-native side and Workday from the enterprise side.
To build your list fast, start with KCT’s ERP Tools Directory, a vendor-neutral comparison of 23 public-sector and enterprise ERPs. If you’re already leaning toward a familiar name, read KCT’s breakdowns of Tyler Technologies alternatives and OpenGov alternatives before you lock anything in.
Step 5: Choose your procurement path (RFP, cooperative contract, or piggyback)
Your procurement path decides how your shortlist gets built, so pick it before you score anyone. Cities and counties generally have three options, and which ones you can use depends on state law and your own purchasing code.
Swipe to see all columns →
| Path | How it works | Main advantage | Watch for | Real example |
|---|---|---|---|---|
| Formal RFP | You issue your own solicitation, score proposals, and award | Full control of requirements, competition, and scoring | Takes the longest; needs finished requirements before release | Lowndes County, GA issued its own ERP software and services RFP in April 2025 |
| Cooperative contract | You buy from a contract already competed by a cooperative such as Sourcewell | Skips most of the solicitation work | The contract only covers vendors that hold it, so your shortlist may shrink | Los Altos, CA evaluated Tyler through Sourcewell contract 10515-TTI |
| Piggyback | You use another public agency’s active contract, where state law allows it | Fast when a peer agency recently bought what you need | You still have to show your own bid laws were met | Washington’s RCW 39.34.030, with State Auditor guidance on bid-law compliance |
Before you settle on a path, check with other agencies, cities, and counties near you, with your state, and with the associations your city or county belongs to. One of them may already have a cooperative relationship you can take advantage of, such as a state contract or an association-sponsored purchasing program, or specific procurement rules you have to follow. A few phone calls to purchasing staff at peer agencies and your state procurement office can save months.
Cooperative contracts are a real option for ERP. Los Altos, California used Sourcewell cooperative contract 10515-TTI to formally evaluate Tyler’s products, with staff concluding it would likely be cheaper and more efficient than a standalone procurement.
Piggybacking rests on state law. In Washington, RCW 39.34.030 lets local agencies use another public agency’s active contract, but the State Auditor’s Office points out that the piggybacking government still has to show its own bid laws were met. Many states have similar rules with their own limits.
Approval thresholds still apply either way. Pinal County, Arizona sends cooperative purchases over $250,000 to its Board of Supervisors for approval.
If you go the RFP route, buy the software and the implementation together. GFOA’s August 2026 guidance recommends procuring licenses and implementation services in one RFP, because even great software fails without a good plan to implement it.
A cooperative contract can speed up the purchase, but buying from the only vendor you looked at means you never built a shortlist.
Your action: confirm with procurement, your attorney, and your state procurement office which paths are legal for you, whether a peer agency, the state, or one of your associations already has a cooperative contract you can use, and what dollar thresholds trigger council or board approval. Even on a cooperative path, compare at least two or three vendors that hold qualifying contracts.
The procurement path is an easy place to narrow the field by accident, because the faster option can quietly cut your competition down to one or two vendors. If you want a neutral second set of eyes on your requirements, procurement path, and scoring before the market sees them, KCT’s ERP selection advisory covers this stage from a vendor-neutral seat.
Step 6: Apply knockout criteria and a weighted scoring matrix
Cut the long list in two passes: pass/fail gates first, weighted scores second. Gates remove vendors that can’t work no matter how good the demo looks, and weights rank the ones that remain.
The gates KCT recommends for most cities and counties:
Native fund accounting and encumbrances, not a workaround or add-on
At least two live customers of similar size and complexity, ideally in your state
Hosting and security requirements met, including CJIS if police data touches the system
A named implementation approach with capacity inside your timeline
A price range inside your approved budget band
Older records show the same idea. Clarke County, Virginia started its evaluation by confirming each vendor met the minimum criteria before scoring anything else.
Then score what’s left. Linn County built its matrix around cost, functionality, technical fit, and vendor viability. Cochise County published its full weighting, which makes a useful real-world starting point:
Swipe to see all columns →
| Phase | Criterion | Weight (of 100 points) |
|---|---|---|
| Shortlist (80 points) | Product functionality (from the RFI requirements) | 15 |
| Shortlist (80 points) | Technology | 15 |
| Shortlist (80 points) | Pricing | 25 |
| Shortlist (80 points) | RFP technical evaluation | 15 |
| Shortlist (80 points) | Market data | 10 |
| Finalists (20 points) | Scripted demonstration (ease of use and process fit) | 15 |
| Finalists (20 points) | References | 5 |
| Total | 100 (source: Cochise County Board presentation, April 10, 2024) |
The first 80 points decided who made the shortlist, and the last 20 came from demos and reference calls with the two finalists. If you adapt it, consider giving the implementation partner its own scored line, because a weak partner can sink a strong product.
Your action: lock the weights and get every evaluator to sign off before a single proposal is opened. Changing weights after you’ve seen the responses is how a scoring process turns into a justification for a decision someone already made.
Step 7: Run scripted demos built on your real pain points
Left to themselves, vendors demo whatever shows their product best. A script makes them walk through your processes instead.
Cochise County built its demonstration script from county requirements and the current system’s pain points, then folded the demo scores into each vendor’s final score. Siskiyou County scheduled its software demonstrations across four weeks, from September 10 to October 8, 2024.
What makes a scripted demo work:
Send every finalist the same script two to three weeks ahead.
Use your own data where possible: your chart of accounts, a real grant, a real pay period.
Time-box each scenario and score it live on the same sheet.
Put end users in the room, not just managers.
Require the implementation lead to attend, since that person matters as much as the software.
Keep one evaluator focused only on gaps: what the vendor talked around instead of showing. And when a demo shows something you never saw in the proposal, ask whether it ships in the version and license you’d actually buy.
Step 8: Validate with independent references and total cost of ownership
Choose between finalists on two things a demo can’t show you: how the system worked out for governments like yours, and what it costs over its full life.
Start with references. Vendor-supplied references are their happiest customers, so find your own. Council and board minutes are public, and they’re where you’ll find the governments that bought the same system, what it cost, and whether the go-live slipped. Most of the city and county examples in this post came from records like that.
Questions worth asking every reference:
How far did your go-live date and budget move from the contract?
What did the implementation partner do well, and what did your staff end up doing themselves?
Which modules are you not using, and why?
Would you pick the same vendor and the same implementer again?
Then build total cost of ownership over the same period for each finalist. Include subscription or license fees, implementation services, data conversion, integrations, training, annual escalators, your own outside advisor, and the cost of backfilling staff who’ll be pulled into the project.
The gap between finalists can be large. Cochise County compared 10-year estimated costs, implementation partner included, and its two finalists came in about $1.4 million apart.
Siskiyou County picked Tyler only after demos and reference checks, and GFOA frames the final decision as the best value for the whole package of software and services. Use your TCO model the same way: as the tiebreaker that keeps a low license price from hiding an expensive implementation.
City vs. county: how shortlist criteria differ
Cities and counties run different businesses, so the same shortlist rarely fits both. Cities lean on utility billing and permitting, while counties typically handle property tax collection, courts, and a set of independently elected officials, depending on the state.
Swipe to see all columns →
| Criterion | Cities | Counties |
|---|---|---|
| Revenue modules | Utility billing, business licensing, permitting, and code enforcement | Property tax billing and collection, plus distributions to schools and special districts in many states |
| Justice and public safety | Municipal court and police, where the city runs them | Courts, sheriff, jail, and probation; CJIS requirements if their data touches the ERP |
| Governance | Decision authority usually runs through the city manager or mayor and the council | Independently elected officials (treasurer, assessor, clerk, sheriff) with their own priorities and often their own systems |
| Payroll complexity | Police and fire schedules and bargaining units | 24/7 sheriff and corrections schedules and a wide spread of bargaining units |
| Scope decisions | Whether utility billing is in or out of the ERP | Which elected offices’ systems (assessor, courts, tax) stay separate from the ERP |
The governance row is the one that bites counties. An elected treasurer or assessor doesn’t report to the county administrator, so their buy-in has to be earned in Step 2. Cochise County, for example, brought its Courts, Sheriff’s Office, and Treasurer’s Office into demos as observers.
Scope decisions follow from that. Cochise County kept its Assessor system separate from the ERP, which focused on core business functions instead.
For cities, the big call is usually utility billing. Utility billing depth varies a lot between ERP vendors, so decide whether it’s in scope before you build the long list, not after.
How long does municipal ERP vendor selection take in 2026?
Plan on months, not weeks. In the public records KCT reviewed, Siskiyou County went from RFP to Board in about seven months, and readiness work and requirements come on top of that.
Swipe to see all columns →
| Government | Milestones | Elapsed time |
|---|---|---|
| Lowndes County, GA (planned schedule) | RFP issued April 30, 2025; proposals due July 7, 2025; demos August 4 to 15, 2025; vendor selection August 28, 2025 | About 7 weeks from proposals to selection; about 4 months from RFP to selection |
| Siskiyou County, CA | RFP issued April 9, 2024; demos September 10 to October 8, 2024; staff recommendation to the Board November 12, 2024 | About 7 months from RFP to Board |
| Readiness and requirements (any government) | Process mapping, team charter, prioritized requirements, procurement path | KCT rule of thumb: plan for this before the RFP clock starts, and budget it in months, not weeks |
Lowndes County planned about seven weeks from proposals to selection, which only works when requirements are finished before the RFP goes out. Siskiyou’s seven months include demos and reference checks.
Cooperative contracts can shorten the procurement step, but they don’t shorten readiness, requirements, demos, or reference calls. If someone promises you a 60-day ERP selection, ask which of the eight steps they’re skipping.
Government ERP vendor shortlist mistakes to avoid
The mistakes to watch for, and how to avoid each:
Swipe to see all columns →
| Mistake | Why it hurts | How to avoid it |
|---|---|---|
| Opening the market before mapping current processes | Vendor demos end up defining your requirements | Finish process mapping first (Step 1) |
| Letting finance and IT choose alone | Departments and elected officials who weren’t consulted resist the system later | Build a cross-department team with clear decision rights (Step 2) |
| Writing generic requirements | Every vendor answers yes, so scores don’t separate anyone | Write scenario-based requirements and make must-haves pass/fail (Step 3) |
| Only looking at one lane of the market | You never see the alternatives that might fit better | Build the long list from both government-native and enterprise ERPs (Step 4) |
| Taking the fastest procurement path by default | Competition quietly drops to one or two vendors | Compare at least two or three vendors even on a cooperative path (Step 5) |
| Changing weights after proposals are opened | Scoring turns into a justification for a decision already made | Lock and sign off on weights before opening proposals (Step 6) |
| Letting vendors run their standard demo | You see the product’s best side, not your processes | Send every finalist the same script built on your pain points (Step 7) |
| Comparing license price instead of total cost | A cheap subscription can hide an expensive implementation | Compare multi-year total cost of ownership, implementation partner included (Step 8) |
For what happens when these go wrong, see KCT’s breakdown of why public-sector ERP projects fail and its government ERP statistics.
FAQ
How many vendors should be on an ERP shortlist?
ERP shortlists for cities and counties usually hold three to five vendors, narrowing to two or three finalists for scripted demos. Fewer finalists can weaken your pricing leverage, and more than five spreads evaluators thin. Cochise County, Arizona went from five RFP responses to two finalists before on-site demos.
Can a city buy an ERP without issuing an RFP?
Cities can often buy an ERP without their own RFP by using a cooperative contract or piggybacking on another government’s award, where state law and local purchasing code allow it. Los Altos, California evaluated Tyler through a Sourcewell cooperative contract. Council or board approval thresholds still apply, so confirm with procurement and your attorney first.
What criteria should be used to evaluate government ERP vendors?
Government ERP vendors should be judged on functional fit for public-sector processes, implementation approach and team, total cost of ownership, technology and integration, and vendor viability. Fund accounting, encumbrances, grant tracking, and GASB reporting should be pass/fail gates, not weighted extras. Lock the weights before you open any proposals.
Should software and implementation be procured together?
Software and implementation should usually be procured together in a single RFP. GFOA’s August 2026 guidance recommends evaluating licenses and implementation services as one package, because great software still fails with a weak implementation plan. Bundling also lets you compare best value across finalists rather than license price alone.
Do you need an ERP selection consultant?
ERP selection consultants aren’t required, but they’re common: Cochise County, Catawba County, the City of Ventura, and Sacramento’s transportation authority all brought in outside advisors. Whoever you hire should have no ties to the vendors being evaluated.
ERP selection consulting fees vary based on the number of modules, departments, stakeholders, and procurement support required. Smaller cities often need targeted help with requirements, the RFP, and evaluation, while larger counties and multi-agency organizations typically need more extensive facilitation, requirements development, vendor demonstrations, contract negotiation support, and governance. The biggest driver of cost is usually the amount of staff time and stakeholder coordination needed to reach a defensible selection decision.
An assessment should be the first step any consultant takes with your agency. Not all ERP selection consultants are the same, either: some are strongest at running the selection process, some focus on advising during implementation, and some, like KCT, can support you at any point in the process.
What’s the difference between an RFI and an RFP for ERP?
An RFI (request for information) is a light, non-binding market scan that helps you trim a long list and sharpen requirements. An RFP (request for proposal) asks vendors for binding proposals with pricing, scored against your criteria. A common pattern is an RFI to inform Step 4 and an RFP to run Steps 6 through 8.
How is shortlisting ERP vendors for the public sector different from the private sector?
Shortlisting ERP vendors for the public sector differs in three main ways. The software has to handle fund accounting, encumbrances, and GASB reporting. The purchase has to follow procurement law, usually with council or board approval. And the process happens in public: Cochise County presented its scores and recommendation to its Board of Supervisors in an open work session.
Start with the work before the RFP
Most of a shortlist gets decided before any vendor walks in, by your process maps, your requirements, and the procurement path you choose. Get those right and the scoring, demos, and reference calls have something solid to test against.
If you’re at the very start, map your processes first. Every other step on this list leans on them.
If you’d like a vendor-neutral team to run that work with you, from readiness through finalist scoring and contract review, KCT’s ERP selection advisory is set up for it.