I used to spend more time writing about work than actually doing it.
Proposal for a new client? 45 minutes. Follow-up after a missed deadline? 30 minutes. Explaining to a non-technical founder why their "quick fix" isn't quick? A diplomatic exercise I still haven't fully figured out.
Then I started building a prompt library. Not vague "help me write an email" prompts — structured templates that tell ChatGPT exactly what context it needs and what I want back.
Here's what actually works.
The Problem With Generic AI Prompts
Most developers use ChatGPT like a search engine. "Write me a professional email." The result is corporate mush. "I hope this finds you well. Please see the attached."
The fix is giving the model a structure it can fill in:
- Your role and context
- The specific situation
- What format you want
- What tone rules to follow
- What to avoid
Once you have that structure, it takes 2 minutes to get a usable first draft.
The Categories I Built Out
I organized my prompts into 5 areas where I was losing the most time:
1. Client Proposals & Quotes
The hardest part of a proposal isn't the price — it's framing the scope so the client understands what they're getting without you underselling yourself.
My most-used prompt:
I'm a freelance [your specialty, e.g. React developer] and I need to write a proposal:
Client: [company type]
Project: [describe in 2 sentences]
Budget they mentioned: [amount or 'not specified']
My estimated timeline: [your estimate]
Write a professional proposal covering: what I understand about their problem,
my approach (3-4 steps), what's included and excluded, price with payment terms
(30% upfront, 70% on delivery), and a clear next step.
Keep it under 400 words. Sound confident, not desperate.
The "sound confident, not desperate" line matters. It shifts the tone from vendor-pitching to peer-collaborating.
2. Difficult Client Emails
Scope creep at 3pm on a Friday. The client who hasn't paid in 47 days. The founder certain your architecture recommendation is wrong.
Scope creep prompt:
My client is asking me to add [describe new request] to a project that's already
scoped and priced. This wasn't in the original brief.
Write a professional email that: acknowledges their request positively, explains
it's outside the original scope, gives a specific price and timeline for the
addition, and offers the choice: add now at extra cost or after project completion.
Don't apologize for having boundaries.
I've sent variations of this maybe 20 times this year. ChatGPT drafts it in 15 seconds. I edit for 3 minutes. Done.
3. Code Quality & Documentation
My README prompt:
Write a professional README.md for my project:
Project name: [name]
What it does: [one sentence]
Tech stack: [list]
How to install and run locally: [your steps]
Environment variables needed: [list]
How to run tests: [command]
License: [MIT / proprietary]
Format with proper markdown headers. Include badges for build status,
license, and language. Keep it technical but friendly.
90 seconds to fill in the blanks. Saves 40 minutes staring at a blank document.
4. Pricing & Rates
The Upwork objection:
A client told me they can get it cheaper on Upwork/Fiverr. They want me to match it.
Write a response that: doesn't match the price, explains the real risk of the
cheaper option (without arrogance), quantifies what they're actually paying for
(accountability, timezone, communication, no rework costs), and offers a choice
rather than an ultimatum. End by asking what matters most in a developer relationship.
The last line reframes price → value and puts the next move on them.
5. LinkedIn & Portfolio Content
LinkedIn post prompt:
Write a LinkedIn post about a project I just completed:
What I built: [describe]
Client type: [e.g. e-commerce startup]
Main challenge solved: [describe]
Result/outcome: [what happened after launch]
Tech used: [stack]
Start with a hook (not 'I'm excited to share...'). Tell the problem-solution story.
Include one specific number. End with a question for comments.
3-4 relevant hashtags. Max 200 words. First person, casual but professional.
How to Actually Use These
Keep them in Notion, VSCode, Obsidian — anywhere accessible. Fill in the brackets, paste into ChatGPT.
Total time per email: 5-8 minutes vs 30-45 from scratch. Over a week with 15+ client comms, that's 5+ hours back.
The Full Set
I compiled 50 of these prompts — all 5 categories — into a downloadable pack.
Get it here:
Price: $19. Instant download, 5 text files, open in any editor.
What email do you dread writing most as a freelancer? Drop it in the comments — I will write the prompt for it.
Top comments (0)