I run Mindful Yen from a desk in the corner of a small Tokyo apartment, between the window and the bookshelf where my grandmother's ledgers are kept. There is one laptop, one notebook, one cup of tea that has usually gone cold by the time I notice. There is no team. There is no project manager. There is, instead, a Notion workspace with four databases and a handful of pages, and that workspace is the closest thing to a colleague I have.
This essay is about that setup. Not as a template to copy in full — your one-person studio will not look like mine — but as a thinking tool. After three years of running a publication, an Etsy shop, a Substack, and the slow domestic rhythm of kakeibo all out of the same Notion workspace, I have a fairly clear sense of what is essential and what is decoration. The setup below is what remains after the decoration was archived.
If you would prefer to skip ahead and look at the workspace itself, you can try the Notion workspace I use here →. The walkthrough below explains why each database exists.
The premise: a one-person studio is not a small company
Most Notion advice for creators is, in practice, advice for small companies translated downward. Editorial calendars meant for teams of five. Asset libraries meant for marketing departments. Sprint boards meant for software developers. When a single person tries to run that machinery alone, the result is the same as one person trying to run a small restaurant alone — exhausting, and most of the work is administrative.
A solo creator's workspace has to be designed around a different premise: that the operator is also the writer, the photographer, the bookkeeper, the customer service desk, and the person who occasionally has to lie down. The four databases below are chosen because each one removes a category of administrative work, not because each one tracks a category of activity. That distinction matters. If a database makes you do more work to feel organised, it is the wrong database.
The same logic underlies kakeibo, which I have written about extensively — most recently in the kakeibo Notion template essay. Kakeibo is not a budgeting system. It is an attention-shaping ritual that happens to use numbers. The workspace below is the same idea, scaled up to a creative practice. It is an attention-shaping ritual that happens to use databases.
1. The editorial calendar
One database. Each row is a piece of writing, in any state — idea, drafted, edited, scheduled, published. The fields are spare: title, status, publish date (only filled in once it has one), where it lives (Mindful Yen, Substack, somewhere else), and a long-text field for the one-sentence pitch that will eventually become the meta description.
The calendar view is the one I open most mornings. It shows the next eight weeks. Anything past eight weeks is, frankly, fictional, and pretending otherwise is one of the most reliable ways to make a solo studio feel chaotic. I learned this the hard way during my first year, when I had a Notion view that showed the next six months and I spent more time rearranging it than writing.
The editorial calendar is also where the workspace's only real automation lives — a simple linked view on the home page that shows "next three pieces" and nothing else. That view is the home page's only piece of dynamic content. The rest is static. The reason is that a one-person studio does not need a dashboard; it needs a quiet desk with the next three things on it.
What the editorial calendar deliberately does not track
It does not track word count, reading time, or analytics. It does not track when something was tweeted or how it performed. Those numbers exist elsewhere, in the platforms that produced them, and pulling them into Notion turned out to be a way of giving the numbers more weight than they deserved. The calendar is for what I am working on now. Performance is for the monthly reflection, where it can be considered slowly.
2. The reader inbox
This is the database I am most attached to. Every email from a reader, every Substack reply, every Etsy review that contains an actual question — they all get logged here. The fields are minimal: date, name (or initials, if the reader prefers), question or comment (long text, paraphrased), and responded (a checkbox).
The reason this database matters is not that I forget to reply to readers — I do not — but that the patterns in reader letters are the single best signal of what to write next. Three readers asking variations of the same question in a month is, almost without exception, a future essay. The "letters from readers" sections that occasionally appear in Mindful Yen pieces come directly from this database. They are the publication's quiet research department, run by the readers themselves.
I would suggest any solo creator with even a modest audience start a database like this on day one. It takes thirty seconds per letter. By month six, it will be the most valuable database in your workspace, ahead of the editorial calendar.
3. The asset library
One database, three fields: file, type (photograph, scan, illustration, audio note, recipe, anything else), and where it might belong. The "where it might belong" field is a long-text note, not a select — because most assets do not belong cleanly in one essay, and forcing the categorisation up front makes the field useless.
Photographs of the kitchen table, scans from my grandmother's ledger, audio notes from cafés, illustrations I have commissioned and not yet used — they all live here. When I am drafting an essay and I think there was a photograph of the shiso last spring, I open this database and search "shiso." If I had filed it under the essay it eventually appeared in, I would not be able to find it later when I want to use it again.
The asset library replaced about four separate folders on my laptop and one folder in iCloud, all of which had drifted into a state of polite neglect. Notion is not technically the best tool for managing media — its file uploads are clunky and the storage limits matter at scale — but for a one-person studio at modest scale, the unification is worth more than the technical perfection.
4. The monthly reflection
I have written about this in the slow-living templates essay, but it bears repeating in the solo-creator context. One database, one row per month, four long-text fields: what I made, what I let go of, what surprised me, and what I want less of next month.
For a solo creator, the monthly reflection does the job that a manager would do in a small company — it is the moment when someone looks at the work of the past month and asks honest questions about it. Without it, a one-person studio drifts. The drift is hard to feel from inside the week, because every week looks busy. It only becomes legible at the month boundary, in writing.
I do this on the first Sunday of each new month, on paper first and then in Notion. The transcription is part of the practice. The act of typing what I had handwritten gives me a second pass at every sentence, and I have caught more useful things in the second pass than in the first. The same trick applies to the four kakeibo questions, which I do at the same sitting.
5. The financial ledger (kakeibo)
The fifth database, which I almost left off this list because I have written about it elsewhere, is the kakeibo ledger itself. For a solo creator, kakeibo is not optional. The ledger is the only place where the studio's finances become visible in a form that you can think with — invoices in, expenses out, what the month actually cost to run, what it actually earned.
I keep two parallel kakeibo ledgers, one personal and one for the studio. They share a structure but live in separate Notion pages, because mixing them produces a particular kind of confusion that takes weeks to untangle. If you are running a solo studio at all, separate the ledgers from day one. If you have already mixed them, the starter guide has the cleanest method for splitting them I have found.
The shape of the home page
The home page of the workspace is almost embarrassingly plain. At the top: a single sentence that names what the studio is currently focused on, rewritten roughly once a quarter. Below that: the linked view of "next three pieces" from the editorial calendar. Below that: links to the four databases above and to the kakeibo ledger. That is the entire home page.
I have tried, more than once, to build a more impressive home page. Dashboards with progress bars, gallery views with cover images, embedded calendars from external services. They were all eventually removed. The dashboard that looked most impressive was also the one I opened least, because it made me feel observed rather than helped. A one-person studio does not need to be observed. It needs the next three things on a clear surface.
What runs outside Notion (and why)
For honesty, a brief note on what does not live in Notion. Email lives in Substack and in regular email — I have not found a way to mirror them into Notion that does not produce more work than it saves. Photographs at full resolution live on a small external drive, with thumbnails in the asset library. Long-form drafts above about 3,000 words I write in iA Writer first and paste into Notion only at the editing stage, because Notion's editor still becomes slightly sluggish in very long documents. Invoicing happens in a separate tool, with totals copied monthly into the kakeibo ledger.
None of these are Notion's failures, exactly. They are simply places where another tool is better and the cost of unifying is higher than the cost of switching. A solo creator's workspace should never be precious about staying in one tool. It should be precious about not running the same thing in two tools at once.
How long it took to get here
This setup is the result of three years of subtraction. The first year I had eleven databases, three dashboards, and a tagging system I am still slightly embarrassed about. The second year I removed about half of it. The third year I removed about half of what was left, and the workspace has been roughly stable since.
If you are starting a one-person studio in Notion now, I would skip the first two years if you can. Start with the editorial calendar and the reader inbox. Add the monthly reflection in the second month. Add the asset library when you have enough assets to lose one. Add the kakeibo ledger when the studio earns or spends its first thousand yen. That is the entire build sequence, and it will get you, in three months, to roughly where I am after three years.
If you want the workspace I actually use, you can download it here →. It is on Notion's free plan, and the only reason I would ever recommend upgrading is if you are sharing it with a collaborator. For a true solo studio, the free plan is enough indefinitely.
One closing thought, from the desk
The reason I keep this workspace small is the same reason my grandmother kept her ledger small. A small notebook is one you actually open. A large one becomes a project in itself, and the project starts to compete with the work the notebook was supposed to support. Notion makes large workspaces easy and small ones slightly harder, because the empty space looks like a void to be filled. Resist filling it. The void is where the writing happens.
If you find this useful, I write more about the daily texture of running a solo studio in the Mindful Yen Substack, and the printable kakeibo journal in my Etsy shop is the paper companion to the digital ledger described above. Either is a fine place to continue.