From workspace setup to full business operations.

Step 1

Create a workspace and configure it.

When you create an account, the first thing you create is a workspace — the top-level container for your organization's data, with a name, logo, currency, timezone, and configuration options that cascade through every module. You define them once and every module respects them.

Currency affects how figures display and export across invoices, budgets, and reports. Timezone affects leave requests, schedules, and time-sensitive automations. Fiscal year affects budget periods and performance comparisons in finance and analytics.

Most organizations need one workspace. Some run several — a holding company per subsidiary, a consulting firm per major client, a franchise per location. Each workspace is a fully separate data environment; records never cross workspace boundaries, enforced structurally at the database layer.

Step 2

Invite your team and configure roles and permissions.

Once the workspace is configured, you invite team members. There's no per-seat charge — every team member is included in the subscription. What scales with your plan is workspace capacity (storage, compute, AI calls, automation runs), not headcount.

Each user gets one or more roles. Administrator has all 795 permissions; Viewer has read-only access everywhere; Finance Manager can manage invoices, budgets, and expenses but has no HR or vendor-deletion access. Roles can be customized permission by permission.

Permissions are checked at the UI layer (unauthorized views and controls simply don't render) and the database layer (isolation policies reject unauthorized queries regardless of what the frontend sends) — the database never trusts the frontend to have applied permissions correctly.

Step 3

Configure the structural data that all modules share.

Before modules produce useful data, the workspace needs structural configuration — work for an administrator or implementation specialist that shapes how all subsequent data looks and connects. Getting this right early prevents data cleanup later.

Departments and teams are the organizational units records are assigned to — an invoice to Finance, a project to Engineering. Used for filtering, budget allocation, access scoping, and reporting. A poorly defined structure makes cost-center reporting unreliable.

Chart of accounts defines how income and expenses are categorized across invoicing, budgeting, and P&L. Ships with 10 built-in expense categories plus support for custom ones.

Custom fields can be added to any entity — projects, contacts, employees, vendors, invoices, risks — as text, number, date, dropdown, multi-select, or boolean, appearing in every view, filter, report, and export for that entity.

Step 4

Enable modules and start building operational data.

Most organizations don't configure all 160+ modules simultaneously. A common pattern is starting with the modules replacing the most painful parts of the current stack, stabilizing those workflows, then expanding — new modules automatically see the existing records.

Starting with project management gives the delivery team a Kanban board, sprint planning with capacity tracking, milestone gates, a portfolio timeline, a Work Breakdown Structure editor, a risk register, and Earned Value Management. All assignees pull from the same employee records HR uses.

Starting with finance gives the finance team an invoice manager (draft to paid, multi-currency), a budget planner with real-time variance, an expense tracker, and a P&L that aggregates by any period.

Starting with HR gives the people team employee records, 8 leave types with automatic day calculation, an 8-stage recruitment pipeline, payroll with UK tax code support, and attendance tracking.

Step 5

Build dashboards and reports from live operational data.

Once operational data is being created, the reporting layer becomes valuable. The main dashboard is divided into 10 sections — Finance, Portfolio, Management, People, Governance, Operations, Content, Analytics, Communication, Productivity — each loading category-specific widgets automatically.

The KPI dashboard lets you define indicators with a name, category, current value, target, and unit. Status calculates automatically: On Target ≥95%, Near Target 75–95%, Off Target below 75%, each with an 8-point sparkline.

The executive dashboard gives leadership four financial KPIs with red-amber-green status, performance charts, attrition and NPS trends, and operational alerts — all from data the team creates daily. The executive summary generates a structured period report with headline, status, KPIs, risks, decisions, and next-period focus, printable directly from the browser.

The report builder allows ad-hoc reports from any entity with configurable filters, grouping, sorting, and calculated fields — schedulable for automated delivery and exportable to CSV.

Step 6

Add automation, integrations, and intelligence.

Once core workflows are running on real operational data, automation and AI add compounding value — they run on top of the same shared data layer, not as separate products to connect.

Automation rules allow trigger-action workflows without writing code — a project going "at risk" can create a task, notify the team lead, and flag the risk register in one automation.

Webhook integrations push events to external systems — an approved purchase order can notify an external system, a dropping health score can trigger an alert. Incoming webhooks can trigger automation rules in return.

AI assistance operates over the workspace's structured data, so answers about delivery status, budget variance, or vendor performance come from structured records — not free-text documents requiring interpretation.