> ## Documentation Index
> Fetch the complete documentation index at: https://docs.depost.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Running client work

> Onboarding a client, the weekly rhythm, reporting, and the mistakes that cost you a morning.

[Agencies and teams](/agencies/overview) covers how the pieces fit. This page is the
operating side: what you do on day one with a new client, what the week looks like, and what
to hand over at the end of the month.

## Onboarding a client

<Steps>
  <Step title="Create the brand">
    **Add personal brand** from the switcher. It's named after the person who publishes —
    a brand is an identity, not a company account. See [brands](/agencies/brands).
  </Step>

  <Step title="Let it run its own setup">
    Paste that person's LinkedIn profile and let the analysis run. This is the step that
    makes their content sound like them rather than like you, so don't skip it even when
    you already know the client well.
  </Step>

  <Step title="Check the strategy with the client, not for them">
    The drafted [strategy](/settings/strategy) is the best conversation starter you'll get
    — it's specific, it's drawn from their own posts, and it's wrong in interesting places.
    Correcting it together takes ten minutes and settles what you'd otherwise argue about
    in draft comments for a month.
  </Step>

  <Step title="Add the objections they actually hear">
    The one row nobody can read off posts. Ask the client what people say that stops them
    buying, and put it in **Objections you hear**. It's the difference between posts that
    state a position and posts that answer one.
  </Step>

  <Step title="Grant access deliberately">
    Add the people who work on this client, and only them. Role and brand access are
    separate — see [your team](/agencies/team).
  </Step>

  <Step title="Turn on review before the first post">
    Assign a reviewer so nothing reaches a client's audience unapproved. It's much easier to
    start with review than to introduce it after something goes out wrong. See
    [review and approval](/posts/review).
  </Step>
</Steps>

<Tip>
  Do the whole thing on one client before you onboard five. The second one takes a third of
  the time, and you'll want the first one's mistakes to be cheap.
</Tip>

## The weekly rhythm

<AccordionGroup>
  <Accordion icon="repeat" title="Start in the workspace view, not in a brand">
    One screen tells you which client has failed posts, which has nothing scheduled, and
    which has gone quiet for a week. Starting inside a brand tells you about one client and
    hides the rest. See [the workspace view](/agencies/workspace).
  </Accordion>

  <Accordion icon="shuffle" title="Switch brand before you create anything">
    Everything — chats, drafts, bookmarks, infographics — is scoped to the brand you're in.
    The switcher is at the top of the sidebar, and the browser extension holds its **own**
    selection, set separately.
  </Accordion>

  <Accordion icon="folder" title="Keep each client's chats together">
    Use campaigns so a client's threads stay findable in a month's time, and
    [labels](/settings/labels) to mark stage or owner. See
    [organize chats](/chat/organize).
  </Accordion>

  <Accordion icon="calendar" title="Plan per client, check across clients">
    Build the week inside the brand — [plan your content](/chat/plan) — then look at the
    workspace calendar to see whether four clients are all publishing on Tuesday morning.
  </Accordion>
</AccordionGroup>

## Reporting

Analytics read per brand or across every brand, and **Export CSV** takes whichever view is
on screen. So the client report and the agency roll-up come from the same place rather than
from stitching exports together.

What makes a Depost report different from a screenshot of LinkedIn's own numbers is the
comparison: each figure is measured against that client's **own typical post**, and against
creators in their field measured the same way. "This post did 2.4× your average" is a
sentence a client can act on. "This post got 419 engagements" isn't.

<Tip>
  Send the comparison, not the raw count. A client whose numbers went down in a quiet month
  still has posts that beat their own average, and that's the thing worth repeating next
  month.
</Tip>

## What goes wrong

<AccordionGroup>
  <Accordion icon="triangle-alert" title="Work created against the wrong brand">
    The most common one, and the most tedious to undo. Check the switcher before a batch of
    work, and check the extension separately — a bookmark saved to the wrong client has to
    be moved by hand.
  </Accordion>

  <Accordion icon="triangle-alert" title="The strategy was never corrected">
    A drafted strategy that nobody confirmed produces drafts that are all slightly wrong in
    the same direction. It never looks like an error; it just reads as "not quite them" on
    every single post.
  </Accordion>

  <Accordion icon="triangle-alert" title="One login shared across the team">
    It costs you per-brand access, review, and any idea of who wrote what. Invites are
    free — the plan limits team members, not logins, and a shared login can't be given
    access to one client only.
  </Accordion>

  <Accordion icon="triangle-alert" title="Client material in the workspace library">
    Workspace material is readable by everyone in the workspace, and reachable by every
    brand's drafts. A client's pricing or case studies belong in that brand's library.
  </Accordion>

  <Accordion icon="triangle-alert" title="A lapsed LinkedIn connection nobody noticed">
    It shows as posts landing in **Failed** and analytics going stale. The workspace
    dashboard flags it per brand; from inside one client you'd only find out when a post
    didn't go out. See [troubleshooting](/help/troubleshooting).
  </Accordion>
</AccordionGroup>

## When a client leaves

Don't delete the brand on the last day. Deleting takes the posts, the analytics and the
library with it, and there is no undo — while an unused brand costs nothing to keep.

Remove the people who no longer need access, disconnect the LinkedIn account if the client
asks, and keep the history. It's the only record of what worked, and it's what makes a case
study possible six months later.

## Related

<CardGroup cols={2}>
  <Card title="Agencies and teams" icon="briefcase" href="/agencies/overview">
    What's separate per brand, and what's shared.
  </Card>

  <Card title="The workspace view" icon="layout-dashboard" href="/agencies/workspace">
    Every client on one screen.
  </Card>

  <Card title="Review and approval" icon="check" href="/posts/review">
    Sign-off before anything goes out.
  </Card>

  <Card title="Analytics" icon="chart-line" href="/analytics/overview">
    Per-brand and cross-brand reporting.
  </Card>
</CardGroup>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.