ChatGPT, Claude & Gemini Prompts for Freelancers

Positioning, Niche & Your Offer

Most freelancers lose work before a conversation starts, because nobody can tell what they do or who it is for. These prompts help you choose a niche from your real history, test positioning lines on real people, define the clients worth chasing, package your services into clear offers, tidy your bio and study how peers present themselves using only public text you paste.

You are a pragmatic business coach for freelancers. Help me choose a niche I can actually serve, using only what I tell you.

My trade: {{TRADE}}
Skills and tools I am strong at: {{STRENGTHS}}
Past clients and project types (anonymised): {{PAST_WORK}}
Work I want to do less of: {{AVOID_WORK}}

Produce a shortlist:
1. Four candidate niches, each defined as "who I help" plus "the problem I solve" (for example an industry, a client stage or a recurring job type).
2. For each niche: why my background fits, what I would still need to prove, and one risk (too small, too crowded, hard to reach, price-sensitive buyers).
3. A quick scoring table (1-5) for fit, demand I can check, ease of finding clients and enjoyment, with a one-line reason per score.
4. A recommended pick and one cheap test I could run in two weeks, such as five conversations or one targeted post.

Rules: do not quote market sizes, demand figures or typical rates. Where demand matters, tell me how to check it myself (job boards, search results, asking past clients). Mark every guess as an assumption.
Output: the shortlist, the table, then the recommendation and test.

You are a positioning copywriter who works with solo service providers. Write positioning statements I can test with real people.

What I do: {{SERVICE}}
Who I do it for: {{TARGET_CLIENT}}
The problem they have before they hire me: {{CLIENT_PROBLEM}}
How my approach differs, in plain facts: {{DIFFERENTIATOR}}
Tone: {{TONE}}

Write:
1. Six one-sentence positioning statements, each using a different structure (problem-first, outcome-first, audience-first, process-first, contrast-first, plain-and-literal).
2. For each, a "say it out loud" version of under 15 words that I could use in conversation.
3. One line on who each statement would attract and who it might put off.
4. A recommendation of two to test, plus the question I should ask five prospects to learn which one lands.

Rules: no invented results, client names, awards, years of experience or numbers. No buzzwords such as "world-class", "passionate" or "synergy". Do not claim outcomes I have not stated; describe what I do and for whom. If my inputs are too vague to write something specific, say what is missing instead of padding.
Output: a numbered list of six, then the two-to-test recommendation.

Act as a client-acquisition strategist for independent professionals. Build an ideal client profile from my real experience, not from stereotypes.

My service: {{SERVICE}}
My best two or three past clients and why they were great (anonymised): {{BEST_CLIENTS}}
My worst client experience and what made it bad: {{WORST_CLIENT}}
Where I have already found work: {{CURRENT_CHANNELS}}

Create:
1. A one-page profile: company or person type, size or stage, the trigger event that makes them look for help, who the buyer is, and what they care about when comparing freelancers.
2. Five green flags and five red flags to spot in a first conversation, drawn from my best and worst clients.
3. Six places this client plausibly looks for freelancers or gathers (communities, directories, events, marketplaces, referral sources), each with a low-effort first action.
4. Three questions I can ask on a call to confirm someone fits.

Rules: do not state statistics or budgets for this client type. Where you infer something beyond my notes, label it "inference". Keep suggestions free or cheap, and realistic for one person with limited time.
Output: headed sections matching the numbered list.

You are a business advisor who helps freelancers productise their work. Turn my loose list of services into offers a buyer can understand quickly.

Services I currently provide: {{SERVICES}}
Typical client request that arrives first: {{TYPICAL_REQUEST}}
Hours I realistically have per week for client work: {{WEEKLY_HOURS}}
Things clients often ask for that I do not want to do: {{NOT_OFFERED}}

Design three packaged offers (entry, core, premium or retainer):
1. Name, who it is for, the problem it solves, and what is included as a plain list of deliverables.
2. What is explicitly not included, number of revisions or calls as a placeholder for me to set, and what I need from the client.
3. A suggested sequence of work in steps, with the time I should expect it to take, flagged as [MY ESTIMATE] for me to confirm.
4. How a client would move from the entry offer to the next one.

Rules: do not suggest prices; leave "Price: [SET MINE]". Do not promise outcomes such as rankings, revenue or growth; promise deliverables and process. No fake scarcity.
Output: three offer cards followed by a short note on gaps in my information.

You are an editor who writes professional bios for freelancers. Rewrite my bio and headline so a stranger understands what I do in five seconds.

Current headline and bio: {{CURRENT_BIO}}
Target client: {{TARGET_CLIENT}}
Facts I can back up (tools, years, types of projects, named sectors; nothing else): {{PROVABLE_FACTS}}
Platform: {{PLATFORM}}
Voice: {{VOICE}}

Write:
1. Five headline options within the usual length limit for the platform (tell me the limit you assumed and say if you are unsure).
2. A short bio (about 80 words) and a long bio (about 160 words) in first person, opening with the client's problem rather than my history.
3. A one-line call to action that fits the platform.
4. A list of anything in my current bio that is vague, unprovable or generic, with a suggested replacement.

Rules: use only the facts I gave. Do not add awards, client names, numbers, results or claims such as "top-rated" unless I listed them. If a detail would strengthen the bio, ask for it in a list at the end labelled "Add if true".
Output: headlines, both bios, CTA, then the audit list.

You are a market analyst reviewing how freelancers present themselves. Compare how others in my space position themselves, using only the profile text I paste.

My trade: {{MY_TRADE}}
My target client: {{MY_CLIENT}}
Profiles or website "about" text from 4 to 6 peers (paste the public text, remove personal details): {{PEER_PROFILES}}
How I currently describe myself: {{MY_POSITIONING}}

Analyse:
1. A grid with one row per peer: who they say they serve, their main promise, the proof they cite, their tone, and what they leave out.
2. Patterns: phrases and claims that every peer repeats, and which ones have become noise.
3. Gaps: audiences, problems or kinds of proof that nobody addresses well, based strictly on what I pasted.
4. Three ways I could differentiate honestly, given the facts in my own description.

Rules: only draw conclusions from the pasted text. Do not guess their prices, results or client lists. If a claim is not in the text, write "not stated". Say plainly that five profiles is a small sample and not a market view. Do not suggest copying anyone's wording.
Output: the grid, a short pattern list, the gaps, then the three options.

Portfolio, Case Studies & Testimonials

Proof sells freelance work, and proof has to be true. Turn rough project notes into a case study with every missing number flagged instead of invented, ask clients for results with neutral questions, write short portfolio captions, choose which pieces to show a target client, request testimonials and trim them without changing what the client said.

You are a case-study writer for independent professionals. Turn my rough project notes into a credible case study that never claims more than I can prove.

Notes: {{PROJECT_NOTES}}
Client type (anonymised unless I have permission): {{CLIENT_TYPE}}
My role and tools: {{MY_ROLE}}
Results I can prove, with how I know (leave blank if none): {{PROVEN_RESULTS}}
Lessons I learned (leave blank if none): {{LESSONS_LEARNED}}
Length: {{LENGTH}}

Write the case study in this order: situation, the problem and why it mattered, what I did and why, what changed, and what I would do differently.

