Architecture Bureau: Real Profit Per Project and Per Stage, Not Per Fee

«We run six projects at once, the pipeline is booked almost a year ahead, fees are ₴800,000, close to a million per site. Yet in July I had nothing to cover payroll and borrowed from a friend. Six projects — and a cash gap. I honestly couldn't work out how that happens», — says Andrii, founder of an architecture bureau of nine people.

Sound familiar? The phone keeps ringing, clients are queuing, the portfolio is full of headline sites you're proud to post on Instagram. And at the end of the quarter you look at the account — and can't work out where those millions in fees went. The first thought is always the same: «I need to take on more projects, raise the rate, hire another architect.» Yet the trouble is almost never the number of projects.

The trouble is that the bureau is counted as one big till. An advance comes in for one site — you close payroll across all six with it. A stage payment arrives from another — you cover rent and taxes. The money blends into one pot, and while it's all lumped together you can't see one simple thing: one project brings the bureau 40% net, while another has dragged you into the red for the third month running. Both look equally «important.» Both consume your team's time. But only one feeds you.

This article is about breaking the bureau down into separate projects and stages. So you can finally see which site actually feeds the team, and which merely creates the illusion of being busy and quietly eats your margin.

How Andrii Hit a Cash Gap With a Full Pipeline

Andrii opened the bureau after twelve years as an employed architect. First — alone with a laptop at the kitchen table, then two of them, then a rented open space and a team of nine: architects, a structural engineer, a visualiser, a project manager. The sites grew serious: private houses, restaurants, turnkey offices with author's supervision. Fees climbed from tens of thousands to hundreds.

But his grasp of the money didn't grow with the bureau. Andrii, like most architect-owners, kept the finances in his head and in three Excel files no one but him could read. He knew the total value of the year's contracts and roughly pictured the costs. But to the question «how much did you actually earn on the restaurant?» he had no honest answer. «Somewhere in the plus, I think» was the most precise thing he could say.

The illusion held while there were two or three projects. When there were six, and the team was nine people on fixed monthly salaries, it all fell apart. Money came in bursts — by advances and stages, while costs flowed evenly every day. And that gap between bursts of income and the steady stream of costs turned into that July «nothing to pay salaries with.»

How the Money in a Bureau Actually Works

A project, for an architecture bureau, is not «a fee minus a few costs.» It's a small business inside your business, with its own income, its own costs and, above all, its own timetable of when that money arrives and leaves.

Picture each project as a separate folder. It has income — the whole fee for the site, split into stages. And it has direct costs — what disappears specifically because of this project: your architects' hours, subcontractor pay (structural engineer, MEP engineers, cost estimator), 3D visualisations, printing, site trips during author's supervision. The difference between the fee and those costs is the project margin. What actually stayed with the bureau, not just what «passed through the account.»

The formula here is childishly simple, and that's exactly why you can trust it: fee minus direct costs = project margin. Direct costs are the team's salaries in hours spent on this very site, plus subcontracting and materials for it. Rent, the accountant, advertising — those are no longer about a single project, we allocate them separately. First learn to see the margin on each site, and half the fog clears.

Staged Payments vs the Day the Salaries Are Due

Here's where the main trap of a bureau hides. You receive the fee in stages: an advance at the start, a payment after the concept, a payment after the working documentation, the balance after author's supervision. Between those payments — weeks, sometimes months. But you pay the team salaries every month, regardless of whether an advance for some stage arrived this month.

In plain words: income comes in steps, while costs flow in a straight line. While there's one project, you feel that gap in your gut and somehow balance it. When there are six, all at different stages — one waiting for the concept payment, another bogged down in revisions, a third not yet started — guessing whether next month will cover salaries becomes impossible by eye. This is exactly where cash gaps are born with a full pipeline.

An advance in the account is not your money yet. It's money you still have to earn with the team, with rent that will keep being written off against it for the next three months.

An Advance Is Not Profit — It's a Debt Owed in Work

The client paid ₴300,000 as an advance for the start of a large project. There's a pleasant sum in the account at once, and the temptation is to treat it as earnings. But that advance is not profit. It's an obligation: ahead lie months of the team's work, subcontracting, visualisations, supervision. You'll pay all those costs out of this same advance — and often out of future payments for other sites. If you spend the advance as if it were already earned, sooner or later you land in Andrii's situation: the money came, the money went, and there's still half a year of work left.

A Worked Example: Four Projects, Four Different Stories

Let's take four of the bureau's sites that all look «profitable» at first glance — the fees are decent, after all. Let's count honestly: fee minus direct costs (team hours at their rates plus subcontracting and visualisations).

See the trick? The loudest site in the portfolio — the restaurant at ₴1.1 million — leaves the bureau less than the more modest ₴800,000 office. Because the revisions and the endless «let's look at another option once more» ate almost the whole margin. And the «favour» project at a discount was worked at an outright loss: the team spent more hours on it than the entire fee was worth. Formally the bureau is «busy with four sites.» In fact two of them feed you, one barely breathes, and one quietly drags you down.

Imagine Andrii spends the whole next year taking mostly such «restaurants» and «favour» projects, because they're loud and prestigious. The portfolio roars, the fees run into the millions, and the margin quietly limps toward zero. That's where the feeling comes from: «we work like crazy, and there's no money.»

