A first client needs a reason to trust the work you propose. Without reviews, the strongest evidence available to you may be a small, clearly labelled practice sample and a precise explanation of what you will deliver. This guide focuses on the path from that sample to a written scope.
Describe an output a buyer can recognise
Choose a service small enough to verify. For example: “I will check the supplied product CSV against agreed rules and return a cleaned file plus an issue log.” Define a row limit only after measuring your capacity. Do not claim to build dashboards or recover missing facts if your evidence only covers basic cleanup.
Link the 20-order exercise as a reference, then create your own adaptation with changes you can explain. Identify it as practice. A borrowed sample with a different name is not evidence that you can do the task.
Find a brief that matches the evidence
Use public job listings, enquiries invited by a business, or introductions from people you know. Check the actual request rather than sending a generic offer to every address you find. An order-cleaning sample fits a messy CSV brief; it does not establish competence in tax reporting or financial modelling.
For each opportunity, record the deliverable, deadline, known inputs, missing information and relevant sample. Skip work whose central requirement you cannot meet. This saves both application cost and the time needed to explain a mismatch later.
Write an enquiry with one useful question
Hello, your brief asks for a cleaned order list with unresolved records flagged. My sample is a fictional cleanup exercise showing the original file, answer and issue log. Before estimating, could you confirm whether repeated order IDs represent duplicate exports or separate order lines? I would use that rule to define the cleaned output.
This is an example to adapt where enquiries are invited. Use the marketplace's permitted channel when applicable. Do not send repeated messages after someone declines or assume a publicly visible address invites unlimited marketing.
Turn a positive reply into an agreement
| Item | What needs to be written down |
|---|---|
| Input | File, allowed values, data meaning and who answers questions |
| Output | File format, columns, issue log and short handoff note |
| Acceptance | The checks the output must pass |
| Timing | Start condition and realistic delivery date |
| Revision | What corrections are included and what changes require a new scope |
| Payment | Amount, currency and the permitted contract/payment process |
A conversation is not automatically a funded agreement. Confirm the relevant platform process before starting paid work. For a direct enquiry, independently verify the counterparty and use written terms appropriate to the project.
Respond to common first-client situations
If the buyer asks for a full live project as an unpaid test, propose a short fictional sample or a clearly scoped paid trial. If the dataset expands after the estimate, pause and revise the scope. If the buyer wants an outcome beyond the evidence—such as “guaranteed error-free accounting”—explain what your checking process covers and decline the unsupported promise.
Download the application tracker. Record interest, questions, an agreed project and collected payment as separate events. A reply is not a sale, and an unpaid invoice is not income. Review actual objections or missing evidence before deciding what to change next.
Practice work and illustrative amounts are labelled in the article. See how we prepare and correct guides and how the resource checks work. Report a specific error or broken step.