Why consultants outgrow Notion — and what comes next.

Notion is, by some distance, the best general-purpose workspace that has ever been built. For most knowledge workers, picking Notion is the right call. For consultants, it works beautifully for about eighteen months — and then quietly stops scaling. This post is about why that happens, why it's structural rather than fixable, and what a workspace built specifically for consulting work looks like instead.

The honest case for Notion

Notion's success is not an accident. It is the result of a small set of design decisions that genuinely advanced the state of work software, and any tool that wants to compete with it has to take those decisions seriously rather than dismiss them.

The first decision is that documents and databases are the same kind of object. Anything can be a page, and any page can be a database, and any row in a database can itself be a page with arbitrary nested content. This sounds technical, but the practical effect is that the cost of structuring information in Notion is much lower than in almost any other tool. A consultant who wants to track a list of clients can spin up a database in two minutes. The same consultant in Google Docs would be writing a document; in Excel they would be staring at a grid of cells with no obvious way to attach context to each row. Notion removes that friction.

The second decision is that the design is calm. Notion looks like a writing tool, not a project management tool. There are no progress dashboards screaming for attention, no Gantt charts cluttering the sidebar, no "11 overdue!" badges raising the cortisol level of every login. For knowledge workers who do their best thinking in long-form prose, this matters. Notion respects the medium.

The third decision is composability. A Notion workspace is whatever its owner builds. There are no opinionated workflows imposed from above, no project templates that have to be wrestled into shape, no required fields the user has to leave blank just to advance a card. Consultants in particular love this, because consulting work refuses to fit anyone else's mental model. Notion lets the consultant impose their own.

For these reasons, Notion is genuinely better than the tools it replaced. It is better than spreadsheets, because spreadsheets cannot hold prose. It is better than long Google Docs, because Docs cannot query themselves. It is better than rigid project tools like Asana or Jira, because those tools force the work to look the way they expect rather than the way it actually is. For a consultant moving away from scattered files and unhappy with the heaviness of traditional PM software, Notion is the obvious answer. It should be.

Why consultants pick Notion in the first place

Most consultants discover Notion the same way. They open it on a whim, build a "Clients" database in an afternoon, add a few columns — status, point of contact, last touchpoint, notes — and feel, for the first time in their working life, that the tool is on their side. They expand it the next week to track projects per client. The week after that, they add a meetings database that links to clients. By the end of the first month, they have a small empire of interlinked pages and the sense that they have finally solved the consulting-tool problem.

For a while, they have. The first eighteen months in Notion are usually the best stretch of organisation a consultant has ever had. The trouble is what happens after that.

The ceiling consultants hit

Somewhere between months twelve and twenty-four, three quiet failures start compounding. None of them is dramatic. None of them shows up in a Notion review. But together they explain why almost every consultant who has used Notion seriously for two years has a private feeling that something is wrong.

The "linked" pages are not actually connected.

When a Notion user links a meeting page to a client page, what is created is a reference — a link, in the literal hyperlink sense. The meeting page knows about the client page. The client page does not, on its own, know about the meeting. To make the client page "know" about meetings, the user has to manually add a related-database view, configure the filter, decide what columns to show, and remember to maintain that view as the schema evolves.

Multiply this across accounts, projects, people, action items, and notes, and the consultant ends up running a small information architecture project on the side of their actual job. The connections between the things they care about are not modelled by Notion — they are reconstructed, page by page, by the user, every time they want to see them.

The template-maintenance tax.

Notion's flexibility is its strength and the source of its ongoing cost. Every consultant who uses Notion at scale builds templates: a project page template, a client page template, a 1-1 template, a weekly review template. Those templates work beautifully on day one and decay steadily from there. A field gets renamed. A view gets edited inconsistently across pages. A new field is added to the master and the older pages don't backfill. Six months in, the templates are subtly out of sync with each other and the user's confidence in their own system erodes.

Fixing this is not a single afternoon's work. It is an ongoing tax that the user pays in exchange for the privilege of having a flexible workspace. Most consultants pay it until they don't, and then the system quietly falls apart.

The 1-1 and account-history problem.

The single hardest thing for a Notion-based workflow to handle is the one most central to consulting work: keeping track of who has asked for what, across which accounts, over time. A consultant talks to dozens of people across multiple engagements. Each conversation produces commitments. Those commitments belong simultaneously to the person who asked, the account they came from, the project they affect, and the day they need to be acted on.

In Notion, that single commitment becomes either a duplicated entry across four databases, or a single entry in one database that the other three have to query into. Either way, the connections are fragile and the consultant has to remember the system to navigate it. Six months later, they don't.

The deepest problem with Notion for consulting work is not that anything is broken. It is that the model — pages and databases linked by references — does not match the shape of the work, which is accounts and projects and people connected by commitments.

What "outgrowing Notion" actually means

