Most small businesses don’t have a tool problem. They have a “where does this live?” problem. Tasks are in Slack, client notes are in email, the SOP is in someone’s Google Drive, and the priorities are in the founder’s head.
An operations hub fixes that. It’s one place where everyone can see what’s being worked on, who owns it, when it’s due, and how it should be done. This guide shows you how I set one up for small teams of 2 to 15 people, first in ClickUp, then the Notion version.
ClickUp or Notion: which should you use?
Both work. Pick based on how your team works, not on which one is trendier.
Choose ClickUp if:
- Most of your work is tasks with owners, deadlines and stages, such as client delivery, content production or projects.
- You want built-in automations, time tracking, workload views and recurring tasks without extra tools.
- Your team is comfortable with a busier interface in exchange for more control.
Choose Notion if:
- Much of your work is documentation: SOPs, wikis, client briefs and knowledge bases.
- Your task management is fairly light.
- You want something calmer and more flexible, and you’re happy to build more of the structure yourself.
Many teams use both: Notion as the wiki, ClickUp for delivery. That’s fine, as long as everyone knows which tool is the source of truth for what.
Before you open either tool: decide three things
Skipping this step is why most setups fail within three months.
- What are your main types of work? For example: client delivery, sales, marketing and internal admin. These become your top-level areas.
- What stages does each type of work move through? For example, client delivery might be Brief → In progress → Internal review → Client review → Done.
- What do you need to know about every task at a glance? Usually: owner, due date, client and priority. Resist adding more for now.
Write these down on one page. That page is your blueprint.
Building it in ClickUp
ClickUp organises work in layers: Workspace → Spaces → Folders → Lists → Tasks. Here’s how I map a small business onto that.
Step 1: Create one Space per area of work
For a typical service business:
- Delivery for client work
- Growth for sales and marketing
- Operations for admin, finance, hiring and tools
- HQ for priorities, meetings and SOPs
Keep it to four or five Spaces. If you have twelve, nobody will know where to look.
Step 2: Use Folders and Lists sensibly
Inside Delivery, create a Folder per service line, or per client if you have a few large retainers. Inside each, use Lists for active projects. Inside Growth, you might have Lists for Leads, Content and Partnerships.
A good rule: if a List would only ever hold three tasks, it shouldn’t be a List.
Step 3: Set statuses that match your real stages
ClickUp lets you set custom statuses per Space or List. Use the stages you wrote in your blueprint. Keep it to five or six. Add a status called Waiting on client or Blocked, so stuck work is visible instead of quietly sitting in “In progress”.
Step 4: Add only the custom fields you need
Start with three or four:
- Client (dropdown or relationship)
- Priority (ClickUp has a built-in priority flag; use that)
- Effort (small, medium or large) if you plan capacity
- Link to deliverable (URL field)
You can always add more later. Too many fields is the fastest way to get a team to stop updating tasks.
Step 5: Build task templates for repeat work
If you onboard clients the same way every time, build a task template with the full checklist and subtasks, then apply it to each new client. The same goes for monthly reports, content pieces and new-hire onboarding. This is where ClickUp starts to save serious time.
Step 6: Set up the views people actually use
Every List can show the same tasks in different views. The useful ones:
- Board view for delivery: drag tasks across stages.
- List view grouped by assignee for weekly check-ins.
- Calendar view for content and deadlines.
- Workload view (on paid plans) to see who’s overloaded.
Pin the default view for each List so new team members land somewhere sensible.
Step 7: Add a few automations
ClickUp’s built-in automations work on a simple “when this happens, do that” pattern. My starter set:
- When status changes to Internal review, assign the reviewer and set a due date two days out.
- When status changes to Done, notify the client lead in a comment.
- When a task is overdue, change priority to Urgent.
- When a new task is created in Leads, apply the lead template.
Start with three or four. Every automation is something that can break silently later, so add them only when the manual version is clearly a pain.
Step 8: Build the HQ Space
This is the part most teams skip, and it’s what turns a task tool into an operating system.
- Weekly Priorities: a recurring task every Monday with the top five priorities for the week, each linked to the real tasks.
- Meetings: a Doc per recurring meeting with a running agenda and decisions log.
- SOPs: ClickUp Docs for each repeatable process, linked from the task templates that use them.
- Metrics: a Dashboard with the five to eight numbers that tell you whether the week went well, such as open tasks per person, overdue tasks, new leads and invoices outstanding.
Building it in Notion
Notion has no fixed hierarchy; you build structure with pages and databases. The trick is to use a small number of connected databases instead of dozens of separate pages.
The four databases you need
- Projects: one row per client project or internal initiative, with properties for client, owner, status and dates.
- Tasks: one row per task, with a relation to Projects, plus owner, due date, status and priority.
- SOPs: one page per process, tagged by area, with a relation to the Projects or Tasks that use it.
- Meetings: one page per meeting, using a template with agenda, decisions and actions.
Relations are what make Notion powerful: open a project and you’ll see every task and SOP linked to it.
Views to create
- My tasks: Tasks filtered to “Assignee is me” and “Status is not Done”, sorted by due date. Make this everyone’s home page.
- This week: Tasks due in the next seven days, grouped by person.
- Project board: Projects as a Board grouped by status.
- Overdue: Tasks past their due date and not done. Review it every Monday.
Templates and automations
Create database templates for recurring work. A new-client project template can create the project page and pre-fill a checklist. Notion also supports recurring templates and simple database automations, such as notifying someone when a status changes. For anything more complex, connect it to Zapier or Make.
The HQ page
Make one page called HQ and pin it in the sidebar. Put on it: this week’s priorities, a linked view of overdue tasks, links to the SOP library and the meeting notes, and a short “how we work” section explaining where things live.
Getting your team to actually use it
The tool is the easy part. Adoption is where hubs live or die.
- Move everything at once. If tasks can still live in Slack or email, they will.
- Write a one-page “how we work” guide: where tasks go, what each status means, and how to ask for help.
- Run your weekly meeting from the hub. If the meeting uses it, people will keep it updated.
- Review it weekly for the first month. Fix confusing statuses, delete unused fields, and ask the team what’s annoying.
- Have one owner. Someone has to tidy the hub, update templates and archive old work. Without an owner, every hub becomes a junk drawer within six months.
Where AI fits in
Both tools now have AI built in: ClickUp Brain and Notion AI. Used well, they’re helpful for:
- Summarising long task threads or meeting notes into decisions and actions.
- Drafting SOPs from a rough description, which you then edit.
- Answering “where is X?” questions across your workspace.
- Writing weekly status updates from completed tasks.
Treat their output as a first draft. Read any AI-written SOP line by line before your team follows it.
Common mistakes to avoid
- Copying someone else’s template wholesale. Their business isn’t yours.
- Building for the team you’ll have in two years instead of the one you have now.
- Too many statuses, fields and automations on day one.
- No weekly review, so the hub slowly drifts out of date.
If you’d like an operations hub built around how your business actually runs, and someone to keep it tidy afterwards, that’s part of what I do in the Build and Run stages.