What you actually build, week by week, from June 9 to August 27. Click any week to see the focus, the outputs, and the principle behind it.
Join Summer School →This page, the dashboards, the CRMs, the lead magnets you see in the showcase, all built with Claude Code inside the system you'll build.
Summer School makes your life and business sharper, week by week. You pick up Claude Code as you go, while you build the thing you actually need. By the end you own everything: CRM, dashboard, lead magnets, course platform, automations. No Kajabi. No Buffer. No Notion-as-a-database. Just Claude Pro, hosting, and a folder that gets smarter every day you use it.
But you do not have to take my word for it. Here is what the women who built theirs this spring say.
"I cannot say enough about her. She is patient. She is brilliant. She meets you where you are, which for me was with zero coding knowledge."
Jasz, marketing agency founder
"Maaria built me an entire AI system so I have more time for my baby, and she consistently reminds me of what I'm capable of."
Maren, life and CrossFit coach
"The biggest mindset shift is just not waiting to know how to do something. You don't know how to build the thing, but you go in and figure it out anyway."
Lavinia, founder of Livit Hub Bali
❤️ Maaria
Every week of summer school
Every week of every sprint runs the same way. Show up to as many as you can. All sessions are recorded.
Tuesday · The why
Live teaching on what we're building this week and why it matters. The thinking behind the structure and the parts most people get wrong. You leave with a clear picture of what you're about to build.
Wednesday · Life co-build
A live co-build for a life-related skill or application of your system. Cycle tracking, energy logs, dream diary, food protocols, anything that connects your system to how you live.
Thursday · Work co-build
A live co-build for the week's work output. The CRM piece, the lead magnet, the dashboard tab, the automation. You build it with me and the cohort in the room.
Part 1 · Starts June 9
Local-first. Everything lives on your computer. You set up the folders, train the memory, write the protocols, and end with a working dashboard fed by your real life.
This week, your root system learns who you are. Your values, your work, your voice. Then it builds something real.
If you have years of writing, decks, voice notes, brand work already, there's a clean way to import all of it. Every step has a guide inside the system, so Claude walks you through it. You can do it again later, by yourself, anytime.
What you ship this week
The about page is created based on the things that you train it. You don't really need to do it yourself.
Your root system gets smarter every time you use it. Structured memory, compound learning, a system that remembers what matters. This is how it deepens.
This is the part most different from using Claude any other way. You learn which files guide Claude and which ones it uses as content. You learn what loads automatically and what loads only when a task calls for it. With regular Claude you can't really control any of that. Here you can. You decide, you can audit, and when it drifts you can find the file and change it. That is why the system actually gets accurate.
What you ship this week
You have control over what it remembers, how it remembers. If you notice it goes rogue, you can ask where it is, find it, and change it.
Morning protocols, evening protocols, energy tracking. Your root system fits into your life, not the other way around.
You can run them light. You can skip parts when the week is heavy. The system stays usable either way.
What you ship this week
The more time you put into it, the better it gets. But you can't do all of it at once, obviously.
Your dashboard has five tabs. Each one is a window into a different part of your system. This week you will launch it, populate every tab with real data, and see the full picture of what you have built.
Every tab is a template you can modify. Add a tab for what only you need (your tarot, your training plan, your F1 calendar, Stripe webhooks). The dashboard is wired straight into the data your system already holds.
What you ship this week
You can modify everything. Kanbans, your cycle, your days, your tarot, whatever you want. It's a template you can use.
Part 2 · Starts July 7
This is the plumbing. Move from local to hosted. Database, deployment, scaffolding for everything you'll publish, a CRM you actually want to use.
The minimum stack that powers your business. Set it up once. It works from here.
The database here is the same kind powering the SaaS tools you already pay for (Notion, Hubspot, etc). Safe, free, well-established. Mostly invisible once it's set up. You stop owning a folder on one laptop and start owning real infrastructure.
What you ship this week
These are really safe and well established. It's just a setup question.
Your website, auth, payments, emails, course delivery. The whole thing live, in your brand, on your domain. You pick what your business actually needs. Less is better.
After this week, "deploy" is one word. Lead magnets, quizzes, sales pages, course modules, any page goes live without copy-pasting or FTP clients. Because every piece of content, every brand guide, every offering already lives in your folder, Claude pulls from them directly. You stop building from scratch, every page arrives already in your voice.
What you ship this week
You just say "deploy", and it puts it there on your website.
Proof
Five solopreneurs, five different root systems. Click any face to see what they shipped.
Your own CRM. No subscription. No data lock-in. Real relationships, tracked the way you actually think about people.
You already have a CRM from Part 1. This week is where you refine it. Do you want a reminder email when a contact goes cold? A Discord ping when a sales call books? One-click sequences from the dashboard? You decide what your CRM does for you. The plumbing is already there.
What you ship this week
You essentially create the next version of your CRM, and how to use it in daily life.
Stop repeating yourself. Build skills and automations so you can focus on the work that actually needs you.
This is also the week you build the safety layer. Daily health checks. Alerts when something quietly stops working, so you find out before a customer does. A system that's running isn't enough. You need to know when it isn't.
What you ship this week
You don't only have a system that's running. You're informed if something doesn't work the way it should.
Part 3 · Starts August 4 · First run
This is the first run of Part 3. Sharing the system with your team, building AI-powered products for your clients, and going deeper on automation, monitoring, and pricing.
If you have collaborators (team, VAs, contractors, partners), this is where you give them safe, scoped access to your root system. They get the parts they need, you keep the rest.
The handoff is the work. A team member or VA shouldn't need to know your folder. They should land in a clean view, do their part, and have it flow back into the same source of truth you read from in the morning.
What you ship this week
You'll be able to share it. If you have team members or collaborators, they can build with the same root system.
Not quizzes. Real products. Diagnostic web apps, AI assessments, AI homework tools your clients interact with directly. Jasz built one of these in the spring sprint: a tool inside her course that walks each student through their own revenue numbers and tells them what to focus on next.
You learn how to scope it, build it, and ship it for your own work. The framing, the prompts, the safety rails, the bits that show up on the customer side and the bits that stay hidden.
What you ship this week
Including AI touchpoints in your products isn't that difficult. There's just a few things in the background that are good to know if you're not used to building products.
This week is about the difference between a system that runs and a system you can trust running. Daily checkups, alerts, security, the things you only notice when they aren't there.
You also go deeper on automations. The parts of your week you've decided to give up entirely. The pieces that should run on their own and surface only when something needs your eyes.
What you ship this week
You don't only have a system that's running. You're informed if something doesn't work the way it should.
The last week. You take what you've built and put a price on it. How AI products are priced (per use, per outcome, per seat, bundled). How you charge for something that runs while you sleep. How you talk about it in a way that lands with your audience, not with developers.
Then we close with a showcase. You demo what you built. Like the spring cohort did. Your turn.
What you ship this week
Everything that I learn throughout the sprints, I share with the rest of you. Any learnings, any new templates, you decide whether to embed them into your system or not.
Three ways in
“I want to build at my own pace.”
€350
Get it →“I want to keep building, month after month.”
€150 / month
Start →“I want to build it in 3 months, with others.”
€1,500
Reserve →All the templates are built for your needs. If something is missing, we build it together <3