How a freelance designer handles 5 clients instead of 2

The bottleneck isn't how fast you work. It's the hours lost hunting for the current version and assembling decks. Here's what comes off your plate, and what stays yours.

Sound familiar?

You do UI/UX, branding and decks for small businesses. Solo, two clients right now, aiming for five.

  • Your tools: Figma, Notion, Google Drive, and a lot of Slack threads.
  • Moodboard versions have spread across folders, and finding the live one is its own task.
  • Client feedback lives in messages — some in voice notes, some in comments on the file.
  • Resizing for formats and assembling decks eats hours, with zero craft in it.

The moment it usually breaks

Two clients ask for urgent changes on the same day — and half of it goes to digging through Notion and Drive for the right versions. It lands: at five clients this is physically impossible.
Try it on your own projectsSetup is a conversation, 15–30 minutes

What you actually need

Not another task tracker. You need the admin around the work to stop occupying the space the work needs.

  • Versions and files surface immediately, without excavating three storage systems.
  • Feedback from threads becomes an edit list instead of dissolving into voice notes.
  • Resizes and deck assembly happen without you.
  • You can see where every project stands without opening five tabs.

How it's put together

BossForce sets up a workspace for this: agents with clear ownership, a goal with a measurable metric, and playbooks — processes that fire on an event.

This example is built on a model situation, not a real client's projects. The structure and format are what the product creates during setup.

The goal

Run 5 clients instead of 2in progress

Free up the hours going into version hunting, feedback triage and mechanical file prep.

Concurrent clients
2 → 5
Hours on admin per week
10 → 3
Finding the live version
half a day → minutes

Processes that run themselves

Feedback roundactive
Fires when

A client sends comments on a file

Collect the notes into one list, flag contradictions and anything outside the agreed scope. Hand you the decision before any work starts.

coffee shop rebrand: 4 of 5 steps
Client handoff packactive
Fires when

Artwork is marked approved

Produce the format set, assemble a draft deck, and put it in one folder with names a human can read.

this week: 3 of 4 steps

What happens, step by step

Collect edits for the coffee shop rebranddone
Feedback Agent · Playbook: Feedback round
  • Pull notes from threads and file comments
  • Consolidate into one list per screen
  • Flag two mutually exclusive requests

12 edits, 2 contradictions raised with you

Produce the format setin progress
Production Agent · Playbook: Client handoff pack
  • Take the approved artwork
  • Build the main formats
  • Your check on the crops

Formats built, waiting on your eye

An edit falls outside the agreed scopewith you
Feedback Agent · Playbook: Feedback round
  • Compare the request against what was agreed
  • Do not start the work
  • Your call: absorb it or reopen the budget

Waiting on your decision

How this got set up

I lost half a day finding the current moodboard between Notion and Drive. At five clients I'll drown in this.
Understood. I'll build a project map: where things live, what's approved, what's in flight. One question about the boundary — what do I do when a client's edits contradict each other?
Don't choose for me. And if an edit is outside the quote, that comes to me first too.
Recorded: contradictions and anything outside the agreed scope come to you as a question before work starts. I make no design decisions.

Where you're still required

The agent handles what surrounds the work, not the work. Anything involving taste or an agreement stays with you.

  • Design decisions are yours. The agent prepares options and formats; it doesn't pick.
  • Contradictory edits aren't resolved on its own — they come back as a question.
  • Anything outside the agreed scope stops until the budget conversation happens.
  • Files are never deleted or overwritten: the agent arranges, it doesn't tidy up to its own taste.

What changes

  • The live version surfaces in seconds instead of half a day of digging.
  • Thread feedback becomes a readable edit list with the contradictions marked.
  • Resizes and draft decks get produced without you.
  • The hours you get back go into new clients rather than into finding files.
Start for freeNo card required

FAQ

Does it need access to my Figma?

Not necessarily. The baseline works from exports and files. A direct integration is something you connect deliberately; it isn't on by default.

Will the agent delete things in my folders?

No. It arranges and points at what's current, but never deletes or overwrites. Tidying to its own judgement is the fastest way to lose the version you needed.

Will it make design decisions for me?

No. Options, formats and drafts, yes; the choice, no. The choice is what the client is actually buying from you.

Does this work if I'm an editor rather than a designer?

The mechanics are the same: many clients, many versions, feedback buried in threads. The file formats change, the shape of the work doesn't.

Related walkthroughs

All walkthroughs