DEV Community: Jason DePardo

How to Write Proposals That Actually Close (Using AI as Your Co-Writer)

Jason DePardo — Sat, 18 Apr 2026 18:28:16 +0000

Most freelance proposals fail for the same reason: they talk about the freelancer instead of the client's problem.

Here's the framework I use to write proposals that close at 40%+ (industry average is 10-20%), and how AI makes the whole process take 15 minutes instead of 2 hours.

The Proposal Structure That Closes

1. Problem Statement (Not Your Bio)

Start with THEIR problem, not your credentials.

Bad: "I'm a web designer with 8 years of experience specializing in..."

Good: "Your website currently converts at 1.2%. Industry benchmark for [their niche] is 3.5%. That gap represents approximately $[X] in annual lost revenue."

The second version makes the client think: "This person understands my problem."

2. Proposed Solution (Not a Feature List)

Don't list features. Describe the outcome.

Bad: "I will redesign your homepage, create new landing pages, optimize your forms..."

Good: "I'll rebuild your conversion path to close the gap between your current 1.2% and the 3.5% benchmark. This involves three targeted changes: [X], [Y], [Z]."

3. Proof (Not Testimonials)

Show results from similar work:

"For [similar client], I implemented the same conversion optimization approach. Their conversion rate went from 1.8% to 4.1% in 6 weeks, generating an additional $12,000/month."

Specific numbers > generic praise.

4. Investment (Not Price)

Frame pricing against the value, not the cost:

"Investment: $5,000. Based on your current traffic of [X] visitors/month, closing even half the conversion gap would generate an additional $[Y]/month — a [Z]x return within the first 90 days."

5. Next Steps (Not "Let Me Know")

End with a specific, low-friction next action:

"If this approach makes sense, I have availability starting [date]. I've blocked a 30-minute slot on [specific date/time] to walk through the details. Does that work?"

How AI Accelerates This

The framework above works. But researching the client, calculating ROI, and writing it all up takes 1-2 hours. Here's how AI cuts that to 15 minutes:

Step 1: Research Prompt (2 minutes)

Research [company name] and tell me:
- Their primary business model
- Their target customer
- 3 problems they likely face based on their industry
- Any public metrics or benchmarks I can reference

Step 2: ROI Calculator Prompt (3 minutes)

Based on [industry], estimate:
- Average website conversion rate
- Average customer lifetime value
- Monthly traffic range for a company of [size]
Calculate the revenue impact of improving conversion by 1-2%.

Step 3: Proposal Draft Prompt (10 minutes)

Using this framework, write a proposal for [service]
for [client name] in [industry].

Their problem: [from research]
My solution: [your approach]
Proof: [your case study data]
Investment: $[price]
ROI estimate: [from calculator]

Tone: confident but not arrogant. Conversational but professional.
Length: 1 page max.

The Numbers Don't Lie

Since switching to this AI-assisted framework:

Proposal writing time: 2 hours → 15 minutes
Close rate: 15% → 42%
Average project value: up 35% (because value-framing works)

Get the Full System

I packaged this entire framework into an AI Proposal Generator Pack — complete with prompt templates for every proposal section, SOW templates, pricing frameworks, and follow-up sequences. Turn 15 minutes of AI-assisted work into proposals that close.

What's your proposal close rate? And what do you think is the biggest reason proposals fail? Let's discuss in the comments.

How to Write Proposals That Actually Close (Using AI as Your Co-Writer)

Jason DePardo — Sat, 18 Apr 2026 17:13:06 +0000

Most freelance proposals fail for the same reason: they talk about the freelancer instead of the client's problem.

Here's the framework I use to write proposals that close at 40%+ (industry average is 10-20%), and how AI makes the whole process take 15 minutes instead of 2 hours.

The Proposal Structure That Closes

1. Problem Statement (Not Your Bio)

Start with THEIR problem, not your credentials.

Bad: "I'm a web designer with 8 years of experience specializing in..."

Good: "Your website currently converts at 1.2%. Industry benchmark for [their niche] is 3.5%. That gap represents approximately $[X] in annual lost revenue."

The second version makes the client think: "This person understands my problem."

