Choose by the output you need to make

ChatGPT Prompts for Freelancers

Independent consultants and service providers managing proposals, scope, clients, and support.

Role starter

Start with the task that matches your work

Choose a task, paste the real material, then copy one role-aware prompt.

Paste current workAudience and constraintsWho checks it

Ready checks3 of 3 ready

Current work is concreteReady

Paste notes, constraints, examples, or the half-finished version you already have.

Audience and constraints are clearReady

Name who will use the answer, where it appears, and what limits matter.

Who checks it is namedReady

Keep one person or review lens responsible before the answer is reused.

Prompt to run

Open full workflow

Help me start the right Freelancers workflow.
Task to use: Write Proposals: prepare proposal section outline with scope and assumptions.
Paste current work: Need proposal with goals, scope, deliverables, timeline, client inputs, assumptions, out-of-scope items, and next step. proposal section outline with scope and assumptions would be weak without the source details, so the evidence has to stay attached. A reviewable answer should keep the original constraint in the open. Freelancers should use the note as the base for a proposal outline. Before freelancers run this, separate facts, preferences, and limits so the finished answer does not hide assumptions..
Audience and constraints: Independent consultants and service providers managing proposals, scope, clients, and support..
Who checks it: A reviewer close to the work should test the answer's claims before the output moves to a client, prospect, or project stakeholder..
Before writing, ask for anything missing that would change the write proposals: prepare proposal section outline with scope and assumptions output.
Return: The final pass should leave a proposal outline ready for a client, prospect, or project stakeholder, with the uncertain parts marked instead of smoothed over.
Stop if: Do not use the answer if it hides unsupported claims about verified account context, buyer language, and deal stage or treats uncertainty as fact.

After the first answer

Save what came back, what needs fixing, and the next prompt change before moving to another task.

Answer returnedNeeds fixingNext try

0No role notes yet
Run the prompt once, check the answer, then save the problem and next try here.

Nothing saved yet

Where ChatGPT helps this role

Turn rough notes into a reviewable asset for a client, prospect, or project stakeholder.
Convert a recurring freelancers workflow into a reusable prompt sequence.
Ask ChatGPT for clarifying questions before committing to tone, format, or evidence.
Create a quick version for routine work and a deeper version for high-stakes work.
Review an existing answer against privacy, accuracy, and role-specific constraints.
Rewrite output for a different audience without changing the underlying facts.
Build a checklist that makes the human review faster and less subjective.

Main Risks

Prompts should clarify scope and expectations instead of promising results the freelancer cannot control.
A broad prompt can hide missing source material, so freelancers should name the exact evidence before asking for output.
Over-polished wording can make weak assumptions look finished; every page links the prompt to a review step.
Copying the same prompt across tasks weakens results because freelancers need different inputs for planning, review, outreach, and explanation work.

Recommended Workflow

Pick the task page that matches the work to finish, not just the closest job title.
Prepare the source notes, audience, constraints, and forbidden assumptions before copying a prompt.
Run the prompt once for structure, then run a review prompt against facts, tone, and missing context.
Save the final prompt with the human review checklist so the workflow can be reused without becoming automatic.

Choose the first task by situation

Start with Write proposals when the user has source notes but does not yet know the right output structure, then move to Prepare discovery questions or Write scopes of work only after the audience and review owner are clear.

Choose by situation

Choose Write proposals when the main problem is shaping raw context into something a client, prospect, or project stakeholder can inspect.
Choose Prepare discovery questions when the user already has a first version and needs the next artifact in the same freelancers loop.
Choose Write scopes of work when the risk is quality control, review consistency, or a clearer handoff to another person.
Open the role guide when the user cannot name the task yet and needs to decide whether to create, revise, review, or sanitize context first.

Avoid starting with

Do not start from a broad role prompt when the user already knows the concrete task.
Do not start from a writing prompt when the missing piece is source material or named human check.
Do not reuse a freelancers prompt across unrelated tasks without changing inputs, constraints, and review checks.

Freelancers pages are organized by the choice a person is trying to make, not by a generic prompt collection. The role page should help the user pick the first useful task, then the task page should carry the details: source material, variable fill, example, stronger prompt, and human review boundary.

Pick the workflow by the work in front of you

Write proposals

Use when the next useful output is a proposal outline and the answer needs a proposal outline with named sections, action bullets, and a final reviewer pass.