Rules: use only facts in my notes. Never invent metrics, quotes, percentages, timelines, client names, reasons or testimonials. If no result is proven, describe the observable outcome qualitatively and say so. If I gave no lessons, write "[ADD: lesson]" under the last heading rather than inventing one. Wherever a number or quote would strengthen the piece, insert a bracket such as [ADD: before and after figure, if the client agrees to share]. Credit the client's team where they did work.
Output: the case study with headings, then a list of every bracketed gap and the question I should ask the client to fill it.

You are a freelancer's assistant who prepares client conversations. Draft the questions I should ask a happy client so I can document results accurately, without putting words in their mouth.

Project I delivered: {{PROJECT_DESCRIPTION}}
What the client originally wanted: {{ORIGINAL_GOAL}}
Metrics they probably track (guess if unsure, I will confirm): {{POSSIBLE_METRICS}}
Our relationship: {{RELATIONSHIP}}

Write:
1. A short, warm email asking for a 15-minute call or five written answers, saying what I want to use the answers for and offering them approval before anything is published.
2. Eight neutral questions covering before, after, what was hard, what surprised them, and what they would tell someone considering me. Questions must not suggest the answer.
3. Three questions specifically about measurable change, each with an easy way for them to say "I can't share that".
4. A short note for me on what to record (date, who said it, their permission) so every claim has a source.

Rules: do not draft the answers for them or assume any result happened. Do not pressure. Keep the email under 130 words.
Output: the email, the question list, then the record-keeping note.

You are a portfolio editor. Write the short description that sits under one project on my portfolio page so a busy prospect understands it in 20 seconds.

Project name or label: {{PROJECT_LABEL}}
What it was and who it was for: {{PROJECT_SUMMARY}}
What I personally did: {{MY_CONTRIBUTION}}
Proof I have permission to show (outcome, quote, link): {{PERMITTED_PROOF}}
The kind of client I want this piece to attract: {{TARGET_CLIENT}}

Write:
1. A one-line caption of under 15 words.
2. A 50-70 word description: the brief, my part, the result I can support.
3. Three tags for filtering (for example project type, industry, tool).
4. A single sentence a visitor can read as "this could be me", written for my target client.
5. A note on anything I should check before publishing (client permission, confidentiality, attribution).

Rules: use only the information supplied. No superlatives, no invented outcomes or numbers. Do not name the client unless I gave permission in the proof field. If the contribution is shared with a team, say so.
Output: the five items labelled, ready to paste.

You are a portfolio strategist. Help me choose which projects to show and in what order for a specific kind of client, with no more than {{MAX_PIECES}} pieces.

Target client or role I am pursuing: {{TARGET}}
My project list (one line each: what it was, my role, any proof I can show, whether public or confidential): {{PROJECT_LIST}}
Skills I want to be hired for next: {{DESIRED_WORK}}
Constraints (confidentiality, formats, platform limits): {{CONSTRAINTS}}

Do this:
1. Score each project for relevance to the target, strength of proof, and permission to show it. Use High, Medium or Low, with one sentence of reasoning.
2. Choose the final selection and explain why each earns its place.
3. Recommend an order, saying what the first and last pieces should accomplish.
4. List what is missing for this target (for example no example of a certain format) and a small self-initiated project I could do to fill it, clearly labelled as a personal or spec project.

Rules: never suggest presenting spec or personal work as client work. Do not invent projects or results. If a project's permission is unknown, mark it "ask before using".
Output: scoring table, final order with reasons, then the gap list.

You are a writer of friendly, brief client emails for freelancers. Draft a testimonial request that makes it easy for the client to give something specific and true.

Client first name: {{CLIENT_NAME}}
Project I finished: {{PROJECT}}
When it ended: {{END_DATE}}
Where I plan to use the testimonial: {{USE_CASE}}
My tone with this client: {{TONE}}

Write:
1. A subject line (three options).
2. An email under 140 words that thanks them for a specific part of the project, asks for a testimonial, and says where it will appear.
3. Three short prompts they can answer in a sentence each: what was the situation, what was it like working together, and what changed afterwards. Avoid leading wording.
4. A line offering to draft something for their approval if writing is a chore, with a plain statement that I will change nothing without their sign-off.
5. A polite reminder to send if I have not heard in a week, under 60 words.

Rules: do not write the testimonial itself or imply they have promised one. No pressure, guilt or flattery. Do not offer discounts or favours in exchange for praise.
Output: subjects, email, questions, approval line, reminder.

You are a careful editor. I have a real testimonial and want a shorter version for my site. You may trim it but you may not change what the client said.

Original testimonial exactly as received: {{ORIGINAL_TESTIMONIAL}}
Client name and role as they want it shown: {{ATTRIBUTION}}
Space available: {{TARGET_LENGTH}}
Where it will appear: {{PLACEMENT}}

Do this:
1. Provide up to three trimmed versions, each shorter than the last, using only words and phrases from the original. Use an ellipsis for cuts, and fix only obvious typos.
2. Show for each version what was removed, so I can check meaning is intact.
3. Suggest a pull quote of one sentence to use as a headline, taken verbatim.
4. Flag anything in the original that makes a claim I should be able to back up (a number, a ranking, a promise about me) and any detail that could identify the client against their wishes.
5. Draft a two-line message to send the client with the edited version for approval.

Rules: no paraphrasing, no added praise, no new facts, and no merging of separate statements into a single claim they did not make.
Output: the three versions with removals noted, the pull quote, the flags, then the approval message.

Proposals & Pitches: Marketplaces and Direct

A good proposal shows you read the brief. Decode a job post for hidden scope and red flags, write a tailored Upwork-style cover letter, set up a Fiverr-style gig, send a cold pitch built on one real observation, follow up without nagging, write a direct-client proposal and decide with a scorecard whether a lead deserves your time at all.

You are an experienced freelancer who writes short, specific marketplace proposals that clients actually read to the end.

Job post (paste in full): {{JOB_POST}}
My relevant experience, stated as facts I can prove: {{MY_EXPERIENCE}}
Link or description of the one most relevant sample: {{RELEVANT_SAMPLE}}
My availability and rough timeline: {{AVAILABILITY}}
Pricing approach I want to mention, if any: {{PRICING_NOTE}}

Write a cover letter of 120-170 words:
1. Opening line that shows I understood their specific problem, quoting or echoing a detail from the post (not "I am excited to apply").
2. Two sentences on why my background fits, tied to their situation.
3. One sample reference, described honestly.
4. A short plan: what I would do first and what I need from them.
5. Two clarifying questions that show thinking, not stalling.
6. A simple next step.

Rules: do not invent experience, results, client names or reviews. If the job post asks for something I do not do, flag it in a note to me rather than pretending. Do not use template phrases such as "I am a perfect fit". Plain tone, no emojis unless the post uses them.
Output: the proposal, then a short list of anything I should confirm before sending.

You are a seasoned freelancer who reads job posts like contracts. Analyse the post below before I decide whether to bid.

Job post: {{JOB_POST}}
My skills and rate floor (the lowest I would accept): {{MY_PROFILE}}
My current workload: {{WORKLOAD}}
Anything the client has said about budget or timeline: {{BUDGET_TIMELINE}}

Provide:
1. A plain restatement of what the client actually wants, separating stated requirements from guesses.
2. What is missing or ambiguous (scope, deliverables, who approves, data or access, revision limits).
3. Warning signs, each quoted from the post with why it matters (for example open-ended revisions implied, "quick" job with large scope, unpaid test work, off-platform payment requests). If there are none, say so; do not invent concerns.
4. Eight clarifying questions in priority order.
5. A bid recommendation (bid, bid with conditions, or pass) with the deciding reasons.

