Business Proposal Prompt

What it does

Writes a structured business proposal for a client, project, or partnership opportunity. The output covers the standard proposal structure — problem definition, proposed solution, scope of work, pricing, timeline, and next steps — without the boilerplate language that makes proposals feel like they were generated from a template. Each section is tailored to the specific opportunity.

undefined

How to use it

The problem statement input is the most important field. If you're not sure what the client's actual business problem is (as opposed to what they asked for), go back and ask before writing the proposal. A proposal that accurately names the problem is 3x more likely to close than one that leads with deliverables.

After generating, review the pricing section — make sure the framing positions value, not hours.

Example output

Problem: "[Company] is expanding its sales team from 4 to 14 reps over the next 6 months. At current content production speed, marketing can produce 3–4 sales enablement assets per month — a rate that worked at 4 reps but won't scale to 14. The gap means new reps will either delay their ramp time or work with outdated assets from 18+ months ago."

Solution: "I'll build a 3-month content sprint that front-loads the highest-priority assets (battle cards, one-pagers, case studies) before the first wave of new reps starts, then establish a quarterly update cadence that sales ops can manage without agency support."

Investment: "Project fee: $8,500 for 90 days..."

Variations

Unsolicited proposal: Add "The client hasn't asked for a proposal — I'm proactively pitching this. Lead with the problem discovery rather than the solution, so they feel understood before they hear the pitch."

Agency / multi-person proposal: Add "This is from an agency, not a solo consultant. Include a 'our team' section and frame the proposal in 'we.'"

Retainer proposal: Add "This is for an ongoing monthly retainer. The pricing section should justify the recurring cost by showing what's included each month."

SaaS or product (not services): Add "I'm not selling consulting — I'm proposing a software partnership or reseller agreement. Adjust the format accordingly."

Common pitfalls

Leading with credentials. "We are a [X]-year-old agency with expertise in..." is not a problem statement. Start with what the client is experiencing, not with who you are.

Vague scope. "Content strategy and execution" is not a scope. "Two blog posts per month, one case study per quarter, and a quarterly content audit" is a scope. Ambiguity creates scope creep.

Hiding the price. Don't bury pricing at the end after 6 pages of buildup. Clients who've decided to buy are frustrated by the delay. Clients who are on the fence will skip to the price anyway.

No clear next step. The proposal should end with a specific action: "Reply to accept," "Schedule a call to discuss," or "Sign the attached agreement." Not "let me know if you have questions."

Who uses this prompt

Freelancers and consultants sending proposals to potential clients. Small business owners responding to RFPs. Agency founders standardizing their proposal process. Sales reps at professional services firms who need a starting document before legal cleans it up.