ENROLLMENT OPEN · 21 JUL 22 SEP 2026 · 9 WEEKS

You tell people you’re not technical.You’re lying to yourself.

You use AI every day. You’re getting good at it. You know what’s possible. You suspect you’re using maybe five percent of it.

You’ve tried tutorials. You opened the thing they told you to open. It didn’t help. Not because you’re not smart enough, but because nobody handed you a map.

You’re spending time on things you know you could automate. But the idea dies in the gap between “I should learn this” and “where do I even start.”

You’re paying $200+ a month and way too many hours for tools you suspect you could build yourself.

9 weeks · 3 systems · 15 seats
Hold your seat →
02

What that lie is costing you right now.

There isn’t time tomorrow for this. AI is moving at the speed of light. The coworker who figured out how to make it work for her is outshipping you. The guy you don’t like is using it to plan the next two moves of his career.

You’re on the sideline. The sideline is moving backwards.

A · What it’s costing you
B · What you’d own
01
Hours of mindless email every morning
hours/week · paid in attention
An agent that runs your inbox before breakfast.
→ R-07 · email automation
02
$200+/month in SaaS you suspect you could replace
Quicken · Rocket Money · YNAB · etc.
A financial system that runs on your machine, owned by you.
→ R-06 · saves Alex ~$200/mo
03
A someday list two years deep
ideas · paid in regret
Three of those ideas, shipped, in your hands by week 9.
→ MCP + recipe + your own
04
Bracing in every conversation about technology
I’m more of an analog person
A different posture when the topic comes up.
→ the felt-sense shift
Σ
Total · running cost
Total · what you’d own

You’re not analog. You’re scared. Fear of technology is a shadow, like not ignoring your finances and hope they get better. You can’t ignore what’s happening around you.

03

Three systems you build. Three things you’ll never put back down.

By week nine you have three systems. Built by you. Running on your machine. Yours to keep.

PL · 02 · ABUILD 01 · PERSONAL MCPREV. A · KEYSTONE
BUILD 01 · ANCHOR

Personal MCP

Your private context layer. Your notes, your journal, your project history, indexed and queryable from any AI client. The spine of everything else.

ValuePerfect context for any AI
OwnsYou
CostA few hours upfront, a few bucks a year
Built inWeeks 2–3
FILE · TPA·01·B-017 INGEST · 1 KEYSTONE · ∞ QUERIES→ The thing I use every day.
PL · 02 · BBUILD 02 · RECIPE FROM THE SHELFREV. A
BUILD 02 · CHOSEN

A build from the recipe shelf

Twelve recipes I’ve built and run myself, all on the recipes page. Pick yours based on what’s eating your week. Fast builders pick two or three. Steady builders go deep on one.

Source12-recipe shelf
OwnsYou
CostA weekend project, but you’ll make up that time in automation in days
Built inWeeks 4–6
FILE · TPA·01·B-0212 RECIPES · 1 PICK→ The map is the recipe. The hands are yours.
PL · 02 · CBUILD 03 · YOUR OWNREV. A · UNSCOPED
BUILD 03 · WILD

Your own build

Entirely your idea. By week 7 you know enough to scope something neither of us has built before. We design it together. You ship it.

StackYou decide
OwnsYou
CostAs ambitious or simple as you want
Built inWeeks 7–9
FILE · TPA·01·B-03SCOPE · UNDETERMINED · CO-DESIGNED→ Something neither of us has built before.
B-Side · the things that don’t show up in the deliverablesPG · 04 · B

The three deliverables are the receipt. This is what you’re actually paying for.

Three systems is the visible part, the part you’ll see in front of you. But the real value is the confidence.

A · Architect skillA

Design. Before code.

Choosing, imagining, weighing tradeoffs. You’ll apply it to every problem in your life from week 4 forward.

B · Build habitB

The reflex to ship.

Open the editor, write the thing, debug it, ship it. By week 4 it’s automatic. It’s part of the offering, not a side effect.

C · ContainerC

Fourteen peers.

