I’ll be adding a new file into the classroom shortly that I wanted to flag to the wider group.
This isn’t about clever tech for the sake of it. It's about what happens when you remove repetitive, boring admin from someone’s day.
In our case, this automation has been built around James Daniels in our team.
Before:
- Manual Rightmove checks (BORING)
- Copying links (BORING)
- Searching descriptions (BORING)
- Trying to work out who the developer actually is (BORING)
- Easy to skip when things get busy (BORING)
Now:
- Every 14 days, Rightmove listings are pulled automatically
- Developer names are extracted
- Contact details are found
- Everything lands structured and ready to review
- James spends his time thinking, qualifying, and following up, not scraping
The outcome isn’t “more tech”. It’s more consistency, less friction, and better use of aspiring team members.
That’s why I wanted to share the file:
- To help you visualise where automation fits into a real business
- To show how systems can support people, not replace them
- To spark ideas for your team, intern, or next hire
📂 You’ll find the full walkthrough and explanation in the classroom but a quick pdf is attached as a walkthrough.
If this triggers questions like:
- “Where does my team waste time?”
- “What’s the first task I should automate?”
- “How do I give juniors better structure without micromanaging?”
…then it’s doing its job.
Happy to talk through it live in Coffee Hour or in the comments. Challenge yourself and ask what could you replace that is repetitive and BORING!