What should be in the opening of a sample proposal?

Open with the project name, client name, and a one-paragraph summary of what you're proposing to do. This gives instant clarity about what the proposal covers.

How detailed should the scope section be?

Detailed enough that both you and the client know exactly what's included and what's not. Use bullet points for deliverables and be specific about any limitations or exclusions.

Should I include competitor references in a proposal?

No, avoid mentioning competitors. Instead, focus on why your approach is right for this specific client's situation and goals.

Sample Project Proposal: Annotated Walkthrough

The best way to learn proposal writing is to look at one that works. This walkthrough shows you a real project proposal, broken down section by section, so you see how pros structure their pitch. Each part does something specific: build credibility, set clear expectations, close the deal.

The Opening Section: Set Context Immediately

Start with headers that make it easy to scan. Your first section should list the project name, client name, date, and a brief summary. Example: “Proposal: Freelance Invoice System Implementation for Smith Creative Collective, May 28, 2026.” Follow with a two-sentence project overview. “This proposal outlines Waco3 invoice management implementation, including custom branding and team training. The goal is to automate invoice creation and tracking so your team spends less time on admin and more on client work.”

Why: It tells the client exactly what they’re reading. No confusion. No flipping through wondering if it’s the right document.

The Problem Statement: Show You Listened

Restate the client’s problem in their own words before suggesting anything. This shows you listened during discovery calls. Example: “Your invoicing process uses spreadsheets, email, and a shared Google Sheet to track payments. That creates three problems: reminders are hit-or-miss, late payment data is fuzzy, and your team sometimes forgets to send invoices.”

Keep this to 3-5 sentences. Use details the client told you, not generic complaints. Stick to their language. Show you care without being patronizing.

The Solution: Make It Step by Step

Break your solution into numbered phases. Each phase should have a brief description and list of deliverables. Here’s an example:

“Phase 1: Setup and Integration (Week 1-2)

Configure Waco3 with your branding (logo, colors, payment terms)
Connect to your existing accounting software
Create proposal and invoice templates that match your brand
Deliverable: Live, branded system ready for team use”

“Phase 2: Team Training (Week 3)

Conduct 2-hour training session for your full team
Create video tutorials for common tasks
Provide written documentation
Deliverable: Team confident and independent with the system”

Pipeline spreadsheet data on screen — Breaking work into clear phases removes confusion and builds confidence.

The Timeline: Specific Dates, Not Vague Language

Don’t write “approximately 4 weeks.” Write:

“Project Timeline

May 30 to June 6: Setup and integration
June 9 to June 13: Team training
June 16: Project completion and handoff
June 16 to June 30: 14-day support period with priority email response”

Specificity signals professionalism. Clients trust a timeline they can plan around. Include milestone dates and any dependencies they need to know about.

Pricing: Clear, Simple, No Surprises

State exactly what you’re charging and what’s included. Example:

“Investment: $3,500 (fixed price)

Implementation and setup: $2,000
Team training and documentation: $1,000
Two weeks of post-launch support: $500

Payment terms: 50% due upon signature, 50% upon completion”

Breaking out the cost by phase helps clients see where their money goes. Fixed pricing is often better for new clients because it removes uncertainty. If there are scope add-ons, list them with pricing so the client knows what extra features cost.

If you have relevant past work, show it here. Example:

“We implemented this same system for Apex Design Studio in March 2026. Within 30 days, they reduced invoice processing time from 45 minutes per invoice to 8 minutes. They now send invoices the same day work is completed, which led to 3 fewer days in average payment collection time.”

Numbers are powerful. Even a short, well-written case study boosts your win rate significantly. If you don’t have relevant examples, use your own experience instead.