ArcGrid runs four ways. All the same platform.
Every operator is different. The size of the team, the volume of clients, the complexity of the work. ArcGrid runs four activation postures so the platform fits the business you actually have, not a generic tier you have to grow into.
Find the posture that fits your operation.
Same platform. Same Queue. Same Vault. Different scale, different configuration, different surface layout, activated once at onboarding and tuned as your operation grows.
One person who needs the grid to carry the preparation work.
Solo operators, independents, and freelancers who run real client engagements but are spending too much time assembling context before every call, project, and deliverable. The grid handles preparation so you can stay in the actual work: your calendar is staged, your clients are briefed, your deliverables are drafted before you touch them.
A small team where coordination and memory are the bottleneck.
Creative and professional services teams of two to ten people who are outgrowing shared inboxes and ad-hoc channels. You need the Vault for shared context, channels for team coordination, and a single place where every client engagement lives. Not a stack of project management tools that only track tasks.
An established practice with multiple clients and complex workflows.
Professional services firms of ten to fifty people handling multiple client engagements simultaneously, with compliance requirements and reporting obligations that demand more than a shared drive. Firm activates the full platform: workload management across your team, structured reports for clients and principals, and a configuration that reflects how your practice actually bills and operates.
Multiple entities that need to coordinate without merging their data.
Multi-entity operations, white-label deployments, or firms with distributed teams where each entity needs its own sovereign workspace, its own Vault, and its own approval gates. The grid connects them for orchestration and reporting. But nothing crosses the boundary between workspaces unless you open that gate deliberately.
What you need before you start.
ArcGrid is not a tool you trial and abandon. It is a platform you configure once and run from. The engagement works when these three things are true.
Three conditions
- 01 You run a real business with clients or active projects. The grid needs a model to work from. It cannot prepare work that does not exist yet.
- 02 You are spending meaningful time on coordination and preparation: briefing yourself before meetings, assembling status for clients, tracking who is doing what across projects. That is the load the grid is built to carry.
- 03 You are ready to model your business once and run it from a surface, not a spreadsheet. The onboarding engagement captures how you work, after that, the platform projects it forward every day.
Honest about what this is not.
ArcGrid is not a feature list. It requires a real engagement to configure and delivers value to operators who are ready to use it seriously.
If you are looking for
- / / A project management tool you can trial for free, click around, and cancel next month. This is not that.
- / / A chatbot you can prompt for answers without any underlying business model or client context. This is not that.
- / / A dashboard that replaces your spreadsheet without changing how you work. This is not that either.
The engagement is how you get on the platform.
There is no self-serve signup. An engagement is a short scoping session where we confirm fit, select your track, and configure your onboarding. It takes less than a week from first contact to a running Surface.