Onboarding

Client onboarding

Before a system takes on your work,
it needs what any new hire needs:

Clear access.A written brief.
OnboardingThe first weekDay 0 to Day 7

Five steps, about a week.Then we build.

Onboarding is how we learn your work before a system touches it. Nothing is connected until you have read and signed the access list.

  1. Day 0

    You fill in the card

    Pick the systems you want, the tools you use, and roughly when. About four minutes.

  2. Day 1

    A person replies

    Not an autoresponder. Two or three questions, and times for a call.

  3. Day 2–3

    A thirty-minute call

    We walk through how the work is done today, and where the hours actually go.

  4. Day 4

    Scope and access list

    A written scope, a timeline, and every account, key and permission each system needs.

  5. Day 5–7

    Sign-off and kickoff

    You grant the scoped access, we confirm it works, and the build begins.

Day 0 — Start here

Tell us whichhours you want back.

The card builds the exact access list from the systems you pick, so you know what we will ask for before we ask. When you finish, it opens in your mail app, addressed to us.

Reply
Within a day, from a person
Cost to start
Nothing. The call is free
Shared so far
Nothing, until you sign the list
AccessLeast, alwaysRevocable

What we ask for,and what we never do.

We ask for

  • Scoped API keys, wherever a platform offers them
  • Read access first, write access only where a system has to act
  • Test or sandbox accounts for building
  • Your brand assets, voice samples and source lists
  • One person who can say yes

We never ask for

  • Your personal passwords
  • Card or banking details
  • More access than a system needs
  • Live accounts before the shadow run
  • Access we cannot list in writing