What to Know Before Hiring in Your Creative Agency
By Danielle Stephanie, founder of Get Your Ops Together | Last updated November 1, 2026
Disclaimer: This article is for general information only and isn't legal advice. Talk to a qualified attorney before changing your contracts or agreements.
In this guide
- Why can a new hire make you busier instead of freeing up your time?
- How do you know which work to hand off first?
- Should you write SOPs first or hire first?
- Who will your new hire report to, and how will decisions get made?
- What should onboarding look like for a new team member?
- How will you define good work and review it?
- Should your hire be a freelancer, a contractor or an employee?
- How often should you meet with your new hire?
- What does this look like in a real agency?
- Frequently asked questions
- Ready to hire without becoming the bottleneck?
Your new designer starts on Monday, and by lunch they've asked you where the brand files live, which fonts the client approved, whether "final" really means final, and how this client likes to get updates. You answered every one of those questions yourself, in between two client calls, and the week you hired them to give you back hasn't even started yet.
If you want your next hire to actually free up your time, have six things in place before they start: a clear decision about which work you're handing off and why, the core processes for that work documented, a named person they report to, an agreed list of decisions they can make on their own, an onboarding path covering access, tools, SOPs and communication rules, and a written standard for finished work and how it gets reviewed. You'll also want a high-level call on whether the role suits a freelancer, a contractor or an employee. The setup is the same whether you're hiring a designer, a video editor or an account manager.
Why can a new hire make you busier instead of freeing up your time?
In the agencies we work with, the first few weeks with a new team member decide whether the hire gives you hours back or eats more of them. Your new designer or editor walks in without any of the knowledge you carry around in your head: how you name files, how each client likes to receive updates, what finished looks like for a carousel compared to a brand deck, where the brand assets live and who on the client side actually signs off. If none of that is documented, the only place they can get it is from you.
So the person you hired to take work off your plate hands you a new job, which is answering their questions and checking every piece of work before it goes out. When that happens, look at the setup they walked into before you look at the person. Most of what makes a hire work comes down to a handful of decisions you make ahead of time and a few processes you get into writing before their first day.
How do you know which work to hand off first?
Run a time-tracking audit before you write the role
I always start here, because your sense of where your week goes is usually off. The tasks that drain you most and the tasks that take the most hours are often different, and the work quietly eating your week, like revision rounds, Slack replies, scheduling posts and chasing approvals, rarely makes it onto the list you'd write from memory.
For two weeks, track your time on everything you do, and if you already have a team, have them track theirs too. Then sort it by task type: client calls, design or editing, revision rounds, scheduling, proposals, answering Slack, invoicing and internal review. You'll see which recurring work takes the biggest share of your hours and which of those tasks someone else could do well with clear instructions. That recurring, documentable work is what your new hire should own.
| Task type | Hours over two weeks | Recurring? | Could someone else do it with an SOP? |
|---|---|---|---|
| Client calls | |||
| Design or editing | |||
| Revision rounds | |||
| Scheduling | |||
| Proposals | |||
| Answering Slack | |||
| Invoicing | |||
| Internal review |
Write down why you're hiring
"I need help" is too broad to build a role around. "I need someone to own first-round design for our retainer clients so I can focus on creative direction and sales" gives you a clear role, a clear handoff and a way to tell a few months from now whether the hire worked. If the audit shows the bigger problem is how the agency runs rather than how much creative work there is, you may need a different kind of help altogether, so read up on the difference between an operations manager, a project manager and a virtual assistant before you post the role.
Should you write SOPs first or hire first?
Document the processes they'll touch in their first month
Document first. When you hire into an agency where nothing is written down, every task turns into a conversation with you. When the core of the work is documented, your new hire has one place to go to answer their own questions from day one, and the questions they do bring you show you exactly where an SOP needs more detail.
You don't need to document the whole agency before you hire. Start with the processes the new person will touch in their first month. For a designer, that might be how you set up and name files, how you prepare work for internal review and how you package final deliverables for the client. For an account manager, it might be how client updates go out, how approvals get chased and how a new client request gets logged so it doesn't slip into someone's DMs.
The quickest way I know to get these down is to open Kommodo or Loom, record yourself doing the task while you talk through each step and why you do it that way, pull the transcript and turn it into written steps. Then review your SOPs every quarter so they keep up with how the work actually runs.
Put your values and policies in place underneath them
Your SOPs sit on top of two other layers. Your core values are what the business stands on, and they drive everything, from who you hire to how you build your processes and how you treat clients. Your policies are built on those values and guide how you operate, for example how your team communicates, how you use AI, and how you handle late payments or refunds. Your SOPs document the day-to-day processes that stand on those policies, and they should never contradict them. When your new hire hits a situation no SOP covers, the values and policies are what tell them what to do without messaging you first.
Start from our free SOP kits
If you'd rather not start from a blank page, our free SOP kits in the Template Shop give you policies, an SOP template, an industry SOP vault and an AI SOP builder. There's a kit for different types of creative agency, for example social media, content and video or brand design.
Who will your new hire report to, and how will decisions get made?
Name the person they report to
Documentation tells your new hire how to do the work, but they also need to know who to go to. Without that, every question and every decision lands on you by default. In a small agency, the person they report to might be you, an account manager or a project manager. Decide it before they start, write it into their role, and make sure everyone on the team and every client contact knows it too.
Agree which decisions they can make on their own
Then agree ahead of time who decides what. For a new designer, that might look like this: they make small revisions within the brief on their own and answer their own how-to questions from the SOPs, the account manager approves work before it goes to the client and logs any new client request, and anything that changes the timeline, the deliverables or the capacity a project needs comes to you. The right split depends on the role and the experience the person brings, so there's no single list to copy.
The easiest way to build yours is to go back through the last few weeks of Slack and write down every decision someone brought to you. For each one, ask whether someone else could make it with clear guidelines. Those become your new hire's decision rights, and the rest stay with you. Our guide on how to manage a small agency team goes deeper on roles and delegation as your team grows.
| Decision | New designer | Account manager | You |
|---|---|---|---|
| Small revisions within the brief | ✓ | ||
| How-to questions an SOP already answers | ✓ | ||
| Approving work before it goes to the client | ✓ | ||
| Logging a new client request | ✓ | ||
| Anything that changes the timeline, the deliverables or the capacity a project needs | ✓ |
What should onboarding look like for a new team member?
With the role, the SOPs and the decision rights in place, you can build one onboarding path you reuse for every hire instead of rebuilding the same explanations each time. For a creative agency team member, it covers four things: access, tools, SOPs and communication rules.
Access
Set up every account they need before day one: your project management tool, Slack, the shared drive, your design or editing software and your password manager, so no login ever gets pasted into a message. Give them access only to what their role needs, and keep a record of what you shared so you can remove it in one go if they leave.
Tools
Walk them through how work is tracked in your project management tool: where their tasks live, what each status means, how to move work into internal review and where client feedback comes in. A recorded walkthrough of a real project gives them something to go back to, which a live tour on day one rarely does. In ClickUp, we give each team member their own desk in a Team Space and keep every SOP in a Knowledge Base, so a new hire knows exactly where their work and their answers live.
- CEO Desk
- Brain Dump
- CEO Day Checklist
- My Tasks
- Team Assignments Overview
- Plans and Reports
- Meeting Documentation
- Admin
- Delivery Workflow (list)
- Client List (list)
- Team Member Desks: [New Hire]'s Desk
- Team Meeting Notes
- Meet the Team
- SOP Index
- How to Recruit a New Team Member
- Team Member Self-Onboarding Checklist
- Team Member Offboarding Checklist
- Submitting OOO Dates (OOO Policy)
- Issue Escalation Protocol
- Time Tracking
- How We Use ClickUp as a Team
- How We Use Slack
- Task Management
- Screen Recording SOP
- AI Management SOP
- Creating a Password Vault (LastPass)
- How to Build a Monthly Content Plan
- Content Creation and Management
- Scheduling Social Posts
- Templates
- Trainings
- Resources
SOPs
Give them time in their first week to read and practise the SOPs for their role, ideally against a recorded example of a real project, before they touch live client work. Ask them to note anything that's unclear as they go, because those notes become your first round of SOP updates.
Communication rules
Write down your Slack norms: which channels are for what, how quickly people are expected to respond, what counts as urgent and where questions should go, so they don't all end up in your DMs.
How you pace all of this depends on the role and how quickly you need them on client projects. A small first task with a clear review, followed by a check-in once they've settled in, helps them build confidence before they take on more.
How will you define good work and review it?
Write the standard for finished work
A new hire can't meet a standard nobody has described. If "good" only lives in your head, every review turns into personal taste, and your new person learns what you want by trial and error, one round of your edits at a time. Before they start, write down what finished looks like for each deliverable they'll handle. For a video editor, that covers pacing, captions, aspect ratios, export settings and file naming. For a graphic designer, it covers brand guidelines, export settings, how many concepts to present and how files get packaged for handoff. Turn each standard into a short checklist they run through before anything goes to review.
Decide how review happens
Then decide who reviews the work, at which stage, where feedback gets left and how quickly it comes back. Comments on the task in your project management tool are far easier to follow than notes scattered across Slack, email and voice notes. Over time, hand internal review to another team member so you only check what you choose to. Our guide on setting up a client delivery system shows how internal review fits with client approvals and revision rounds.
Should your hire be a freelancer, a contractor or an employee?
At some point you'll decide what kind of working arrangement the role suits. At a high level, a freelancer or contractor usually works on specific projects or set hours and often has other clients, while an employee works for your agency on an ongoing basis with more day-to-day direction from you. Plenty of small creative agencies start with contractors for design and editing, then bring on employees as the work becomes steadier.
How someone should be classified, what goes into their agreement and what it all means for taxes where you operate are questions for an accountant or an employment lawyer. Whichever arrangement you land on, everything operational in this post still applies: the role, the SOPs, the decision rights, the onboarding and the review standard.
How often should you meet with your new hire?
It's tempting to plan a daily check-in with a new hire so nothing slips. In my view, needing daily meetings usually points to one of two things: the systems aren't clear enough for people to work on their own, or someone is being micromanaged, and neither is something you want to build your agency around.
A lighter rhythm works when your systems carry the information in between. Task statuses live in the project management tool, questions go to the right Slack channel, and the SOPs answer most of the how-to questions. Your new hire will need more check-ins in their first few weeks, and that's normal. Plan to taper those as they settle in, then move them onto the same team meeting rhythm as everyone else.
What does this look like in a real agency?
We worked with Shannelle and Omari of Koined Digital, a content, social media and branding agency, to get Koined's operations ready for a growing team. We ran a two-week time-tracking audit to see where the hours were actually going, set up ClickUp with a desk for each team member, wrote Slack rules, built a Frame.io review flow and documented detailed SOPs. New hires were then fitted into Koined's systems, so they had something to follow from their first day instead of learning everything from the founders one question at a time. With the systems carrying that load, Shannelle and Omari were able to step back into their CEO roles, with more room for their marriage too.
You can read the full Koined Digital case study and our other client stories, or see how hiring fits with everything else your agency runs on in our guide to the systems a creative agency needs.
Frequently asked questions
Do you need a written job description before you hire?
Yes, even for a contractor. Write down what the person will own, what they won't own, who they report to, which decisions they can make on their own and how their work will be reviewed. If you can't fill that in yet, the role isn't clear enough to hire for, and your time-tracking audit is the place to go back to.
Should a new hire talk to clients directly from the start?
Decide that before they start, because it changes their onboarding. If they'll be client-facing, introduce them to each client by email with what they'll handle and how to reach them. If they won't be, make sure every client knows who their contact is, so requests don't land with the new person and then get forwarded to you.
How do you keep work consistent when two people work on the same client?
Give them one source for everything: the client's preferences guide and brand assets in that client's folder in your project management tool, one SOP and finished-work checklist per deliverable, and one internal review stage that everything passes through before the client sees it. When client feedback changes how the work should be done, update the preferences guide so both people work from the same version.
How often should you update your SOPs once a new hire starts?
Have your new hire flag anything missing or out of date as they work through each SOP in their first month, because they'll spot gaps you stopped seeing a long time ago. After that, review your SOPs every quarter so they keep up with how the work actually runs.
What should you do when a team member leaves?
Run your team member offboarding checklist: remove their access to every account, reassign their open tasks, collect any files that only live in their accounts, and update any SOPs that depended on what they knew. If you kept a record of what you shared during onboarding, removing access takes minutes instead of an afternoon of guessing.
Ready to hire without becoming the bottleneck?
Start documenting on your own with our free SOP kits. Grab the free SOP starter kit for your type of agency in the Template Shop, for example the social media agency SOP starter kit or the content and video agency SOP starter kit, and get the policies and SOPs your new hire will work from in place before their first day.
If you're not sure which area to build first, take the free Baggage Check. It audits where your agency still depends on you and tells you which area to build first, so you know exactly what needs to be in place before your next hire starts.
If you'd like support, RESORT Mode is our group program for creatives scaling to $30k+ months without the burnout, with the systems you need and real-time coaching as you grow. Ops Concierge is our done-for-you system build, set up in the tools your agency already uses and around how it already works. And Residents' Lounge gives you an embedded operations partner on retainer. Not sure which one fits? See which offer is right for you.
