Help me prepare a project proposal submission for [DECISION MAKER OR CLIENT]. The project is [PROJECT IDEA], and the decision we need is [APPROVAL ASK]. Use this context: [REQUIREMENTS AND EVIDENCE], [RESOURCES AND CONSTRAINTS], and [TARGET DATE]. First, identify the decision criteria, stated requirements, unknowns, dependencies, exclusions, and approval conditions. Build two feasible delivery options if the scope, timing, or approach is genuinely open. Compare each option on outcome, cost basis, timeline, dependencies, delivery risk, and what the approver must provide. Recommend one option with a short rationale. Do not treat assumptions as commitments. Then draft a proposal that can be submitted directly. Use these sections: executive decision summary; problem or opportunity; objectives and success measures; in-scope and out-of-scope work; deliverables and acceptance criteria; work breakdown with owner and accountable approver; milestone timeline; resource and cost estimate with assumptions; dependencies; risk register with early-warning signal, mitigation, owner, and contingency; governance and reporting cadence; and a final approval request naming the exact decision, budget or resources, and deadline. Make the timeline realistic: show dependencies before dependent work, identify the critical path, and distinguish fixed dates from estimates. For each deliverable, define what evidence proves completion. Avoid vague verbs such as "improve" or "support" unless paired with a measurable result. Do not invent client requirements, staffing availability, prices, commitments, results, or stakeholder approval. Mark unsupported items [CONFIRM]. Before answering, self-check that every deliverable has an owner and acceptance criterion, and that the timeline contains no task scheduled before its prerequisite. Ask up to 3 clarifying questions only if a required input is missing.
Fill in
| Placeholder | What to enter | Example |
|---|---|---|
| [DECISION MAKER OR CLIENT] | Enter who will review the proposal and their role or organization. | Maya Chen, VP of Operations at Larkspur Health Clinics |
| [PROJECT IDEA] | Enter the problem, proposed solution, users affected, and intended outcome. | Replace email-based new-patient intake with a secure web form and routing workflow for five clinics. |
| [APPROVAL ASK] | Enter the exact decision, budget, people, or access you need approved. | Approve a $42,000 implementation budget and assign one clinic manager for weekly decisions. |
| [REQUIREMENTS AND EVIDENCE] | Paste the brief, evaluation criteria, current-state facts, stakeholder needs, and related documents. | The brief requires a six-week pilot, HIPAA review, English and Spanish forms, and a 20% reduction in incomplete intake packets. |
| [RESOURCES AND CONSTRAINTS] | Enter available people, budget limits, technical constraints, dependencies, and known risks. | One product manager, two engineers, a vendor form tool, and clinic staff available only on Tuesday afternoons. |
| [TARGET DATE] | Enter the proposal due date and any required launch or delivery date. | Proposal due October 8; pilot must start by November 16. |
How to use
- Paste the recipient's evaluation criteria and any non-negotiable dates before the project description.
- Check that acceptance criteria can be observed or tested, rather than relying on a status update.
- Confirm the named owners have capacity and authority before submitting the proposal.
- Follow up with: "Create a one-page executive version that preserves the approval ask, critical path, and top three risks."
Variations
Client proposal
Use this for a scoped external-services proposal.
Draft a client project proposal for [CLIENT] for [SERVICES] based on [CLIENT BRIEF] and [PRICING AND TERMS]. Include objectives, scope, exclusions, phased deliverables, client responsibilities, assumptions, timeline, fixed-fee or time-and-materials cost basis, change-control process, risks, and acceptance criteria. Make the approval request explicit and identify decisions needed before work begins. Do not imply a guarantee or invent case studies, staffing, terms, or client facts. Check that pricing, dates, and deliverables agree. Ask up to 3 questions only if required inputs are missing.
Internal business case
Use this to seek internal funding or headcount for a project.
Write an internal project business case for [INITIATIVE] seeking [DECISION] from [APPROVERS]. Use [CURRENT STATE DATA], [COSTS], and [CONSTRAINTS]. Provide the problem, options including doing nothing, recommended option, expected benefits separated into quantified and unquantified, implementation plan, owners, dependencies, risks, and milestones. Show all calculations with assumptions and label benefits that cannot yet be measured. Do not invent savings, revenue, capacity, or executive support. Check that the requested resources match the implementation plan. Ask up to 3 questions only if essential inputs are missing.
Proposal response plan
Use this when coordinating a complex RFP or formal submission.
Create a proposal response plan for [SOLICITATION] due [DUE DATE], using [REQUIREMENTS]. Produce a compliance matrix with requirement, response owner, source evidence, page or attachment location, reviewer, and due date. Then make a backwards schedule covering kickoff, questions, draft, technical review, pricing review, executive approval, upload, and submission buffer. Flag mandatory forms, signatures, page limits, and contradictions. Do not claim compliance without supplied evidence. Check that every mandatory requirement has an owner and review step. Ask up to 3 questions only if needed.
Tips
- Put the requested decision in the first paragraph and repeat it in the final approval section; a proposal is not merely a project description.
- Define acceptance criteria at the deliverable level, such as a passed test, signed design, or published report, rather than a percentage-complete estimate.
- Use a backward plan from the immovable deadline and reserve time for approval, procurement, and stakeholder review.
- Separate exclusions from assumptions: exclusions are not being delivered, while assumptions are conditions that could change the plan.
FAQ
How detailed should a project proposal be?
Include enough detail for a reviewer to approve scope, cost basis, owners, timeline, and risk. Put implementation detail in an appendix if it hides the decision.
Should a proposal include alternatives?
Include them when the approver has a real choice about scope, approach, or investment. Explain the consequence of choosing each option, including doing nothing.
Can AI estimate a project timeline?
It can help sequence known work and expose dependencies, but estimates require confirmation from the people doing the work. Do not present model-generated durations as commitments.