# ERP Vendor RFI Letter Template (Request for Information) > Source: https://netray.co/tools/erp-vendor-rfi-letter-template > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Free Tools ## Short answer Generate a request for information letter to send to ERP vendors before the full RFP, with scope, questions, timeline and response rules. ## Category erp-migration ## Audience - CIO - ERP project lead - Procurement ## Tool **Kind:** template **Output:** document **Fields:** #### Company name **Key:** company **Type:** text **Default:** Acme Precision Ltd #### Industry **Key:** industry **Type:** text **Default:** precision machining and aerospace components #### Sites and countries **Key:** sites **Type:** text **Default:** 3 plants in the United States and 1 in Mexico #### Estimated named users **Key:** users **Type:** text **Default:** 250 #### Current system **Key:** current **Type:** text **Default:** a 15 year old on-premise ERP with heavy customisation #### RFI contact name and email **Key:** contact **Type:** text **Default:** Jane Smith, ERP Project Lead, erp-project@example.com #### Response deadline **Key:** deadline **Type:** date **Default:** 2026-12-04 #### Next stage **Key:** next **Type:** select **Options:** - Shortlist invited to RFP - Shortlist invited to demo - Information gathering only **Default:** Shortlist invited to RFP #### Key questions **Key:** questions **Type:** textarea **Default:** 1. Describe your product, version and deployment options. 2. List five customers in discrete manufacturing of similar size. 3. Describe your implementation partner model in our region. 4. Provide indicative pricing structure: subscription or licence, and typical services ratio. 5. Describe your product roadmap for the next three years. 6. Describe your approach to traceability and compliance in regulated manufacturing. **Blocks:** #### Request for Information: ERP Platform **Body:** From: {{company}} Contact: {{contact}} Response due: {{deadline}} #### 1. Purpose **Body:** {{company}} is evaluating enterprise resource planning solutions to replace {{current}}. This request for information helps us build a shortlist. It is not a request for proposal, it is not a commitment to purchase, and it does not create any obligation on either party. #### 2. About us **Body:** {{company}} operates in {{industry}}. We run {{sites}}, with approximately {{users}} named ERP users. #### 3. Information requested **Body:** {{questions}} #### 4. Response format **Body:** Please respond in no more than 15 pages plus appendices, in PDF. Answer in the order of the questions above. Where a capability depends on a partner or add-on product, say so clearly. Indicative pricing is welcome and will be treated as non-binding. #### 5. Process and next stage **Body:** Questions about this request must be sent in writing to the contact above. Answers that matter to all vendors will be shared with every recipient without naming the asker. After review, the next stage is: {{next}}. Vendors will be told of the outcome in writing. #### 6. Confidentiality **Body:** Information in this letter is confidential to the recipient and must not be shared outside your response team. Your response will be treated as confidential and used only for this evaluation. #### Issued by **Signatures:** - ERP project lead - Procurement **Notes:** A starting point, not legal advice. Have your procurement or legal team review confidentiality wording and any local public procurement rules before sending, especially for public sector or defense related bodies. ## Content **Intro:** A request for information is the light first step before an RFP. It lets you collect basic product, pricing and partner details from many vendors cheaply, then decide who deserves a full RFP. This template produces a ready to send letter. **Sections:** #### How to use the template **Body:** Enter your company, sites, user count, current system and response deadline, and edit the question list. The preview shows a complete letter. Export to Word to adjust tone or add a vendor specific cover note, or to PDF to send as is. Send the same letter to every vendor and log who received it and when. **Bullets:** - Keep the RFI to fewer than 10 questions - State clearly that it is not an RFP or a commitment - Give one named contact for all questions - Set a deadline of two to three weeks #### RFI versus RFP **Body:** An RFI asks what a vendor offers and whether it is a plausible fit. An RFP asks the vendor to propose a specific solution against your detailed requirements, with binding prices and terms. Use an RFI when you have more than five candidates or little market knowledge. Skip it if you already have a three vendor shortlist and a complete requirements document, because it only adds delay. #### Questions that separate vendors **Body:** Ask for facts a vendor must answer concretely: current version and release cadence, deployment options, named customers of similar size and industry, implementation partners in your country, licensing model, typical services to software ratio and the roadmap. Avoid asking whether the product supports MRP or general ledger, since every vendor will say yes. Instead ask how they handle your hardest process, such as engineering change control with serial traceability. #### Common mistakes **Body:** Do not send a forty page questionnaire as an RFI, because strong vendors will decline to answer. Do not hide your budget range if it would save everyone time. Do not promise a decision date you cannot meet. And do not accept answers by phone only; written responses are what you compare later and what protect you if a claim turns out to be wrong. **Cta:** If AI, reporting or data access over your current ERP is part of your requirements, Netray can supply a short list of technical questions to add to your RFI. **Faq:** #### Is an RFI legally binding? **Answer:** No. A properly written RFI states that it is for information only and creates no obligation to buy or to continue the process. Vendor answers are also typically non-binding. Confirm wording with your legal team if your rules require it. #### How long should vendors have to reply? **Answer:** Two to three weeks is typical for an RFI. Shorter periods give weaker answers because vendors prepare custom responses. Longer periods slow the project without improving quality. #### Do I need an RFI if I already know my shortlist? **Answer:** Often not. If you have three or four named vendors and a requirements list, go directly to the RFP. The RFI is useful when the market is unfamiliar, for example a new region or a new type of ERP. #### Should I include pricing questions? **Answer:** Yes, ask for an indicative structure rather than a quote: licence or subscription model, typical users range and services ratio. Treat the numbers as rough and confirm in the RFP. ## Search terms erp rfi template, erp request for information template, rfi letter to erp vendors, erp rfi questions, rfi vs rfp erp, erp rfi sample, request for information erp word --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json