Rules: judge only what is written. Do not guess the client's budget. Say where a flag is a possibility, not a certainty. This is practical advice, not legal advice.
Output: the five numbered parts, concise.

You are a marketplace copywriter who understands that buyers skim. Write a gig listing for my service.

Service: {{SERVICE}}
Buyer I want: {{TARGET_BUYER}}
What I can deliver in each tier (basic, standard, premium), including turnaround and revisions I am willing to give: {{TIER_DETAILS}}
Questions I need answered by the buyer before starting: {{BUYER_INPUTS}}
Samples I can show: {{SAMPLES}}

Write:
1. Three gig title options in the platform's usual style, with a note that I should check current character limits myself.
2. A description opening with the buyer's problem, then what they get, how the process works, what I need from them, and what is not included.
3. Package descriptions for the three tiers in parallel structure so they compare easily.
4. Six FAQ entries answering real objections (revisions, file formats, rush orders, custom requests, commercial use, communication).
5. Search tags: a list of phrases a buyer might type, longer than needed. Tell me to keep only as many as the gig editor currently allows (I will check the limit and any character limit there), and label the phrases as guesses.

Rules: no inflated claims, fake urgency, "guaranteed" language or invented reviews. State delivery limits clearly. Do not promise anything that breaks the platform's published rules; tell me to check them.
Output: titles, description, tiers, FAQ, tags.

You are a freelance outreach specialist who writes short emails that read like a person wrote them. Draft a first-contact pitch to a business I would genuinely like to work with.

Prospect (company and role, public information only): {{PROSPECT}}
Specific observation I made about their business, which I can point to publicly: {{OBSERVATION}}
The relevant thing I can help with: {{MY_OFFER}}
One piece of proof I can honestly cite: {{PROOF}}
The small first step I want to propose: {{NEXT_STEP}}

Write:
1. Three subject lines, plain and under 7 words.
2. An email of 90-120 words with this shape: the observation, why it matters, what I could do, the proof, and one low-pressure question.
3. A version of the same email under 60 words for LinkedIn or a contact form.
4. A line of guidance on whether this should be sent to a named person or a general address.

Rules: do not flatter, criticise their current work harshly, or claim to have found a "problem" I cannot show. No made-up numbers, mutual connections or familiarity. No attachments or links beyond the one I provided. Note that I should check applicable email and anti-spam rules for my country before sending cold email.
Output: subjects, long email, short version, guidance.

You are an experienced solo freelancer preparing for a short call with a marketplace lead. I must decide whether I can and should take the work.

What I know from their message or job post: {{LEAD_INFO}}
My service: {{MY_SERVICE}}
My capacity in the next two months (hours per week free, current commitments): {{MY_CAPACITY}}
Whether the marketplace holds payment in escrow or I invoice directly: {{PAYMENT_ROUTE}}
My pricing approach, if it comes up: {{PRICING_NOTE}}

Write:
1. A 15-minute agenda with timings.
2. Seven questions in order: what triggered the enquiry, what success looks like, who decides, timing, what they tried before, what they already have, budget range. Mark the two I must not skip.
3. A capacity check: estimate the weekly hours this work might need (labelled an estimate), whether I can start now, later or with a smaller scope, and a polite line for each.
4. Questions on how contract and payment will run on the platform, so I can read its current terms first. Do not suggest going off-platform or avoiding fees.
5. Three signs the lead is not a fit, a polite way to end early, and what to say if asked for a price on the spot without inventing a figure.

Output: the five parts, concise, with no follow-up email.

You are a freelancer who writes clear, one-to-three page proposals that clients can approve quickly. Draft the structure and text for a proposal.

Client and their situation (anonymised if needed): {{CLIENT_SITUATION}}
What they asked for (and where I think the real need differs): {{CLIENT_REQUEST}}
Deliverables and approximate timeline, as I understand them: {{DELIVERABLES_TIMELINE}}
My relevant background, provable facts only: {{MY_BACKGROUND}}
Fee I have decided on: {{FEE}}
Payment terms I have decided on: {{PAYMENT_TERMS}}

Write the proposal with these headings: Understanding of your situation; Proposed approach; Deliverables; Timeline; What I need from you; Not included; Investment and payment; Next steps.

Rules: copy the fee and payment terms exactly as I gave them and do not suggest legal wording. Use "Not included" to list at least four items likely to be assumed, marked [CONFIRM]. Do not invent testimonials, past results or guarantees. Where my notes are thin, insert [MY INPUT NEEDED: question] rather than filling the gap. Keep language plain and free of jargon.
Output: the full proposal with the headings above, then a checklist of every bracketed item I must resolve before sending. Remind me that a signed contract is separate and I may want legal advice on it.

You are an adviser for solo freelancers on marketplaces. Work out what this bid really costs me.

Job post: {{JOB_POST}}
Cost to submit a proposal (credits or connects), or "none": {{BID_COST}}
My win rate on similar bids, or "unknown": {{WIN_RATE}}
Marketplace fee percentage on earnings, or "none": {{PLATFORM_FEE}}
Hours to write a strong proposal: {{PROPOSAL_HOURS}}
My minimum take-home hourly rate: {{MINIMUM_RATE}}

Calculate and explain, showing arithmetic:
1. Cost of one bid in credits and in my time (proposal hours times my minimum rate), from my numbers only.
2. If the job pays what the post suggests: take-home after the platform fee, and effective hourly rate at low, expected and high work hours.
3. Break-even: how many such bids I can lose before this lead type stops paying, using my win rate. If unknown, say so and show a labelled assumption.
4. Three signals in the post that raise or lower the odds, quoted.
5. A recommendation (bid, bid with conditions, pass) and what to learn first.

Rules: do not use outside figures for fees, win rates or budgets. If the post gives no budget, say the calculation is conditional.
Output: a short calculation table, then the signals and recommendation.

You are a profile optimiser for freelancing platforms. Rewrite my profile overview so it speaks to a specific buyer and passes a quick skim.

Platform: {{PLATFORM}}
Current profile text: {{CURRENT_PROFILE}}
Services and skills to emphasise: {{SERVICES}}
The buyer I want: {{TARGET_BUYER}}
The problem I solve for them: {{BUYER_PROBLEM}}
Proof I can verify (completed work types, tools, certifications I hold, genuine reviews I may quote): {{VERIFIABLE_PROOF}}

Write:
1. A strong first two lines, since most platforms show only those before a "read more".
2. A full overview of 150-220 words with short paragraphs and a scannable list of services.
3. A closing call to action that tells the visitor what to send me first.
4. A list of skill keywords I should consider, longer than needed, labelled as suggestions; I will check how many skills the profile editor allows and choose within that limit.
5. A list of what I should avoid saying on this platform (for example contact details or off-platform links where rules forbid them), with a reminder to read the current rules.

Rules: no invented ratings, earnings, job counts or badges. Quote reviews only if I supplied the exact text. Avoid cliches such as "hard-working team player". Write in the first person.
Output: opening lines, overview, CTA, keywords, avoid-list.

Pricing, Quotes & Rates

Pricing is where freelancers feel most alone. These prompts structure the thinking and leave the numbers to you: three-option project pricing, converting hours into a fair fee with risk buffers, a retainer proposal, a rate increase email, a calm reply to price objections and a quote email that spells out its assumptions. None quote market rates, because the model does not know yours.

You are a pricing coach for freelancers who sell projects rather than hours. Structure three options for a client proposal. You will not set the numbers; I will.

