A county ERP RFP is harder than a city or company RFP because the people who will live on the system often report to different elected officials. Finance, HR, land records, the assessor, the treasurer, the sheriff, and the courts can each be a system with its own user community. The solicitation also names integrations the county does not control (state systems, courts, CAMA, jail), and it becomes a public record a losing vendor will read.
The Government Finance Officers Association notes that many governments implement an ERP only once every 10 to 15 years (Developing an RFP for an ERP System). Follow your state's procurement rules and county counsel. This page is a method, not legal advice.
What is an ERP RFP, and what makes a county's different?
An RFP for an ERP system is a formal solicitation that tells every vendor the same facts, states the requirements, and sets the rules for scoring and contracting.
For a county, that document is also a political and legal instrument. Scope usually spans offices that report to different elected officials, so decision rights have to be settled before anyone drafts a sentence. Avero's work with counties starts from that fact: finance, HR, land records, assessor, treasurer, sheriff, and courts, each with its own user community. If those offices have not agreed who decides when the treasurer and the auditor want different things, the RFP will paper over a fight that reappears at evaluation, at award, and in a protest.
Should your county write an RFP at all?
Going to market is a decision, not a diagnostic. An RFP tells you what vendors want to sell. It does not tell you whether you need a new system. GFOA's own ERP RFP course includes deciding whether to upgrade or replace as a learning objective, which is the right order.
Three questions, from Going to Market Is a Decision, Not a Diagnostic and the Going to Market field brief, settle it before a procurement officer opens a template.
Is this a configuration problem or a platform limitation? Name the technical constraint. A shrug means you may be buying a new system to fix a setup problem.
What do you need, as distinct from what you have? Requirements copied from the incumbent buy the same thing again. Write them from the work, then test both paths against that list (Start at Zero).
What is the honest cost of both paths? Put replacement and optimization on the same assumptions, including staff time, conversion, and reduced throughput while people relearn the work.
What are the 7 steps to writing a county ERP RFP?
These seven steps are the sequence a procurement officer can run. Each one produces a record.
- Confirm the decision and the sponsor. Replace or optimize is answered, an executive sponsor is named, and the commission or board has been briefed.
- Set governance across offices. Decide who prevails when elected offices disagree, and put a steering committee, an evaluation team, and conflict-of-interest forms in place.
- Run discovery office by office. Map current-state processes, workarounds, shadow systems, and every integration (GIS, CAMA, courts, jail, state reporting).
- Write the requirements traceability matrix. Functional, technical, integration, security, and reporting requirements, each one scoreable and traceable to evaluation and acceptance testing.
- Draft the RFP package. Background, scope, matrix, demo scripts, cost form, references, weights, and draft contract terms.
- Evaluate with scripts, not slideware. Score written responses, then scripted demonstrations, reference checks, and a normalized cost model.
- Negotiate and award. Read contract terms before award: milestone payments, exit and data ownership, AI provisions, and price protection.
1. Confirm the decision and the sponsor
If replace or optimize is still open, stop. Name the executive sponsor who will carry a contested award into a public meeting, and brief the commission or board before vendors are in the building. ERP advisory and selection is this work, not a software sale.
2. Set governance across offices
Write down who decides when the treasurer and the auditor want different things. A steering committee sets direction. An evaluation team scores. Conflict-of-interest forms go out before anyone sees a demo. Clackamas County, with Lane and Wasco, is the pattern: Avero facilitates discovery and fit-gap across jurisdictions and supports vendor selection and contract negotiation (Clackamas County).
3. Run discovery office by office
Requirements come from the offices that touch the money, not from the incumbent system and not from IT alone. Tarrant County, Texas engaged Avero from April 2025 to January 2026 for ERP replacement planning and procurement readiness across Budget, HR, Payroll, Purchasing, and the Auditor's Office. The work produced a needs assessment, business process maps, a requirements traceability matrix, a procurement strategy, and governance and change planning. No software was sold, and no referral fee was paid (Tarrant County).
Santa Fe County, New Mexico (150,000+ residents, engaged January 2025) ran department-by-department discovery and a procurement-compliant ERP RFP under New Mexico rules, with integration specifications for more than a dozen systems (Kronos, NeoGov, ProVal, GeoCivix, ESRI). Jail Management System replacement was sequenced ahead of end of life. Phase 2 is complete and vendor evaluation is underway (Santa Fe County).
4. Write the requirements traceability matrix
Write functional, technical, integration, security, and reporting requirements from the work, not from the screens you have. Avero's requirements-definition note says a finished definition often runs two to 3,000 lines, with separate tabs for each functional area, and that interfaces (including GIS) have to be named. Each requirement should be scoreable and traceable forward to evaluation and to acceptance testing.
Avero keeps that record in Caliber: more than 1,400 pre-built government requirements across 25 functional modules, and every score traces back to evidence so a scorecard holds up when a losing vendor challenges it. Caliber is how the work is run. It is not sold as a product (Caliber).
5. Draft the RFP package
The next section is the contents list. That package is what a public records request will later produce.
6. Evaluate with scripts, not slideware
Score the written responses against the matrix first. Then run scripted demonstrations on county scenarios and county data, call references yourself (including at least one hard go-live), and model cost on one set of assumptions. The Port of Portland is not a county. It is the evaluation method: 17 proposals received, four finalists, four days of scenario-based demonstrations using the Port's data and scenarios, one vendor selected (Port of Portland).
7. Negotiate and award
Read the contract before you award. Milestone-based payments, exit and data ownership, AI provisions, and price protection belong in the record, not in a side letter after the vote. Contract advisory is a short, separate pass (published range: 1 to 4 weeks, $10K to $35K) so the county is not negotiating from the vendor's paper alone.
What should a county ERP RFP include?
A government RFP looks like a controlled package, not a narrative. Every proposer answers the same sections, in the same codes, against the same cost assumptions.
| Section | What goes in it | Why it matters for a county |
|---|---|---|
| County background | Population, employees, departments, and elected offices in scope. | Proposers price what they have been shown. |
| Current system landscape | Every system in scope and every interface that must survive. | State systems, courts, CAMA, jail, and GIS are often outside county control. |
| Scope by module and office | What is in, and what is explicitly out. | Offices left unnamed get assumed in. |
| Requirements matrix | Fixed response codes, one requirement per row. | Free text cannot be scored the same way twice. |
| Demonstration scenarios | Processes finalists must walk through live. | A slide does not show a close or a public-safety payroll. |
| Implementation approach | Named key staff, and the county staff time assumed. | Meet the people named in the proposal before award. |
| Multi-year cost template | Subscription or license, implementation, conversion, integrations, training, support, escalators. | Different scopes make the low number meaningless. |
| References | At least one comparable county, including a hard go-live. | A commercial reference does not answer a public meeting. |
| Evaluation criteria and weights | Stated up front. | Weights set after proposals arrive fail a protest. |
| Draft contract terms | The county's terms, or an exceptions process. | The award is a contract. |
| Schedule and rules | Pre-proposal conference, Q&A rules, submission checklist. | Avero's RFP masterclass recommends at least four to six weeks for significant projects. |
One county's approach, not a template Avero wrote: Brown County, Wisconsin's ERP RFP (Project 2775) attached a requirements workbook, a vendor questionnaire, a total cost of ownership workbook, a references form, and a current-state software landscape. Its evaluation criteria included functionality, usability, technical fit, implementation methodology, support, total cost of ownership, vendor viability, references, and demonstrations (Brown County ERP RFP, Project 2775).
How should a county evaluate ERP proposals?
Draw the evaluation team from the offices in scope. Score written responses against the matrix first, then shortlist. Script demonstrations on county data. Run reference calls yourselves. Normalize cost to the same assumptions.
GFOA's August 2026 Government Finance Review article recommends procuring software licenses and implementation services together in one RFP and evaluating best value across both (Which System is Truly Best?). That is GFOA's recommendation, not a universal rule. Your procurement code may split the buys. Either way, require named implementation staff and a meeting with them before award.
Every score traces to a requirement and an evidence note, so the file survives a protest and a public records request. Monroe County, New York (750,000+ residents on aging SAP ECC, engaged February 2022) is the full arc: enterprise-wide discovery, a procurement-ready RFP, and an evaluation that selected Workday Financials and HCM, with best-of-breed tools for budgeting, treasury, asset management, and tax. Avero now governs the program as PMO on the county's side (Monroe County).
What are the most common county ERP RFP mistakes?
- Requirements that describe the incumbent. You buy the constraints you meant to leave. Write from the work (Start at Zero).
- Requirements from one department, or from IT alone. Tarrant County's discovery ran across Budget, HR, Payroll, Purchasing, and the Auditor's Office because those offices touch the money.
- A yes/no checklist with no scripted demonstrations. A checked box is not evidence that the process works on your data.
- Cost forms that let vendors price different scopes. Itemize licenses or subscription, implementation, conversion, integrations, training, support, and escalators, on fixed assumptions.
- Never meeting the implementation team that will actually show up. The pursuit team is not the team that arrives after award.
- Integrations left vague. State systems, courts, CAMA, jail, and GIS have to be named, priced, and tested. Santa Fe County specified more than a dozen third-party systems before evaluation.
- Rushing requirements. Avero's services FAQ calls rushing the requirements phase the most common cause of a failed implementation two years later.
- A response window too short for serious bidders. The RFP masterclass recommends at least four to six weeks for significant projects.
How long does a county ERP selection take?
Avero's published ranges, from the services FAQ and the services page: selection runs three to eighteen months overall. Discovery and requirements typically take two to four months. RFP development and release take one to two. Evaluation through contract award takes three to six. ERP Advisory and Selection is listed at 3 to 18 months and $150K to $1.5M+. County board calendars and protest periods often set the real schedule on top of those ranges.
Who can help a county write an ERP RFP?
Help falls into three structures. The structure matters more than the logo.
GFOA offers training and a consulting practice. The course linked above is the source most people find first. It is orientation. It is not a county method you can hand a procurement officer tomorrow.
Independent advisory firms are paid only by the agency. They can tell you to optimize, to delay, or to award a product they do not sell, because none of those answers changes their fee.
Firms that also resell, implement, or take vendor fees have a structural conflict. Implementation revenue and referral fees rise when you replace, and they rise more for some products than others. You do not need to impugn anyone's motives. You need to know how they are paid.
Questions to ask any advisor before you hire them:
- Do you resell or implement any product we might evaluate?
- Do you accept referral fees or partner payments?
- Who on your team does the work?
- Will you stay through contract negotiation and go-live?
- Can we reach the people who hired you?
- Can we contract through an existing cooperative vehicle?
Avero Advisors, an independent firm in Knoxville, Tennessee that works only for public agencies and does not sell or implement software, runs county ERP discovery, requirements, RFP development, and evaluation. Founded in 2016, Avero holds no licenses, takes no referral fees, and has no reseller relationships with Tyler, Workday, SAP, Oracle, Infor, or any other vendor (About). Representative county clients include Monroe County NY, Tarrant County TX, Blount County TN, Lake County CA, and Santa Fe County NM. Agencies can contract through TXShare, Port of Portland, NY Edge, and the State of Oklahoma.
On the Blount County engagement, Tyler Munis was selected and went live in February 2019, after the out-of-support AS400 was stabilized so the county could choose on evidence. Avero's role was selection and implementation management on the county's side.
A readiness check before you release
There is no downloadable template. Run these checks before release. The replace-or-optimize worksheet is the gated Going to Market field brief.
- Replace or optimize is settled.
- An executive sponsor is named.
- Decision rights across elected offices are documented.
- Every office in scope has been interviewed.
- The integration inventory is complete.
- Requirements are written without naming the incumbent.
- Response codes are fixed.
- Demo scripts are drafted from the county's five hardest processes.
- The multi-year cost form uses fixed assumptions.
- Evaluation weights are published in the RFP.
- Draft contract terms are attached, or an exceptions process is defined.
- The scoring record can be produced if a losing vendor protests.
Tell us where you are. A sentence is enough. A senior person replies within one working day. Call 865-415-3848, write to us, or request the Going to Market field brief.
Questions about a county ERP RFP
What is an ERP RFP for a county?
A formal solicitation that tells every ERP vendor the same facts about the county, states the requirements and scoring rules, and sets up contract terms, so the award is competitive and defensible.
What should a county ERP RFP include?
County background, current systems and interfaces, scope by office, a requirements matrix, scripted demo scenarios, implementation staffing, a multi-year itemized cost form, references, weighted evaluation criteria, and draft contract terms.
How long does a county ERP selection take?
Typically three to eighteen months: two to four for discovery and requirements, one to two to build and release the RFP, and three to six from evaluation to contract award. (Avero published ranges.)
What are the most common ERP RFP mistakes?
Requirements that describe the old system, requirements from one department, yes/no checklists without scripted demos, cost forms that allow different scopes, and vague integration requirements.
Do we need a consultant to write an ERP RFP?
Not always, but most counties lack staff who have run an ERP selection recently. If you hire help, choose an advisor paid only by the county, with no resale, implementation, or referral-fee ties to any vendor you might evaluate.
Who can help a county write an ERP RFP?
GFOA offers training and consulting, and independent advisory firms run the full process. Avero Advisors is one vendor-neutral option: it runs discovery, requirements, RFP development, and evaluation for counties and takes no vendor fees.
Should we decide whether to replace our ERP before writing the RFP?
Yes. An RFP tells you what vendors want to sell, not whether you need a new system. Settle replace or optimize first.