Session 3: Delivering Professional Work

Most client problems are created before the work starts, by expectations that were never stated. The client assumed three revisions; you assumed one. They assumed the website included writing; you assumed it did not. They assumed delivery Friday; you meant Friday next week. None of this is anyone's fault — it is simply what happens when nobody writes it down.

So state it before starting, in a short written note even for informal work. What is included: the exact deliverables, in what format, at what size or length. What is not included: photography, printing, copywriting, hosting, anything the client might reasonably assume. How many revisions, and what counts as one. When each stage is delivered, with dates. How you communicate and how fast you reply.

That note is not bureaucracy; it is the cheapest insurance available. It takes ten minutes and it prevents the argument that costs you a day of unpaid work and a client. And it makes you look professional, because almost nobody does it — which means the client immediately understands that working with you is different from working with the last person.

Estimate generously and then add more. Work takes longer than expected for reasons you cannot predict — a client who takes four days to reply, a font that will not licence, a machine that fails — and a deadline you cannot meet costs you far more than a longer one costs the client. The rule that works: quote the deadline you are confident in, not the one that wins the job.

Then build in checkpoints rather than delivering everything at the end. Send an early draft or a first version at roughly a third of the way through. It catches a misunderstanding while it is cheap to fix, it reassures a client who has not heard from you, and it protects you: if the direction is wrong, you find out in two days rather than in two weeks.

And when you are going to miss a deadline — which will happen — tell them before it passes, not after. 'I will not make Friday; I can deliver Tuesday' said on Thursday is a small inconvenience handled well. The same words said on Saturday are a broken promise. Clients forgive a delay far more readily than they forgive discovering a delay, and the difference is entirely about when you told them.

Revisions are changes to work you delivered; scope creep is new work presented as a small change. The line is not always obvious, which is exactly why it must be defined in advance. 'Change the blue to green' is a revision. 'Add a section about our new product line' is new work, however small it seems.

Set a number — two rounds is standard — and define what a round is: one consolidated list of changes, not a stream of messages. That single definition solves most of the problem, because clients who send fifteen separate messages over three weeks are not being difficult; nobody told them how revisions work. Tell them, and most will happily collect their notes.

Then handle the excess without conflict. 'That is outside the two rounds we agreed. I can do it for ₦8,000, or I can fold it into next month's work.' Stated plainly and early, this is normal business. Left unaddressed until the tenth unpaid change, it becomes resentment, and resentment is what ends freelance relationships — not the money.

Delivery is not sending files. It is making the work usable and the client confident. Send the right formats — print-ready PDF as well as the editable file if agreed, images at the sizes they will actually be used, documents in a format they can open. Name the files sensibly: 'Menu-Final-A4-Print.pdf' rather than 'final_v3_REAL_final.pdf', because the client will look for it in three months.

Then explain what you delivered and how to use it. A short note: what is in each file, what size each is for, how to send the print file to a printer, and what to do if something looks wrong. Clients who do not understand the deliverable cannot use it, and unused work produces no referral — however good it is.

Finally, ask for the two things that build the business: a testimonial, in their words, about the problem you solved; and one referral — a name of someone else with a similar problem. Ask while satisfaction is highest, which is at delivery, not three weeks later. Most freelancers never ask, which is why most freelancers restart their pipeline from zero every month.

A complaint is not a disaster; it is information delivered badly. The response that works has three parts and must happen in order. Acknowledge — say you understand and you take it seriously, without arguing about whether they are right. Establish the facts — what was agreed, what was delivered, what is missing or wrong. Propose a fix — a specific action with a date.

The instinct to defend yourself is strong and almost always counter-productive. Even when the client is factually wrong, arguing first makes the conversation about winning rather than about solving, and a client who feels unheard escalates. Acknowledge first, establish facts second, and very often the disagreement resolves itself once they feel taken seriously.

Where you are genuinely at fault, say so plainly and fix it. 'I delivered late and that caused you a problem. I have reduced the fee by ₦10,000 and the final files are attached.' An owned mistake with a concrete remedy usually strengthens the relationship, because the client learns what happens when you get it wrong — and the answer being 'they fix it and make it right' is worth more than never having erred. What destroys a reputation is not a mistake; it is a mistake handled dishonestly.