Project: {{PROJECT}}
Client goal: {{CLIENT_GOAL}}
Core deliverable that must be in every option: {{CORE_DELIVERABLE}}
Extras I could add: {{OPTIONAL_EXTRAS}}
What a good outcome is worth to this client, in their words or my best reading (label which): {{CLIENT_VALUE}}
My costs in time and tools: {{MY_COSTS}}

Build:
1. Three options: a lean one, a recommended one, and a premium one. Show what differs in scope, support, speed and revisions, in a comparison table.
2. A short reason a client might choose each.
3. Placeholders for my price on each line, in the form [PRICE A], [PRICE B], [PRICE C], and a method for me to set them: cost floor, value anchor, and the ratio between options. Explain the method without suggesting dollar figures.
4. A paragraph I can paste into the proposal introducing the options.
5. Two things that might cause the client to push back and how to respond.

Rules: no invented market rates, no claims that the work will deliver a specific financial return, and no guarantees. Where client value is a guess, say so.
Output: comparison table, intro paragraph, pricing method, pushback notes.

You are a freelancing finance coach. Help me turn my hour estimates into a project fee that reflects the real work, using only my own figures.

Project description: {{PROJECT}}
Task list with my best hour estimate for each: {{TASK_HOURS}}
My target hourly equivalent: {{TARGET_RATE}}
My usual overhead on projects like this, as a percentage of delivery hours, from my own records (if I have none, write "no data"): {{OVERHEAD_PERCENT}}
Risks that could expand the work: {{RISKS}}

Calculate and explain:
1. A table of tasks with low, expected and high hours; flag optimistic estimates.
2. Overhead hours from my percentage. If I wrote "no data", show the fee at 10%, 20% and 30%, labelled as my assumptions to replace.
3. A contingency in hours for each named risk, which I can accept or reject.
4. A floor, target and stretch fee, with arithmetic shown from my target rate.
5. A sanity check against my weekly hours, and what belongs in a change-order note instead.

Rules: show every calculation. Do not use outside market data or typical rates. Remind me that taxes, platform fees and unpaid time affect take-home, and to confirm those with an accountant.
Output: table, calculation steps, three fee figures, sanity check.

You are a business adviser helping a freelancer propose a monthly retainer to a client who keeps coming back. Write the proposal structure and wording.

Client and the recurring work they already give me: {{RECURRING_WORK}}
What a retainer should do for them (priority access, predictability, consistent quality): {{CLIENT_BENEFITS}}
Monthly capacity I can reserve: {{MONTHLY_CAPACITY}}
What happens beyond it: {{OVERFLOW_RULE}}
Preferred term and notice period, if I have one: {{TERM}}
Fee per month once I decide it: {{MONTHLY_FEE}}

Write:
1. A short email introducing the idea from the client's point of view.
2. A one-page retainer outline: included activities, monthly hour or deliverable cap, response times I can commit to, what happens with unused time (my policy placeholder: [ROLLOVER POLICY]), reporting, and how extra work is quoted.
3. Review points at 90 days and what we would look at then.
4. Three objections the client may raise and calm, honest answers.
5. A short list of things to decide before sending, such as notice, price changes and cancellation.

Rules: copy my fee exactly as given; do not draft contract clauses or legal terms. Don't promise availability I haven't stated. No claims about savings the client will make.
Output: email, outline, review points, objections, decision list.

You are an experienced freelancer who handles rate increases with courtesy and confidence. Draft the email and a plan for the likely replies.

Client name: {{CLIENT_NAME}}
Current rate or fee and when it last changed: {{CURRENT_RATE}}
New rate: {{NEW_RATE}}
Effective date: {{EFFECTIVE_DATE}}
Honest reasons for the increase (skills added, costs, demand on my time): {{REASONS}}
What I am willing to offer in return, if anything (grandfathering for current projects, notice period): {{CONCESSIONS}}

Write:
1. An email of 120-150 words that opens with appreciation of something specific, states the new rate and date plainly, gives one honest reason, and invites questions. No apologising or over-explaining.
2. A short variant for a client I may be happy to lose.
3. Three possible replies (accept, ask for a discount, push back strongly) with a calm response to each, within my stated concessions.
4. A line I can say if the conversation is by phone.
5. Notes on timing and what I should check in my existing agreements before changing a rate.

Rules: use only the figures I gave. Don't invent market data or imply that other clients have already agreed. Don't use threats or guilt.
Output: email, variant, reply scripts, phone line, notes.

You are a sales-minded coach for freelancers who dislike selling. Prepare my response to a client who says my quote is too high.

What I quoted: {{QUOTE}}
What it covers: {{QUOTE_SCOPE}}
Client's exact words or message: {{CLIENT_OBJECTION}}
What I know about their budget, decision process and alternatives: {{CLIENT_CONTEXT}}
My minimum below which I would walk away (kept private): {{WALK_AWAY_POINT}}

Provide:
1. A diagnosis: which of these the objection most likely is (budget, value not clear, comparing to a cheaper option, no authority, stalling), with the evidence from their words and the questions that would confirm it.
2. A calm reply that asks about their real constraint and does not defend myself.
3. Three ways to meet a genuine budget limit that protect my rate, such as reducing scope, phasing, or removing a deliverable, each with the exact wording to propose.
4. A line for declining politely if none work.
5. What I should not do (for example discount without changing scope).

Rules: by default, do not suggest lowering the price with the scope unchanged, unless I say in CLIENT_CONTEXT that I am open to a goodwill discount. Do not invent competitor prices or claim my quote is "the market rate". Don't use manipulation or false scarcity.
Output: diagnosis, reply message, three options, polite decline, avoid-list.

You are a freelancer who writes quotes that prevent disputes later. Draft the email accompanying my quote, addressed to "Hi [NAME]".

Project: {{PROJECT}}
What the quote includes: {{INCLUDED}}
Assumptions the price depends on (client supplies content, number of revisions, review turnaround, access): {{ASSUMPTIONS}}
Fee: {{FEE}}
Deposit and schedule as I decided: {{DEPOSIT_SCHEDULE}}
Quote valid until: {{VALID_UNTIL}}

Write:
1. A subject line.
2. An email of under 200 words: a one-line summary of what I understood, the fee, the deposit and schedule exactly as given, the key assumptions in a bulleted list, and a clear next step to accept.
3. A sentence explaining that changes outside these assumptions will be quoted separately before any work begins, written in friendly language.
4. A short "what happens after you say yes" paragraph with three steps.
5. A list of what I should attach or link (scope document, terms, example) and the details I should verify in my own paperwork.

Rules: copy numbers and dates exactly; do not recalculate or invent. No legal wording; if my terms are in a separate contract, refer to it generically. No guarantee of results.
Output: subject, email, assumption sentence, next-steps paragraph, attachment checklist.

Scope, Contracts & Client Onboarding

Clear starts prevent most later disputes. Draft a scope with explicit exclusions, get a plain-English reading of a contract clause so you know what to ask, prepare a checklist for a lawyer or the client, run a kickoff questionnaire, send a welcome plan for week one and explain your revision policy kindly. Contract prompts explain and prepare; they never replace legal advice.

You are an adviser for solo freelancers. Build a one-page scope sheet covering what a one-person business must settle.

Project and the client's goal: {{PROJECT_GOAL}}
Deliverables with format and quantity: {{DELIVERABLES}}
My availability for this client (days, holidays, other commitments): {{MY_AVAILABILITY}}
Marketplace or platform fee that applies, or "none": {{PLATFORM_FEE}}
What the client has hinted they may also want: {{POSSIBLE_EXTRAS}}

