Learning Path
Productivity and Tool Stack Path
Every productivity list online is a link farm written by people who have never run a solo business. This path is organised by problem instead: time, money, clients, content — one tool per problem, free tier first, and a rule against tool overload. The stack is the tool layer for every other path on this site, and it is taught the way a solo business actually uses it.
How this path works. Each lesson below is a short summary of the topic it links to, with an exercise that proves you can do the work. Work through them in order, do the exercise, and mark each lesson complete when you have read the guide and done the work. The two-question check under each lesson is for yourself — it is not scored and it is not a certificate. Your progress is stored only in your own browser, in local storage — no account, nothing sent to us. Completing this path gives you no certificate and no qualification, and it promises no income: the proof is the finished work from the capstone lesson, not a certificate.
What you will learn
- The minimal stack: one tool per problem, free tier first.
- Time: tracking billable hours without drowning in apps.
- Money: invoicing, tracking, expenses — in one place.
- Clients: communication, scheduling, onboarding.
- Choosing without overload: the one-in, one-out rule.
Your progress
0 of 6 lessons complete.
The lessons
Read each lesson summary, then open the full guide it links to. The summaries are written for this path — they do not repeat the guides, they prepare you for them.
Lesson 1: The minimal stack — one tool per problem, free tier first
The minimal stack is one tool per problem, free tier first: time, money, clients, content — four problems, four tools, and nothing else until a fifth problem proves it needs one. The rule is the overhead rule: every app you maintain costs time to log into, learn and keep in sync, and a stack of ten apps is a part-time job in itself. The stack is the tool catalogue on this site made personal — your four, chosen for your problems.
This lesson assembles your minimal stack from the problems you actually have, not from a listicle: which problem hurts most, which free tool solves it, and what it costs when you outgrow the free tier. You will learn why a stack you can explain in one sentence is a stack you will use, and a stack you cannot explain is a stack you will abandon.
Exercise: List your four problems and one free tool for each, with the monthly cost totalled.
Check yourself — two questions on this lesson
1. What is the minimal stack?
One tool per problem, free tier first — time, money, clients, content.
2. Why does every extra app cost?
Because logging in, learning and syncing it is a part-time job in itself.
Lesson 2: Time — tracking billable hours
Billable hours are the freelancer's currency, and the money leaks in two places: hours worked but never recorded, and hours recorded but never billed. Tracking is the habit that stops both — a start and a stop time, a note of what the hour was for, and a weekly total that goes on the invoice. The tool is a calculator, not a tracker; the tracker is the habit.
This lesson sets up the time habit: how to record hours, how to turn hours worked into billable hours, and how the total feeds the rate — because a rate that ignores non-billable hours pays you for fewer hours than you worked. You will learn the weekly review: what was billed, what was not, and what the gap means for the next week's price.
Exercise: Track your hours for one week: worked, billable, and the gap between them.
Check yourself — two questions on this lesson
1. Where does freelance money leak?
Hours worked but never recorded, and hours recorded but never billed.
2. What is the weekly review for?
What was billed, what was not, and what the gap means for next week's price.
Lesson 3: Money — invoicing, tracking, expenses
The money tools are three, and they cover the whole of freelance money: an invoice that says what is owed, a tracker that says who owes it, and an expense planner that says what the business costs. None of them needs to be complicated; all of them need to be used. A freelancer with an invoice habit, a tracker habit and an expense habit knows what they earned, what they are owed, and what they spent — which is the whole of money management at this size.
This lesson wires the three tools together into one weekly routine: invoice on completion, enter the payment the day it lands, record the expense the day it is spent, and review the three numbers every Friday. You will learn the one mistake that breaks the system — recording from memory at the end of the month — and why the day-of habit is the whole of it.
Exercise: Wire the three money tools into one weekly routine and write it down.
Check yourself — two questions on this lesson
1. What are the three money tools?
Invoice, payment tracker, expense planner.
2. What breaks the system?
Recording from memory at the end of the month.
Lesson 4: Clients — comms, scheduling, onboarding
The client tools are the ones that keep a client: communication that is prompt and in one place, scheduling that respects both calendars, and onboarding that records how the client works so the job survives a holiday. A client lost to slow replies is a client lost for free; a client kept by a system is a client kept by design. The tool is not the answer — the habit of answering promptly, in one place, is.
This lesson builds the client system from the communication lesson in the freelancing path: one place for messages, one scheduling link, an onboarding note for each client, and the boundary that says when you are available. You will learn the small habit that keeps clients for years: report progress before being asked, and raise problems the moment you see them.
Exercise: Write your client system: one message place, one scheduling link, and an onboarding note template.
Check yourself — two questions on this lesson
1. What keeps a client?
Prompt communication in one place, scheduling that works, and an onboarding note.
2. What is the habit that keeps clients years?
Report progress before being asked, and raise problems early.
Lesson 5: Content — calendar, captions, scheduling
Content tools solve a simple problem: knowing what to publish, when, and in words that fit. A calendar turns a pile of ideas into a plan; a caption counter keeps a post inside the length that works; a scheduler posts it while you do other work. The content tool that matters most is the calendar — because a creator without a plan publishes when they feel like it, which is to say rarely, and a creator with a plan publishes weekly whether they feel like it or not.
This lesson builds the content system: a calendar with a month of ideas, captions checked for length, and a scheduling habit that takes an hour a week. You will learn why the calendar is a commitment device, not a decoration — the promise to publish weekly, written down, is what keeps the content coming.
Exercise: Generate a content calendar for one month from your own ideas.
Check yourself — two questions on this lesson
1. What is the content tool that matters most?
The calendar — it turns ideas into a weekly promise.
2. Why check caption length?
Because a caption that fits the platform works, and one that does not is cut off.
Lesson 6: Choosing without tool overload — the one-in-one-out rule, price checks
Every productivity list is, in practice, a link farm written by people who have never built a business alone — most lists are affiliate collections, and the honest outlier is the guide that refuses to name monthly ranges for lack of sources. The final lesson is the choosing method: by problem, not by tool; by the price when you outgrow the free tier, not by the feature list; and with the honesty label where a tool was not independently tested. No list can claim a best tool without a stated method, and this path does not.
This lesson ends with the defence against overload — the one-in, one-out rule: a new tool enters only when an old one leaves. Prices go stale fast, so check the current price on the tool's own pricing page before you pay for anything. It ends with the capstone: your minimal stack, one tool per problem, with the monthly cost totalled.
Exercise: Capstone: finish your minimal stack — one tool per problem, with the monthly cost totalled.
Check yourself — two questions on this lesson
1. What is the one-in, one-out rule?
A new tool enters only when an old one leaves.
2. Why check the current price yourself?
Prices go stale fast — last year's price is not today's.
Try the tools
These free tools let you practise what the lessons describe — everything runs in your browser, and nothing you type is sent anywhere.
- Working Hours Calculator — turn hours worked into billable hours
- Client Payment Tracker — track who owes what and when
- Monthly Expense Planner — work out what the business costs each month
- Content Calendar Generator — plan content without a new app
Check what you learned
6 questions, all based on the lessons above. Answer them all, then check your score — each answer explains itself, so a wrong answer teaches as much as a right one. The quiz is practice, not a test: there is no pass mark and no certificate.
Answer all 6 questions, then check your score.
Download your notes
Download a plain-text summary of this path: the lesson list, which lessons you marked complete, and your quiz score. The file is generated on your device — nothing is uploaded.
Key terms in this path
The terms this path uses are defined in the Glossary, each with an example. If a lesson uses a word you do not know, look it up there first.
Frequently asked questions
How many tools does a freelancer need?
One per problem — time, money, clients, content — free tier first. More tools than problems is not a stack; it is a cost.
Are free tiers good enough?
Yes, for a beginner — the free tier of most tools covers a solo business. The check is what the tool costs when you outgrow it, not what the free tier lacks today.
What is tool overload?
The cost of maintaining too many apps: logging in, learning, syncing, paying — until the tools cost more time than they save. The one-in, one-out rule is the defence.
Should I use one all-in-one tool?
Only if it genuinely solves your problems better than separate tools. One app that does four jobs badly is worse than four that do one job well.
How do I choose between two similar tools?
By the method in the final lesson: the problem it solves, the price when you outgrow the free tier, and whether it was independently tested — with the honest label where it was not.