The Dollar Client Kit course

Lesson 08 · Ch 7 · Delivery

Chapter 7: Delivery, handover and keeping clients

Read aloud
In this lesson (12 sections)
  1. Part 1: Presenting concepts remotely
  2. Part 2: Handling feedback and revisions
  3. Part 3: Brand guidelines
  4. Part 4: The handover
  5. Part 5: Testimonials
  6. Part 6: Turning projects into case studies
  7. Part 7: Referrals and repeat work
  8. Part 8: Agency relationships
  9. Part 9: A simple post-project review
  10. Part 10: When things go wrong at the end
  11. Checklist: delivery and retention
  12. End-of-chapter exercises

The end of a project is not the end of the relationship. It's the moment when the client decides whether to recommend you, hire you again or forget you. This chapter covers the last stretch, from concept presentation through handover, and then how to turn finished projects into testimonials, case studies, referrals and retainers.

Part 1: Presenting concepts remotely

When you can't sit in the same room, your presentation has to do the persuading on its own. A logo on a white background asks the client to imagine everything else. A well-built presentation shows them.

Step-by-step: build a concept presentation

  1. Restate the brief. Open with the client's goals and audience, in their own words from discovery (Template 6). This reminds everyone what the work is meant to achieve.
  2. Show the strategy. One or two slides on positioning, personality and key insights.
  3. Present each direction separately. For each:
    • A name and a one-line idea ("Market Stall: warm, handmade, generous")
    • The logo, large and in context
    • Colour and type
    • Applications: packaging, website header, social post, signage or pitch deck, whatever fits their world
    • The reasoning: why this direction serves the brief
  4. Recommend one. Clients appreciate a professional opinion. Explain why.
  5. Explain next steps: how to give feedback, by when, and how many revision rounds remain.

Delivery format

  • Recorded walkthrough (5–10 minutes) so the client can watch at a convenient time and share it with colleagues
  • PDF of the presentation for reference
  • Optional live call to discuss it, scheduled across time zones (Chapter 6)

How many directions?

Show a small number of strong directions, often two or three, rather than a pile of options. Too many choices make decisions harder and suggest you're unsure. [Assumption: the right number depends on your contract and the client.]

HYPOTHETICAL worked example: presenting with reasoning

Invented scenario.

Femi presents two directions to a Dublin-based coffee brand founded by a Nigerian-Irish couple. For Direction A he writes: "Your discovery answers said customers describe you as 'the friendly corner café that feels like a trip'. This direction uses a hand-drawn mark and warm terracotta from your Lagos roots, while keeping a clean layout that fits Dublin café culture." The client chooses A and asks for one colour tweak. Because the reasoning links back to their own words, the feedback stays focused on refinement instead of starting over.

Part 2: Handling feedback and revisions

  • Ask for consolidated feedback: one set from the decision-maker, per round.
  • Clarify vague feedback with specific questions (Chapter 6).
  • Count rounds openly: "This is round 1 of 2."
  • Quote extra rounds before doing them (Template 2, clause 5.3).
  • Confirm final approval in writing before preparing final files.

Part 3: Brand guidelines

Even a short guidelines document makes your work more professional, protects the identity once you've handed it over, and gives the client something tangible to share with printers, developers and future designers.

What to include (scale to the package)

  1. Brand overview: mission, personality, audience (from discovery)
  2. Logo: versions, clear space, minimum sizes, colour variations
  3. Logo misuse: stretching, recolouring, effects, busy backgrounds
  4. Colour: HEX, RGB, CMYK and, if relevant, Pantone values, with usage proportions
  5. Typography: fonts, weights, hierarchy, fallback fonts, licence notes
  6. Imagery: photo style, illustration style, iconography
  7. Applications: examples of the identity in use
  8. Contacts: who to ask for files or questions

Tip: build your own guidelines template once, then adapt it for each client. It saves time on every project.

Part 4: The handover

Use Template 9 (Client handover checklist). Key steps:

1. Confirm final payment

Release final files only after full payment (contract clause 8.1). Send the final invoice when the work is approved, and prepare the files while you wait.

2. Prepare an organised file package

A clear folder structure makes a strong last impression:

