You're a founder. Your Monday starts with pulling MRR from Stripe, chasing a CSV from your ops person, and pasting numbers into an email your investors probably skim in ten seconds. What's the most expensive part of that ritual?
Honestly? The time. I'm the most expensive person doing the least leveraged work every week.
Exactly. Before we write a single line of code, I want an honest baseline — not where you wish you were, but where you actually are right now. A 1 on everything is the right answer if you've never opened a Python file.
I'm the CEO, not the engineer. Should I even be learning this?
You're already doing the hard part — the judgment, the prioritisation, reading what matters. Python is the plumbing that stops you being bottlenecked by your team for things that aren't engineering. Rate honestly. Day 30 shows the delta.
Thirty days. One real project: a weekly investor update generator. By Day 28 you'll have working Python that takes a dict of this week's metrics — revenue, signups, churn, top customer — computes deltas, and returns a markdown-formatted update body ready to send.
| Week | Focus | Founder framing |
|---|---|---|
| 1 | Variables, strings, f-strings, booleans, if/elif | "Your investor asks for MTD revenue. Print it." |
| 2 | Lists, loops, dicts, nested structures | "500 customers. Group by plan, not by hand." |
| 3 | Functions, defaults, CSV, JSON | "Turn the MRR query into a function you call every Monday." |
| 4 | Comprehensions, sorting, error handling, capstone | "Ship the investor update as code — it runs itself." |
Every lesson is a Socratic conversation plus one small coding challenge. Tests tell you immediately what went wrong.
You're a founder. Your Monday starts with pulling MRR from Stripe, chasing a CSV from your ops person, and pasting numbers into an email your investors probably skim in ten seconds. What's the most expensive part of that ritual?
Honestly? The time. I'm the most expensive person doing the least leveraged work every week.
Exactly. Before we write a single line of code, I want an honest baseline — not where you wish you were, but where you actually are right now. A 1 on everything is the right answer if you've never opened a Python file.
I'm the CEO, not the engineer. Should I even be learning this?
You're already doing the hard part — the judgment, the prioritisation, reading what matters. Python is the plumbing that stops you being bottlenecked by your team for things that aren't engineering. Rate honestly. Day 30 shows the delta.
Thirty days. One real project: a weekly investor update generator. By Day 28 you'll have working Python that takes a dict of this week's metrics — revenue, signups, churn, top customer — computes deltas, and returns a markdown-formatted update body ready to send.
| Week | Focus | Founder framing |
|---|---|---|
| 1 | Variables, strings, f-strings, booleans, if/elif | "Your investor asks for MTD revenue. Print it." |
| 2 | Lists, loops, dicts, nested structures | "500 customers. Group by plan, not by hand." |
| 3 | Functions, defaults, CSV, JSON | "Turn the MRR query into a function you call every Monday." |
| 4 | Comprehensions, sorting, error handling, capstone | "Ship the investor update as code — it runs itself." |
Every lesson is a Socratic conversation plus one small coding challenge. Tests tell you immediately what went wrong.
