Growth minds Malaga "Clockwork OS" Retreat
Make Your Business Run Like Clockwork — in Malaga
Invite your co-founder and join us in Marbella for a focused, immersive retreat designed to transform how your company operates for years to come. Over two days, you’ll build a complete entrepreneurial operating system for your company, using the Growth Minds “Clockwork OS” framework.
Clockwork OS is the operating system that third-generation entrepreneur Graham Richardson used to build a music marketing company from scratch into an agency working with Justin Bieber, Kelly Clarkson, Sony Music, Warner Music, and nearly every major label. The system draws on a deep family legacy of entrepreneurship: a father who built a sailboat parts company, an uncle who built winemaking software for Napa Valley wineries, another uncle whose company engineered 70% of Times Square’s giant LED displays, and grandparents who ran one of Sacramento’s first rock & roll nightclubs. Entrepreneurship runs deep—and Clockwork OS is the synthesis of those lessons.
Across the retreat, you’ll build the full structure of your business—from your 10-year vision all the way down to your weekly execution rhythm. You’ll design your core values, your strategic focus, your marketing foundation, your quarterly milestones, your scorecard, your issues system, and your weekly Shiatsu meeting. By the end, your company will have a complete operating system that brings clarity, accountability, consistency, and momentum to every part of the business.
This is hands-on, not theoretical. You will leave Marbella with:
A full 10-year → 3-year → 1-year → quarterly → weekly operating system
A working Notion-compatible template for your team
A clear structure for tasks, issues, milestones, scorecards, and accountability
Your weekly meeting rhythm in place and on your calendar
A system that makes your business run like clockwork
And yes—it will also be fun. We’re going somewhere beautiful, eating well, and creating the space founders rarely get: uninterrupted time to think deeply about the future of the company.
Travel Schedule
Note: Flights are not included as every person may have different requirements for baggage, seat class, arrival and departure times. Below is a suggested itinerary:
Arrival:
Thursday evening, 29 January
Direct flight (not included) 19:00–23:00 → Málaga
Arrive just in time for classic late Spanish dinner.
Workshop:
Friday 09:00–18:00
Saturday 09:00–18:00
Departure:
Sunday, 1 February
Flight (not included) 14:25 → 18:50 Stockholm
CLOCKWORK OS ITINERARY:
DAY 1 — 9:00 to 17:00
Vision → Strategy → Multi-Year Planning → Quarterly Milestones
9:00–9:10 (10 min) — Welcome
Explanation: Retreat overview, materials, what we’ll accomplish.
Action: Set up laptops, open templates.
CORE VALUES + CORE FOCUS (Purpose + Niche)
9:10–9:20 (10 min) — Explanation
What Core Values are, how to write useful ones, what Purpose and Niche mean, examples.
9:20–9:55 (35 min) — Action
Write five Core Values
Define Purpose + Niche
Refine with co-founder or paired partner
10-YEAR TARGET
9:55–10:10 (15 min) — Explanation
How a 10-Year Target works, what makes a good one, examples.
10:10–10:40 (30 min) — Action
Create and finalize your 10-Year Target.
10:40–11:50 (1 hr 10 min) — Lunch Break
TARGET MARKET + THREE UNIQUES
11:50–12:05 (15 min) — Explanation
What a Target Market is, what Three Uniques are, examples.
12:05–12:35 (30 min) — Action
Define Target Market.
12:35–13:05 (30 min) — Action
Define Three Uniques.
PROVEN PROCESS
13:05–13:15 (10 min) — Explanation
What a Proven Process is, sample diagrams, examples from real businesses.
13:15–14:35 (1 hr 20 min) — Action
Build your 10-step Proven Process.
Refine wording, simplify, align with customer journey.
14:35–14:45 (10 min) — Break
3-YEAR PICTURE + 1-YEAR PLAN
14:45–14:55 (10 min) — Explanation
Show examples of 3-Year Picture and 1-Year Plan; explain how they cascade from the 10-Year Target.
14:55–15:25 (30 min) — Action
Create your Three-Year Picture.
15:25–15:55 (30 min) — Action
Create your One-Year Plan.
QUARTERLY MILESTONES (Q1 ROCKS)
15:55–16:05 (10 min) — Explanation
How to translate the One-Year Plan into quarterly priorities.
16:05–17:00 (55 min) — Action
Build your Q1 Rocks (Quarterly Milestones).
Define ownership, expected outcomes, on/off-track criteria.
17:00–17:30 (30 min) — Break & Freshen Up
Get ready to leave for Pia's house
17:30–18:00 (30 min) — Travel to Pia's House
18:00 — Mingle, Drinks, Snacks @ Pia's
DAY 2 — 9:00 to 17:00
Scorecard → Issues → Tasks → Automation → Weekly Meeting → Scheduling → Tech Setup
9:00–9:10 (10 min) — Welcome
Explanation: Outline of Day 2 and goals for execution systems.
Action: Open templates and prepare for buildout.
SCORECARD BUILDOUT
9:10–10:30 (1 hr 20 min) — Action
Build the 15-number weekly Scorecard.
Each metric tied to a Q1 Rock or operational KPI.
TASK DATABASE SETUP
10:30–10:40 (10 min) — Explanation
How task databases work, naming rules, linking to Issues and Rocks.
10:40–11:40 (1 hr) — Action
Create Task DB, link relations, set up statuses, create first tasks.
ISSUES LIST SETUP
11:40–11:50 (10 min) — Explanation
What belongs on the Issues list, how it drives weekly execution.
11:50–12:10 (20 min) — Action
Build Issues list and add initial issues.
12:10–13:30 (1 hr 20 min) — Lunch Break
AUTOMATION SETUP (WEEKLY SHIATSU MEETING NOTES)
13:30–13:45 (15 min) — Explanation & Action
Set up automatic weekly meeting note templates in Notion.
FULL MOCK SHIATSU MEETING (2 HOURS)
13:45–15:45 (2 hrs) — Action
Teams run a complete weekly meeting using their systems:
Intro → Data → Execution → Conclusion
Practice:
Scorecard review
Rock review
Unfinished task review
Issues → Tasks conversion
Assigning next-week deliverables
SCHEDULING BLOCK (ROCK DAY + WEEKLY SHIATSU MEETING)
15:45–16:00 (15 min) — Action
Add next quarterly Rock Day to calendar.
Add weekly Shiatsu Meeting to calendar.
Invite co-founders / team members.
TECHNICAL FIXING + SYSTEM VERIFICATION
16:00–17:00 (1 hr) — Action
Solve all technical issues:
Template linking
Database errors
Scorecard formulas
Relations & rollups
Permissions
Automation debugging
Naming conventions
System syncing