01 / Discover & design
Start with the work.
Map the workflows, employee roles, and outcomes that matter to your organization.
- Workflow boundaries and priorities
- Roles, responsibilities, and success criteria
- A proposed scope and delivery approach
AI Employees — Managed service
Deep integration.
Ongoing partnership.
Work with Atlas to build AI Employees into your workflows, systems, and teams—with an implementation and service agreement shaped around the organization.
Optional service on top of AI Employees
Engagement outline
Built around your organization.
Your teamAtlas team
Roles & workflows
Systems & data
Access & approvals
Operation & improvement
From discovery to ongoing work
The work, connected.
The responsibilities, clear.
Start with the outcomes and the people involved. Agree the implementation, the handover, and the service that should follow.
02 / Integrate
Connect the operation.
Bring the relevant systems and data into the workflow with the access your team approves.
- Systems, documents, and data readiness
- Permissions and approval paths
- Integration design and configuration
03 / Deploy & hand over
Put it into practice.
Introduce the agreed workflows, review them with your team, and prepare the people who will use them.
- Agreed testing and acceptance points
- Team training and operating guidance
- Ownership and handover arrangements
04 / Ongoing service
Keep improving the work.
Define the support, review, and improvement work that should continue after implementation.
- Agreed support and review cadence
- Workflow refinements and maintenance
- A process for changes to the scope
Forward-deployed engineers & consultants
Work alongside people
who learn your operation.
Depending on the engagement, engineers or consultants can work alongside your teams to translate day-to-day work into a practical AI implementation.
The scope defines the roles, level of involvement, and working arrangements. The proposal defines staffing and service commitments for your engagement.
Your business owners
Bring the priorities, operating context, and decisions that the workflow must support.
The implementation team
Design and configure the agreed roles, integrations, and delivery work alongside your team.
Your system and security owners
Review access, permissions, data requirements, and the responsibilities for ongoing operation.
A proposal around the scope
Price the work.
Make the terms clear.
The proposal reflects the implementation and services your organization needs. We agree the scope and commercial terms before the work begins.
The work itself
The number, complexity, and depth of the workflows and employee roles.
Connected systems
The integrations, interfaces, and environments involved.
Data readiness
The preparation, structure, and quality of the information the workflows use.
Access requirements
Your security, permissions, approval, and review requirements.
Delivery and handover
The rollout approach, testing, training, and handover work.
Ongoing service
The support, operating responsibilities, and improvement cadence you agree.
The statement of work
A clear agreement.
A shared way forward.
Use the agreement to make the boundaries, ownership, and expectations visible to everyone involved.
Scope and deliverables
The workflows, integrations, outputs, and exclusions covered by the engagement.
People and responsibilities
The client and Atlas owners, required inputs, access decisions, and approval responsibilities.
Delivery and acceptance
The delivery approach, review points, acceptance criteria, training, and handover.
Fees and usage
Implementation fees, ongoing service, platform access, and AI usage, itemized as agreed.
Ongoing arrangements
The service activities, support expectations, review cadence, and ownership after launch.
Changes to the work
How scope changes, additional integrations, and related commercial changes are reviewed and agreed.
Before we begin
The right scope.
An informed next step.
Is Managed required to use AI Employees?
No. AI Employees is the technology product. Access to the software and its capabilities depends on your platform plan. Managed is an optional service engagement for implementation, integration, and ongoing work.
How do forward-deployed engineers or consultants work with us?
Depending on the agreed scope, engineers or consultants can work alongside your business and technical teams. The proposal defines their involvement, responsibilities, working arrangements, and the work they will help deliver.
How is the engagement priced?
We develop a proposal around the workflows, integrations, data, access requirements, delivery work, and ongoing services involved. The statement of work sets out the scope and commercial terms.
Does the service agreement include platform access and AI usage?
The agreement states how platform access and AI usage are treated, including what is included and what is billed separately. A managed engagement does not automatically change your existing subscription or entitlements.
Can we begin with one workflow?
A focused initial workflow can be discussed during discovery. The agreed scope defines the work, deliverables, responsibilities, and what a later expansion would involve.
Who controls permissions and approvals?
Your designated owners grant access and approve the relevant permissions. The engagement defines responsibilities for configuration, review, approval, and ongoing operation so those decisions remain explicit.
Begin with discovery
Bring us the workflow.
Let’s shape the engagement.
Talk through your organization, the work you want to improve, and the systems and people involved.