Write proposals needs client problem, scope, deliverables, timeline, support, assumptions, and pricing context; the check focuses on proposal outline quality, client scope and deliverable boundary, and scope and value-risk check, not a generic writing pass.

Prepare discovery questions

Use when the next useful output is discovery questions and the answer needs discovery questions with named sections, action bullets, and a final reviewer pass.

Prepare discovery questions needs buyer role, suspected problem, deal stage, product fit, and learning goal; the check focuses on discovery questions quality, client goals and scope risk, and client-approval boundary, not a generic writing pass.

Write scopes of work

Use when the next useful output is a scope of work and the answer needs a scope of work split into reader-ready copy, open questions, and reviewer notes.

Write scopes of work needs client goal, deliverables, exclusions, timeline, acceptance criteria, and change rules; the check focuses on scope of work quality, deliverable boundary and exclusions, and scope and value-risk check, not a generic writing pass.

Plan client onboarding

Use when the next useful output is a client onboarding plan and the answer needs a sequenced plan with stages, owners, timing, and choice checkpoints.

Plan client onboarding needs client goals, access needs, kickoff agenda, owners, and communication cadence; the check focuses on client onboarding plan quality, kickoff agenda and access checklist, and client-approval boundary, not a generic writing pass.

Send project updates

Use when the next useful output is a project update and the answer needs a project update with copy-ready parts, needs-checking parts, and reuse fields.

Send project updates needs completed work, blockers, choices needed, next steps, and deadline risk; the check focuses on project update quality, completed work and blocker, and client-approval boundary, not a generic writing pass.

Write case studies

Use when the next useful output is a case study outline and the answer needs a case study outline arranged as a working version, check questions, and next steps.

Write case studies needs customer context, problem, approach, evidence, outcome, and permission limits; the check focuses on case study outline quality, before state and intervention, and learning-integrity check, not a generic writing pass.

Request testimonials

Use when the next useful output is a testimonial request and the answer needs a testimonial request with copy-ready parts, needs-checking parts, and reuse fields.

Request testimonials needs client relationship, result achieved, timing, ask, and approval path; the check focuses on testimonial request quality, relationship context and result prompt, and client-approval boundary, not a generic writing pass.

Explain pricing

Use when the next useful output is a pricing explanation and the answer needs a sequenced plan with stages, owners, timing, and choice checkpoints.

Explain pricing needs service scope, value support, cost drivers, alternatives, and boundaries; the check focuses on pricing explanation quality, cost drivers and value logic, and scope and value-risk check, not a generic writing pass.

Open a prompt workbench

Review-first run

Write Proposals: prepare proposal section outline with scope and assumptions

Freelancers can move from client problem, scope, deliverables, timeline, support, assumptions, and pricing context to a proposal outline without treating the first answer as finished. The workflow adds a messy-note example, answer checks, and a follow-up prompt for proposal outline quality, client scope and deliverable boundary.

Turn client problem, scope, deliverables, timeline, support, assumptions, and pricing context into a proposal outline for a client, prospect, or project stakeholder.

Bring first: Need proposal with goals, scope, deliverables, timeline, client inputs, assumptions, out-of-scope items, and next step. proposal section outline with scope and assumptions would be weak without the source details, so the evidence has to stay attached. A reviewable answer should keep the original constraint in the open. Freelancers should use the note as the base for a proposal outline. Before freelancers run this, separate facts, preferences, and limits so the finished answer does not hide assumptions.
Reject if: Do not use the answer if it hides unsupported claims about verified account context, buyer language, and deal stage or treats uncertainty as fact.

Prepare discovery questions Write scopes of work Plan client onboarding

Ready-to-run path

Prepare Discovery Questions: prepare question ladder by buyer signal

Freelancers can move from buyer role, suspected problem, deal stage, product fit, and learning to discovery questions without treating the first answer as finished. The workflow adds a messy-note example, answer checks, and a follow-up prompt for discovery questions quality, client goals and scope risk.

Turn buyer role, suspected problem, deal stage, product fit, and learning goal into discovery questions for a client, prospect, or project stakeholder.

