You've shipped Python scripts that format invoice strings and group client data. Now the question is: can you make those scripts talk to the real apps on your desktop — Gmail, Sheets, Calendar, LinkedIn? Before we wire a single connection, tell me: which client-facing workflow burns the most unbillable hours each month?
Sending monthly invoices. I write the same email six times, attach the PDF, change the client name. It's forty-five minutes I'll never recover.
Forty-five minutes a month sounds small. That's nine hours a year. Python plus one Gmail connection ends it. Rate yourself on six skills before we start — honest numbers only.
I've never called an API before. Is connecting to Gmail actually something I can do without a backend?
You're not building a backend. You're writing a Python function that calls a pre-wired toolset. One line gets your inbox. Rate yourself on where you are today — Day 30 will show the delta.
Thirty days. One real workflow: an end-of-month client digest. By Day 28 you'll have a Python script that reads tracked hours from a Google Sheet, generates a summary email per client and sends it (to yourself, safely), and drafts a LinkedIn post recapping completed projects.
| Week | Focus | Freelancer framing |
|---|---|---|
| 1 | Gmail read, fetch, search, draft, send | "Send your monthly invoice email from code, not by hand." |
| 2 | Calendar, Tasks | "Create a client kickoff event the moment a project is confirmed." |
| 3 | Sheets, Docs | "Append every tracked hour to your time-log Sheet automatically." |
| 4 | Cross-app workflows, capstone | "Wire your whole end-of-month admin into one Python function." |
Every lesson uses your live Gmail, Sheets, and Calendar — real data, safe patterns.
You've shipped Python scripts that format invoice strings and group client data. Now the question is: can you make those scripts talk to the real apps on your desktop — Gmail, Sheets, Calendar, LinkedIn? Before we wire a single connection, tell me: which client-facing workflow burns the most unbillable hours each month?
Sending monthly invoices. I write the same email six times, attach the PDF, change the client name. It's forty-five minutes I'll never recover.
Forty-five minutes a month sounds small. That's nine hours a year. Python plus one Gmail connection ends it. Rate yourself on six skills before we start — honest numbers only.
I've never called an API before. Is connecting to Gmail actually something I can do without a backend?
You're not building a backend. You're writing a Python function that calls a pre-wired toolset. One line gets your inbox. Rate yourself on where you are today — Day 30 will show the delta.
Thirty days. One real workflow: an end-of-month client digest. By Day 28 you'll have a Python script that reads tracked hours from a Google Sheet, generates a summary email per client and sends it (to yourself, safely), and drafts a LinkedIn post recapping completed projects.
| Week | Focus | Freelancer framing |
|---|---|---|
| 1 | Gmail read, fetch, search, draft, send | "Send your monthly invoice email from code, not by hand." |
| 2 | Calendar, Tasks | "Create a client kickoff event the moment a project is confirmed." |
| 3 | Sheets, Docs | "Append every tracked hour to your time-log Sheet automatically." |
| 4 | Cross-app workflows, capstone | "Wire your whole end-of-month admin into one Python function." |
Every lesson uses your live Gmail, Sheets, and Calendar — real data, safe patterns.
Create a free account to get started. Paid plans unlock all tracks.