Running our 15-person studio, we spent the best part of two years trying to make Notion the operating system of the business. We bought the templates. We hired a consultant. We built our own. Each version held together for about a quarter before something cracked, and a partner spent another weekend rebuilding the workspace from scratch.
We were not bad at Notion. We were trying to use a document tool to run a financial operation, and the architecture was never going to let us.
What Notion was actually built to do
Notion's design philosophy is documents and databases as the same primitive. A page is a database row. A database is a collection of pages. Everything you see is a flexible rendering of that same underlying model, which is what makes Notion so good at wikis, knowledge bases, meeting notes, product specs and lightweight CRM views.
Ivan Zhao and the early Notion team have been clear about this in interviews going back to 2018. The product was designed as "Lego blocks for software", a workspace where any team could compose the tools they needed out of pages, blocks and relations. It is a brilliant proposition for a knowledge layer. It is the wrong proposition for a financial operating layer.
The reason is that financial operations are not flexible. A billable hour is a specific number against a specific person against a specific project at a specific rate, and it has to flow into an invoice that has to flow into cash. None of that benefits from being modelled as a flexible block. It benefits from being modelled as a transaction.
What an agency economics problem actually looks like
The economics of an agency rest on three numbers that move every day. Billable rate multiplied by hours delivered gives you revenue. Revenue minus loaded cost gives you delivery margin. Hours burned against hours quoted gives you budget burn. The job of an operating system is to keep those three numbers visible, accurate and live.
A senior on $120 an hour delivering 28 billable hours in a week is $3,360 of theoretical revenue. If those 28 hours were budgeted as 22, the project is 27% over before anyone has looked at it. If 4 of those hours were logged against the wrong code, the realised revenue is $2,880, 14% short of what should have been invoiced. None of this is exotic. It is the daily arithmetic of every studio with timesheets and a budget.
The agency operating problem is not "where do we put this information". It is "how do we make sure the right numbers update in real time, against a contract, against a rate card, against an invoice, so the team and the owner see the gap on a Tuesday and not at month-end." That is a transactional problem with a financial spine. Notion does not have one.
Why the Notion "agency template" looks like a CRM and does not act like one
Most agency Notion workspaces include a "Clients" database, a "Projects" database, a "Tasks" database, a "Time" database and a "Proposals" database. They are wired together with relations. From a distance it looks indistinguishable from a purpose-built agency operating system. From the inside, it is five linked spreadsheets that do not know what each other mean.
The time database does not have a timer that updates the project's remaining budget. It has a number field that a person typed into a row. The proposal database does not have an e-signature workflow that closes a contract and triggers the project. It has a status column that someone changed by hand. The invoice database does not have a payment gateway that flips cash on receipt. It has a "Paid" checkbox that someone ticked when the bank statement came in.
Every one of those interactions is a manual operation pretending to be a transaction. When the manual operation does not happen, the database is silently wrong. When it happens late, the database is silently late. The owner looking at the dashboard at the end of the month sees a picture that was assembled by hand all month, and trusts it about as far as they should.
The 30-hour template build and the quarterly refactor
There is a pattern most agency owners on Notion will recognise. The initial build of a "proper" agency workspace takes around 30 hours, either as a partner's weekend project or as a paid template plus configuration. Reddit's r/Notion and r/agency threads are full of these builds, with consultants quoting £1,500 to £4,000 for the work, then rebuilding it every six to nine months as the agency changes.
The refactor cadence is real because the architecture cannot absorb operational change. A new pricing model, a retainer with overage, a discount for a long-standing client, a freelancer on a sub-contracted rate, none of these can be added without restructuring the underlying databases and the formulas that depend on them. The system is not extensible at the data layer; it is rebuildable at the page layer. Those are not the same thing.
The cost is rarely on a card. It is a partner working two weekends a quarter, a consultant invoice every nine months, and a team that has learned not to fully trust the numbers because they have seen the workspace break before. The Notion subscription itself, $10 per seat on Plus or $20 per seat on Business with Notion AI included, is the smallest line on this bill.
What teams should actually do
The fix is not to abandon Notion. Notion is excellent at what it was built for, and most agencies should keep it for exactly that work. Client wikis, project notes, internal SOPs, brief documents, retros, the company handbook, all of it belongs in Notion. Trying to take that off Notion is a different kind of mistake.
The fix is to consolidate the operational layer into a single financial spine and let Notion be the document layer next to it. The operational spine needs to know about billable hours, rates, budgets, margins, contracts, invoices and cash as connected transactions, not as linked database rows that someone updates by hand.
AgencyFlo is what we built when we worked out what that spine should look like for our own studio. Project budgets, time, proposals, contracts and invoices run on one data model, with FloAI in the loop instead of as a separate add-on. The pricing is flat: $50 a month for teams up to 25 people, $100 above. That sits next to a Notion workspace, not on top of it.
The simplest test of whether your current setup is in the right shape: open the system right now and try to answer "what is the live margin on our top five projects this week." If the answer requires opening more than one tool, or any spreadsheet, the spine is not in the right place yet.
Key takeaways
- Notion treats pages and databases as the same flexible building block.
- Agency money (hours, rates, budgets, invoices) needs fixed transactions, not flexible blocks.
- An agency Notion setup is really five linked spreadsheets updated by hand.
- When someone forgets to update a row, the numbers go quietly wrong.
- Keep Notion for notes and wikis. Run the money on a tool built for it.
Frequently asked questions
Can you actually run an agency on Notion?+
You can run the documentation layer of an agency on Notion very well: wikis, briefs, SOPs, retros, client notes. You cannot run the financial operating layer on it without significant manual maintenance, because Notion has no native concept of a billable hour, a rate card, a contract or an invoice transaction. Most agencies that "run on Notion" are actually running on Notion plus a timer, a proposals tool, an invoicing tool and a spreadsheet, with Notion as the front page.
What is missing from Notion for agency project management?+
Three things that are structural, not configurable. First, a timer that decrements a live budget and updates project margin as it ticks. Second, an e-signature flow that converts a proposal into a signed contract and a started project in one action. Third, an invoice send that records receivables and flips cash on payment. All three are transactions, not document edits, and Notion's architecture is built around document edits.
How much does the typical agency Notion build cost in time and money?+
Public consultant quotes for a serious agency Notion workspace sit between £1,500 and £4,000 for the initial build, with most internal builds clocking around 30 hours of partner or senior time. The hidden cost is the refactor cadence: most agencies rebuild the workspace meaningfully every six to nine months as pricing models, retainers and team structures change. The subscription itself at $10 to $20 per seat is the smallest line on the bill.
Should you keep Notion if you adopt an agency operating system?+
Yes, in almost every case. Notion is excellent for documents, wikis, SOPs and internal knowledge, which is what it was built for. The work is to move the financial spine (budgets, time, contracts, invoices, margin) into a system designed for transactions, and to let Notion be the document layer next to that spine rather than the place where the financial picture lives. Most studios end up with a much smaller, cleaner Notion workspace as a result.
Sources
- Notion pricing - Notion
- Notion founder Ivan Zhao on the "Lego blocks for software" philosophy - First Round Review
- The Social Economy: productivity through social technologies - McKinsey & Company
- r/agency: Notion build and refactor threads - Reddit
- Pulse of the Profession 2024: Project Success in Disruptive Times - Project Management Institute
