Teams and email first
Users request, approve, and review work in the channels they already use.
User Experience
The agent meets people in Teams and email.
Employees do not need another portal to use Agent Aech. Requests, approvals, replies, documents, and handoffs stay in the Microsoft 365 surfaces where the business already works.
Outlook and shared inboxes
Customer requests, approvals, drafts, and handoffs stay in the inboxes where work already lands.
Microsoft Teams
People can request work, review agent output, answer exceptions, and approve next steps in Teams.
OneDrive and SharePoint context
Agents can work with the files, documents, and records they are explicitly allowed to use.
Human review loops
Sensitive moments stay reviewable: the agent prepares the work, and the right person approves it.
Small Teams First
Built for small teams that cannot afford dropped work.
Most small businesses do not need another system to manage. They need the work to move. Agent Aech starts where your team already works and gives you a practical way to automate the recurring work that steals attention from customers and delivery.
- No system overhaul required to start.
- Start with one workflow and expand when it works.
- Keep humans in the loop for pricing, commitments, and customer-facing actions.
- Use your existing email, Teams, and operating records.
- Add stronger controls as the workflow becomes business-critical.
Administration
Advanced administration for governed AI operations.
Agent Aech gives operators the business controls behind each production agent: RBAC, Agent ID, Microsoft 365 delegation, Teams/email capability scope, review policy, spend visibility, and audit-ready run history.
- Role-based access controls define who can administer agents, approve actions, and inspect runs.
- Agent ID, owner, Microsoft 365 delegation, Teams/email access, prompts, tools, and memory stay configurable.
- Capability scope, privacy controls, review policy, and egress rules are managed per agent.
- Run history shows reviewer output, runtime events, token usage, cache behavior, and per-run spend.
- Private, on-prem, and dedicated hardware runtime options fit the same administration model.
Dashboard spend and agents
1 of 6
Use Cases
Start small. Expand when the workflow proves itself.
SMB
Customer Work Coordinator
Keep recurring customer follow-up, quote prep, approvals, and handoffs moving without adding another admin ritual.
View use caseEnterprise
Velocity Pod
Reserved AI delivery capacity that ships agents while training the internal owner who will keep the factory running.
View use caseMSP
MSP Software Factory
Host Agent Aech, build customer-specific agents, and turn trusted managed services into recurring AI solution revenue.
View use caseMSPs
Turn your MSP into an AI software factory.
Agent Aech MSP is built for providers who already run trusted customer operations. Use it inside your own service desk, then host Agent Aech and use the agent builder to deliver AI solutions for your customers.
New AI services revenue without rebuilding every workflow from zero.
Deeper customer engagements through agents tied to real operations.
More revenue per customer with hosting, agent builds, and recurring improvement.
How It Works
From one workflow to a working agent.
- 1
Pick the workflow
Choose a recurring workflow with clear inputs, handoffs, and decisions.
- 2
Teach the agent the rules
Connect the relevant context, define what the agent can do, and set review points for sensitive actions.
- 3
Run with review
Let the agent work through email, Teams, and business records while humans approve the moments that matter.
- 4
Improve or expand
Use the audit trail to decide what to automate next and where more control is needed.
Enterprise
Have a larger AI program that needs to ship?
Enterprise teams use Agent Aech Velocity Pods to reserve a weekly delivery lane, ship governed agents, and train the internal AI or IT owner who will keep building in Harness Manager.