Starter
A first team workflow
USD—per month
- Company size
- —
- Agent
- —
PLANS
Choose the coordination your work needs.
Find a useful starting scope for your team before comparing a service offer. Starter, Business and Enterprise organise the discussion around a first team, cross-team work and company-wide requirements.
Business
Coordination across teams
USD—per month
- Company size
- —
- Agent
- —
Enterprise
Company-specific requirements
USD—per month
- Company size
- —
- Agent
- —
01
Describe the workflow before choosing its scope.
Start with a checkable outcome and its review boundary. The AI Chief connects the roles involved. Use the product overview and relevant company situations to identify who contributes, who receives the result and which choice follows review.
02
Ask the same practical questions of each scope.
A dashboard makes the next responsibility visible. Exception handling routes a specific question. Use the columns to identify the coordination, source and receiving needs of the process. A service offer defines the actual allowances and terms.
| Question | Starter direction | Business direction | Enterprise discussion |
|---|---|---|---|
| Coordination | First team and reviewer | Several receiving teams | Company-defined responsibilities |
| Source context | First workflow references | Shared dependencies | Information boundaries and owners |
| Review | Defined contribution | Cross-team consequences | Reserved company decisions |
| Connections | Required inputs | Meaning of shared records | Access and recovery requirements |
| People and specialist roles | Identify initial participants | Map team contributions | Describe organisation-wide roles |
03
Consider monthly and annual terms against the same workflow.
The page switches the displayed billing period. It does not quote a price or activate paid access. Review the website terms, use the company form to organise your company background, and read the privacy and security information. A service offer should state the amount, billing terms and included allowances explicitly.
04
List the contributions your team actually needs.
A Sales Agent organises customer follow-up, a Procurement Agent compares terms and a Finance Agent gathers record questions. Use the Agent brief template to define the task, the company knowledge design to identify sources and the Integration requirements to describe the relevant data and actions.
05
Use one receiving handoff to guide the comparison.
The first-goal guide gives the result a clear purpose. Bring that workflow to the demo discussion, apply the human-control model and use the company background to explain who contributes and decides.
- 01
Name the outcome
Choose a result a real colleague can review.
- 02
Map the responsibilities
List participants, sources and reserved decisions.
- 03
Compare an explicit offer
Check price, billing period, user allowances and service terms against that workflow.
Product illustration
Choose a coordination scope
| Planning question | Starter | Business | Enterprise |
|---|---|---|---|
| Coordination boundary | A first team process | Several teams | Specific organization requirements |
| Review emphasis | Task responsibility | Cross-team decisions | Governance requirements |
| Users and Agents | — | — | — |
| Integration discussion | Required inputs | Shared sources | Technical acceptance review |
Questions, answered.
What should I compare first?
Compare the workflow, participating roles, source requirements and receiving responsibilities.
How do I assess user and Agent needs?
List the actual people and specialist contributions required for the first process and any shared work.
What should an offer specify?
The price, billing period, included allowances, actual functions and applicable service terms.
How can I prepare for the discussion?
Write one goal brief with its sources, reviewer and the next business decision.