Evidence of Ability and Trust
Before paying, a client needs to judge whether you can complete the work they have in mind. Proof of capability answers that question. It's anything tied to the specific work at hand that a buyer can understand and check before committing, a sample, a record of past deliveries, a concrete review from someone who hired you before.
Why Your First Delivery Has a Second Life
An experiment published in 2014 on an online labor market hired 952 workers at random, then gave them public reviews that varied in how detailed they were. Two things came out of it. Getting the job improved the participants' chances afterward. And more detailed reviews did the same.
One job leaves two things behind: the deliverable, and information about the person who made it. Whatever the next client can read from that information is what your first delivery is worth beyond its own fee. That only works when reviews are usable, and usable means stating what was done and how well it was done. "Great service!" is easy to hand out and hard to reuse. A note saying you handled the color grading yourself and turned the second revision around the same day is something the next buyer can actually act on.
Make Your Samples Look Like the Job You Want
A work sample is a demonstration built around the target task. A good one surfaces the requirements the future job will really throw at you, the conditions, the constraints, the details, so the client can judge your ability from both the result and the process.
Take clothing product photography. A single polished image shows less of your delivery capability than a complete set: colorways, fabric texture, close-ups of seams, and repeated shots of the same garment across different setups, which shows consistency. Then attach the task sheet. Where will the images be used? What camera, lights, and props went into it? Which steps did you own? How long did it take? What changed after you received feedback? From that, a buyer can judge whether your routine would work on their own garments.
Be honest about where samples come from. Self-directed practice should say so. Team projects should mark which part is yours. Real client work should record what you delivered and what the outcome was. If AI or any other tool was involved, describe how you selected, checked, and revised the output. Buyers want to know what you were responsible for.
Three Kinds of Proof, Three Different Questions
| Material | What it lets the client judge | What to prepare |
|---|---|---|
| Samples close to the need | What result can you actually produce? | The task requirements, the complete output, the process behind it |
| Records of real deliveries | How do you perform under agreed conditions? | Your responsibilities, delivery dates, revisions, acceptance |
| Specific reviews from clients or peers | What have other people actually observed? | Who the reviewer is, the setting, which parts went well |
Certificates and awards can add relevant background. When assembling anything, put the work closest to the client's actual task first, so they spend less time searching and more time deciding.
From "I Like Your Work" to "Let's Work"
Start with people who genuinely need this kind of output. Who counts as a real need for your work is covered in why clients need you, and how you get noticed at all is a separate problem in the scarcity of attention and being discovered.
The pitch itself runs in an order. Open with the problem the client is solving right now. Then the part of it you can take. Then your closest similar results. Then the small collaboration itself: what you'll deliver, at what price, by when. Whatever still feels unverified on their side can be tested with one clear, small task instead of a leap of faith.
Once they hand you clear requirements, negotiate against the actual scope. When the delivery lands, don't let it end. Turn the result into a case you can show next time, and ask the reviewer to describe what they actually saw you do. Checking that delivered content matches what was really paid for is covered in willingness to pay and validating demand.
For a concrete walkthrough of selling without past clients, see how to make people believe you can deliver without case studies. On practicing the skill and improving it, read building capability and getting useful feedback. The reading order across all these steps is in from learning a skill to your first payment. For using role-relevant results in salary discussions, see When they ask your expected salary, how do you name a number and keep going?.