Claude prompts for offers, pages, outreach and packages
Copy-ready prompts for freelance offers, service pages, outreach, productized packages, discovery calls and pipeline admin. Paste what you already sell. Not a get-rich-quick kit, and not financial advice.
In short: This page contains 30 copy-paste ready prompts, organized into 6 categories with a description and pro tip for each. The first 5 prompts are free instantly, no signup needed. Drafted with AI writing assistance and checked against our editorial policy.
Freelance Offers
5 promptsOffer statement from real work
1/30✨ What it does
Writes a 40 to 60 word offer statement from the service, client type and outcome you already deliver. Missing proof is tagged, and no result is invented.
Write an offer statement of 40 to 60 words from work I already do. Service: [SERVICE]. Who I serve: [CLIENT TYPE]. Outcome they hire me for: [OUTCOME]. Proof I can show: [PROOF I CAN SHOW]. Stay inside those brackets. If proof is missing, write [VERIFY] on that clause and do not invent a result, a client count or a year in business. End with one sentence on who this is not for, drawn only from [WHO THIS IS NOT FOR].
Pro tip: Name the outcome in the client's words, not your internal label.
Scope versus not in scope
2/30✨ What it does
Splits your notes into in-scope and not-in-scope lists plus a rule for new asks. Grey items stay tagged, and no extra deliverable is added.
Split this work into In scope and Not in scope lists. Work I sell: [PASTE SCOPE NOTES]. Extras people ask for: [PASTE EXTRA REQUESTS]. Output two numbered lists of 6 items or fewer, then a one-line rule for anything new. If an extra is something I have never delivered, put it in Not in scope. If I left a grey item, write [VERIFY] beside it. Never invent a deliverable, a round of revisions or a tool I did not name.
Pro tip: Paste the extras clients actually ask for, including the ones you resent.
Three package shapes from hours
3/30✨ What it does
Builds three package shapes from deliverables and the hours you can keep, with no fee stated. Blank hours stop the run instead of inventing a package you cannot staff.
Shape three packages from the hours I can actually give. Hours I can keep for one client in a four week stretch: [HOURS I CAN KEEP]. Work I already deliver: [PASTE DELIVERABLES]. Output a table with columns Shape, What is in, Hours I spend, Who it suits, and Main risk. Hours must fit inside [HOURS I CAN KEEP] for a single client. Do not state a fee. If hours are blank, write [VERIFY] and stop. Inventing a package I cannot staff would break delivery.
Pro tip: Start from hours you kept last month, not hours you wish you had.
Offer names a buyer can parse
4/30✨ What it does
Produces three short offer names and picks the one a tired buyer can parse first. Vague outcomes are tagged, and no extra promise is added.
Give me three offer names of two to four words for [SERVICE] sold to [CLIENT TYPE] who want [OUTCOME]. One line of reason per name, then pick the name a tired buyer would parse first, in 40 words. Do not claim awards, years or results I did not give. If the outcome is vague, tag it [VERIFY]. A bigger promise I did not write is off limits; inventing one would mislead buyers.
Pro tip: Say the names out loud. If you need a subtitle, the name is still vague.
Who this offer is not for
5/30✨ What it does
Writes a 90 word not-for block with three self-select bullets from your bad-fit notes. If those notes are empty, it asks questions instead of inventing a persona.
Write a 90 word not-for block for my offer. Offer: [PASTE OFFER]. People I already know are a bad fit: [BAD FIT NOTES]. Output three bullets a visitor can self-select on, then a kinder redirect of one sentence. Stay inside the notes. If I did not describe a bad fit, write [VERIFY] and ask me two questions instead of inventing a persona I refuse to serve.
Pro tip: Use real people you declined, with names removed.
Service Pages
5 promptsService page outline from facts
6/30✨ What it does
Outlines a service page with fixed H2s and bullets drawn only from your facts. Empty sections stay tagged, and no logo row or metric is invented.
Outline a service page from facts I will stand behind. Facts: [PASTE FACTS]. Reader: [READER TYPE]. Output H2s in this order: Who it is for, What we do, How it runs, Proof I can show, What happens next. Under each H2, three bullets drawn only from the facts. If a section has no fact, write [VERIFY] and leave bullets blank. Do not invent a logo row, a metric or a client story.
Pro tip: Paste facts as they appear on invoices and emails, not as you wish they read.
FAQ from questions you already hear
7/30✨ What it does
Builds an eight-item FAQ from questions you already hear and answers you can stand behind. Unanswered items are tagged, and no policy is invented.
Turn these real questions into a FAQ of eight items. Questions I hear: [PASTE QUESTIONS]. Answers I can stand behind: [PASTE ANSWER NOTES]. Output Question, Answer of 40 to 70 words, and Source in my notes. If I have no answer for a question, write [VERIFY] and skip a guessed reply. Never invent a policy, a turnaround or a guarantee.
Pro tip: Paste questions in the client's wording, including the blunt ones.
Proof placement without new claims
8/30✨ What it does
Maps proof you already have onto sections of a page draft, with a 20 word line you could add. Sections without matching proof stay tagged.
Place proof I already have onto this page draft. Draft: [PASTE PAGE DRAFT]. Proof I can show: [PASTE PROOF]. Output a table with columns Proof item, Page section it supports, and Line I would add in 20 words. If a section has no matching proof, write [VERIFY] and do not invent a testimonial, a logo or a figure to fill it.
Pro tip: Proof is a named artefact you can show, not a vibe.
Service page gap checklist
9/30✨ What it does
Turns your service page into ten buyer questions marked Answered, Partly or Missing, then flags the two gaps that would stop a yes. Guessed details stay tagged.
Make a checklist of ten questions a buyer should answer from this page. Page text: [PASTE PAGE TEXT]. Mark each Answered, Partly or Missing. List the two gaps that would stop a yes. Do not rewrite the page. If you would have to guess a detail I did not write, mark Missing and tag [VERIFY]. Never invent a spec, a result or a process step.
Pro tip: Paste the live page, including the weak middle.
Rewrite the page for a named reader
10/30✨ What it does
Rewrites a 120 word service summary for a named reader and lists what changed. Needed-but-missing facts are tagged, and unsourced lines are dropped.
Rewrite this service summary for [READER TYPE] in 120 words, keeping the same facts. Summary: [PASTE SUMMARY]. Then list three bullets on what changed and why. Do not add results, clients, awards or years. If the rewrite needs a fact I did not give, write [VERIFY] at that point. Drop the unsourced line rather than inventing it.
Pro tip: Name a real reader type, such as a bakery owner, not everyone.
Outreach Drafts
5 promptsIntro email from a real reason
11/30✨ What it does
Drafts a 110 word intro email from a reason you can defend, optional proof and one ask. Missing reason or proof is tagged, and no mutual contact is invented.
Draft an intro email of about 110 words to [PERSON FIRST NAME] at [ORGANISATION]. Reason I am writing, in my words: [REASON I CAN DEFEND]. Proof I can mention: [PROOF I CAN MENTION]. Ask: [ASK, such as a 15 minute call]. No exclamation marks. If the reason, org or proof is missing, write [VERIFY] in its place. Do not invent a mutual contact, a job they hold or a metric.
Pro tip: Make the ask one sentence at the end so a reply is easy.
Follow-up after silence
12/30✨ What it does
Writes an 80 word follow-up that asks for a yes, a no or a later date. Missing sent dates are tagged, and no scarcity or competitor line is invented.
Write a 80 word follow-up to [PERSON FIRST NAME] after I sent [WHAT I SENT] on [SENT DATE]. Last thing they said, if anything: [PASTE LAST LINE]. Ask once for a yes, a no, or a later date. If I have no sent date, write [VERIFY]. Do not invent a deadline they missed, a competitor they hired or a scarcity line.
Pro tip: Quote their last line so the thread is easy to find.
Referral ask to someone you know
13/30✨ What it does
Writes a 90 word referral ask that states how you know the person and who you want to meet, with an easy no. Blank relationship lines are tagged.
Write a 90 word referral ask to [PERSON FIRST NAME], who knows me as [HOW THEY KNOW ME]. Who I want to meet: [CLIENT TYPE]. Why I am a fit, in my words: [FIT NOTES]. Offer them an easy no. If [HOW THEY KNOW ME] is blank, write [VERIFY]. Never invent a shared project, a result we got together or a person inside their firm.
Pro tip: Give them a sentence they can forward, not a pitch they must rewrite.
Outreach critique before send
14/30✨ What it does
Scores your outreach on clarity, proof, ask and length, then rewrites it from facts you can prove. Unproven names and numbers are tagged in the rewrite.
Score my outreach draft from 1 to 10 on clarity, proof, ask and length. Then rewrite it in 90 to 120 words. Draft: [PASTE OUTREACH DRAFT]. Facts I can prove: [PASTE PROVABLE FACTS]. Output the four scores, then the rewrite. Cut any claim not in the facts. If the draft names a person, title or number I did not prove, tag it [VERIFY]. Inventing a warmer proof point is not allowed.
Pro tip: Paste the first draft, not the polished one, so the scores are honest.
Target list from your own notes
15/30✨ What it does
Ranks organisations you already chose, with a fit line and the first asset you already have. Short lists are not padded, and unsupported fit lines are tagged.
Build a target list from organisations I already chose. Names: [PASTE ORGANISATION LIST]. Why each might fit, in my notes: [PASTE FIT NOTES]. Output a table with columns Name, Fit line under 20 words, First asset I already have, and Open gap. Use only names I pasted. If I pasted fewer than three, say so and do not pad. If a fit line has no support, write [VERIFY]. Inventing an extra buyer would waste a week.
Pro tip: Paste names you could actually email this month, not a dream board.
These prompts give you the what. Tutorials give you the why.
Learn when to use extended thinking, how to build Claude Projects, and workflows that compound. The library keeps growing.
Productized Packages
5 promptsPackage table from a repeated job
16/30✨ What it does
Turns a job you keep repeating into a step table with inputs, hours and late-input risk. Blank hours are tagged, and no fee is stated.
I keep doing [REPEATED JOB] for [CLIENT TYPE]. Hours it usually takes: [HOURS IT TAKES]. Inputs I need: [INPUTS]. Output a table with columns Step, What I do, What they send, Hours, and Risk if that input is late. Steps must add up near [HOURS IT TAKES]. If hours are blank, write [VERIFY] and do not invent a duration. Do not state a fee.
Pro tip: Time the last three jobs. Use the median, not the fastest.
In and out card for a package
17/30✨ What it does
Writes a 120 word in-and-out card with five inclusions, five exclusions and your change rule. A missing change rule is tagged, and no bonus workshop is added.
Write an in and out card of 120 words for this package. Package notes: [PASTE PACKAGE NOTES]. In list of 5, out list of 5, then one sentence on how a change request is handled using [CHANGE RULE I USE]. If I have no change rule, write [VERIFY] on that sentence. Never invent a revision cap, a tool or a bonus workshop.
Pro tip: Put the out list in the same size type as the in list.
Onboarding steps buyers can finish
18/30✨ What it does
Builds an eight-step onboarding list from inputs, access and the start condition you already use. Unnamed tools stay generic and tagged, with no portal invented.
Write an onboarding list of no more than 8 steps for someone who just bought [PACKAGE NAME]. Inputs I need: [INPUTS NEEDED]. Access I need: [ACCESS NEEDED]. Start condition I already use: [START CONDITION]. Number the steps. Do not ask for passwords or bank details. If a step needs a tool I did not name, write [VERIFY] and keep it generic. Do not invent a portal, a login or a kickoff gift.
Pro tip: Ask for access in step 2. Missing logins are the usual delay.
Delivery calendar from your hours
19/30✨ What it does
Lays out a weekly delivery calendar that fits your hour cap and named milestones. Undated milestones are tagged, and no extra review meeting is invented.
Lay out a delivery calendar for [PACKAGE NAME] starting [START DATE]. Hours I can give each week: [HOURS PER WEEK]. Milestones I already promise: [PASTE MILESTONES]. Output one row per week with Week, Milestone, Hours and Rest day [REST DAY]. Fit hours to the weekly cap. If a milestone has no date I can defend, write [VERIFY]. Do not invent a review meeting or a stakeholder I did not name.
Pro tip: Put your rest day on the calendar first so it does not vanish.
Change request reply in hours
20/30✨ What it does
Drafts a 90 word reply that turns an out-of-scope ask into two options costed in hours, with no fee stated. Invoice impact is tagged for you to check.
A client asked for [NEW REQUEST], which sits outside [AGREED SCOPE]. Draft a 90 word reply that offers two ways forward: include it for [EXTRA HOURS] extra hours, or move it to the next cycle. Do not state a fee. If extra hours would change the invoice, write [VERIFY]. Do not interpret a contract. Do not invent extra work I did not describe. Keep the tone friendly and firm.
Pro tip: Give the client the choice. A flat no starts an argument.
Discovery Calls
5 promptsForty minute discovery agenda
21/30✨ What it does
Splits a 40 minute discovery call into five timed blocks with one question each. Missing constraints are tagged, and no budget figure is invented.
Fill a 40 minute discovery agenda for a call with [LEAD NAME] about [SERVICE]. Split minutes across five blocks: context, current setup, success picture, constraints, next step. Output a table with columns Block, Minutes, Goal and Question I will ask. Minutes must add up to 40. Draw questions from [PASTE NOTES]. If notes lack a constraint, write [VERIFY] in that cell. Do not invent a budget, a deadline or a competitor.
Pro tip: Keep your own pitch under eight minutes so they can talk.
Ten questions I actually need
22/30✨ What it does
Writes ten grouped discovery questions under Now, Tried, Constraints and Success. Tool-specific questions stay general and tagged unless you named the tool.
Write ten numbered questions I will ask [LEAD TYPE] on a discovery call for [SERVICE]. Group them under Now, Tried, Constraints and Success. Each question one sentence. Do not ask for bank details or passwords. If a question depends on a tool I did not name, write [VERIFY] and keep it general. Never invent a qualification score or a disqualify rule I did not give you.
Pro tip: Ask what they already tried before you describe your process.
Call notes into a decision table
23/30✨ What it does
Sorts call notes into at most eight rows of quotes, fit and open questions. Unclear points stay tagged, and the proposal-or-decline line stays inside the notes.
Turn these call notes into a decision table. Notes: [PASTE CALL NOTES]. Columns Point, Exact quote, Fit yes no or wait, and Open question. At most 8 rows. Keep quotes word for word. If a point is unclear, tag it [VERIFY]. Guessing what they meant is inventing, so leave the meaning open. End with one sentence on whether I should send a proposal, wait, or decline, using only the notes.
Pro tip: Paste the whole transcript scrap, not the line you liked.
Proposal outline from the call
24/30✨ What it does
Outlines a proposal from the call notes with problem, approach, exclusions, a defensible timeline and a next step. Unsupported sections are tagged.
Outline a proposal from this call, not from my standard deck. Notes: [PASTE CALL NOTES]. Service I can sell: [SERVICE]. Output sections Problem they named, Approach I can take, What I will not do, Timeline I can defend, and Next step. Each section 40 to 70 words. If a section has no support, write [VERIFY]. Do not invent a case study, a team size or a start date.
Pro tip: Echo their words for the problem. Your labels make people feel unsold.
Next step email after the call
25/30✨ What it does
Drafts a 100 word post-call email that restates the promised item, the send date and one open question. Missing dates are tagged, and no bonus session is invented.
Draft a 100 word next-step email to [LEAD FIRST NAME] after a call on [CALL DATE]. What I promised to send: [PROMISED ITEM]. Date I will send it: [SEND DATE]. One question I still have: [OPEN QUESTION]. If a date or promised item is missing, write [VERIFY]. Do not invent a discount, a bonus session or a slot I did not hold.
Pro tip: Send it the same day while the call is still in their head.
Most people use 10% of Claude. Tutorials unlock the rest.
AI Academy: hands-on tutorials on Claude, ChatGPT, Midjourney, and many other AI tools. New tutorials are added regularly.
Pipeline Admin
5 promptsWeekly money-task triage
26/30✨ What it does
Sorts your task list into close, deliver, chase or admin and marks do-this-week against real hours. Missing hour estimates are tagged, and no extra lead is added.
Sort this list into money tasks for the week of [WEEK DATES]. List: [PASTE TASK LIST]. Hours I have: [HOURS AVAILABLE]. Output a table with columns Task, Type (close, deliver, chase, admin), Hours, and Do this week yes or later. Cap hours at what I gave. If a task has no hour estimate, write [VERIFY] rather than inventing a duration that would wreck the week. Do not invent a lead I did not list.
Pro tip: Put close and chase above admin, even when admin feels easier.
Stalled lead triage
27/30✨ What it does
Marks each stalled lead keep, wait or drop with a 12 word next action from your notes. Missing dates are tagged, and no imagined reply is added.
Triage these stalled leads. Notes: [PASTE LEAD NOTES]. For each lead output Name, Last real step, Days since that step if I gave a date, Next action of 12 words, and Keep wait or drop. If I gave no date, write [VERIFY] in Days. Do not invent a reply they sent or a reason they went quiet. Stay inside the notes.
Pro tip: Drop is allowed. A long maybe list hides the people who will buy.
Testimonial request from finished work
28/30✨ What it does
Drafts a 90 word testimonial request after finished work, mentioning a result only when you supplied it. Blank results stay tagged, with no invented quote.
Draft a 90 word testimonial request to [CLIENT FIRST NAME] after [FINISHED WORK]. Specific result I may mention, only if I wrote it: [RESULT I MAY MENTION]. Offer a yes by reply or a short call. If the result is blank, write [VERIFY] and ask about the work without a number. Do not invent a metric, a quote they said or a company they did not name.
Pro tip: Ask while the work is still warm, and make no a fine answer.
Case study skeleton from notes
29/30✨ What it does
Builds a four-part case study skeleton from notes you took, with the client unnamed. Missing result numbers are tagged, and no percentage is invented.
Build a case study skeleton from notes I took, not from memory. Notes: [PASTE CASE NOTES]. Output Problem, Approach, Result, and Quote if one exists in the notes, each 40 to 80 words. Call the client a client. If a result number is missing, write [VERIFY] in Result. Do not invent an industry, a headcount or a percentage.
Pro tip: Get a yes from the client before any public version, even when unnamed.
Decline a bad-fit lead kindly
30/30✨ What it does
Drafts an 80 word decline that shares a reason you can stand behind and one real redirect. Missing redirects are tagged and skipped, not filled with a fake name.
Draft an 80 word decline to [LEAD FIRST NAME] because [REASON I CAN SHARE]. Offer one redirect I actually know: [REDIRECT I CAN NAME]. Keep it warm and short. If I have no redirect, write [VERIFY] and skip that sentence rather than inventing a person, a firm or a product I would send them to. Do not apologise for a full paragraph.
Pro tip: Decline in writing the same day you decide. Silence wastes their hunt.
Free tool
Prompt Optimizer
Turn a rough idea into a structured, professional AI prompt.
Frequently Asked Questions
Prompts are the starting line. Tutorials are the finish.
A growing library of hands-on tutorials on ChatGPT, Claude, Midjourney, and many other AI tools. New tutorials are added regularly.
Related guides