Outgrowing Notion is not the consultant's fault, and it is not Notion's fault either. Notion was built to be a general-purpose workspace. It does that brilliantly. Consulting work, however, is not general-purpose. It has a specific shape — accounts contain projects, projects contain tasks, tasks have owners and deadlines, people accumulate action items across meetings, time is finite, and progress on any of these things should be visible without re-aggregating it by hand every Monday.

A workspace that matches that shape will, structurally, beat a workspace that has to be assembled to approximate it. That is the bet behind Callisto.

How Callisto is structurally different

Callisto is not "Notion with project management bolted on", and it is not a heavier Asana-style tool either. It is a workspace built around the observation that consulting work is fundamentally a graph of connected objects, and that the connections should be modelled by the application rather than reconstructed by the user.

In Callisto, an account is not a page. It is a first-class object that contains projects, people, notes, and a stream of activity, all natively. A project is not a database row. It is an object that knows which account it belongs to, which people are involved, which tasks remain, and what its current progress is — without anyone having to maintain a roll-up formula. A person is not a profile to be queried; it is the home of every action item that has ever come up in conversation with them, automatically available the next time their name appears on the calendar.

The user does not assemble these connections. They are the data model.

Connected objects, not linked pages

The clearest demonstration of the difference happens on the Time tab. A consultant adds today's priorities by picking from work that already exists elsewhere — a task from a project, an action item from a 1-1, an ad-hoc request from a colleague. Nothing is retyped. Nothing is duplicated.

When that priority is marked complete on the timeline, Callisto updates the underlying object wherever it lives. The project's progress bar moves. The action item disappears from the relevant person's profile. The ad-hoc request is closed across the app. The consultant did the work once. The bookkeeping happens by itself.

In Notion, that same workflow requires either four manual updates across four databases, or an elaborate relation-and-rollup setup that the user is responsible for maintaining as their schema evolves. In Callisto, it is not a workflow — it is the consequence of the data model. There is nothing to maintain because there is no duplication to keep in sync.

Accounts, projects, and people on one graph

The second structural advantage is that every surface in Callisto is a view onto the same underlying graph. The Accounts tab shows everything Callisto knows about a client — the projects underway, the people involved, the action items still open, the meetings logged, the notes accumulated over time. None of this is queried into; all of it is native. Opening a client account before a call surfaces months of context without anyone having to remember which database to pull from.

The People tab is the same idea applied to relationships. Every action item ever captured against a person sits there, ready to be pulled into a 1-1 agenda or onto today's timeline. The next 1-1 starts with the prior commitments already on the screen. This is the single most career-relevant feature Callisto offers a consultant, and it exists because the underlying objects are connected by design.

The Projects tab, the Time tab, the Memo tab, the Planner — they are not separate features. They are different perspectives on the same connected data. Notion can be coaxed into approximating this with enough effort. Callisto begins there.

Where Callisto is strictly better than Notion for consulting work

Stated plainly:

Callisto eliminates the maintenance tax. There are no templates to keep in sync, no databases to migrate when a column is renamed, no rollup formulas to debug. The structure is fixed in the right places and flexible in the right places, and the user is freed from the ongoing cost of maintaining their own information architecture.

Callisto models the work, not the document. An account is an account. A project is a project. A 1-1 commitment is a 1-1 commitment. None of these are stand-ins for something else. None of them require the user to invent a schema that approximates them.

Callisto keeps the consultant's mental load low. The cognitive cost of using Callisto does not grow with the number of clients, projects, or people. In Notion, that cost scales linearly — and eventually superlinearly — with the workspace size. Callisto's load stays roughly constant because the connections are computed, not authored.

Callisto closes loops by itself. The single biggest source of professional embarrassment for a consultant — losing track of what was promised and to whom — is structurally prevented, because the commitment exists in only one place and that place is connected to everywhere it needs to show up.

Notion is a more powerful tool in the abstract. Callisto is a more capable tool for the specific work consultants actually do. For everything else, Notion remains an excellent choice. For consulting and services, Callisto is the answer.

When to make the move

The honest signal that a consultant has outgrown Notion is not dissatisfaction. It is the moment they realise they are spending more time keeping their workspace coherent than they are spending on the work the workspace is supposed to support. The templates feel like a part-time job. The roll-ups stop updating. The 1-1 prep, which was once a quick five-minute glance, has become a fifteen-minute archaeological dig through three databases. The system that once felt empowering is starting to feel like another stakeholder.

When that moment arrives, the answer is not a heavier project tool — Asana and Jira do not solve the connection problem, they just impose more structure on top of it. The answer is a workspace that was designed from the start around the connected nature of consulting work.

Getting started

The recommended first week with Callisto is small. Add one or two real accounts. Add the projects under them. Drop the next 1-1 into the People tab with two action items attached. Put today's priorities on the Time tab by pulling from the work that already exists. By the end of the week, the connections will have shown their value — items close themselves across the app, progress updates without effort, and 1-1s start themselves with prior context on the screen.

For consultants who have spent two years building Notion workspaces that have started to feel heavier than the work itself, that experience tends to be the moment the decision becomes obvious.