Write the sheet with these headings:
1. Deliverables, each with an "accepted when" test, plus a "Not included" list covering the hinted extras and four commonly assumed items, marked [CONFIRM].
2. My capacity: reply times, illness cover, and whether a subcontractor may be used (a question for me).
3. Money placeholders: [DEPOSIT], [KILL FEE IF CLIENT CANCELS], [PLATFORM FEE: WHO BEARS IT], [RUSH SURCHARGE].
4. Rights questions: portfolio use, credit, when ownership passes.
5. Change-request steps.

Rules: this is a planning sheet, not a contract. Do not suggest figures or legal wording; for kill fees and rights, list the questions and say a lawyer should draft the terms. Do not invent deliverables.
Output: the sheet with the five headings, then a list of unanswered questions.

You are a plain-language explainer, not a lawyer. I am a solo freelancer reading a client's contract. Help me understand one clause from a freelancer's point of view so I know what to ask.

Clause text (paste only the clause, remove names): {{CLAUSE_TEXT}}
Clause topic (for example kill fee, ownership of work, portfolio rights, non-compete, payment on approval, indemnity): {{CLAUSE_TOPIC}}
My trade: {{MY_TRADE}}
Country or state whose law probably applies: {{JURISDICTION}}
What the client told me it means: {{CLIENT_EXPLANATION}}

Provide:
1. A one- or two-sentence paraphrase, and any wording that could be read two ways.
2. What this clause could mean for a one-person business in a realistic case for my trade (for example work cancelled halfway, a client who reuses my work, a competitor client).
3. Whether the clause is usually negotiated and what I could ask for in general terms, without drafting replacement wording.
4. Three questions for the client and three for a qualified lawyer.
5. How confident you are (high, medium, low) and why.

Rules: laws vary by place and change; say you cannot be sure how this would be read in my jurisdiction. Do not tell me whether to sign. Do not cite statutes or cases.
Output: the five parts, then one sentence recommending professional advice before signing.

You are a freelancer's business-operations assistant. Create a checklist of the topics to look for in a client's contract so I can spot gaps. You are not a lawyer and this is not legal advice.

Type of work I do: {{WORK_TYPE}}
Client type: {{CLIENT_TYPE}}
Where the client is located: {{CLIENT_LOCATION}}
Contract text or a bullet summary of its headings (paste what you have): {{CONTRACT_SUMMARY}}
The things most important to me in this relationship: {{MY_PRIORITIES}}
Past problems I have had with clients: {{PAST_PROBLEMS}}

Provide:
1. A table of topics to check, each with "present in my contract (yes, no, unclear)", why the topic matters to a freelancer, and the question to ask. Cover payment terms, late fees, kill fees, ownership of work, credit and portfolio use, confidentiality, revisions, termination, liability, who pays expenses, and anything specific to my work type.
2. A list of items that appear in the text but need explaining.
3. The five questions most worth taking to a lawyer, given my situation.
4. A short script for asking the client for a change without souring the relationship.

Rules: do not draft legal wording or tell me what is enforceable. Mark any statement that depends on local law as "check locally". Do not say a contract is safe or unsafe.
Output: the table, the lists, the script.

You are a project-minded freelancer who runs smooth starts. Create a kickoff questionnaire for a new client in my field.

My trade: {{TRADE}}
The project: {{PROJECT}}
What I already know about the client: {{KNOWN_INFO}}
Materials, access or accounts I need: {{NEEDS}}
Decision-makers and approval process, if known: {{APPROVAL_PROCESS}}
Preferred communication channel: {{CHANNEL}}

Write:
1. An intro paragraph under 60 words explaining why the answers help and how long they will take.
2. A questionnaire of 15 to 20 questions grouped under: goals and success, audience, brand and examples they like or dislike, content and assets, approvals and people, timing and constraints, and communication preferences. Each question should be answerable in a sentence or two.
3. Mark the five most essential questions and what I cannot start without.
4. A short follow-up message to send if the questionnaire is not returned in three days.
5. A suggestion for turning the answers into a half-page project brief that I send back for confirmation.

Rules: no questions about budget unless I flagged it. Avoid jargon and any question the proposal already answers. Do not assume facts about the client's industry.
Output: intro, grouped questionnaire with essentials marked, reminder, brief template.

You are a freelancer who makes onboarding feel organised and calm. Write the welcome message and the plan for week one.

Client name: {{CLIENT_NAME}}
Project: {{PROJECT}}
What has been agreed so far (scope, start date, deposit received): {{AGREED}}
What I need from them in week one: {{WEEK_ONE_NEEDS}}
How we will communicate and how fast I normally reply: {{COMMUNICATION}}
Key dates and milestones: {{KEY_DATES}}

Write:
1. A welcome email under 180 words: thanks, what happens next, the three things I need from them with dates, and how to reach me.
2. A one-page "how we will work together" note: communication channels, reply times, how feedback should be given (one set of consolidated comments), how approvals work, and who holds what.
3. A day-by-day outline for the first five working days showing who does what.
4. A short list of tools or accounts the client may need to set up, and anything I should avoid asking them to share by email (such as passwords) with a safer alternative.

Rules: do not promise availability or response times I have not stated. Don't introduce new scope or fees. Keep the tone friendly and professional without being gushing.
Output: the email, the working note, the day plan, the tools list.

You are a communications adviser for freelancers. Help me tell clients honestly how I use AI tools and protect their information.

My trade: {{MY_TRADE}}
Where I use AI today (for example research, first drafts, editing, code suggestions, transcription): {{AI_USES}}
Where I never use AI or always review by hand: {{AI_LIMITS}}
How I handle client files and confidential material: {{DATA_HANDLING}}
What the client's contract or brief says about AI, if anything: {{CLIENT_AI_RULES}}

Write:
1. A disclosure paragraph for proposals or my site (under 90 words).
2. A fuller onboarding note (150-200 words) on how I use AI and protect information.
3. A truthful reply to "do you use AI?", and a reply for a client who forbids AI use.
4. Questions to settle before sharing confidential material (tools, account type, retention, approval), and questions for a lawyer if the contract mentions AI, ownership or confidentiality.

Rules: describe only the uses and safeguards I listed; do not claim safeguards, certifications or tool settings I did not state, and tell me to check each tool's current data terms myself. Do not draft legal wording. Never suggest hiding AI use from a client who asked.
Output: the paragraph, the note, the two replies, the checklist.

You are a communication specialist for freelancers. Turn my revision approach into wording that is clear and warm rather than legalistic.

How many rounds of revisions are included: {{REVISION_ROUNDS}}
What counts as a revision versus a new request: {{DEFINITION}}
How feedback should be given and who consolidates it: {{FEEDBACK_PROCESS}}
How long the client has to respond before the project pauses: {{RESPONSE_WINDOW}}
What happens when we exceed the included rounds: {{EXTRA_ROUNDS_APPROACH}}

Write:
1. A policy paragraph for my proposal (under 120 words).
2. A shorter version for a website FAQ or service page.
3. A script for explaining it live on a kickoff call.
4. An example showing the difference between a revision and a new request, using a made-up generic project for my trade.
5. A gentle reply to use when a client asks for something that goes beyond the included rounds.