Building in parallel with you. Async support, real arch review, builds-in-progress visible to the room. Nobody at this scale gets lost.

D · A stack that’s yoursD

Yours, portable.

Your tools, your data, model-agnostic. When the next model drops, you swap a config line.

04

A conductor doesn’t play every note.

FIG · A · PLAYER · REV · Aone phrase, one player
REV · A
A · PLAYER

One line at a time. No score.

The model writes one phrase. You ask for the next. You ship a feature. You never hear the symphony.

ONE LINE AT A TIME. NO SCORE.1 PROMPT · 1 REPLY
FIG · B · CONDUCTOR · REV · Done score, marked & conducted
REV · D
B · CONDUCTOR

One score, conducted.

You hear the whole. You set structure, dynamics, tempo. The orchestra plays. You make the calls.

ONE SCORE, CONDUCTED.4 SECTIONS · 1 SCORE

Stop using AI like a toddler.

Use it like a super intelligence.

Conduct with it.

05

I am not the guy selling you Claude Code in ten steps.

I don’t teach the tool. I teach the skill that masters any tool.

01
DESIGN BEFORE PROMPTS

Design, then build.

The model writes the code. You design the system. Most people never make that shift.

02
CONFIDENCE FOR LIFE

The skill that stays.

Open the window. Write the thing. Persist when it breaks. Ship. Eventually the thing that used to feel impossible takes forty minutes.

I’d rather teach fifteen people to think like architects than fifteen thousand to copy and paste.

06

I’m Alexander Habiby. I failed out of computer science.

I was twenty. I was told I just didn’t have what it takes. They were right academically. They were wrong professionally.I’ve spent the last decade proving them wrong without fully believing it.

60+ enterprise systems in production. Currently the architect on massive state platform builds. NYC’s COVID vaccine management system, architected at the peak of the pandemic.

On my own machine in the last eight months: a personal MCP with five years of my journal, notes, emails and texts queryable from any AI client. A local agent (Hermes) that runs my finances, sorts my files, and orchestrates everything else. A financial automation stack that saves me about $200 a month and got me an extra $30k in tax refund.

Not because I had to. Because I want to own my tools instead of renting them.

Alexander Habiby · drafting-table portrait, ink on cream paper. FIG · A · ALEXANDER · REV · A.
07

Format.

Two live calls a week, two hours each. Monday at 6 PM CT for the main session. Saturday at noon CTfor Q&A and lab work. Recordings posted within 24 hours. Async support from me between calls, not a bot.

FIG · 14 · CADENCE · REV · C
SCALE · ONE WEEK
LIVE CALLS · MON 6PM CT · SAT 12PM CT · 18 SESSIONS · 9 WEEKS
FIG · 15 · SEATS
SCALE · ROOM
FIFTEEN SEATS · SMALL ON PURPOSE
REV · C

What this course is.

  • Architecture skills for everyone.
  • For people using AI daily but ready to build with it.
  • For solo operators paying for too many subscriptions.
  • For people sitting on a list of someday I’ll builds.

What this course isn’t.

  • A starting point for total beginners with no AI history.
  • For people who already run their own agent infrastructure.
  • A toolbox tutorial in a fancy frame.
  • For people who passively watch hoping to learn through osmosis.
YOU DON’T NEED · CODING · TERMINAL · ENGINEERING CREDENTIALS
08

$999.

Founding cohort price. Pay in full or hold your seat with a $250 deposit. The price is the price. No upsell. No certification scheme.

THE ASK

In exchange for the cohort 01 rate, you commit to a written testimonial after week 8 if you got value.

GUARANTEE · 01

Three working systems or full refund.

GUARANTEE · 02

Architecture intake before the cohort starts.

GUARANTEE · 03

Weekly office hours for personalized assistance.

Complete the nine weeks, submit the homework. If you don’t have three AI-native systems you built yourself and use daily, full refund.

09

Build the thing you keep not building.

Fifteen of us are going to spend nine weeks building tools we own.

Seats close when the cohort fills, or July 14, whichever comes first.