2. Proposed Solution (Not a Feature List)

Don't list features. Describe the outcome.

Bad: "I will redesign your homepage, create new landing pages, optimize your forms..."

Good: "I'll rebuild your conversion path to close the gap between your current 1.2% and the 3.5% benchmark. This involves three targeted changes: [X], [Y], [Z]."

3. Proof (Not Testimonials)

Show results from similar work:

"For [similar client], I implemented the same conversion optimization approach. Their conversion rate went from 1.8% to 4.1% in 6 weeks, generating an additional $12,000/month."

Specific numbers > generic praise.

4. Investment (Not Price)

Frame pricing against the value, not the cost:

"Investment: $5,000. Based on your current traffic of [X] visitors/month, closing even half the conversion gap would generate an additional $[Y]/month — a [Z]x return within the first 90 days."

5. Next Steps (Not "Let Me Know")

End with a specific, low-friction next action:

"If this approach makes sense, I have availability starting [date]. I've blocked a 30-minute slot on [specific date/time] to walk through the details. Does that work?"

How AI Accelerates This

The framework above works. But researching the client, calculating ROI, and writing it all up takes 1-2 hours. Here's how AI cuts that to 15 minutes:

Step 1: Research Prompt (2 minutes)

Research [company name] and tell me:
- Their primary business model
- Their target customer
- 3 problems they likely face based on their industry
- Any public metrics or benchmarks I can reference

Step 2: ROI Calculator Prompt (3 minutes)

Based on [industry], estimate:
- Average website conversion rate
- Average customer lifetime value
- Monthly traffic range for a company of [size]
Calculate the revenue impact of improving conversion by 1-2%.

Step 3: Proposal Draft Prompt (10 minutes)

Using this framework, write a proposal for [service]
for [client name] in [industry].

Their problem: [from research]
My solution: [your approach]
Proof: [your case study data]
Investment: $[price]
ROI estimate: [from calculator]

Tone: confident but not arrogant. Conversational but professional.
Length: 1 page max.

The Numbers Don't Lie

Since switching to this AI-assisted framework:

Proposal writing time: 2 hours → 15 minutes
Close rate: 15% → 42%
Average project value: up 35% (because value-framing works)

Get the Full System

What's your proposal close rate? And what do you think is the biggest reason proposals fail? Let's discuss in the comments.

50 AI Prompts That Write Professional Emails in Under 60 Seconds

Jason DePardo — Sat, 18 Apr 2026 15:43:50 +0000

I used to spend 20-30 minutes crafting important emails. Now I spend 60 seconds.

The trick isn't just "use ChatGPT." It's using the right prompt structure with the right context variables. Here are the categories and a few examples from my collection of 50 battle-tested prompts.

The Prompt Structure That Works

Every effective email prompt follows this structure:

Role: [who you are]
Context: [the situation]
Recipient: [who they are and what they care about]
Goal: [what you want to happen after they read this]
Constraints: [tone, length, specific things to include/avoid]

Without this structure, you get generic output. With it, you get emails that sound like you wrote them on your best day.

Cold Outreach Prompts

The Value-First Introduction

You are a [your role] reaching out to [prospect role] at [company].
I noticed they [specific observation about their business].
Write a cold email that:
- Opens with a specific observation (not flattery)
- Offers one concrete insight they can use today
- Ends with a low-friction CTA (not "hop on a call")
- Under 150 words
- Tone: helpful peer, not salesperson

The Referral Request

I completed a project for [client name] with [specific result].
Write an email asking them to refer me to one colleague who
might need [your service]. Include a one-sentence description
of the result I achieved for them. Make it easy — they should
be able to forward this email directly.

Follow-Up Prompts

The Gentle Nudge (3 Days After No Response)

I sent [recipient] an email about [topic] 3 days ago.
No response. Write a follow-up that:
- Doesn't start with "just following up" or "bumping this"
- Adds one new piece of value
- Gives them an easy out ("if the timing isn't right")
- Under 75 words

The Break-Up Email