Bring first: Need questions about audience, offer, current page, support, competitors, timeline, budget, approvals, and red flags. question ladder by buyer signal would be weak without the source details, so the evidence has to stay attached. A reviewable answer should keep the original constraint in the open. Freelancers should use the note as the base for discovery questions. Before freelancers run this, separate facts, preferences, and limits so the finished answer does not hide assumptions.
Reject if: Do not use the answer if it hides unsupported claims about true experience, measurable support, and target role fit or treats uncertainty as fact.

Write proposals Write scopes of work Plan client onboarding

Ready-to-run path

Write Scopes of Work: turn notes into scope of work

Use this scope of work workflow when the raw material is client goal, deliverables, exclusions, timeline, acceptance criteria, and change rules. It turns that material into a scope of work split into reader-ready copy, open questions and keeps the pasted notes, concrete examples, hard limits, and reviewer in front of the person checking the answer.

Turn client goal, deliverables, exclusions, timeline, acceptance criteria, and change rules into a scope of work for a client, prospect, or project stakeholder.

Bring first: Need SOW sections, deliverables, client inputs, timeline, revision policy, exclusions, acceptance criteria, and change request language. scope table with exclusions and acceptance terms needs the source note, output shape, and review owner in the same pass. The prompt run should carry the rough note forward. a scope of work should use the note as its source. Before freelancers run this, separate facts, preferences, and limits so the finished answer does not hide assumptions.
Reject if: Hold the answer if it blurs what is known, what is assumed, and what still needs evidence.

Write proposals Prepare discovery questions Plan client onboarding

Review-first run

Plan Client Onboarding: make onboarding checklist with owner and access fields reviewable

Start with this material: client goals, access needs, kickoff agenda, owners, and communication cadence. Use the client onboarding plan workflow to create a client onboarding plan, keep onboarding checklist with owner and access fields visible, add reject rules, and show a client, prospect, or project stakeholder what to check next.

Turn client goals, access needs, kickoff agenda, owners, and communication cadence into a client onboarding plan for a client, prospect, or project stakeholder.

Bring first: Need onboarding checklist, account access, brand assets, audience info, approvals, timeline, and first-week agenda. Phrase shopping fails for client onboarding plan work because the note should become onboarding checklist with owner and access fields. The user's note should stay readable after the answer is organized. This client onboarding plan work run should turn that note into a client onboarding plan. For client onboarding plan work, paste the source as bullets, constraints, and audience notes so the model has enough shape for a sequenced plan with stages, owners, timing, and choice checkpoints.
Reject if: Reject the answer if it invents facts, numbers, policy claims, citations, credentials, or examples that were not in the notes.

Write proposals Prepare discovery questions Write scopes of work

Ready-to-run path

Send Project Updates: prepare status update with blocker and choice rows

The project update workflow turns rough notes into a project update around completed work, blocker, choice needed, timeline risk, and owner. It includes a sample run, rerun instruction, and reusable fields for the next pass.

Turn completed work, blockers, choices needed, next steps, and deadline risk into a project update for a client, prospect, or project stakeholder.

Bring first: Need update with completed work, current blocker, choice needed, next milestone, timeline impact, and friendly tone. Phrase shopping fails for project update work because the note should become status update with blocker and choice rows. A safer answer should separate source notes from guesses. This project update work run should turn that note into a project update. For project update work, paste the source as bullets, constraints, and audience notes so the model has enough shape for a project update with copy-ready parts, needs-checking parts, and reuse fields.
Reject if: Reject the answer if it invents facts, numbers, policy claims, citations, credentials, or examples that were not in the notes.

Write proposals Prepare discovery questions Write scopes of work

Ready-to-run path

Write Case Studies: check before state and intervention

Bring customer context, problem, approach, evidence, outcome, and permission limits into the case study outline workflow and keep before state, intervention, evidence, outcome, and permission boundary visible from the first run. freelancers can check case study outline quality, before state and intervention before sharing the result.

Turn customer context, problem, approach, evidence, outcome, and permission limits into a case study outline for a client, prospect, or project stakeholder.

Bring first: Need case study outline with problem, approach, deliverables, client quote, visual support, limits, and CTA. No fake metrics. Freelancers need more than broad ChatGPT advice here; the answer has to work against the actual note and reviewer. The model output should keep the rough request attached to each choice. a client, prospect, or project stakeholder should still see the note while a case study outline is being built. Write Case Studies works better when the context is in named fields, because each variable can be checked before copying.
Reject if: Stop before sharing if it cannot show support, numbers, or authority that the user did not provide.

