Notes · Freelancers & solo founders
Three apps for three modes is friction; one app for all of it is a mess. Here is a third option — one system, three contexts, with clear boundaries between them.
You wake up. You open the laptop. You also open the iPad. You also open the phone.
On the laptop: the project-management tool with your client work.
On the iPad: the notes app with your half-formed product ideas.
On the phone: the calendar with your dentist appointment and your friend's birthday.
By 8:45 a.m., you have read three different applications, in three different visual languages, with three different vocabularies for task, commitment, and next thing. None of them know what the others contain. You, the user, are the integration layer. The integration layer is tired.
This article is about the third option — between one app per mode (high friction) and one app for everything (poor fit). The third option is one app, with explicit contexts inside it, and clean boundaries about which lives in the system and which lives outside.
A common mistake is treating client work, admin, and personal as the same kind of thing. They are not.
Client work is committed to other people. Missing it has consequences for the relationship. It needs deadlines, and the deadlines need teeth.
Admin is committed to a calendar or a process. Filing the VAT. Paying the invoice. Renewing the domain. These have hard deadlines, often arbitrary, and consequences for not doing them (penalties, lapses) but not really consequences for when you do them within the window.
Personal is committed to your own life. Visiting your parents. Reading the book. Doing the laundry. The deadlines are softer, mostly self-imposed, and the consequences are emotional rather than contractual.
The reason these need separate visibility is that they require different mental modes. Client work wants the deadline-led view. Admin wants the batched, low-thought view. Personal wants the low-pressure, when-you-have-energy view.
If you mix them all into one undifferentiated list, you get the worst of each: client items lose their urgency among the noise, admin items steal attention from work that matters more, and personal items quietly disappear because they have the softest deadlines.
The fix is not to use three apps. It is to use one app with explicit contexts inside it.
Contexts are useful. Too many contexts are a tag system in disguise. The line is at three or four.
A reasonable solo-worker context set:
Three or four contexts is the limit because more than that, you spend time deciding which context a task belongs to. The categorisation is supposed to reduce decision load, not add to it.
Notice what is not a context: a client-by-client breakdown, a tag-by-mood breakdown, a priority-level breakdown. Those can live inside a context (sub-Oases, in Oasa's vocabulary) but they should not be the top-level structure. Top-level structure is for modes of life, not for fine sorting.
A practical week-shape that puts the principles to work.
Sunday evening, 25 minutes. Plan the week. Look at each of your three (or four) contexts in turn. For each, name the one major thing and the one supporting thing. That is six things across three contexts. Add five-to-eight smaller items if needed (admin and personal usually generate these). You now have a week.
Monday morning, 15 minutes. Translate the week into the calendar. The major client-work block goes first — pick the time when your focus is strongest. The admin batch goes at a low-energy time. The personal items go in the spaces you actually have, not in aspirational windows.
Inside the day, stay in one context per block. When you are doing client work, do not look at admin. When you are doing admin, do not switch to client work. The context-switching cost is real; the discipline of one-context-per-block is more useful than any productivity hack.
Friday afternoon, 15 minutes. Glance at each context. What moved? What did not? What carries over to next week? Write three sentences for next week's one major thing per context.
Total weekly overhead: under an hour. Total tools opened during the day: ideally one (the task manager) plus the calendar. Phone is on Do Not Disturb during deep blocks.
This is, by design, low-overhead. The lighter the cadence, the more likely it survives a difficult week.
A surprising amount of what looks like a task is not, actually, a task. It is something else dressed as a task.
A few things that do not belong in the task manager:
A clean task manager only holds things that you, personally, will do, within a knowable horizon, that have a clear definition of done. Everything else corrupts it.
This is a kind of triage hygiene. The lighter you keep the list, the more honest the list becomes — and the more honest the list, the calmer it is to look at.
A specific category worth pulling out: things with time attached to them.
A task with a date in the future is not really a task; it is an appointment. If it has a clear time slot, it belongs in the calendar. Anything else is a maybe.
A useful test: a task that has been on your list for a month, with a due date that you have moved three times, is not actually a task with a due date. It is an aspiration. Move it to a someday list or delete it, and stop pretending the due date is real.
This adjustment alone removes about a third of the items from most freelancers' lists. You will be surprised by how much lighter the system feels afterward.
Oasa is built around the idea of Oases — focused spaces, each with one intention and one rhythm. The natural use for a mixed-responsibilities worker is to have a small number of Oases mapped to your contexts.
A typical setup might look like:
You can pick a different Oasis type per Oasis. Client work usually wants 80/20 — Golden Seeds rise. Admin usually wants Simple — clean list, batched, low-thought. Personal usually wants Simple too, with the unhurried pace its real-life nature wants.
The Zen Garden grows across all Oases. So a quiet week of admin followed by a productive week of client work both contribute to the same visible record of what you have built. That visible record is the part most multi-context systems miss.
For a closer look, the home page walks through how the pieces fit together.
Read next:
(No extra footnotes for this article; the argument is built from common solo-worker practice and the structure of the freelance research surfaced in our supporting sources.)
A calmer way to make progress
Oasa is a calm productivity app for focused work. Plant Oases, tend one Seed at a time, watch your Zen Garden grow. Free. Made in Switzerland.