I've sent [number] emails to [prospect] about [service] with
no response. Write a final email that:
- Acknowledges I've been persistent
- Removes all pressure
- Leaves the door open
- Creates subtle FOMO without being manipulative
- Under 50 words

Client Management Prompts

The Project Kickoff

I just signed a new client for [project type].
Write a kickoff email that:
- Thanks them for choosing me
- Sets expectations for communication cadence
- Lists what I need from them to start
- Establishes the first milestone and date
- Professional but warm tone

The Scope Change Response

My client just asked for [additional work] that's outside
the original scope. Write an email that:
- Acknowledges the request positively
- Explains it's outside the agreed scope
- Offers to do it as a paid addition
- Provides a rough estimate
- Doesn't make them feel bad for asking

Why These Work Better Than Winging It

Consistency — every email hits the same quality bar
Speed — 60 seconds vs. 20 minutes
Objectivity — removes the emotional second-guessing
Personalization — the context variables make each output unique

The Full Collection

These are 6 of the 50 prompts in my AI Email Copywriting Prompts Pack. The full pack covers cold outreach, follow-ups, proposals, client management, upsells, and more. Each prompt includes context variables so you get personalized output every time.

What's your most-used AI prompt for work? Drop it in the comments — let's build a community collection.

How to Stop Scope Creep Before It Eats Your Profit Margin

Jason DePardo — Sat, 18 Apr 2026 15:43:39 +0000

You quoted $3,000 for a website redesign. Three months later, you've built a website, a mobile app, a CRM integration, and a custom analytics dashboard. Your total compensation? Still $3,000.

Scope creep is the #1 profit killer for freelancers and agencies. Here's how to stop it.

Why Scope Creep Happens

Scope creep isn't malicious (usually). It happens because:

The scope wasn't defined clearly enough — "redesign the website" means different things to different people
You said yes to small requests — each one was tiny, but they compounded
There's no change order process — the client doesn't know how to formally request additions
You're afraid to say no — you don't want to seem difficult or lose the client

The 4-Part Defense System

1. Define Scope Like a Contract Lawyer

Your scope document should answer:

What are the exact deliverables? (List them)
What format will they be in?
How many revision rounds are included?
What is explicitly NOT included?

That last one is critical. A clear "out of scope" section prevents more disputes than the scope section itself.

2. Create a Change Request Form

When a client asks for something outside scope, don't say no. Say: "Absolutely! Let me send you a change request form."

The form should include:

Description of the additional work
Estimated hours and cost
Impact on timeline
Client signature/approval

This transforms a confrontation into a business process. The client feels heard. You get paid for the extra work.

3. Use the 24-Hour Rule

Never agree to scope changes on a call. Always say: "Let me review this and send you a formal change request within 24 hours."

This gives you time to:

Accurately estimate the additional work
Assess the impact on your timeline
Decide if you even want to do it

4. Document Everything in Writing

Verbal agreements are scope creep's best friend. After every call, send a summary email:

"Per our conversation today, we agreed to [X]. This is within/outside the original scope. [If outside: I'll send a change request form shortly.]"

The Math That Changes Your Mind

Let's say you quoted $5,000 for a project estimated at 50 hours ($100/hour).

Scope creep adds 20 hours of uncompensated work. Your effective rate drops to $71/hour — a 29% pay cut you gave yourself.

At 10 projects per year, that's $20,000 in lost revenue annually.

Get the Full System

I built a Scope Creep Defense Kit with boundary-setting templates, change request forms, scope definition frameworks, and client communication scripts. Stop doing free work.

What's the worst scope creep story you've experienced? I bet the comments on this one will be therapy for freelancers everywhere.

The 5-Stage System for Chasing Late Invoices (Without Burning Bridges)

Jason DePardo — Sat, 18 Apr 2026 15:35:17 +0000

Late payments are the silent killer of freelance businesses. You did the work. You sent the invoice. And now... crickets.

Most freelancers either send one awkward follow-up email or go straight to threats. Both approaches fail. Here's the 5-stage escalation system that actually works:

Stage 1: The Friendly Reminder (Day 3 After Due Date)

Tone: warm, assumes good intent.

