5 AI prompts I use every time I start a new freelance project

Polly1301 — Wed, 08 Apr 2026 16:15:07 +0000

Everyone talks about using AI to write code faster. Nobody talks about using it for the stuff that actually eats your time as a freelance developer.

I mean the emails. The scope documents. The awkward conversation when a client adds three new features and calls it "a small change." The invoice that's been overdue for two weeks.

I've been freelancing for a while and I use AI for all of it — but I kept rewriting the same prompts from scratch every time. So I finally cleaned them up. Here are 5 of the ones I use most.

1. Turn a messy client brief into a clean scope document

Clients rarely send you a clean brief. They send you a wall of text, a voice note transcript, or a vague idea with no boundaries. This prompt cleans it up fast.

You are a senior project manager. A client sent me this brief:

[PASTE CLIENT MESSAGE HERE]

Turn it into a clean scope document with these sections:
1. Project Summary (2-3 sentences)
2. Deliverables (bullet list, specific and measurable)
3. What is NOT included (assumptions & exclusions)
4. Open questions I need to ask the client before starting
5. Suggested timeline (rough phases)

Be direct. No filler. Flag anything vague or risky.

I run this before every discovery call. It prepares me and genuinely impresses clients when I send back something structured within minutes of their rambling brief.

2. Explain a bug to a non-technical client

This one saves relationships.

Explain this technical bug to a non-technical client in plain language.

The bug: [DESCRIBE WHAT WENT WRONG TECHNICALLY]
Impact on the client: [WHAT THE CLIENT EXPERIENCED]

Write a short explanation (max 150 words) that:
- Does NOT use technical jargon
- Explains what happened using an analogy if helpful
- States what I'm doing to fix it
- Gives a realistic time to resolution
- Ends on a reassuring note without making empty promises

Do not be defensive. Be clear and calm.

Clients don't care about the cause. They care about the fix and the timeline. This prompt nails that every time.

3. Push back on scope creep professionally

Scope creep is the silent killer of fixed-price projects. This prompt helps you say no without saying no.

Write a professional reply to a client who is requesting something outside the original project scope.

Original scope: [WHAT WAS AGREED]
New request: [WHAT THEY'RE ASKING FOR NOW]
My relationship with this client: [NEW / ONGOING / HIGH VALUE]

The reply should:
- Acknowledge their request positively
- Reference the original scope clearly
- Offer two options: add it as a paid extra (with rough cost), or defer to a future phase
- NOT sound defensive, annoyed, or passive-aggressive
- Be under 150 words

Always offer options, not just "no." This keeps the relationship and protects your time.

4. Follow up on an unpaid invoice without being awkward

Write a follow-up email for an overdue invoice.

Invoice amount: [AMOUNT]
Days overdue: [NUMBER]
Our relationship: [FIRST TIME LATE / USUALLY PAYS / CHRONIC ISSUE]
Tone needed: [GENTLE REMINDER / FIRM / FINAL NOTICE]

Requirements:
- Reference the invoice number and due date
- Assume good faith (the first two reminders)
- Include a clear call to action with a specific date
- Keep it professional, not passive-aggressive

The "assume good faith" instruction is key. It keeps the tone right even when you're frustrated.

5. Price a project you've never done before

Pricing unfamiliar work is one of the hardest parts of freelancing. This prompt helps you think it through before you commit.

Help me estimate a software project I haven't done before.

Project description: [DESCRIBE]
My hourly rate: [RATE] or target budget: [BUDGET]

Break it down into:
1. Core development phases with rough hours per phase
2. Hidden complexity I might be underestimating
3. A low / mid / high estimate with reasons
4. 3 clarifying questions to ask the client before committing
5. What I should charge extra for (scope creep traps)

Think like a freelancer who has been burned before.

Always present the mid estimate. Low gets you burned, high scares clients.

There are 35 more where these came from

These are 5 of the 40 prompts I packaged into a PDF called the Developer's AI Prompt Pack. It covers client scoping, communication, code documentation, business stuff like proposals and retainers, and productivity.

If these were useful, the full pack is at Developer's AI Prompt Pack — 40 prompts for the work around the code for €25.

Either way — save the 5 above. They'll pay for themselves the first time you use them.

What do you use AI for in your freelance work outside of coding? Would love to hear what's working for others.