CRM and client history
Clients, leads, meetings, messages, requests, documents, and relationship context.
This matrix describes the current product surfaces and their role in a connected client-work system. Availability can depend on plan, permissions, workspace configuration, and provider setup.
Clients, leads, meetings, messages, requests, documents, and relationship context.
Projects, tasks, plans, files, approvals, time, budgets, capacity, and reporting.
Estimates, contracts, invoices, payment connections, expenses, retainers, and margin context.
The value comes from the links between capabilities, while each record still has a defined owner and lifecycle.
Maintain client and lead records, contacts, relationship history, requests, meetings, messages, and connected work.
Coordinate projects, tasks, dates, goals, roadmaps, files, approvals, time, budgets, capacity, and delivery reporting.
Create and connect estimates, contracts, invoices, expenses, payment status, retainers, and project profitability context.
Provide scoped client portal access, forms, galleries, websites, automations, research, and Aria assistance around workspace context.
Manage members, access, workspace configuration, provider connections, import, security, and operational controls.
A clear boundary is more useful than an exaggerated replacement claim.
Not necessarily. Availability may depend on plan, workspace configuration, permissions, rollout status, and provider credentials. Confirm current details on pricing and product surfaces.
No. It coordinates the client, project, approval, file, and commercial workflow around specialist production tools.
The visible review date shows the latest documentation audit. Product behavior and plan availability should still be confirmed during evaluation.
Start with one active client and see how the records work together.