There's a gap between "I tried AI" and "AI saved me 10 hours this week." The gap is almost entirely about prompts: specifically, whether you have a library of prompts that work for your actual workflow versus starting from scratch every time.
These are the prompts creative agencies and freelancers are using in 2026 for real client work. Copy them, adapt them, build your own library.
Before the project: client intake and briefing
Turn a vague email into a structured brief
Paste the client's email, then use:
You're a senior creative director. The following is a client email requesting a project.
Extract and structure this into a formal creative brief with these sections:
- Project objective (one sentence)
- Target audience (who, what they care about)
- Key message (what we want them to think/feel/do)
- Deliverables (list format)
- Constraints (budget signals, timeline, must-avoid)
- Open questions that need answering before work begins
Client email:
[paste email]
Be direct. If information is missing, say it's missing: don't guess.
This turns a 3-paragraph email of vague requests into something the team can actually work from. More importantly, it surfaces the open questions you need answered before starting.
Write a project proposal
I'm a [type of agency/freelancer] pitching a project to [type of client].
Here's what they asked for: [brief description]
Here's what I'm planning to deliver: [your plan]
Here's the price: [your price]
Write a project proposal that:
- Opens with what they get (outcome), not what we do (process)
- Explains the three phases of work in plain language
- Frames the price in terms of ROI or comparison ("this is about the cost of one poorly-executed rebrand that needs to be redone")
- Ends with a clear next step
Tone: professional but direct. No jargon. No "passionate about delivering results."
During the project: writing and copy
Brand voice guide from existing copy
Here is copy written by or approved by [brand name].
Analyze it and produce a brand voice guide with:
- 3–5 adjectives that describe the voice
- What it sounds like vs. what it doesn't (provide contrasting examples)
- Sentence length and structure patterns
- Words and phrases the brand uses / avoids
- How it handles technical information
- Tone difference between marketing copy and functional copy (e.g. button labels vs. hero text)
Copy samples:
[paste copy]
Generate social captions in brand voice
Write 10 Instagram captions for [brand name] announcing [topic].
Brand voice: [paste your brand voice summary or 3 adjectives]
Audience: [describe audience]
Goal: [awareness / engagement / click / purchase]
Avoid: [anything they hate: excessive hashtags, certain phrases, etc.]
Format: one caption per line. Include 3 with no hashtags, 3 with 2–3 hashtags, 3 with 5+ hashtags, 1 long-form (150+ words). Label each.
Write a deck narrative
I'm building a client presentation on [topic]. Here are my slides in order:
[list slide titles/topics]
Write the presenter notes for each slide: what I would actually say out loud, not what's on the slide.
Each slide gets 3–5 sentences maximum.
Transition sentence between each slide included.
Tone: confident, conversational, no filler phrases.
Client communication
The status update that doesn't sound like a status update
Write a client update email for this situation:
- Project: [project name]
- What we completed this week: [list]
- What's blocked or needs client input: [list]
- What's next: [list]
- Timeline status: [on track / at risk / delayed, with brief reason]
Write this as a short, direct email (under 150 words).
Don't use "touching base", "as per my last email", or similar phrases.
Start with the most important thing, not pleasantries.
Difficult client email
I need to send an email to a client about [difficult situation: e.g., project delay, scope creep, missed feedback deadline].
Context: [brief description of what happened]
What I need from them: [specific action or decision]
What I want to avoid: [defensive tone / making it their fault / being vague]
Write a direct, professional email that:
- States the situation factually in one sentence
- Explains the impact
- Proposes the solution
- Asks for a specific decision or action by a specific date
Under 120 words.
Turning client feedback into a revision list
Here is feedback from a client on our design work.
Some of it is vague, some contradicts previous requests, some is actually a new scope item.
Categorize this feedback into:
1. Clear revisions we can action directly
2. Feedback that needs clarification before we can act (explain why)
3. Scope changes (new requests not in the original brief)
4. Feedback we should push back on (and suggest what to say)
Client feedback:
[paste feedback]
Proposals and pricing
Scope a project and flag risks
A client wants [describe the project].
I'm going to propose [describe your approach].
Identify:
1. The three most likely scope creep risks on this project
2. The assumptions in my approach that, if wrong, would blow the budget
3. What I should include in the contract to protect against each
Be specific to this type of project, not generic.
Write a contract clause for a common problem
I'm a freelance [type] working on [type of project].
Write a contract clause that addresses [specific scenario: e.g., "client requests unlimited revisions", "client goes silent for more than 2 weeks", "client wants to own AI-generated elements in the work"].
Plain language. Enforceable. No legal jargon.
Delivery and approval
Write the file handoff email
I'm delivering final files to a client.
Project: [project name]
What's included: [list of files/deliverables]
What they need to know to use them: [any technical instructions]
What comes next: [e.g., "this completes the project" or "feedback needed by X"]
Write a short handoff email (under 100 words) that:
- Lists what's included clearly
- Explains how to access or use it (if relevant)
- States what the next step is
- Doesn't invite endless revision after sign-off
For the actual delivery, link to your portal (8fs.io/p/project-name) instead of attaching files or using a Google Drive link: it gives clients a proper branded page with inline preview and an Approve button, and you get notified when they act.
Write the follow-up when a client hasn't opened the files
My client hasn't opened the delivery link I sent [X days ago].
I don't want to sound passive-aggressive or needy.
Write a one-sentence follow-up that:
- Acknowledges they're probably busy
- Reminds them the link is there
- Makes it easy to ask a question if they have one
- Doesn't ask "did you get a chance to look at it"
The prompt habits that separate good from bad results
Include the negative. "Don't use corporate jargon" and "avoid passive voice" consistently improve outputs more than adding positive instructions.
Specify the format. "Under 150 words", "5 bullet points", "3 options": format constraints produce usable outputs. Open-ended prompts produce essays.
Give context about the reader. The model doesn't know your client. "Write this for a 50-year-old operations director who has never worked with a creative agency before" changes the output more than almost any other instruction.
Iterate. The first output is rarely final. "Make the opening punchier", "shorten it by 40%", "the third option is best: write 3 variations of that one" is how you get from good to great.
Build your own library. The prompts that work for your specific context are worth saving. A shared Notion doc (or any format) with your team's best prompts pays back in hours per week.
When the work is done, 8fs handles the delivery: permanent branded portals where clients view, comment, and approve: without creating accounts.