While an agency has one or two projects, you can hold the finances in your head. But the moment you've got five, ten, each at its own stage with different payments and contractors, your head stops keeping up. The money blends into a single flow, and there's no answer to a simple question: "how much did this particular project actually earn?" And without that, you don't know what to scale and what to wind down.
Running several projects at once without getting lost isn't about a phenomenal memory — it's about a system. Let's break down how to build one so you can see each project on its own, even when there are dozens.
Why several projects break everything
The problem isn't the number — it's that every project lives in one shared "pot." A payment from client A, an advance from client B, salaries for a team working on three projects at once, a payment to a contractor who handles two of them — it all pours into one common flow. In the end there's some amount sitting in the account, but who owns what is anyone's guess. A profitable project masks a losing one, and you never see it.
There's only one fix: split the flow by project right at the entry point. It's the same principle as a P&L by client — just at the project level. You can even check a single project's profitability in 15 minutes, as in the article Which project is actually profitable.
Step 1. Every project is its own entity
Set up each project as a separate "container" that all of its money attaches to. It doesn't matter what your tool calls it — project, tag, line of business — what matters is that every transaction carries a project label. No project without a label, no transaction without an attachment. That's the basic rule everything else rests on.
Step 2. Tag every transaction on the spot
The main mistake is putting the sorting off "for later." A week on, you no longer remember what that payment was for or which project it belonged to. So the label goes on at the moment of the transaction: a payment comes in — you assign the project right away; you pay a contractor — you note which project right away. That's 10 seconds in the moment versus hours of untangling at month-end.
Step 3. Allocate shared costs by a rule
Some costs don't belong to a single project: the salary of someone working across several, rent, management. These need to be allocated by a simple, consistent rule — by hours on each project or in proportion to revenue. What matters isn't precision to the last kopeck, but that the rule is the same for every project. There's more on splitting shared costs in the article Margin by direction, location and channel.
Step 4. See your projects in one place
Once the transactions are sorted, you need a single screen that shows every project and each one's result: how much came in, how much went out, how much is left. It's exactly this consolidated view that saves you from the confusion: instead of "there's something in the account," you see "project A +80k, project B −15k, project C in progress." Now decisions are made project by project.
Example: five projects in one flow, and apart
An agency runs 5 projects. At month-end there's +120 thousand in the account — the owner is relaxed. But broken down by project: A +90, B +70, C +40, D −30, E −50. Two projects (D and E) ate 80 thousand of the others' profit, and without them the month would have been +200, not +120. With no project-level breakdown these two "money-eaters" would have stayed invisible; with one, the decision writes itself: deal with D and E (raise the price, change the scope, or close them).
Where to start
Take your current projects, set each one up separately, and for a month tag every transaction to a project the moment it happens. Within a month you'll see each project's result for the first time, instead of one "overall plus." When the money moving between projects gets to be too much to hold in your head, that's a signal it's time for systems — there's an article on that: When there's too much money between projects to keep in your head.
In Finmap every transaction is tied to a project, and the result of all your projects shows up on one screen — with no manual spreadsheet consolidation. Try it free for 7 days.
Frequently asked questions
Separately — all the ones that noticeably affect the money. Small one-offs can be merged into a single "pool," but big, long-running projects are always kept separate, otherwise their result dissolves.
At the moment of the transaction, without delay. After a few days the details fade and the sorting turns into guesswork. 10 seconds up front saves hours at month-end.
Allocate them by a consistent rule — by the team's hours on each project or in proportion to revenue. Precision to the last kopeck isn't needed; what matters is a uniform rule.
Up to a point — yes. But at 10+ projects the spreadsheets break, and you end up assembling the summary by hand. At that point it's cheaper to move to a service where the project-level breakdown is calculated for you.
