← All case studies Technology

Skool.com

Online community platform

18,000 hours a year of repeat work, now running on its own.

18,000+hours saved a year
$750K+value of time saved a year
~350hours back every week

In one minute

Who they are

The platform where creators run online communities and courses.

What was slow

A large part of the team's week went on business and operations tasks done the same way, every week.

What we did

We mapped their recurring work, then automated the repeat processes from start to finish.

What changed

That time now goes to work that actually needs people.

The problem, in plain words

Skool's team spent a large part of every week on recurring business and operations work. Each task was done the same way every time, handed from person to person, and checked by hand.

Before and after

Before: the long way

  1. The same task comes round again
  2. Someone does it by hand
  3. Hands it to the next person
  4. It gets checked

Repeated every single week.

After: with MCode

  1. The task starts on its own
  2. Every step runs automatically
  3. The result lands where it's needed

Nobody has to remember to do it.

What we set up, piece by piece

Each part, what it does now, and the manual work it replaced.

01

Recurring processes

Runs the business processes the team used to repeat every week.

ReplacedDoing the same steps by hand, week after week.

02

Operations tasks

Handles routine operations work from start to finish.

ReplacedSomeone remembering and doing each task.

03

Hand-offs

Passes work from one step to the next automatically.

ReplacedHanding work over by message or email.

The numbers, explained

Here is what 18,000 hours a year looks like, broken down.

18,000+hours saved a year
~1,500hours saved a month
~350hours saved a week
~69hours saved every working day
~9full-time people's worth of work
$750K+value of that time, a year

We add up the time the team used to spend on these tasks each year. Based on a 40-hour week, 52 weeks and 260 working days a year.

How we worked

  1. 01Mapped the work

    Sat with the team and listed every step of the jobs they repeat.

  2. 02Picked what to fix first

    Chose the steps that cost the most time and were safe to hand over.

  3. 03Set it up in their tools

    Built it inside the tools the team already uses. Nothing new to learn.

  4. 04Handed it over

    Showed the team how it works, then let it run every day.

Questions you might have

Did the team have to learn new software?

Very little. Wherever we can, we build inside the tools a team already uses, so there is almost nothing new to learn.

How do you count the hours saved?

We add up the time the team used to spend on these tasks each year, before they ran on their own. The value is what that time is worth to the business.

Could this work for my company?

If your team repeats the same steps every week, very likely. The free audit shows you exactly where, and what it is worth.

Want this for your team?

Get a free audit. We'll show you what can run on its own in your business, and what it's worth.

Get your free audit →