FreeFree RFPs on Craxy AI — no subscription required
Back to Blog

Good vs Bad Proposals: Five Illustrative Examples

Compare fictional proposal examples across requirements, approach, pricing and presentation. Learn where verified evidence belongs before submission.

Sher Rahim
Sher RahimCo-founder & Technical Architect
•
November 18, 2024
•
3 min read
Good vs Bad Proposals: Five Illustrative Examples

Every proposal tells a story. The difference between winning and losing often comes down to how clearly it connects the buyer's requirements with your approach and evidence. These five editorial examples illustrate common review questions.

Below, we break down each dimension with fictional, illustrative examples. Click each card to flip between the bad and good versions, and compare clearer wording. Names, numbers and scenarios are invented; these are not customer outcomes or verified credentials.

1. Executive Summary

Your executive summary is your first impression—and often your only chance to grab an evaluator's attention. Yet most proposals waste this prime real estate on generic company descriptions that could apply to any competitor.

Executive Summary• Click to flip
Bad Example

Generic Company-Focused Opening

"ABC Solutions is a leading provider of innovative technology solutions with over 20 years of experience serving clients across various industries. Our team of certified professionals is committed to excellence and delivering value to our customers."

What's Wrong:

  • Focuses on the company, not the client's problem
  • Uses meaningless buzzwords ('innovative', 'excellence')
  • Could be copied into any proposal
  • Doesn't mention the specific project or requirements
Flip for good example
Good Example

Client-Focused Problem-Solution Opening

"Your agency wants to shorten permit review times. We propose a pilot to measure the current baseline, test automated routing, and agree on acceptance targets before rollout. Attach relevant, verified customer evidence here."

Why It Works:

  • Leads with the client's specific challenge
  • Defines a measurable pilot
  • Identifies where verified evidence belongs
  • Shows you understand their unique situation
Flip back

2. Compliance & Requirements

Compliance isn't just about checking boxes—it's about demonstrating that you read, understood, and thoughtfully responded to every requirement. Missing even one mandatory element can disqualify your entire proposal.

Compliance & Requirements• Click to flip
Bad Example

Vague, Assumed Compliance

"Our solution meets all industry standards and regulatory requirements. We have extensive experience complying with government regulations and will ensure full compliance with all applicable laws."

What's Wrong:

  • Doesn't reference specific RFP requirements
  • Uses vague language ('all applicable')
  • No evidence or proof of compliance
  • Evaluator can't verify claims
Flip for good example
Good Example

Explicit Requirement-by-Requirement Response

"Per Section 3.2.1, insert the actual authorization status and a verifiable source if required. Per Section 3.2.3, document the implemented encryption controls and test evidence. Per Section 3.2.5, state the offered uptime commitment and approved service-credit terms. Resolve any gaps before claiming compliance."

Why It Works:

  • References specific RFP section numbers
  • Calls for verifiable evidence
  • Maps evidence to each requirement
  • Makes evaluation easy and clear
Flip back

3. Technical Approach

Your technical approach should paint a clear picture of how you'll solve the problem, not just what technology you'll use. Evaluators want to see your thinking process, not a feature dump.

Technical Approach• Click to flip
Bad Example

Feature List Without Context

"Our platform includes: AI-powered analytics, cloud-native architecture, microservices, real-time dashboards, API integrations, mobile apps, automated workflows, machine learning models, and 24/7 monitoring."

What's Wrong:

  • Lists features without explaining benefits
  • No connection to client's specific needs
  • Reads like a product brochure
  • Doesn't explain HOW these solve the problem
Flip for good example
Good Example

Problem-Solution-Benefit Framework

"Challenge: Manual data entry delays intake. Approach: Pilot assisted document intake with staff review before records enter the database. Implementation: Agree on a pilot scope, acceptance tests and rollout milestones. Evidence: Measure baseline processing time, extraction errors and staff workload before promising improvements."

Why It Works:

  • Ties every feature to a specific client pain point
  • Explains the implementation approach
  • Provides a realistic timeline
  • Defines measurements to validate the approach
Flip back

4. Pricing Clarity

Unclear pricing creates doubt. When evaluators can't understand your cost structure, they assume the worst—hidden fees, scope creep, and budget overruns. Transparent pricing builds trust.

Pricing Clarity• Click to flip
Bad Example

Vague, Bundled Pricing

"Total Project Cost: $450,000. This includes all software, implementation, training, and first-year support. Additional services available upon request. Pricing subject to final scope confirmation."

What's Wrong:

  • No breakdown of cost components
  • Hidden behind 'upon request' language
  • Leaves room for scope disputes
  • Evaluator can't compare line items
Flip for good example
Good Example

Transparent Line-Item Breakdown

"Software Licenses (50 users × $200/yr): $10,000/yr. Implementation (400 hrs × $175): $70,000. Training (5 sessions × $2,000): $10,000. Year 1 Support (included): $0. Total Year 1: $90,000. Years 2-5: $15,000/yr. 5-Year TCO: $150,000."

Why It Works:

  • Every cost component is visible
  • Shows calculation methodology
  • Includes multi-year projection
  • Easy to compare against competitors
Flip back

5. Visual Design & Formatting

Evaluators review dozens of proposals. Visual design isn't about being pretty—it's about making your proposal easy to evaluate. Good formatting respects the reader's time and guides them through your response.

Visual Design & Formatting• Click to flip
Bad Example

Wall of Text, No Visual Hierarchy

"Our implementation methodology follows industry best practices and includes discovery, design, development, testing, deployment, and training phases. During discovery we conduct stakeholder interviews and requirements gathering sessions to understand your needs. The design phase produces wireframes and technical specifications..."

What's Wrong:

  • Dense paragraphs with no breaks
  • No headings, bullets, or visual cues
  • Important information buried in text
  • Exhausting to read and evaluate
Flip for good example
Good Example

Scannable, Visually Organized Content

"PHASE 1: DISCOVERY (Weeks 1-2) → Stakeholder interviews, Requirements validation, Risk assessment. PHASE 2: DESIGN (Weeks 3-4) → System architecture, Integration mapping, UAT test plan. [Includes timeline graphic and milestone table]"

Why It Works:

  • Clear phase headers with timeframes
  • Bullet points for quick scanning
  • Visual elements (tables, timelines)
  • Respects evaluator's limited time
Flip back

Review guidance checked October 3, 2026. Federal evaluators use the solicitation’s factors; see FAR 15.305. Download our free proposal templates to track evidence and review tasks.

Your Pre-Submission Checklist

Before you hit submit, run through these five questions:

  1. Executive Summary: Does it lead with the client's problem, not your company history?
  2. Compliance: Can an evaluator verify every requirement without searching?
  3. Technical Approach: Does each feature connect to a specific client benefit?
  4. Pricing: Is every dollar accounted for with no hidden costs?
  5. Visual Design: Can someone skim it in 2 minutes and understand your approach?

If you answered "no" to any of these, your proposal needs work before submission.


Automate Your Quality Checks

Catching these issues manually takes time—time you don't have when deadlines are tight. That's why we built Craxy AI to automatically analyze your proposals against these quality questions and suggest improvements.

Our AI reviews your draft, flags weak sections, and suggests improvements based on what your source documents and draft. Human reviewers must check the evidence, resolve gaps and approve the final submission.

Ready to write winning proposals?

Try AI-assisted draft review and verify the suggestions against your solicitation.

Get started free