Plan every client project
when you are the whole studio.

The smallest thing that answers your daily question. Trello suits cards moving through columns, Notion suits structured, repeatable work, and Asana suits bringing in collaborators who need assignments. Storyflow fits when the work is visual and the plan keeps drifting away from it: the brief, references, drafts and deliverables sit on one canvas, and a client opens it without an account. Avoid any system you will abandon in your first busy week.

Make the agreed deliverables visible to the client instead of burying them in a contract. Scope creep is rarely one large request; it is small ones that each feel easier to absorb than to price. When the deliverables list sits on a board the client can see, an extra request becomes a visible addition to a countable list. Also agree the number of revision rounds at the start, with further rounds priced separately.

Fewer than the calendar suggests, because the limit is collisions between the intensive phases of two projects rather than total hours. Discovery and the final push take most of the attention, and the middle is often waiting. Three or four projects can work when those stretches are staggered and hurt when two land in the same week. Before saying yes to the next job, put every project's demanding stretch on one picture.

Get seven answers before you start designing: the client's goal, the exact deliverables, the deadline, the budget, the decision maker, what the client owes you and when, and what success looks like. The decision maker and the client's dependencies are the two most often skipped. An unnamed decision maker produces contradictory feedback later, and unnamed dependencies such as assets, copy or access are where solo projects most often stall.

Set three rules at the start. One consolidated list per round, because contradictory notes from several people are the most expensive feedback. One named decision maker, so the client side settles disagreements before they reach you. And a dated deadline for their response on the project board, because late feedback moves your delivery date. In Storyflow a client who signs in can comment on the specific piece, so nothing has to be matched up from an email.

Storyflow is paid-only during early access, with plans from $7.99 a month billed annually ($9.99 monthly). A free plan launches before the end of 2026, and anyone a paid member invites to a board joins free, so a subcontractor adds nothing to the bill. Clients viewing a link never need an account. Until then, a free spreadsheet with a row per project and a column for what it is waiting on goes a long way.

A curated version, yes. A client who can see where things stand stops asking for updates and reacts to work in progress rather than only to finished files, which is where late change requests come from. Keep your working board private and share a separate view-only board with the brief, the agreed deliverables, the current state and what you are waiting on them for. That last section does more for your deadlines than a chase email.

An agency workflow is mostly coordination between people: assignment, status, capacity and handoffs. A solo workflow has none of those problems and two that agencies barely have. You switch between unrelated projects several times a day, so rebuilding a project's context is your largest hidden cost. And you are the only defence against scope creep and deadline collisions. The useful system is built around visibility and fast context recovery, not coordination.

Put it on the board as part of delivery, not as something that happens afterwards. Six items cover most creative work: final files exported, source files stored where you will find them, client approval confirmed in writing, invoice sent, portfolio permission asked, and the project archived. None is urgent on the day, which is why they slip by a month. Ask for portfolio permission in the week you deliver, while the client is happy.

Yes, as the colleague you do not have. Describe a project and Storyflow's AI lays out the usual phases, including the handover or second review round nobody reminded you about. It reads the whole board, so you can ask what has no next action or what is waiting on a client. It also drafts the chase for overdue feedback and the out-of-scope note. What to charge and what to take on stay with you.

Spend ten minutes after each project answering four questions where you will see them next time: what slowed you down, what you underestimated, what should become a template, and whether the project made money. The last is the one most freelancers avoid and the one that changes behaviour. The template question compounds: duplicate a finished project board and it carries your real way of working into the next job.