Download / No signup
Make proposals
easier to compare.
Give potential partners a consistent brief, then ask them to separate capability, scope, cost and uncertainty in their responses.
Inside the template
A brief that travels
with the decision.
Markdown opens in any text editor. The comparison CSV opens in common spreadsheet applications. All fields are editable; neither file contains invented supplier data.
Product and use
Describe users, environment, functions and the starting technical material.
Scope and ownership
State required development work, design-file access, firmware and tooling responsibilities.
Quantities and assumptions
Separate samples, pilot and volume scenarios. Label forecasts and target costs as assumptions.
Requirements and evidence
Name target markets and specialist owners; request evidence relevant to the actual product.
Quote breakdown
Request unit costs by volume, NRE, tooling, test, packaging, exclusions and change assumptions.
Response and review
Use one response structure, record clarifications and compare like-for-like scope.
Use one version.
Track every clarification.
Send the same released brief to the partners being compared. Keep a shared clarification log and record when a change affects cost, scope or schedule. Treat unanswered questions as open items, not implicit agreement.
Read the RFQ guide