Revisions and Scope Creep: How Margin Melts Unnoticed

The biggest quiet killer of an architecture bureau's margin is scope creep. It starts innocently: «show us one more façade option,» «let's move the kitchen,» «what if it's two storeys instead of one,» «my wife wants to redo the living room.» Each such change on its own feels like a trifle, and saying «no» feels awkward — the client is paying a million, after all.

But every revision is real hours of your team that you can no longer sell a second time. The fee is fixed in the contract, while the hours on the site keep growing. The margin melts not with one blow, but through a thousand small concessions. And since no one counts the hours per project, you notice the problem only when the site is already delivered and the bureau earned nothing on it.

This is cured by two things. The first — a clear contract: how many iterations are included in the fee and what costs extra. The second, without which the first doesn't work — tracking hours by project. When you see that the restaurant has already eaten 1.5 of its budgeted hours, the conversation with the client about paying for a new wave of revisions becomes not emotional but factual: «here's the scope in the contract, here's what we did beyond it.»

Every free «let's just try one more option» is not a goodwill gesture. It's an hour of work you just gave away, taken straight out of your own margin.

Life Before Finmap: How It Felt

Most often Andrii described his state with lines like these — you may recognise yourself too:

• «The pipeline's booked a year ahead, and in July I covered payroll out of my own pocket.»
• «I know the total value of the contracts, but I can't tell you how much I earned on a specific site.»
• «An advance comes in — all's well; a month later it's empty again, and it's unclear where the money for the next salary will come from.»
• «I've run the restaurant for half a year, it seems profitable because the fee is big. But I don't really know.»
• «My wife keeps the Excel in the evenings, and every new project is a new file no one can make sense of a month later.»

Behind each of these lines is the same thing: the bureau is counted with one general account, not as margin by project and a payment schedule by stage. The money is there — the understanding isn't.

How the Bureau Put Things in Order

The turning point came after that very July. Andrii sat down and did three things that changed how the bureau is run.

First — he connected the banks for auto-import. All incomings and outgoings began to pull in automatically, without retyping into Excel. That alone removed half the pain: the numbers stopped living in his head and in files kept «when there's time.»

Second — he set up each site as a separate project. Now every advance, every stage payment, every payout to a subcontractor was tagged with which project it belonged to. For the first time the margin on each site became visible on its own — and that's when it emerged that the restaurant was barely in the plus and the «favour» project was in the red.

Third — he built a payment calendar. All future stage incomings and all future costs — salaries, rent, taxes, subcontracting — were laid out on the calendar in advance. And the gap between bursts of income and the steady stream of costs finally became visible before it turned into a catastrophe.

Finances Now: What Changed

After a few months of working with projects and the calendar, the bureau's picture changed not cosmetically but in substance. Here's the main thing — before and after.

• Before: «the restaurant seems profitable.» After: the restaurant's margin is 11%, and that's a direct signal to revisit the contract on the number of iterations.
• Before: cash gaps arrived suddenly, mid-month. After: the payment calendar shows the coming gap three to four weeks out, and Andrii has time to shift a subcontractor payout or discuss an advance for the next stage.
• Before: an advance was perceived as profit and quickly «dissolved.» After: he sees how much work still stands behind each advance, so the money isn't spent ahead of time.
• Before: «we take every project on offer.» After: before the start Andrii estimates the margin and consciously turns down sites that drag him into the red, or re-prices them.

The main thing here is not a single number but the dynamics. When you see the margin by project not for one month but for a quarter running, things surface that you didn't notice before: a certain type of client always brings a wave of revisions, author's supervision is systematically underpriced in the fee, and «friendly» discounts cost the bureau more than the whole year's saving on rent.

How to See This in Finmap

All this maths works only when you see it every day — not once a quarter, gathering scattered Excel files together. Here's how it looks in Finmap.

• Bank integrations and auto-import. Stage incomings and subcontractor payouts pull in from the bank automatically. All you have to do is assign them to projects — that's seconds, not evenings with a calculator.
• Projects for per-site profitability. Each site is a separate project with its own income and direct costs. The margin on each calculates itself, and it's immediately clear who feeds the bureau and who drags it down.
• A payment calendar for advances and salaries. Future stage payments and future costs lie on the calendar in advance. A cash gap is visible weeks before it arrives.
• Cash Flow and P&L in plain language. Not accounting screeds «for the tax office,» but a picture an owner understands: where the money comes from, where it goes and how much actually stays.

If you want to start with something concrete, first look at how to work out in 15 minutes which project is actually profitable, and then get to grips with how to calculate project margin so you don't work at a loss. And when you want to clear the cash gaps between stages — here's how to build a payment calendar from scratch.

You Don't Need More Projects — You Need to See Each One

Money in an architecture bureau never disappears. It simply dissolves between sites, stages and revisions while you stare at one shared account. The moment you break it apart by project margin and lay the advances over the salary schedule, it becomes clear which site feeds the team and which merely creates motion and fatigue. And then the question «take this project or not» stops being a gamble.

Try looking at your bureau in a new way — 7 days free, no card required. Within a week you'll already see the margin on each site and the coming gaps on the calendar. Order in your finances begins the moment you finally see each project on its own. Start with Finmap.