ERP Selection RFP Timeline: How Long It Takes
how long does an ERP selection RFP take
Also searched as
- ERP selection RFP timeline
- ERP selection process timeline months
- ERP RFP schedule with AI proof of value
- how long to select an ERP vendor
Short answer
A well-run ERP selection for a mid-size manufacturer usually takes about 4 to 8 months from kickoff to signed contract, and longer for multi-site or regulated companies. Adding an AI proof of value adds roughly 3 to 6 weeks if run in parallel with reference checks, and much more if left to the end.
Applies to: Mid-size and enterprise ERP replacement or major upgrade selections; ranges are planning estimates, not guarantees
A typical phase plan
- 1Weeks 1 to 4: Charter and requirements. Confirm sponsor and decision rights, collect pain points, document current processes and integrations, and draft the requirement list and scenarios. Use /tools/erp-rfp-completeness-checklist to check the draft.
- 2Weeks 4 to 7: Market scan and RFI. Send a short information request to 8 to 12 vendors to screen on fit, deployment and size; shortlist 4 to 6 for the RFP.
- 3Weeks 7 to 10: RFP issue and response. Allow 3 to 4 weeks for responses, with a Q and A window and a single contact point.
- 4Weeks 10 to 12: Written scoring. Run gates, independent scoring and calibration; shortlist 2 to 3.
- 5Weeks 12 to 17: Scripted demos and AI proof of value. Use your scenarios and sanitized data; include security and integration sessions.
- 6Weeks 15 to 19: Reference calls, site visits, implementation partner review and total cost of ownership modelling.
- 7Weeks 19 to 26: Negotiation, legal and security review, board or steering approval, and contract signature.
What drives the range
Four things move the schedule most: decision-making structure, scope, regulation and internal availability. A single sponsor with authority can close a selection in 4 months; a committee needing consensus across plants often needs 8 or more. Multi-site, multi-country scope multiplies requirements and demo time.
Regulated environments add security, export control and quality system reviews. If you handle controlled technical data, bring security in at the requirement stage rather than at contract, because discovering a deployment mismatch after two rounds of demos wastes months.
Internal availability is often the true limiter. Your best process owners are also your busiest. Plan their time explicitly, typically several days per person per month, and back-fill their roles or the schedule will slip.
Where the AI step fits
Treat AI as an extension of the demo and proof stages, not a separate phase at the end. Include AI deployment and data requirements in the RFP gates, score written answers with the rest, and run the AI proof of value in parallel with scripted demos for the 2 or 3 finalists.
A proof of value needs a sanitized data extract, a test question set, a security review of the setup and time for the vendor to configure. Plan 3 to 6 weeks end to end. If your data extract and approvals are not prepared early, they become the critical path.
If you keep your current ERP and only buy an AI layer, the timeline is shorter: roughly 2 to 4 months, as there is no replacement scope, though data access approvals can still dominate. See erp-ai-pilot-90-days on the AI side for how a pilot is typically sequenced.
Ways to compress without cutting corners
Prepare requirements from real usage: list the reports, interfaces and customisations in your current ERP rather than starting from a blank workshop. Reuse scorecards such as /tools/erp-selection-scorecard and /tools/erp-vendor-demo-scorecard instead of building from scratch.
Shorten the vendor list early with firm gates, run reference calls in parallel with demos, and pre-clear legal terms. Run negotiation with two finalists in parallel so you keep leverage.
Do not compress the proof of value, the reference checks or the implementation partner assessment. Those are where expensive surprises are found, and each costs far less than a failed implementation.
After signature
Selection is not the start of the implementation clock. Allow time for the statement of work, team onboarding, environment setup and data migration planning, often 1 to 3 months before design starts. Contracts negotiated at quarter-end create pressure that vendors use; start negotiating early enough that you are not forced to sign against their calendar. The /tools/erp-contract-negotiation-checklist tool is a useful companion at this stage.
Common pitfalls
- !Starting the RFP before agreeing decision rights, then reopening decisions at every stage.
- !Leaving security and legal review until after the vendor is chosen.
- !Skipping the RFI and issuing a long RFP to too many vendors, creating weeks of unnecessary scoring.
- !Treating the AI proof of value as optional and discovering data access approvals late.
- !Underestimating internal staff time and letting demos slip for lack of attendees.
- !Negotiating with one finalist only, losing leverage on price and terms.
How an ERP-grounded AI assistant handles this
AI can shorten the early phases when it is grounded in your own system: an assistant over ERP data and documentation can inventory the reports, custom screens, integrations and data volumes your requirements workshop would otherwise take weeks to uncover. ERPray or SyteRay-style tooling reads this from the live system. It speeds discovery but does not replace stakeholder interviews or the decisions that follow.
Frequently asked questions
How long should an ERP RFP response period be?
Three to four weeks is normal for a structured RFP, with a question window in the first week. Shorter periods lower response quality and discourage serious bidders; longer ones rarely improve answers and delay the project.
Can we skip the RFI?
If you already know a short list of 3 or 4 credible vendors, yes. Otherwise a 2 or 3 page RFI is a low-cost way to screen on deployment, size and fit before investing in a full RFP and scoring effort.
Does adding AI to the scope make selection much longer?
Moderately, if planned. Writing AI gates into the RFP costs little; the proof of value adds about 3 to 6 weeks if run in parallel with demos and references. The big delays come from late data access or security approvals.
When should we start contract negotiation?
Start redlines with the top two vendors once scoring and the proof of value narrow the field, while references are still in progress. Negotiating with both keeps price and terms competitive until the final decision is approved.
Related
ERP Selection in 2026: Where AI Actually Matters
Treat AI as one evaluation column among many, not the deciding factor: fit, data model, industry depth, and total cost of ownership still decide most ERP selections. Test AI claims live against your own data during the demo, not the vendor's canned dataset, and separate "embedded copilot" marketing from features that ship and work today.
CIO briefingHow to Write an RFP for ERP AI
Write the ERP AI RFP as two linked scopes: the ERP platform and the AI layer that reads or acts on its data. Define the business questions the AI must answer, where data may and may not travel, which ERP roles apply, and how you will test answers before you sign. Vague asks like 'must have AI' produce slideware, not comparable bids.
How-toHow to Score ERP AI Vendors in an RFP
Score in two passes: pass/fail gates first (deployment, data residency, security, mandatory functionality), then weighted criteria on a defined 0 to 4 scale with evidence required for every score. Fix the weights before bids arrive, score independently, then reconcile, and keep price as a separate, calculated factor.
CIO briefingBuilding an ERP Modernization Roadmap That Includes AI
Sequence a modernization roadmap as data and integration cleanup first, a grounded AI query layer second (which can run on the current ERP, before any platform upgrade), and platform migration or upgrade third, timed on its own business case rather than forced early to enable AI. Trying to do all three simultaneously is the most common way modernization programs stall.
CIO briefingERP Upgrade or AI First? A CIO Decision Framework
In most cases, add a grounded AI layer on top of your current ERP first, because it proves value in weeks and shows exactly what an upgrade would need to fix. Reserve a full ERP replacement for cases where the platform itself is end of support, unsupported, or structurally blocking the business, not simply because it feels dated.
CIO briefingHow Much Does ERP AI Actually Cost?
A scoped pilot against one ERP module typically runs 15,000 to 50,000 USD; a single-department production deployment runs 50,000 to 150,000; a multi-module enterprise rollout runs 150,000 to 500,000 or more, plus ongoing hosting and usage costs. Native vendor copilots are usually priced per active user per month on top of existing licensing, not included free.
AI for ERPA 90-Day ERP AI Pilot Plan With Real Success Criteria
A week-by-week 90-day plan for piloting AI on your ERP, with defined success criteria for each phase so the pilot ends in a clear go or no-go decision.
AI for ERPBuild vs Buy: Should You Use Your ERP Vendor's AI Copilot, or Build Your Own?
SAP Joule, Copilot for D365, Infor GenAI, Oracle AI Agent Studio, or a private LLM on your own data. A CIO framework for the build vs buy decision, with real trade-offs.
Stuck on ERP selection and AI?
Talk to engineers who work inside ERP selection and AI every week, and who build private AI that answers these questions from your own ERP data.