Click a card to preview the full template with its theme applied.
ERP RFP
An ERP RFP issued by Northwind Studio covering functional requirements, evaluation, and submission process.
PREPARED FOR
Acme Co
PREPARED BY
Northwind Studio
DATE
August 18, 2026
ERP RFP
An ERP RFP issued by Northwind Studio covering functional requirements, evaluation, and submission process.
ISSUED TO
Acme Co
ISSUED BY
Northwind Studio
ISSUE DATE
August 18, 2026
Northwind Studio
ERP RFP
This RFP invites Acme Co to submit a proposal for the implementation and support of a new ERP system for Northwind Studio. The pages that follow cover the functional scope, evaluation criteria, and submission process.
USERS
200 seats
Across finance, ops, and warehouse.
GO-LIVE
9 months
Target from contract to go-live.
SUBMISSION
4 weeks
Deadline from the issue date.
Northwind Studio
ERP RFP
The proposal should address three areas. Each will be scored during evaluation.
AREA 1 · FUNCTIONALITY
Coverage of finance, procurement, inventory, warehouse, and reporting requirements, plus integrations with our CRM, EDI, and warehouse hardware.
AREA 2 · IMPLEMENTATION
Named team, plan to hit the go-live target, data migration approach, cutover plan, and change management with our internal team.
AREA 3 · PRICE AND SUPPORT
Licenses, implementation fees, and post-go-live support over three years, with clear assumptions and any add-on costs.
Submission format: a single PDF with an executive summary, the three areas above, and a completed requirements matrix. Late or non-conforming submissions may be excluded.
Northwind Studio
ERP RFP
The budget below is for planning purposes and reflects the range this program is scoped to. Adjust rows to match the actual scope.
| Item | Rate | Qty | Amount |
|---|---|---|---|
| Software licenses (annual) | $80,000 | 3 | $240,000 |
| Implementation and cutover | $180,000 | 1 | $180,000 |
| Data migration and integrations | $60,000 | 1 | $60,000 |
| Support and managed services (annual) | $45,000 | 3 | $135,000 |
| Total | $615,000 | ||
| Milestone | Date | Notes |
|---|---|---|
| RFP issued | Today | See cover page |
| Questions due | Day 14 | Written questions only |
| Proposals due | Day 28 | Single PDF plus requirements matrix |
| Shortlist demos | Day 42 | Onsite or virtual |
| Vendor selected | Day 70 | Contract signed |
Payment terms are net 30 from the date of an approved invoice unless negotiated in the final contract. Retainer or milestone billing may be proposed.
Northwind Studio
ERP RFP
Acknowledge receipt of this RFP by completing the fields below and signing. Acknowledgement does not oblige you to submit; it confirms you have received the document and understand the timeline.
PRIMARY CONTACT (RESPONDER)
INTENT TO SUBMIT BY
RESPONDER
Acme Co
ISSUER
Northwind Studio
The ERP RFP template is a five-page request-for-proposal document for evaluating ERP vendors. It states the project overview with user-count, go-live, and submission stat cards, the objectives, the functional scope vendors must respond to — coverage, implementation plan, and total cost of ownership — an indicative budget table, and a submission page with an acknowledgement signature.
In Bonsai you can tune the requirements and evaluation criteria to your systems landscape, set the RFP timeline, and have vendors acknowledge receipt with the built-in contact fields and signature block. Merge fields keep your company details consistent across every copy you send.
Everything below comes pre-configured. Turn sections on or off, edit the copy, or add your own — Bonsai remembers your choices for next time.
Can I edit every section? Yes — every heading, paragraph, stat, table row, and signature block is fully editable in Bonsai.
Can I add more pages? Yes — add, reorder, or duplicate pages once the template is open.
Do merge fields auto-fill? Yes — Sender, Receiver, and Date pull from your client contact and the current date automatically.
Can vendors respond inside the document? Yes — the submission page includes contact inputs and an acknowledgement signature, and you can add more input fields for structured vendor answers.