Summer School · Curriculum Walkthrough

Twelve weeks. Three sprints. One root system.

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.

From your coach

You're building a village of neighbours who build on each other's work, while each serving their own unique role.

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.

Jasz

"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

Maren

"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

Lavinia

"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

Three sessions. One rhythm.

Every week of every sprint runs the same way. Show up to as many as you can. All sessions are recorded.

Tuesday · The why

Teaching the week's focus

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

Build something for your life

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

Build something for your business

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.

Maaria walking through the three weekly sessions.
Join Summer School →

Jump to a part.

22-minute walkthrough of the full summer school curriculum.

Want to build your own?

Join now →

Part 1 · Starts June 9

Build Your System

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.

Week1
Module 1 · Onboarding

your root system knows you

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

  • Your starter template kit installed (folder structure for prompts, skills, memory, history)
  • An onboarding conversation that gives Claude your values, voice, work, direction
  • Existing writing, decks, and voice notes imported and organized inside the folder
  • Your about page, generated from everything Claude now knows about you
  • Guides for every step you ran, so you can repeat or extend them on your own
The about page is created based on the things that you train it. You don't really need to do it yourself.
Week 1 · June 9 - June 15
Week2
Module 2 · Memory

It learns. It deepens.

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

  • A layered memory system: facts that don't change, patterns that emerge, scratchpads, immutable history
  • Facts files for identity, preferences, current state, decisions, goals
  • A routing layer that loads only what each task needs (not the whole archive every time)
  • A pattern log Claude writes to as it learns how you work
  • Audit + edit workflow: find any memory in seconds, change it, watch the behaviour change
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.
Week 2 · June 16 - June 22
Week3
Module 3 · Protocols

Your rhythm, your way

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

  • A morning protocol that opens the day and surfaces what matters
  • An evening protocol that closes it, logs the day, and prepares tomorrow
  • An energy or cycle-aware planning template that fits how you actually work
  • Quality checks Claude runs on itself before shipping anything
  • Hard gates that fire mid-session, so non-negotiables actually happen
  • Save-session routines so nothing important gets lost between conversations
The more time you put into it, the better it gets. But you can't do all of it at once, obviously.
Week 3 · June 23 - June 29
Week4
Module 4 · Dashboard

You see your patterns

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

  • A live 5-tab dashboard wired into the system you built in Weeks 1-3
  • Relationships tab: CRM template seeded from your existing contacts, statuses, and history
  • Network tab: your LinkedIn imported and analyzed for ICP, customers, and your own profile
  • Sequences tab: automated onboarding emails, no extra subscription
  • Rhythm tab: cycle, energy, morning + evening reads, four-language scoring over time
  • Content tab: calendar, ideas vault, inspiration analysis
  • Optional extras: Kanban, tarot pulls, Stripe webhook feed, anything you want next to it
You can modify everything. Kanbans, your cycle, your days, your tarot, whatever you want. It's a template you can use.
Week 4 · June 30 - July 6

Part 2 · Starts July 7

Run Your Business

This is the plumbing. Move from local to hosted. Database, deployment, scaffolding for everything you'll publish, a CRM you actually want to use.

Week5
Module 5 · The stack

Everything connected, once

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

  • A hosted SQL database (Supabase) connected to your folder
  • Your CRM, contacts, and sequences migrated off your laptop into the database
  • Auth layer so only you (and people you choose) can access your data
  • Daily backups + one-click export of everything you own
  • API connections wired up, so any future page or product reads/writes from the same source
  • Connection from your dashboard to the database, no copy-pasting
These are really safe and well established. It's just a setup question.
Week 5 · July 7 - July 13
Week6
Module 6 · Ship

Ship your business

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

  • Hosting connected (Hostinger, Simply, or whatever you already use)
  • Your site live on your domain, in your brand, with your real content
  • Auth flow (signup, login, password reset) for any gated content you ship
  • Payment processing (Stripe) wired in for products, sprints, or membership
  • Transactional emails: receipts, confirmations, password resets
  • Course delivery: logins, modules, progress tracking, if you teach
  • Lead magnet + quiz scaffolding, one-command deployable
  • Page templates pre-shaped to your brand for everything you publish next
You just say "deploy", and it puts it there on your website.
Week 6 · July 14 - July 20

Halfway in, your business already runs on the system you built. Six weeks left.

Reserve a seat →
Week7
Module 7 · CRM