Rules: use only the terms I gave you. Don't set fees or invent a legal term. Don't use threatening language or small print. If my definition is ambiguous, list the questions a client might ask and let me answer them.
Output: the paragraph, FAQ version, kickoff script, example, reply.

Scope Creep, Feedback & Difficult Clients

The hard emails are the ones you put off. Reply to scope creep with a change order, reconcile conflicting feedback, decline work politely, nudge a client who has gone silent, answer a rush request with options and end a relationship cleanly. Each draft is calm, factual and free of threats.

You are an experienced freelancer who handles scope creep without conflict. Draft my reply to a request that goes beyond what we agreed.

Original agreed scope: {{AGREED_SCOPE}}
The new request, in the client's words: {{NEW_REQUEST}}
Is it new work, a change, or something small I might include as goodwill? (my view): {{MY_VIEW}}
Time and cost impact as I estimate them: {{IMPACT}}
Relationship and tone: {{RELATIONSHIP}}

Write:
1. A reply of 120-160 words that acknowledges the idea positively, explains how it sits against the agreed scope without blaming, states the impact, and offers two ways forward (add it as a change with a quote, or swap it for something in scope).
2. A one-paragraph change order summary I can attach: description, effect on timeline, effect on fee in the form [FEE], and approval line.
3. A shorter reply for when I choose to do it for free this once, framed so it does not set a precedent.
4. A line for a call.
5. A short note on spotting the pattern, and what to say if creep keeps happening.

Rules: no accusations, sarcasm or ultimatums. Use my estimates; do not invent costs. No legal wording. Do not promise delivery dates I have not given.
Output: reply, change-order paragraph, goodwill version, call line, pattern note.

You are a calm project editor who untangles feedback from several stakeholders. Help me turn conflicting comments into a plan that respects the brief.

Original brief and goals: {{BRIEF}}
Feedback from each person (label by role, not name): {{FEEDBACK}}
Who has final approval: {{DECISION_MAKER}}
Deadline: {{DEADLINE}}
Revision rounds remaining: {{ROUNDS_LEFT}}

Produce:
1. A table of every comment with: who said it, whether it supports the brief, contradicts another comment, or is new scope.
2. A list of the real conflicts, with the underlying concern behind each position, in a sentence.
3. Questions to ask the decision-maker to settle them, written so I do not appear to take sides.
4. A proposed resolution for each conflict, with the reasoning, and which comments I suggest not acting on and why.
5. A short message to send the client asking them to confirm a single consolidated set of changes before I start.

Rules: base judgements on the brief, not on my taste. Don't speculate about people's motives beyond what the comments show. Flag any change that affects scope or timeline. Be polite about all contributors.
Output: the five parts, concise and ready to act on.

You are a professional communicator. Write a clear, kind message declining a project and, where it makes sense, pointing the person toward a better option.

What they asked me to do: {{REQUEST}}
Why I am declining (be honest; I will choose what to share): {{REASON}}
Whether I would want to work with them in future, and under what conditions: {{FUTURE_INTEREST}}
Referral or alternative I could suggest, if any: {{ALTERNATIVE}}
Relationship and channel: {{RELATIONSHIP_CHANNEL}}

Write:
1. A decline of 70-110 words that thanks them, gives a short honest reason without over-explaining, and avoids false excuses.
2. A version that offers a conditional "yes" (for example a different scope, later date or higher fee) if I am open to it.
3. A version that points to an alternative or colleague, with a reminder for me to ask that person first.
4. A firmer version for someone who has already pushed back once.
5. A one-line response if they ask why.

Rules: no lies such as a fabricated schedule conflict. Don't criticise the client or the brief. Do not recommend a person or tool I have not named. No negotiating tactics or false warmth.
Output: four message variants and the one-line answer.

You are a communications coach for freelancers. Write messages to a client who has stopped responding in the middle of a project.

Project and where we are: {{PROJECT_STATUS}}
What I am waiting for from them: {{WAITING_FOR}}
Dates of my last messages and any deadlines affected: {{TIMELINE}}
What my agreement says about delays, in my own words (I will check the exact wording): {{DELAY_TERMS}}
The relationship so far: {{RELATIONSHIP}}

Write:
1. A first nudge under 70 words: friendly, specific about what I need and why, with a date, and an easy reply option.
2. A second message after a few days: states plainly how the delay affects the schedule and proposes a new timeline.
3. A final message that says the project will be paused until I hear back and what restarting involves, without threats.
4. A suggestion for a different channel, such as a call or another contact, and what to say.
5. A checklist for me: what to document, what to confirm in my agreement, and what not to do (such as withholding anything before checking my rights).

Rules: assume they are busy, not rude. No guilt or sarcasm. Do not invent contract terms or legal consequences. Don't promise anything I have not mentioned.
Output: three messages, channel idea, checklist.

You are a calm, solutions-focused freelancer. Draft a reply that neither gives in to nor shuts down an urgent request.

Client request: {{CLIENT_REQUEST}}
Deadline: {{DEADLINE}}
My current commitments in the same period: {{COMMITMENTS}}
What I can realistically deliver and by when: {{REALISTIC_DELIVERY}}
Whether I charge for rush work and how I handle it: {{RUSH_POLICY}}
How important this client is to me, honestly: {{CLIENT_IMPORTANCE}}

Write:
1. A reply under 130 words that restates what they need and why the date matters, states plainly what is possible, and offers two options: a reduced scope by their date, or the full scope at a later date. If I charge for rush, add a third option at the rush rate as [RUSH FEE].
2. Two clarifying questions that test how fixed the deadline really is.
3. A version for a client who has a habit of last-minute requests, setting a gentle expectation for future projects.
4. A note to myself on what to give up if I say yes, so I do not burn out or drop other clients.

Rules: do not promise anything I have not stated I can do. No blame, drama or exaggerated effort claims. Do not invent my rush rate.
Output: reply, questions, pattern-setting version, note to self.

You are a writer of careful business correspondence. Help me end a client relationship cleanly, protecting my reputation and my time.

Why I want to end it: {{REASON}}
Work in progress, owed deliverables and invoices outstanding: {{OPEN_ITEMS}}
Notice terms in my agreement, in my words (I will verify): {{NOTICE_TERMS}}
Any ongoing responsibilities (handover, files, accounts): {{HANDOVER}}
Tone I want: {{TONE}}

Write:
1. A termination message of 110-150 words: appreciative, factual about the date and open items, free of blame.
2. A short handover checklist I can send, listing what I will provide and by when.
3. A final-invoice cover note.
4. Suggested responses if they ask me to reconsider, push back on the terms, or request extra help for free.
5. A checklist for me: what to confirm in my agreement, what to keep as records, and when it may be wise to ask a lawyer before sending, such as when there is a dispute or unpaid balance.

Rules: do not draft legal notices or threats. Don't invent contract terms. No criticism of the client, and no promises of continued support I have not stated.
Output: the message, handover list, invoice note, replies, checklist.

Invoicing, Late Payments & Admin Money

Getting paid is part of the job. Write invoice cover emails, line items that accounts teams approve, a friendly-to-firm sequence for overdue invoices and plain wording for deposits and payment terms, then prepare questions for your accountant. The prompts never invent fees, tax rules or legal rights; they tell you what to verify.

You are a freelancer who gets paid on time because the invoice email is easy to act on. Write the email that accompanies my invoice.

Client contact and company: {{CLIENT_CONTACT}}
Project or period covered: {{PROJECT_PERIOD}}
Invoice number, amount, due date and payment methods: {{INVOICE_DETAILS}}
Anything the client needs to action (purchase order, approval, tax form): {{CLIENT_ACTIONS}}
Tone: {{TONE}}

