A company does not need more pages. It needs its information connected.

01 — Workspace architecture

Departments first, pages second

Every implementation started with architecture. Dedicated teamspaces were created for each business function, so information is organised by department and responsibility rather than by whoever created the page.

• Management
• Sales
• Finance
• HR
• Operations
• Projects
• Reporting
• Documents

02 — Connected database architecture

Tables that talk to each other

This is the part that decides whether the workspace works. Instead of independent tables that never communicate, the databases are joined with Notion relations and rollups, so information flows between parts of the organisation:

• Employees
• Sales performance
• Daily reports
• Weekly reports
• Monthly reports
• Action items
• Projects and tasks
• Meetings
• HR processes
• Financial information
• Documents and templates
• Management reporting

Relations connect records across databases; rollups summarise the related information automatically. The same number never has to be typed twice.

03 — Executive dashboard

One page instead of eleven databases

A dedicated executive dashboard gives management a high-level view of company performance without opening anything underneath it. Depending on the business, it surfaces KPIs such as total calls, sales activities, pitches, contracts signed, sales volume, and conversion rates.

Every indicator can be compared against a previous period, so the question is not just "what is the number" but "is it getting better". Operational data becomes information management can act on immediately.

04 — Daily, weekly and monthly reporting

A reporting hierarchy, not a folder of documents

Rather than treating each report as an isolated file, reporting is structured across time periods that feed each other.

• Daily — operational performance and visibility into the working day
• Weekly — consolidated performance, trends, and team comparison
• Monthly — the broader view, tracking development over longer periods

Management can move from a single day's detail up to long-run business performance without maintaining three separate reporting systems.

05 — Sales and performance management

The same data, shaped for whoever is reading it

Individual salesperson activity is organised and compared on:

• Calls
• Pitches
• Documents sent
• Contracts
• Signed contracts
• Sales volume
• Conversion rates

A sales manager needs the detailed employee-level table. Executive management needs six numbers and a trend. Linked views serve both from the same underlying database, so the two can never disagree.

06 — Action tracking and accountability

Where reporting turns into work

Reporting databases connect to an action tracker. When management spots an issue, an opportunity, or a next step, it becomes an action assigned to a person with a deadline and a status.

That turns management reporting from passive information into an operational process.

07 — HR and team management

People, in the same system as everything else

HR databases organise employee information, recruitment, onboarding, responsibilities, leave management, and the internal processes around them. Linked views expose the right information to the right team without breaking the structure of the wider workspace.

08 — Finance and operational management

The information that usually lives on one person's laptop

Dedicated areas centralise the administrative and financial side of the business:

• Financial overview
• Budget planning
• Banking information
• Documents
• Investment tracking
• Administrative processes

This is exactly the material that otherwise ends up spread across spreadsheets, shared folders, and individual employees.

09 — Projects, tasks and internal processes

Project management inside the business, not beside it

Projects and tasks were built into the workspace architecture rather than run as a separate tool. Teams organise projects, assign responsibilities, track status and deadlines, and attach the relevant documents.

Internal procedures are documented in their own areas, which turns the workspace into a growing knowledge base instead of tribal memory.

10 — Linked views per department

One database, four audiences

Notion's real advantage is that a single database can support many views. Linked database views present the relevant slice in each area without duplicating anything underneath:

• Executive view — high-level KPIs and management priorities
• Sales view — salesperson performance and activity
• HR view — employees and responsibilities
• Operations view — tasks, projects, and action items

Each department works with what it needs, and the data structure stays centralised.

11 — Notion features used

What it is built on

• TeamspacesDepartmental workspace architecture
• DatabasesStructured company information
• RelationsConnections between separate databases
• RollupsAutomatic aggregation from related records
• Linked database viewsCustomised views across dashboards and departments
• FormulasCalculations and performance indicators
• DashboardsExecutive and departmental visualisation
• Filters and viewsContext-specific access to information

The workspace can also be paired with external automation. Our n8n reporting automation feeds processed data from other business platforms straight into this kind of management infrastructure.

12 — Business impact

The value is the connections, not the page count

What that buys the business:

• A centralised source of company information
• Better management visibility
• More structured reporting
• Clearer responsibilities and accountability
• Better collaboration between departments
• Less duplication of information
• Faster access to operational data
• More consistent internal processes
• Better data-driven decision-making

Notion can be far more than a note-taking or project tool. When databases, relations, rollups, dashboards, reports, tasks, and departmental workspaces are designed as one architecture, it becomes a business operating system — built around how the company actually operates, rather than around where the files happen to sit.