Write proposals Prepare discovery questions Write scopes of work

Review-first run

Request Testimonials: keep request note with approval and quote boundary sourced

Use the testimonial request flow to keep relationship context, result prompt, approval path, and easy reply from disappearing in polished wording. The result is a testimonial request, plus checks for the actual notes, usable examples, boundary checks, and reviewer.

Turn client relationship, result achieved, timing, ask, and approval path into a testimonial request for a client, prospect, or project stakeholder.

Bring first: Need email ask, 4 guiding questions, short LinkedIn version, permission note, and gentle follow-up after one week. Phrase shopping fails for testimonial request work because the note should become request note with approval and quote boundary. The workbench should turn this note into checkable fields. This testimonial request work run should turn that note into a testimonial request. For testimonial request work, paste the source as bullets, constraints, and audience notes so the model has enough shape for a testimonial request with copy-ready parts, needs-checking parts, and reuse fields.
Reject if: Reject the answer if it invents facts, numbers, policy claims, citations, credentials, or examples that were not in the notes.

Write proposals Prepare discovery questions Write scopes of work

Ready-to-run path

Explain Pricing: check cost drivers and value logic

The pricing prompt set keeps a pricing explanation, cost drivers, value logic, tradeoffs, and scope protection, and the final check tied to the same source note. It is built to reduce polished but unsupported answers.

Turn service scope, value support, cost drivers, alternatives, and boundaries into a pricing explanation for a client, prospect, or project stakeholder.

Bring first: Need explanation for price, what is included, why it matters, payment schedule, alternatives, and boundary for extra work. pricing explanation with cost-driver rows needs the source note, output shape, and review owner in the same pass. The answer should protect the real constraint before polish. a pricing explanation should use the note as its source. Before freelancers run this, separate facts, preferences, and limits so the finished answer does not hide assumptions.
Reject if: Hold the answer if it blurs what is known, what is assumed, and what still needs evidence.

Write proposals Prepare discovery questions Write scopes of work

Where to go next

Write proposalsWrite proposals fits when the next useful output is a proposal outline and the answer needs a proposal outline with named sections, action bullets, and a final reviewer pass. Keep it separate because write proposals needs client problem, scope, deliverables, timeline, support, assumptions, and pricing context; the check focuses on proposal outline quality, client scope and deliverable boundary, and scope and value-risk check, not a generic writing pass.Prepare discovery questionsPrepare discovery questions fits when the next useful output is discovery questions and the answer needs discovery questions with named sections, action bullets, and a final reviewer pass. Keep it separate because prepare discovery questions needs buyer role, suspected problem, deal stage, product fit, and learning goal; the check focuses on discovery questions quality, client goals and scope risk, and client-approval boundary, not a generic writing pass.Write scopes of workWrite scopes of work fits when the next useful output is a scope of work and the answer needs a scope of work split into reader-ready copy, open questions, and reviewer notes. Keep it separate because write scopes of work needs client goal, deliverables, exclusions, timeline, acceptance criteria, and change rules; the check focuses on scope of work quality, deliverable boundary and exclusions, and scope and value-risk check, not a generic writing pass.Plan client onboardingPlan client onboarding fits when the next useful output is a client onboarding plan and the answer needs a sequenced plan with stages, owners, timing, and choice checkpoints. Keep it separate because plan client onboarding needs client goals, access needs, kickoff agenda, owners, and communication cadence; the check focuses on client onboarding plan quality, kickoff agenda and access checklist, and client-approval boundary, not a generic writing pass.Send project updatesSend project updates fits when the next useful output is a project update and the answer needs a project update with copy-ready parts, needs-checking parts, and reuse fields. Keep it separate because send project updates needs completed work, blockers, choices needed, next steps, and deadline risk; the check focuses on project update quality, completed work and blocker, and client-approval boundary, not a generic writing pass.Write case studiesWrite case studies fits when the next useful output is a case study outline and the answer needs a case study outline arranged as a working version, check questions, and next steps. Keep it separate because write case studies needs customer context, problem, approach, evidence, outcome, and permission limits; the check focuses on case study outline quality, before state and intervention, and learning-integrity check, not a generic writing pass.How to Use ChatGPT for FreelancersUse this when the user needs a role-level workflow before opening a single task page.