S1E3: Automation
Automation
Building the Future
Scene 1: The Repetition Problem
Section titled “Scene 1: The Repetition Problem”Angus Chalmers was tired of watching his colleagues do the same tasks over and over.
Every Monday, Isla spent two hours copying data from spreadsheets into reports. Every Wednesday, Hodl manually sent project status updates to clients—the same email template, slightly tweaked each time. Every Friday, Flora compiled meeting notes from the week into a summary document.
“We finally have structure,” Angus said quietly during the team standup. “But we’re still doing everything by hand.”
Hodl looked up. “What do you mean?”
“I mean… Claude can do more than organise files. It can build things. Workflows. Automations. Systems that run themselves.”
Scene 2: The First Workflow
Section titled “Scene 2: The First Workflow”They started small. Isla’s Monday report nightmare.
“Walk me through what you do,” Angus said, pulling up a chair next to Isla’s desk.
“Right, so I open the sales spreadsheet, copy the weekly figures, paste them into this Word template, update the client names, add the commentary based on what changed from last week, then format it all nicely and export to PDF.”
Angus nodded slowly. “And that takes two hours?”
“Every. Single. Monday.”
Angus opened Claude Code. “Let’s fix that.”
Within thirty minutes, they’d built a workflow. Upload the spreadsheet, and Claude would analyse the data, generate the report with commentary, format it professionally, and output a client-ready PDF.
Isla ran it for the first time. The report appeared in twelve seconds.
“Twelve seconds,” she whispered. “That’s… that’s my Monday back.”
Scene 3: The Template Factory
Section titled “Scene 3: The Template Factory”News spread fast in a four-person office.
By Wednesday, Hodl had cornered Angus. “The client updates. Can you do those too?”
“Show me the pattern.”
Hodl pulled up his email drafts folder. Dozens of unsent status updates, each one 80% identical to the last.
Angus built a slash command—a simple instruction that Claude could execute instantly.
Type /status Henderson, and Claude would pull the latest project data, generate
a personalised update, and draft the email ready for review.
“I just… type that?” Hodl asked.
“You just type that.”
Hodl tested it. A perfectly formatted status update appeared, client name inserted, recent milestones highlighted, next steps clearly outlined.
“The honey badger,” Hodl said slowly, “is starting to like this coding business.”
Scene 4: Flora’s Knowledge Base
Section titled “Scene 4: Flora’s Knowledge Base”Flora had been watching from her corner of the office. She approached Angus on Thursday.
“I want to build something bigger,” she said. “A knowledge base. Not just files in folders, but… searchable intelligence.”
Angus raised an eyebrow. “Go on.”
“Every proposal we’ve written, every client conversation, every lesson learned. I want Claude to be able to answer questions about our entire history.”
It was a bigger project, but Angus was a sheep who liked a challenge. Together with Flora, they connected Claude to GrowthPath’s entire document archive. They enriched files with metadata—client names, project types, dates, outcomes.
The first query Flora tried: “What marketing approaches have worked best for our fintech clients?”
Claude pulled together insights from three years of projects, four different clients, and twelve separate campaign reports. In seconds, Flora had an answer that would have taken days to compile manually.
“This,” Flora said, “changes everything.”
Scene 5: The Isla Touch
Section titled “Scene 5: The Isla Touch”Isla had been quiet, but her mind was racing.
“Angus,” she said on Friday afternoon, “can we connect Claude to other tools? Not just our files, but… external things?”
Angus smiled. The fox was cunning. “What did you have in mind?”
“I spend half my time switching between apps. Calendar to check availability. Spreadsheets for budget tracking. Design tools for mockups. What if Claude could talk to all of them?”
It took the weekend, but Angus built MCP connections—bridges between Claude and GrowthPath’s toolkit. Calendar access. Spreadsheet integration. Even a link to their design platform.
Monday morning, Isla tested the full workflow:
“Schedule a client call with Henderson next week, block two hours for campaign prep before it, update the marketing budget with the new spend figures, and draft social posts for the product launch.”
Done. Done. Done. Done.
Isla leaned back in her chair. “I just did four hours of work in one sentence.”
Scene 6: The New Normal
Section titled “Scene 6: The New Normal”Three months later, GrowthPath barely resembled the chaotic startup from Episode 1.
Hodl still had vision—but now he could act on it, because his tools worked with him. Flora still loved structure—but now the structure maintained itself. Angus still built methodically—but now his builds multiplied their impact. Isla still thought creatively—but now she had time to think.
“You know,” Hodl said during their quarterly review, staring at metrics that had seemed impossible just weeks ago, “the honey badger doesn’t give up. But it’s nice not to have to fight quite so hard anymore.”
Flora adjusted her glasses. “The owl prefers wisdom to warfare.”
Angus nodded quietly. “The sheep builds foundations that last.”
Isla grinned. “And the fox? The fox always finds a way.”
Scene 7: The Invitation
Section titled “Scene 7: The Invitation”GrowthPath’s transformation hadn’t gone unnoticed. Other small businesses started asking questions. How did you do it? Can you teach us?
The team looked at each other. Four Scottish characters, four different approaches, one shared journey.
“Maybe,” Hodl said slowly, “that’s exactly what we should do next.”
The End of Season 1
Section titled “The End of Season 1”The GrowthPath story continues, but Season 1 ends here—with chaos conquered, structure established, and automation unleashed.
Your turn.
Ready to transform your own workflows?
Join GrowthPath's journey. The CoEngineers course teaches everything they learned—and more.
Start Your Transformation