/[ClientName]_Brand_Final
  /01_Logo (SVG, PDF, EPS, PNG, JPG — colour, mono, reversed)
  /02_Colour (palette PDF with codes)
  /03_Typography (font list + licence links)
  /04_Guidelines (PDF)
  /05_Applications (social templates, stationery, etc.)
  /06_Source (only if included in the contract)
  README.txt (what's in each folder)

3. Name files clearly

For example clientname_logo_primary_colour.svg instead of final_final_v3.svg.

4. List licences

List every font and stock asset, its licence status, and whether the client needs to buy their own licence. Don't pass on licences you're not allowed to transfer. [VERIFY each licence's terms.]

5. Confirm the IP transfer in writing

Once payment has arrived, send a receipt (Template 8) and a short confirmation that ownership of the final deliverables has passed to the client under the contract.

6. Walk the client through it

A short recorded walkthrough of the files and guidelines prevents confused emails later.

7. Agree how long you'll keep files

For example: "I'll keep a backup of your files for [X] months."

Handover email template

Subject: [Brand name] — final brand files and guidelines

Hi [Name],

Thank you. Your final payment has arrived, and I'm happy to hand over your new brand. Files: [link], organised into folders (see README). Guidelines: [link to PDF] Walkthrough video: [link] (6 minutes) Licences: please see the font and image list. You'll need to buy [font] for your team's computers. Ownership: as per our agreement, ownership of the final deliverables now passes to [Company]. I'll keep a backup for [X] months. It's been a pleasure working with you. [Name]

AI shortcut: A text assistant can help you draft a clear handover email or guidelines copy from your notes. Never use AI to write or "improve" a client's testimonial (Chapter 8).

Part 5: Testimonials

Testimonials help future clients trust you, but only when they're real.

Rules

  • Only use real testimonials, with written permission.
  • Never edit the meaning. Fixing a typo is fine with permission; changing what they said is not.
  • Use the name and company the client approves, or a description ("Founder, UK food brand") if they prefer.
  • Keep the emails or messages that show permission.

Step-by-step: asking for a testimonial

  1. Ask soon after handover, while satisfaction is high.
  2. Make it easy by asking two or three specific questions:
    • What was the challenge before we worked together?
    • What was it like working with me remotely?
    • What's different now that you have the new brand?
  3. Offer the option of a short video or written answer.
  4. Send them your draft summary for approval, if you combine their answers.
  5. Ask how they'd like to be credited.

Script:

Hi [Name], I hope the new brand is going well! Would you be open to sharing a few sentences about working together? These three questions might help: [questions]. I'd only use it with your approval and the credit you choose. No pressure at all.

Part 6: Turning projects into case studies

Every finished project can become a portfolio piece (Chapter 2).

  1. Confirm portfolio permission and timing (contract clause 8.4).
  2. Collect process images as you work. It's much harder to recreate them later.
  3. Write the case study within a week of handover, while it's fresh.
  4. Publish it on your website, Behance and LinkedIn (Chapter 3).

Part 7: Referrals and repeat work

Ask for referrals

"If you know anyone who's planning a launch or rebrand, I'd really appreciate an introduction. Here's a one-line description you can forward: [Your one-liner + link]."

Offer the next phase

Many brand projects naturally lead to more work: a website, packaging for new products, a pitch deck, social templates or campaign design. Mention relevant next steps at handover without being pushy.

Retainers

A retainer is a monthly agreement for ongoing brand support. It brings predictable income and keeps you close to the client.

  • Define what's included: hours or deliverables per month, response times, and what happens to unused hours.
  • Paid in advance each month.
  • Review every 3–6 months.

HYPOTHETICAL worked example: from project to retainer

Invented scenario. No income is implied.

After handover, Femi notices the Dublin coffee brand will need regular social templates, seasonal menu designs and event posters. In his handover email he adds: "Many clients find it useful to have ongoing design support as the brand rolls out. If that's helpful, I can put together a small monthly retainer covering [scope]." The client says they'll think about it. Three weeks later, a check-in from Femi coincides with their seasonal menu planning, and they ask for a retainer proposal.

Stay in touch

  • Check in 4–8 weeks after handover: "How is the new brand landing?"
  • Share something useful occasionally: an idea, an article or an observation about their market.
  • Congratulate them publicly (with permission) when they launch.

Part 8: Agency relationships

If you work white-label for agencies:

  • Deliver on time, every time, in their file format and naming conventions.
  • Never contact their clients directly unless the agency explicitly allows it.
  • Respect confidentiality and no-credit agreements.
  • Ask at the end of each project: "What's coming up that I can help with?"

Part 9: A simple post-project review

After every project, spend 15 minutes answering:

  1. Was the project profitable compared with my floor rate (Chapter 4)? How many hours did it really take?
  2. Which phase took longer than expected, and why?
  3. What did the client value most?
  4. What would I change in my proposal, contract or process next time?
  5. How did the payment route perform: timing and fees received (Template 8)?

Keep the answers in your project folder. Over a year, these short reviews become the most useful pricing and process data you have.

Part 10: When things go wrong at the end

Most projects end smoothly when the earlier chapters' systems are in place. Occasionally they don't. Here's how to handle the common problems calmly.

The client is unhappy with the final direction

  1. Listen first. Ask what specifically isn't working, and why.
  2. Check the written record: what was approved, and when?
  3. If the issue is a small refinement within your remaining rounds, fix it.
  4. If it's a new direction after approval, treat it as additional work (contract clause 6) and quote it politely.
  5. If the relationship has broken down, refer to the cancellation clause (clause 11) and agree a fair close.

The client approves the work but doesn't pay the final invoice

  1. Follow the reminder sequence from Chapter 5.
  2. Don't release final files. Clause 8.1 means ownership hasn't passed.
  3. Stay professional in writing. Avoid emotional messages you might regret.
  4. If payment still doesn't come, consider your options with a lawyer. [VERIFY: legal options differ by country.]
  5. Record what happened and adjust your deposit and milestone structure for future clients.

The client asks for source files that weren't included

"Source files weren't part of the original scope, but I'm happy to provide them. The fee for source files is [amount] (as per clause 8.2), and I'll send them once that's settled."

HYPOTHETICAL example: a calm close

Invented scenario.

A client in Texas goes quiet after approving final concepts. After the three-step reminder sequence, Ngozi sends one final message: "I'll keep your files safe until [date]. Once the final invoice is settled, I'll send everything over immediately. Ownership passes on payment under clause 8.1." There's no anger and no threats. Two weeks later the client pays and apologises: their finance contact had changed. Because the files were never released, Ngozi was protected throughout.

Checklist: delivery and retention

  • Concept presentation includes the brief, strategy, applications and reasoning
  • Feedback rounds counted and confirmed in writing
  • Final approval in writing
  • Final payment received before files are released
  • Organised file package with README
  • Font and stock licences listed [VERIFY]
  • IP transfer confirmed in writing
  • Walkthrough recorded
  • Testimonial requested (used only with permission)
  • Case study planned
  • Referral and next-phase conversation held
  • Follow-up check-in scheduled

End-of-chapter exercises

Exercise 7.1: Presentation template. Build a reusable concept presentation template with sections for the brief, strategy, directions, applications and next steps.

Exercise 7.2: Guidelines template. Create a guidelines template in your own style that you can adapt quickly.

Exercise 7.3: Folder structure. Set up a master handover folder structure with a README template.

Exercise 7.4: Testimonial requests. Send the testimonial script to two past clients. Store their replies and permissions carefully.

Exercise 7.5: Next-phase menu. List five follow-on services you could offer after a brand identity project, with a short description of each.

Exercise 7.6: Check-in calendar. Add reminders to check in with your last five clients over the next two months.

Templates in this lesson

Client Handover Checklist (open to read; download .docx)

Template 9 · The Dollar Client Kit · Replace every [placeholder] before sending.

Project: [ ] · Client: [ ] · Handover date: [ ]

Before handover

  • Final balance received (receipt # [ ]). No files go out before this.
  • All approvals saved in writing
  • Files proofed: spelling, colour values, alignment
  • Logo suite: SVG, PDF, EPS, PNG (transparent), JPG, in colour, mono and reversed
  • Favicon / app icon sizes
  • Colour codes: HEX, RGB, CMYK, [Pantone]
  • Brand guidelines PDF
  • Collateral: [list]
  • Source files [if included in the contract]
  • Folder structure: /01_Logo /02_Colour /03_Type /04_Guidelines /05_Collateral

Licences and rights

  • Font list with licence links. Client to buy: [ ]
  • Stock assets list with licence status
  • IP transfer confirmation (per contract clause 8.1)

Walkthrough

  • Recorded walkthrough (Loom) or call at [time in client's time zone]
  • Usage dos and don'ts explained

After handover

  • Ask for a testimonial (only publish with written permission)
  • Ask for a referral
  • Confirm portfolio permission and timing
  • Offer a retainer / next phase: [ ]
  • Archive the project; keep files for [X] months
  • Record income for tax and bookkeeping [VERIFY local rules]

Practise what you just learned

Checkpoint

Complete the activities, then save your checkpoint.