Scotty Systems grew out of years spent making videos, trying side hustles and recording an AI business attempt that did not go to plan.

Follow the journey →

Today, Scotty Systems is becoming an AI toolbox for TikTok and YouTube creators. It starts with a problem I had myself: more footage than I could organise, and no practical way to find the moment I needed.

The first tool built from that problem is Scotty Archive.

Enter the Creator Tools constellation →

View Scotty Systems plans →

Available today

The useful thing to know is the contradiction, not the CV. He had been trying to make videos since he was six or seven. Several channels failed before one finally did not.

He genuinely loves making things — that part came first and has never really stopped. He is also ambitious in a way that is easy to mistake for restlessness: he wants the money and the independence, and he has chased both directly, sometimes clumsily.

The recurring failure is the same one every time. He builds too much. A thing that should have taken a week becomes a system, then a platform, then something that needs its own admin panel. Some of that instinct is why Scotty Systems exists at all. Some of it is why it took three attempts to get there.

None of the decisions on this map were obviously right at the time. The 70-day AI agency attempt looked like the answer while he was in it. What it produced was footage, a first £150 client through one message from his mum, and an uncomfortable lesson: building elaborate systems was often another way to avoid the simple action that could test them.

Old work, failed experiments and current software all belong to the same story. Pretending the failures were strategy would make the story less true and less useful.

This is the foundation, and it is the part most portfolios would hide. Before there was a platform, a prototype or a single line of product copy, there was somebody making things that people chose to watch.

It matters because it is the whole reason the tools are shaped the way they are. The problems being solved further up this map are not problems read about in a market report — they are problems produced here, by actually making the work.

1. The CreatorCreator first, builder second.
2. ScottyThe channel, and the audience it built.
3. Gorilla TagWhere that audience actually came from.
4. Editing & PacingWhere the hours went — and why the archive grew.
5. Scotty’s NecessitiesThe first time attention became something bought.

The channel is not a warm-up act for the software. It is the source of every problem the software is trying to solve.

What happened next: The Journey →

Every channel, failed plan, lost pound and uncomfortable attempt moved me closer to what Scotty Systems is now.

1. Around age 6–14

   Learning to create

   I started recording in a field when I was around six or seven. The early channels failed, but each one taught me how to film, edit and keep making things before there was any reason to believe it would work.

   Biking, then Fortnite montages, then VR. Where it began →

2. Around age 13–15

   Sc0tty

   At 13, one channel finally worked. Sc0tty reached roughly 42,000 subscribers and 5 million views, generating around £12,000 before tax. I eventually became bored of the niche, stopped uploading and had to start again.

   The money did not last either. Approximate figures from memory, not audited accounts.

   The channel → Gorilla Tag →

3. Around age 14–15

   The side hustles

   • Depop dropshipping−£300LOSS
   • TikTok affiliate+£10PROFIT
   • E-commerce dropshipping−£30LOSS

   None became a business. Each one showed me that copying a model was not the same as caring enough to stay with it.

4. Age 15

   The return-to-YouTube plan

   I planned six weeks of videos around a Shopify store selling the audio packs behind my Gorilla Tag edits. I built the plan and edited the final idea. I never published it.

   The sequence was meant to end on a How to Ghost Roll video. The shop →

5. Age 15–16

   The AI agency attempt

   Then I found AI. I built offers, websites, GoHighLevel systems and automations, while repeatedly avoiding the part that could prove any of it: speaking to potential customers.

   What I built → The calls I avoided →

6. About 70 days in

   The first paid proof

   After about 70 days, the first client did not come from the system I had spent months building. One message from my mum created the introduction, and the first website paid £150.

   Distribution and trust beat infrastructure. The work that still stands →

7. Three months, recorded

   The archive wall

   I had recorded nearly all of it for a future video. The result was 293 playable recordings and 82.2 hours of footage — with no useful way to understand what I had captured.

   293 recordings 82.2 hours 3 months documented

   Filming all of it → Hitting the wall →

8. Now

   Turning the problem into the tool

   That mess became the first real Scotty Systems problem: build something that helps a creator understand their own archive. The current answer is Scotty Archive, now live as the first public creator tool.

   It imports supported files, transcribes their audio, summarises, builds a library and timeline, links evidence to what it tells you, suggests filenames and keeps a creative memory. Access now sits under Scotty Systems: Free is available, while paid membership remains clearly marked unavailable.

   The toolbox → Why I turned → Scotty Systems today →

See what the archive became →

Not a generic marketing bundle. Start with the business, understand where growth is breaking, then build the smallest connected system that fixes it.

The website gives the business a clear home. The brand makes it recognisable. Ads bring relevant traffic. Reviews turn customers into proof. n8n handles repetitive work that is specific enough to deserve a custom solution.

These pieces are not all sold as a finished package today. Websites and branding have real work behind them; the wider connected offer is still being assembled and tested.

Start with the website →

Fast, accessible and specific to the business—not a template filled with different words.

The site should explain the offer, establish trust and make the next step obvious. This is the part of the Growth System with real delivered client work behind it.

Next: Brand & logo →

A usable logo, typography, colours and visual rules that can survive outside a single mock-up.

The aim is recognition and consistency across the website, advertisements, reviews and social profiles.

This is being developed as part of the wider system, not presented as proven campaign performance.

The job is to connect targeting and creative to a landing experience and enquiry route that can actually be tracked.

Ask real customers for feedback at the right moment, follow up responsibly and track whether the request was sent.

No generated reviews and no manipulation—only a reliable process around real customer experience.

Start with discovery, map the existing workflow and automate only the steps that are stable enough to trust.

This is intentionally not a menu of fashionable automations. The workflow should exist because the business has the problem, not because n8n has the node.