Hi [Name], just a quick note that invoice #[X] for $[amount] was due on [date]. Sometimes these slip through the cracks — no worries! Here's the invoice link for easy reference: [link]

Most late payments are genuinely forgotten. This email recovers 40-50% of them.

Stage 2: The Professional Follow-Up (Day 7)

Tone: professional, adds urgency.

Hi [Name], following up on invoice #[X] which is now 7 days past due. I want to make sure there aren't any issues with the deliverables or payment process. Could you confirm when I can expect payment?

This one catches the "I meant to pay but kept putting it off" crowd.

Stage 3: The Firm Notice (Day 14)

Tone: business-like, references terms.

This is a formal notice that invoice #[X] is 14 days overdue. Per our agreement, a late fee of [X%] has been applied. Current balance: $[amount + fee]. Please remit payment within 48 hours.

Now you're referencing the contract. This is where your payment terms clause earns its keep.

Stage 4: The Escalation (Day 21)

Tone: serious, mentions consequences.

This is my final attempt to resolve invoice #[X] directly. If payment is not received by [date], I will be forced to [pause all ongoing work / engage a collections agency / pursue legal remedies].

Most clients pay at this stage. The ones who don't are genuinely problematic.

Stage 5: The Final Demand (Day 30)

Tone: formal, legal-adjacent.

This is a formal demand letter. It references the contract, itemizes all amounts owed including late fees, and states your intended next action with a deadline.

The Decision Framework

Not every late payment deserves all 5 stages. Ask yourself:

Is this a repeat offender? Skip to Stage 3.
Is the amount under $500? Consider whether the collection cost is worth it.
Is this a client you want to keep? Stay at Stages 1-2 longer.
Is there a genuine dispute? Pause escalation, resolve the dispute first.

The Complete Kit

I built a Late Payment Invoice Escalation Kit with all 5 email templates, a timing calendar, the decision framework, and an invoice tracking spreadsheet. Everything you need to get paid without burning bridges.

How do you handle late-paying clients? I'd love to hear your strategies in the comments.

7 Contract Clauses Every Freelancer Needs Before Signing Anything

Jason DePardo — Sat, 18 Apr 2026 15:35:16 +0000

Every freelancer has that one story — the project that went sideways because the contract was weak (or nonexistent).

I've seen freelancers lose thousands because they didn't have the right clauses in place. Here are the 7 contract clauses you absolutely need:

1. Scope Definition Clause

This is your first line of defense against scope creep. Define exactly what you're delivering, in what format, and by when. Anything outside this scope is a change order.

Why it matters: Without this, clients will keep adding "just one more thing" until your $5,000 project becomes a $2,000 nightmare.

2. Payment Terms Clause

Specify when you get paid, how you get paid, and what happens if they don't pay. Include:

Payment schedule (50% upfront, 50% on delivery is standard)
Late payment penalties (1.5% per month is common)
Accepted payment methods

3. IP Ownership Clause

Who owns the work? Until the final payment clears, you do. After payment, ownership transfers. This protects you from clients who ghost after receiving deliverables.

4. Revision Limits Clause

"Unlimited revisions" is a trap. Define how many rounds of revisions are included and what constitutes a revision vs. a new request.

Pro tip: 2-3 revision rounds is industry standard. Anything beyond that is billed hourly.

5. Termination Clause

How can either party end the contract? What's the notice period? What happens to work already completed? A clean exit clause prevents messy breakups.

6. Confidentiality Clause

Protects both parties. You won't share their business secrets; they won't share your proprietary processes. Simple, but essential for trust.

7. Dispute Resolution Clause

If things go wrong, how do you resolve it? Mediation first, then arbitration, then litigation. This saves both parties from expensive legal battles.

The Red Flag Checklist

Before signing ANY contract, check for these red flags:

No payment terms or vague payment language
"Work for hire" without fair compensation
Non-compete clauses that are too broad
Automatic renewal without notification
Unlimited liability clauses

Get the Full Kit

I put together a complete Freelancer Contract Protection Kit with all 7 clause templates, a red-flag checklist, and an editable contract template. It's everything you need to protect your freelance income.

What contract lessons have you learned the hard way? Share in the comments.