# ERP Selection RFP Timeline: How Long It Takes > Source: https://netray.co/erp-help/rfp-erp-selection-timeline-months > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: ERP Help ## 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. ## Kind cio ## System cio ## Erp ERP selection and AI ## Module Procurement / project planning ## Query how long does an ERP selection RFP take ## Alternate Queries - ERP selection RFP timeline - ERP selection process timeline months - ERP RFP schedule with AI proof of value - how long to select an ERP vendor ## Applies To Mid-size and enterprise ERP replacement or major upgrade selections; ranges are planning estimates, not guarantees ## Steps ### A typical phase plan **Items:** - Weeks 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. - Weeks 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. - Weeks 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. - Weeks 10 to 12: Written scoring. Run gates, independent scoring and calibration; shortlist 2 to 3. - Weeks 12 to 17: Scripted demos and AI proof of value. Use your scenarios and sanitized data; include security and integration sessions. - Weeks 15 to 19: Reference calls, site visits, implementation partner review and total cost of ownership modelling. - Weeks 19 to 26: Negotiation, legal and security review, board or steering approval, and contract signature. ## Sections ### What drives the range **Body:** 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 **Body:** 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 **Body:** 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 **Body:** 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. ## 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. ## Ai Angle 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. ## Faq ### How long should an ERP RFP response period be? **Answer:** 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? **Answer:** 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? **Answer:** 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? **Answer:** 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. ## Search terms ERP selection timeline, ERP RFP timeline, how long ERP selection takes, ERP selection process steps, ERP RFP schedule, ERP vendor selection months, RFI RFP process ERP, ERP selection project plan, ERP evaluation phases, ERP proof of value timeline --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json