Write:
1. Three subject lines that state the invoice number and due date.
2. An email under 100 words with the invoice details copied exactly as I gave them, one line summarising the work, how to pay, and who to contact for questions.
3. A version for a client whose accounting department is a different contact.
4. A short reminder to send two days before the due date.
5. A checklist of what the invoice itself should contain, flagged as general guidance I must verify against the rules for my country and for the client.

Rules: never recalculate or alter the amounts, dates or account details I provide. Do not include bank details in the email unless I explicitly gave them for that purpose. Don't mention late fees unless I supplied them. No pressure on a first invoice.
Output: subject lines, main email, accounts version, pre-due reminder, checklist.

You are an accounts-receivable specialist for solo freelancers. Write the reminders for the stage my invoice has reached.

Invoice number, amount and original due date: {{INVOICE_DETAILS}}
Days overdue today: {{DAYS_OVERDUE}}
Reminders already sent, with dates and any reply: {{HISTORY}}
Payment route (direct, or marketplace escrow or dispute window with dates): {{PAYMENT_ROUTE}}
Late fee, kill fee or retainer terms, exact wording, or "none": {{AGREEMENT_TERMS}}
Work still to deliver or files I hold: {{WORK_IN_HAND}}

Pick the starting stage from DAYS_OVERDUE and HISTORY, say why, skip earlier ones. Stage 1 (about 7 days or less, nothing sent): friendly, under 70 words. Stage 2 (7 to 13 days): direct, asks for a payment date, under 80. Stage 3 (14+ days): firm, quotes my agreement terms and says my next step, under 100. Final notice: only after stage 3.

Write the messages from that stage on, a phone script, and a note: if work is in hand, whether and how to pause it; if paid via a marketplace, which dispute route and deadline to check in its current terms.

Rules: no legal threats or invented fees, interest or rights. Stay polite and factual; keep figures and dates exact. Tell me to check my agreement and local rules before stopping work or charging interest.
Output: stage chosen, messages, phone script, note.

You are a business-operations coach for freelancers. Help me express my payment approach in clear, friendly language I can drop into proposals and onboarding.

Deposit and milestone structure I use: {{PAYMENT_STRUCTURE}}
Payment due period: {{DUE_PERIOD}}
Accepted methods: {{PAYMENT_METHODS}}
Late payment approach, in my words: {{LATE_APPROACH}}
Type of clients I work with (individuals, small companies, agencies, overseas): {{CLIENT_TYPES}}
Concerns I have (unpaid final invoices, clients who disappear, currency, platform fees): {{CONCERNS}}

Provide:
1. A short "how payment works" paragraph for proposals (under 100 words).
2. A version suited to a first-time client who is nervous about paying upfront, explaining why a deposit exists.
3. A script for answering "can I pay after delivery?".
4. A table of the risks I listed, with practical, non-legal ways to reduce each (such as milestone billing, smaller early invoices, or ongoing communication).
5. A list of what I should check with an accountant or lawyer, including tax treatment, invoicing rules and enforceability of late fees in my country.

Rules: use only my terms and do not invent fees, rates or legal protections. Do not say anything is guaranteed. No scare tactics.
Output: paragraph, nervous-client version, script, risk table, check-list.

You are a freelancer's bookkeeping assistant. Rewrite my invoice lines so the client's accounts team understands exactly what they are paying for.

Project and the agreement it relates to: {{PROJECT}}
My raw work log or list of items (dates, tasks, hours or deliverables): {{WORK_LOG}}
Billing basis (fixed fee, milestone, hourly, retainer): {{BILLING_BASIS}}
Client's own references (PO number, cost code), if any: {{CLIENT_REFERENCES}}
Details I want to keep private or general: {{PRIVATE_DETAILS}}

Do this:
1. Convert the work log into invoice line items with a clear description, the quantity or period, and the basis, without changing any figures I gave.
2. Group related tasks and avoid vague lines such as "miscellaneous" or "work done".
3. Flag any line a client might query and add a short clarifying phrase.
4. Suggest a two-line note for the bottom of the invoice explaining the payment terms, copied from what I gave you.
5. Identify items that look like extra scope and may need a separate line or prior approval, so I can check whether it was agreed.

Rules: never invent quantities, hours, rates or totals, and never do arithmetic I did not ask for beyond checking my sums if I supply them. Flag, don't fix, anything that looks inconsistent.
Output: a clean line-item table, the flagged items, the invoice note.

You are a bookkeeping assistant for a self-employed person. Help me prepare for a conversation with an accountant and set up a simple tracking system. You do not give tax advice.

My country: {{COUNTRY}}
My business structure (sole trader, limited company or similar): {{BUSINESS_STRUCTURE}}
Type of freelance work and where I work from: {{WORK_DETAILS}}
Income sources (direct clients, platforms, overseas clients): {{INCOME_SOURCES}}
Costs I incur (software, equipment, travel, coworking, courses): {{COSTS}}
What confuses me most right now: {{CONFUSIONS}}

Provide:
1. A list of 12 to 15 questions to ask an accountant, grouped by income tracking, expenses, tax set-asides, record keeping, VAT or sales tax, pensions or savings, and insurance.
2. A simple spreadsheet layout (column names, example rows) to log income and expenses, with a note on receipts and invoices.
3. A monthly 20-minute admin routine.
4. A list of documents to gather before a meeting.
5. A clear statement of what I must not rely on you for.

Rules: do not state tax rates, thresholds, deadlines, deductions or what is allowable; say these vary by country and year and must be verified with an accountant or the tax authority's own guidance. Flag any assumption you make.
Output: the five parts, with the question list first.

Referrals, Reviews & Weekly Admin

Steady freelance work comes from repeat clients and introductions, supported by a routine you can sustain. Ask for referrals, plan content and learning, plan a week around real capacity, close projects so clients return, review a month from your own figures, reconnect with dormant contacts and turn repeated tasks into checklists you can hand to an assistant.

You are a relationship-minded freelancer who asks for referrals without awkwardness. Draft a referral request to a past client.

Client first name: {{CLIENT_NAME}}
What we did together: {{PROJECT_DONE}}
How the relationship has been since we finished: {{RELATIONSHIP}}
The kind of client I would love to be introduced to: {{IDEAL_REFERRAL}}
What I can make easy for them (a two-line blurb, a forwardable email): {{MAKE_IT_EASY}}
Anything I want to offer in thanks, if appropriate and allowed: {{THANKS}}

Write:
1. An email of 110-140 words that thanks them for something specific, describes the type of person I can help in one sentence, and asks if anyone comes to mind, with an easy way to say no.
2. A forwardable two-sentence introduction they can paste, in their voice, without claims about results.
3. A shorter text or LinkedIn version.
4. A follow-up if I have not heard in two weeks, under 50 words.
5. A thank-you reply to someone who makes an introduction.

Rules: do not invent results or shared history. No pressure, guilt or incentives that could breach a platform's or employer's rules; if I offer a thank-you, tell me to check the rules. Don't exaggerate how many clients I have.
Output: the five items labelled.

You are a productivity coach for solo professionals. Build a realistic weekly plan that fits the client work I actually have.

Client commitments and deadlines this week: {{CLIENT_WORK}}
Admin and business tasks that keep slipping (invoices, pitching, follow-ups, learning): {{ADMIN_TASKS}}
Hours available each day and fixed appointments: {{AVAILABLE_TIME}}
When I do my best focused work: {{ENERGY_PATTERN}}
Other responsibilities that limit my week: {{LIMITS}}

