The first invoice I ever sent as a freelance writer, in the spring of my twenty-eighth year, took me four hours to write. Not because the invoice was complicated — it was three lines on a single sheet of A4 — but because I had no system, and so each decision was being made from scratch. What rate. What payment terms. What I had actually agreed to deliver. Where I had written that down. Whether I had written it down at all. By the time the PDF was attached to the email, the morning was gone, and the work itself had not begun.
The Notion setup I am about to describe is, in essence, the apology I owe to that morning. It exists to prevent any future decision being made from scratch. Each database below removes a category of administrative reinvention — pitches, drafts, invoices, follow-ups — and what is left, when those four are working, is the actual writing. That is the whole purpose of a freelance writer's workspace, and most of the elaborate Notion templates marketed to freelancers, in my honest experience, have lost sight of it.
If you would like to see the workspace I keep, the link is here: try the Notion workspace I use →. The walkthrough below explains why each piece exists.
The premise: writers do not need project management
Most Notion templates for freelancers are built around the assumption that the freelancer is, essentially, a small agency — handling multiple concurrent clients, balancing capacity, tracking dependencies. For some freelancers this is genuinely true. For most freelance writers, it is not. We typically have between one and five active commissions at any given time, with linear workflows (pitch → accepted → draft → edit → publish → invoice → paid), and the bottleneck is almost never coordination. It is attention.
A workspace designed for an agency model, used by a single writer, produces a particular kind of fatigue. The kanban boards become theatre. The capacity planning becomes a daily ritual that produces no decisions. The status fields multiply until updating them is itself a part-time job. None of this writes the next paragraph.
The setup below is built on the opposite premise: that a freelance writer's workspace should be small, almost embarrassingly so, and should privilege the visibility of what is actually due over the visibility of what is theoretically possible. It is the same logic underlying kakeibo, which I have written about in the kakeibo Notion template essay — that attention, not data, is what changes behaviour. Four databases. One home page. That is the entire workspace.
1. The pitches database
One database, one row per pitch. Fields: publication, editor (name and email, if known), date sent, headline of the pitch, status (sent, replied, accepted, declined, ghosted), follow-up date, and a long-text field with the full pitch text.
The pitches database is the single most undervalued database in a freelance writer's workspace, and the one I would build first. The reason is not that it tracks where pitches go — though it does — but that the long-text field, over time, becomes a personal archive of every pitch you have ever written. Three years in, mine contains roughly four hundred pitches, and I draft new pitches almost entirely by searching for old ones. The good ones are reused, lightly adapted, against new publications. The bad ones are studied, reluctantly, for the patterns that explain why they failed.
The follow-up date field is what stops pitches from quietly disappearing into editors' inboxes. The convention I use is two weeks for first follow-up, three weeks after that for second follow-up, and at that point the pitch is moved to "ghosted" and reused elsewhere. This cadence is generous; many writers use shorter ones. The point is not the specific timing but that the timing exists in writing rather than in memory.
The view that matters most
The view I open every morning is "follow-ups due this week," filtered to status = sent or replied, with follow-up date in the next seven days. There are usually between one and four entries. They take fifteen minutes total to handle. Without this view, follow-ups simply do not happen, and unfollowed pitches are, in my experience, the single biggest source of lost income for freelance writers.
2. The drafts database
One database, one row per commissioned piece. Fields: title, publication, editor, commission date, deadline, fee, word count, status (drafting, edit one, edit two, with editor, awaiting publication, published), and the long-text field for the draft itself.
I want to be honest about a small heresy: I do not actually write drafts inside Notion. Long-form writing in Notion above about 3,000 words becomes, for me, slightly sluggish, and the lack of a true distraction-free mode means that the temptation to fiddle with the page rather than write the next paragraph is constant. I write drafts in iA Writer, in plain Markdown, and paste the finished draft into Notion at the editing stage. The long-text field on the database is, in practice, the archive of finished drafts rather than the drafting environment.
This is, I think, the correct way to use Notion as a writer. The database is the record. The drafting tool is whatever produces the most writing per hour. Trying to make Notion be both has cost me more days than I would like to admit.
The deadline field is what makes the drafts database non-optional. The view I open daily is "drafts due in the next fourteen days, sorted by deadline ascending." That view, opened with morning coffee, is the single most useful piece of project management in my freelance practice. It replaces about six other things I used to maintain.
3. The invoices database
One database, one row per invoice. Fields: invoice number (an auto-incrementing formula), client, date sent, amount, currency, due date, status (sent, paid, overdue, disputed), date paid, and a link to the corresponding draft.
The invoices database is, mathematically, the simplest database in the workspace. It is also the one that took me the longest to take seriously. For my first two years freelancing I tracked invoices in a separate spreadsheet, then in a dedicated invoicing app, then briefly back in the spreadsheet. None of these worked, for the same reason: an invoice tracker that is not in the same workspace as the writing it bills is one extra place to remember to look.
Moving invoices into Notion solved this almost immediately. The "overdue" view, filtered to status = sent and due date in the past, is the second view I open every morning, after the follow-ups view. There are usually zero entries. When there are not, the situation is dealt with the same morning, in the same workspace, with the matching draft and editor email two clicks away. The friction of chasing payment dropped to roughly nothing, and chasing-payment income — which most freelancers under-collect on out of awkwardness — increased noticeably in the first quarter after the switch.
I do not generate the actual invoice PDF in Notion. That happens in a separate tool, and the PDF is attached to the database row for archive. Notion is the ledger; another tool is the printer. This separation has been stable for two years and I see no reason to change it.
The monthly totals from the invoices database feed directly into the studio kakeibo ledger I described in the solo creator setup. That cross-reference — invoiced this month, received this month, outstanding at month-end — is the single financial number a freelance writer most needs, and the one most writers I know cannot answer in under thirty seconds. The Notion setup answers it instantly.
4. The follow-up cadence
This is not a separate database. It is a single dashboard view that combines two filters: pitches with follow-up date in the next seven days, and invoices that are sent and overdue. That dashboard is the home page's only piece of dynamic content, and it is the first thing I see when I open Notion in the morning.
The follow-up cadence is, in my honest assessment, the single most lucrative thirty-second daily ritual I have ever built. Most lost freelance income is not lost to bad writing or bad pitches. It is lost to good pitches that were never followed up on and good invoices that were never chased. A workspace that surfaces both, automatically, removes the need for the writer to remember to be assertive. The view is assertive on the writer's behalf.
What about all-in-one tools?
I am asked occasionally whether Notion is really the right tool for this, given that there are platforms — Systeme.io is one of the cleaner ones for solo creators — that bundle invoicing, contact management, and a website into a single subscription. The honest answer is that the all-in-one tools are excellent for solo creators whose primary product is a course, a membership, or a digital download. For freelance writers, whose primary product is the writing itself and whose clients are publications rather than direct customers, the all-in-one tools solve problems we do not really have.
What freelance writers need is a quiet ledger of pitches, drafts, invoices, and follow-ups. Notion does this in four small databases on the free plan. The cost of an all-in-one tool, both financial and attentional, is hard to justify for a workflow this simple. I would only revisit the question if a freelance practice were expanding into selling products direct to readers — at that point, the calculation changes.
What deliberately does not live in this workspace
For balance, what I have tried and removed.
A time-tracking database. I tried this for six months. The data was honest and unhelpful. Knowing that an essay took fourteen hours to write rather than ten did not change how I priced the next one, because the next one was a different essay. I now estimate fees by category and trust the average over the year.
A CRM-style contacts database. The pitches database already contains every editor I have ever worked with. A separate contacts database duplicated the information without adding anything. It was archived after four months.
A "publications I want to write for" wishlist. This database grew faster than I could ever pitch, became a guilt object, and was archived. The honest replacement is: when I think of a publication I want to write for, I draft the pitch immediately, in the pitches database, with status = draft. If I do not draft it, the wish was not real.
An analytics dashboard. Pageviews, social shares, replies. None of this changed what I wrote next, and looking at it daily produced a small unpleasant feeling that took most of an hour to dissipate. The monthly reflection, which I described in the slow-living templates essay, surfaces what actually matters about performance once a month, in writing, which is the right cadence.
The financial half: kakeibo for freelancers
The four databases above are the operational workspace. The kakeibo ledger I run alongside them is the financial workspace, and for freelance writers I would argue it is non-optional. Freelance income is irregular, freelance expenses are deductible in ways most writers under-claim, and the gap between "feeling solvent" and "actually solvent" can yawn open dangerously without monthly attention.
The kakeibo template I use is the one described in the kakeibo Notion template essay, with one modification for freelancers: the four traditional categories are joined by a fifth, studio, for any expense that is professionally deductible. The monthly reflection asks one additional question — what was the gap this month between invoiced and received, and is the trend getting worse? That single question has, more than once, told me to stop pitching new work and start chasing old payments.
A note on writing the invoices themselves
Since the first-invoice morning that prompted this whole essay: the trick I wish someone had told me earlier is that an invoice template, written once and stored in the invoices database as a sub-page on a "template" row, takes about ten minutes to build and saves several hours per year forever. Mine has fields for client, project, fee, payment terms (thirty days from receipt), bank details for both yen and foreign-currency payments, and a single-sentence "thank you" that has not changed in two years. Generating an invoice now takes about ninety seconds.
If you would like the workspace I keep — pitches, drafts, invoices, follow-ups, kakeibo — you can try the Notion template I use here →. The structure is built for one freelance writer running on the free plan, which is what most of us are. I write occasional follow-ups about freelance practice in the Mindful Yen Substack, and the paper kakeibo journal in my Etsy shop is the analogue companion for the financial half.
One closing thought, from the desk
The freelance life is, on a good week, the most independent work I can imagine. On a bad week, it is the loneliest. The workspace described above does not solve the loneliness. What it does is remove the second-order anxiety — the constant low hum of have I followed up, has the invoice gone in, when is the next deadline — that, for me, used to make the loneliness feel sharper than it needed to. With those four small databases doing their quiet work in the background, what is left is the writing and the reader and the slow building of a practice. That is what I came to freelance writing for. The workspace exists to clear space for it.