Draft a procurement proposal for [PURCHASE OR PROJECT] using the information below. Write for [DECISION MAKERS] and use only the facts, estimates, and policies I provide. Label assumptions and missing information rather than inventing prices, savings, supplier capabilities, or approvals. Business need and scope: [BUSINESS NEED AND SCOPE] Budget and commercial facts: [BUDGET AND COMMERCIAL DETAILS] Requirements and constraints: [REQUIREMENTS AND CONSTRAINTS] Stakeholders and dates: [STAKEHOLDERS AND TARGET DATES] Produce a 1,000–1,400 word proposal with: 1. Executive recommendation: the purchase, sourcing route, spend ceiling, and decision requested. 2. Problem and scope: what is included, excluded, and the consequence of delay or doing nothing. 3. Requirements: separate mandatory requirements, scored preferences, service levels, security/privacy needs, integration needs, and acceptance criteria. 4. Sourcing and evaluation plan: identify whether to renew, run an RFI/RFP, obtain competitive quotes, or use an approved contract; give a weighted evaluation matrix totaling 100 points. Include total cost of ownership categories, not just unit price. 5. Commercial and risk view: assumptions, contract term, implementation costs, supplier concentration, data handling, continuity, and exit risks with mitigations. 6. Delivery plan: a dated table with activity, accountable owner, consulted parties, approval gate, and dependency from requirements sign-off through purchase order, onboarding, acceptance, and invoice approval. 7. Decision and next actions: state exactly who must approve what. Make the proposal fair to suppliers: requirements must be relevant and measurable, and evaluation criteria must be disclosed consistently. Before answering, check that weights total 100 and that every timeline activity has an owner and dependency. Flag conflicts between budget, dates, requirements, and procurement policy. Ask up to 3 clarifying questions only if a required input is missing.
Fill in
| Placeholder | What to enter | Example |
|---|---|---|
| [PURCHASE OR PROJECT] | Name the goods, service, software, or project being purchased. | Customer support platform for a 45-person SaaS company |
| [DECISION MAKERS] | State the people or committee who will review the proposal. | COO, Head of Support, Finance Director, and Security Lead |
| [BUSINESS NEED AND SCOPE] | Describe the problem, desired outcome, scope boundaries, and impact of delay. | Replace shared inboxes before the January support-volume increase; include ticketing and knowledge base, exclude CRM replacement |
| [BUDGET AND COMMERCIAL DETAILS] | Provide available budget, known pricing, contract facts, and cost assumptions. | Up to $42,000 annual recurring spend plus $8,000 implementation; current tool costs $14,000 and ends December 31 |
| [REQUIREMENTS AND CONSTRAINTS] | List mandatory requirements, preferences, policies, technical constraints, and risks. | SSO, SOC 2 report, Salesforce integration, EU data-processing terms, 99.9% uptime target, month-to-month pilot preferred |
| [STAKEHOLDERS AND TARGET DATES] | List owners, reviewers, dependencies, and required delivery or decision dates. | Support Ops owns requirements; Security reviews by October 18; selection by November 8; go-live by December 15 |
How to use
- Paste known constraints, including procurement thresholds and existing-contract limits, before asking for the proposal.
- Check that mandatory requirements are distinct from preferences and that price is not the only cost category.
- Confirm owners can actually approve the named gates and replace tentative dates before circulation.
- Follow up with: "Create an RFP questionnaire and supplier scorecard from this proposal; make every scored question trace to one stated requirement."
Variations
RFP scorecard
You have suppliers to compare and need a consistent scoring tool.
Build an RFP evaluation scorecard for [PURCHASE] from [REQUIREMENTS] and [SUPPLIER LIST]. Create a table of measurable criteria, evidence requested, scoring anchors from 1 to 5, criterion weights totaling 100, and the evaluator role. Separate pass/fail compliance checks from weighted scoring. Include total-cost and implementation-risk items. Flag criteria that are vague, duplicative, or likely to favor one supplier without business justification. Ask up to 3 questions only if needed.
Sole-source case
You need to justify a noncompetitive purchase.
Write a sole-source justification for [SUPPLIER AND PURCHASE] based on [BUSINESS RATIONALE], [MARKET REVIEW], and [COST FACTS]. State the requested approval, scope, contract value, term, alternatives considered, why they do not meet the requirement, price-reasonableness evidence, and risks of sole sourcing. Do not claim exclusivity without proof. End with approval owner and review date. Flag missing policy evidence. Ask up to 3 questions only if required inputs are missing.
Implementation handoff
A selected supplier now needs a controlled rollout plan.
Create a procurement-to-implementation handoff plan for [SELECTED SOLUTION] using [CONTRACT FACTS], [IMPLEMENTATION SCOPE], and [TEAM OWNERS]. Provide milestones from signature to acceptance, with accountable owner, acceptance evidence, dependency, risk, and escalation point for each. Include data migration, security actions, training, change control, invoice milestones, and contract-renewal date. Do not assume a feature or resource exists. Ask up to 3 questions only if needed.
Tips
- Define acceptance criteria before selecting a supplier; "easy to use" should become a measurable test, such as a representative agent completing a ticket workflow within a stated time.
- Evaluate total cost of ownership across subscription, implementation, integration, internal labor, support tiers, data migration, renewal uplift, and exit costs.
- Keep a separate record of mandatory compliance failures so a high weighted score cannot hide a non-negotiable requirement.
- Assign the business owner for each dependency, not only procurement; security review and data migration often set the real schedule.
FAQ
Should the proposal name a preferred supplier?
It can, if the recommendation follows documented criteria and relevant alternatives were considered. Explain the evidence and disclose any limited competition.
How many evaluation criteria should I use?
Use enough to distinguish meaningful tradeoffs, usually 6–12. Consolidate overlapping criteria so evaluators are not scoring the same strength twice.
Can AI determine the right procurement policy?
No. Supply your organization's thresholds and delegation rules, then have a procurement or legal owner confirm the route and approvals.