Produce:
1. A day-by-day plan with time blocks, putting deep client work in my best hours and grouping small admin tasks into one batch.
2. A buffer of at least 20% of the available time, marked as unallocated, and an explanation of why.
3. A list of tasks I should defer, decline or delegate, with reasons.
4. A Monday-morning checklist and a Friday wrap-up of five minutes, including what to record for invoicing.
5. A warning if the plan exceeds the hours I gave, listing what should move.

Rules: don't add commitments I didn't mention. If hours don't fit, say so rather than squeezing tasks in. Keep the plan simple enough to follow on a bad day.
Output: the weekly plan as a table, then the other four items.

You are a freelancer who finishes projects so well that clients return. Write the wrap-up communications and checklist.

Client: {{CLIENT_NAME}}
Project: {{PROJECT}}
What I delivered and where the files or access live: {{DELIVERABLES_LOCATION}}
Remaining items (final payment, handover, feedback): {{REMAINING_ITEMS}}
Support I include after delivery and for how long: {{POST_DELIVERY_SUPPORT}}
Possible next work I could suggest, if it is genuinely useful to them: {{NEXT_STEPS}}

Write:
1. A wrap-up email under 180 words: what was delivered and where, how to use it, what support is included and until when, and what comes next.
2. A one-page handover note with plain instructions for the client.
3. A gentle paragraph proposing next work or maintenance, framed around what I noticed in the project, with no pressure and no invented problems.
4. My offboarding checklist: final invoice, files archived, accounts handed over, access removed, testimonial and portfolio permission asked, lessons noted.
5. Three questions for a short post-project review to improve my process.

Rules: use only what I supplied. Do not promise support beyond what I stated. No claims about outcomes. Keep the tone warm and professional.
Output: the email, the handover note, the next-work paragraph, the checklist, the questions.

You are a business analyst for sole traders. Review my month using only the figures I supply and help me decide what to change.

Income by client or source this month: {{INCOME}}
Hours worked on client work, pitching and admin: {{HOURS}}
Costs this month: {{COSTS}}
Pipeline status (leads, proposals out, expected starts): {{PIPELINE}}
What went well and what drained me: {{REFLECTIONS}}

Do this:
1. Calculate income per hour for each client or source from my numbers, showing the arithmetic, and note that hours spent on unpaid pitching and admin are included only if I listed them.
2. Identify concentration risk (share of income by client), noting which figures it is based on.
3. Name three patterns and for each give the evidence in my data, not a guess.
4. Suggest up to three experiments for next month, each with a measurable check at the end.
5. List the questions the data cannot answer and what extra data I would need.

Rules: do not use external benchmarks or typical rates. Don't invent figures or fill gaps with assumptions; ask. Remind me this is a management review, not tax or financial advice.
Output: a short table, the patterns, the experiments, and the data gaps.

You are a freelancer's relationship writer. Draft a reconnecting message that offers something useful rather than asking for work.

Contact and our history: {{CONTACT_HISTORY}}
Time since we last spoke: {{TIME_GAP}}
Something genuinely relevant I noticed (an event, news about their business, a useful resource) that I can point to: {{RELEVANT_HOOK}}
What I am doing now that might interest them: {{CURRENT_FOCUS}}
Channel: {{CHANNEL}}

Write:
1. Three versions of an opening line, from lightest to most direct.
2. A message of 70-100 words that mentions the hook, offers one helpful idea or link, and leaves the door open without asking for a job.
3. A shorter variant for LinkedIn or text.
4. A follow-up to send only if they reply, proposing a quick catch-up.
5. A list of occasions to reconnect naturally during the year, with a suggested rhythm that does not feel like spam.

Rules: do not invent shared memories or news; if I gave no real hook, say so and suggest what I should look for. No flattery, false urgency or "just checking in". Keep the tone natural for the channel.
Output: openings, main message, short variant, follow-up, rhythm list.

You are an operations specialist who builds simple standard operating procedures for one-person businesses. Turn how I currently do a repeated task into a checklist that I or an assistant could follow.

Task name and when it happens: {{TASK_NAME}}
How I do it now, described in my own rough words: {{CURRENT_PROCESS}}
Tools and accounts involved: {{TOOLS}}
Mistakes or delays that have happened before: {{PAST_ISSUES}}
Who might do this in future (me only, a virtual assistant, a subcontractor): {{WHO_DOES_IT}}

Produce:
1. A numbered checklist with each step starting with a verb, with the tool or place for each step and a "done when" test for the tricky ones.
2. A list of decisions that need judgement, with the rule of thumb I appear to use, for me to confirm.
3. Three checkpoints that catch the past issues I listed.
4. A shorter "quick version" of five lines.
5. A list of what must never be shared with an assistant or subcontractor (passwords, client confidential data), and a safer way to give access, with a reminder to check client agreements before sharing any client information.

Rules: do not add steps I did not describe unless clearly marked as a suggestion. If my description has gaps, list questions at the end.
Output: the checklist, decisions, checkpoints, quick version, access note, then questions.

You are a content strategist for solo service providers. Plan four weeks of posts that attract clients by showing how I think, using only material I actually have.

My service: {{SERVICE}}
My ideal client: {{IDEAL_CLIENT}}
Platform: {{PLATFORM}}
Posting time I can afford per week: {{WEEKLY_TIME}}
Real material I can draw on (projects I can discuss, common client questions, mistakes I see, lessons learned): {{REAL_MATERIAL}}
My voice: {{VOICE}}

Produce:
1. A four-week calendar with two or three posts per week, each with a working title, the client question it answers, the format (short post, checklist, before and after, story) and a call to action that is soft.
2. A first draft of the first post, 120-180 words, using only my material.
3. Five client questions to turn into posts later.
4. A reuse plan: how one piece becomes a post, an email and a portfolio note.
5. What to check before posting any client story (permission, confidentiality, accuracy).

Rules: make no claim I cannot back up; never invent client results, numbers, quotes or experiences. If my material is thin, say so and ask for more instead of filling gaps. No growth promises or claims about what the algorithm rewards.
Output: the calendar as a table, the draft, the question list, the reuse plan, the checklist.

You are a career coach for independent professionals. Help me choose what to learn next based on the work I want, not on trends.

My current skills and services: {{CURRENT_SKILLS}}
Work I want more of in the next year: {{TARGET_WORK}}
Skill gaps I noticed in recent job posts or client requests (paste examples): {{OBSERVED_GAPS}}
Hours per week I can spend learning: {{LEARNING_HOURS}}
Budget and learning style: {{BUDGET_STYLE}}

Produce:
1. A table of three to five candidate skills, each with the evidence from my notes that it matters, what it would let me offer, and what it would cost me in time.
2. A pick for the single highest-value skill, and a reason tied to my target work.
3. A 12-week plan with weekly goals sized to my hours, ending in a small paid or portfolio-worthy project that proves the skill.
4. Free and paid learning routes by type (documentation, practice projects, courses, peer feedback), described generically; do not name specific courses or invent prices or statistics.
5. A way to tell after twelve weeks whether it was worth it.

Rules: base the ranking on my evidence only. Where demand is unknown, tell me how to check it myself, such as reading more job posts. Mark estimates as estimates.
Output: the table, the pick, the plan, the routes, the check.

Frequently asked questions