Your clients, your relationships, remembered

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

  • A refined CRM with the statuses, fields, and views that match your sales process
  • Promises tracked as first-class data (what you said, by when, what you owe)
  • Custom signals: reminders when contacts cool off, alerts on warm threads
  • One-click sequences from the dashboard (welcome, nurture, follow-up)
  • Relationship history surfaced on every contact (every email, call, DM in one view)
  • Daily CRM reads piped into your morning dashboard
  • Full export rights, your data, always yours
You essentially create the next version of your CRM, and how to use it in daily life.
Week 7 · July 21 - July 27
Week8
Module 8 · Automations

Your repetitive work, handled

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

  • Custom skills for the work you do the same way every time (CRM logs, content drafts, weekly emails)
  • Workflows that run on their own end-to-end (e.g. content goes from idea to scheduled social post)
  • Social posting via Postiz from inside the system (no Buffer subscription)
  • Scheduling logic that respects your rhythm, not generic Monday 9am defaults
  • Daily health checks across database, hosting, payments, email, and edge functions
  • Security checks on every public endpoint you've shipped (auth, rate limits, signed tokens)
  • Alerts wired to email or Discord so you find out within minutes when something breaks
You don't only have a system that's running. You're informed if something doesn't work the way it should.
Week 8 · July 28 - August 3

Part 3 · Starts August 4 · First run

Share Your System

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.

Week9
Part 3 · Sharing

Hand the system to your team without losing the soul of it.

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

  • Scoped access for collaborators (read, write, or build) per role
  • A clean handoff dashboard view, so they see only what they need
  • Sync workflows so their work flows back into your main dashboard automatically
  • Audit log of who did what, so you can review at the end of the week
  • Onboarding doc Claude generates for any new collaborator
You'll be able to share it. If you have team members or collaborators, they can build with the same root system.
Week 9 · August 4 - August 10
Week10
Part 3 · AI products

Build products that actually use AI in their flow.

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

  • A working AI-powered product for your clients or your audience
  • The product brief: what AI does, what humans do, where the line is
  • System prompt + persona tuned to your voice and your subject matter
  • Input UI for clients (form, chat, upload, whatever fits the use case)
  • Safety rails: refusal patterns, fallback responses, output validation
  • Cost monitoring per session, so unit economics stay sane
  • Embedded inside your course / site / dashboard, not a separate tool
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.
Week 10 · August 11 - August 17
Week11
Part 3 · Deep automation

Automations you can trust unattended.

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

  • End-to-end automations for repetitive flows (lead capture, CRM enrichment, content scheduling)
  • Cron-scheduled checks across database, payments, email, public endpoints
  • Security review of every public endpoint (auth, rate limits, HMAC tokens, CORS)
  • GDPR review for personal data: retention, deletion, consent logs
  • An incident playbook so you (or your team) know what to do when something breaks
  • Token + cost monitoring on every AI surface so monthly bills hold no surprises
You don't only have a system that's running. You're informed if something doesn't work the way it should.
Week 11 · August 18 - August 24
Week12
Part 3 · Ship & price

Price your AI products. Open the doors. Show your work.

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

  • Pricing for every AI-powered product you've built (with unit economics behind it)
  • A sales page or product page, live and open to the public
  • Stripe checkout wired in, with confirmation emails sent from your system
  • A short launch announcement (newsletter + social) drafted in your voice
  • Your showcase demo, presented in the closing session, recorded for your library
  • A clean ending: archive what you didn't finish, capture what you want to revisit
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.
Week 12 · August 25 - August 27

Three ways in

Pick the rhythm that fits your summer.

30% off until July

DIY

“I want to build at my own pace.”

  • Full self-led course
  • Template kit
  • Lifetime access to the version you got

€350

Get it →

Membership

“I want to keep building, month after month.”

  • Full course and template kit
  • Updates to the template kit
  • Weekly co-build session
  • Discord community
  • Cancel anytime

€150 / month

Start →
Save 25% until July

Summer School

“I want to build it in 3 months, with others.”

  • Everything in Membership
  • Three sprints, June to August
  • Unlimited 1:1 with Maaria
  • Private sprint Discord channel
  • Lifetime cohort access

€1,500

Reserve →

Or pay 3 × €550 monthly

This page too was built with the root system.

Twelve weeks from now, your business runs on what you built.

All the templates are built for your needs. If something is missing, we build it together <3