5 AI Prompts for Freelancer Proposals and Onboarding

Resumen

Pixel shares five practical AI prompt templates to help solo freelancers turn discovery calls into clear records and improve proposals and client onboarding. The prompts address client needs, pricing questions, scope ambiguity, and red flags, helping freelancers reduce admin work and prevent misunderstandings.

DEV Community

5 AI Prompts Every Solo Freelancer Needs for Client Proposals and Onboarding

Most freelancers don't lose clients because the work is bad. They lose them in the two weeks around the work: the proposal that arrives three days late, the onboarding email that misses the one detail that mattered, the scope that quietly doubles because nobody wrote down what "revisions" meant. When you're a one-person business, that admin layer is your second job. It's also the part where AI actually earns its keep, because these are repetitive, high-stakes, text-heavy tasks with a known shape. Below are five prompts I use as the template layer of a solo practice. They're written to be pasted into any capable model (ChatGPT, Claude, Gemini). Replace the bracketed parts with your own context, and keep the output in a file you own rather than in the chat window. 1. The discovery call compressor You finish a call with a good feeling and no notes. Two days later you're reconstructing what they said from memory, and the proposal reflects your optimism rather than their words. You are a business analyst helping a solo consultant turn a sales call
into a shared record of what was agreed.

Here are my raw notes from the call:
[PASTE NOTES OR TRANSCRIPT]

Produce:
1. A two-paragraph summary of the client's situation, in plain language.
2. "What they said they need" — 3-5 bullet points, using their vocabulary,
not mine.
3. "What I think is actually blocking them" — 2-3 bullets, clearly marked
as my interpretation, with the evidence from the notes.
4. Open questions that must be answered before I can quote a price.
5. Red flags: scope ambiguity, budget signals, decision-maker uncertainty.

Do not invent details. If a section has nothing to support it, write
"not enough information" instead of filling the gap.
That last instruction matters more than the rest. A model that invents a budget figure because the section looks empty is worse than no summary at all. 2. The proposal skeleton (with the price logic made explicit) A proposal isn't a price list. It's a document that lets a non-expert decide whether you understand their problem. Draft a project proposal for the client described below.

Client context: [DISCOVERY SUMMARY]
My service: [WHAT YOU DO, IN ONE SENTENCE]
My rate logic: [HOURLY / FIXED / RETAINER + WHY]
Comparable projects: [1-2 PAST PROJECTS AND WHAT THEY COST]

Structure:
1. Their situation in 3 sentences (their words, not mine).
2. What success looks like, stated as outcomes a client could check.
3. Scope: included, explicitly excluded, and what counts as a revision.
4. Two options — a core scope and a larger scope. Never more than two.
5. Timeline with client dependencies named ("waiting on brand assets"
is a line item, not an excuse).
6. Price, payment schedule, and what happens if scope changes.
7. A single, concrete next step.

Tone: direct, no adjectives about my own excellence. Do not use the words
"passionate", "seamless", "cutting-edge", or "holistic".
The two-option structure is the useful part. Three options push the decision back onto the client. One option invites a yes/no on your price. Two options turn the conversation into "which one", which is a different and much easier question. 3. The onboarding packet generator Onboarding is where trust is either confirmed or quietly lost. The freelancer who sends a single, complete email the day the contract is signed looks like an organisation. The one who sends four emails over a week asking for the same asset twice does not. Build a client onboarding packet for a project starting on [DATE].

From the signed scope: [PASTE SCOPE]
Client's main contact: [NAME, ROLE]
How we'll work: [TOOLS, MEETING CADENCE, TIME ZONE]

Produce:
1. A welcome email (150 words max) that confirms the start date, names the
one thing I need from them first, and sets the next checkpoint.
2. A checklist of everything I need from the client before kickoff,
grouped by when it blocks me.
3. A short "how we work" page: response times, revision process, how
changes get price...
5 AI Prompts for Freelancer Proposals and Onboarding
Powered by Readybot.io

Lo último de Pixel

Stop Paying for AI Renders in Test Orders

Pixel’s announcement explains how internal test orders were accidentally triggering paid AI video renders costing just over $1 each. It details a server-side dry-run guard …

Sandblasting Grit Guide: 120 vs 220 vs 320

Pixel’s announcement explains how 120, 220, and 320 grit affect aluminium’s matte finish and reveal die-cast porosity. It also covers how pressure, blast distance, and …

NVIDIA Cosmos 3 Edge: Physical AI on Jetson

Pixel shares the first article in CAVEDU's Cosmos series, introducing NVIDIA Cosmos 3 Edge, an approximately 4-billion-parameter world model for Jetson devices. It explores multimodal …

Laravel Semantic Search with OpenAI and Pinecone

Pixel shares a practical guide to building semantic search in Laravel using OpenAI embeddings and Pinecone. It covers 1536-dimensional vectors, cosine similarity, index setup, environment …