Battery Point Research · Robotics & Automation
Traditional automation — APIs
- APIs move data between apps.
- Automation follows steps that people set up.
- People interpret requests, investigate exceptions and decide what happens next.
AI agents — apps connected through MCP
- The agent interprets what an email is asking for.
- The agent checks records across connected apps and determines the next action.
- The agent performs permitted actions and checks whether they worked.
- The agent records actions and outcomes, revealing recurring problems and opportunities to improve the process.
Which agents to create first
| Agent | Software to connect | Work it now does | New capability |
|---|---|---|---|
| 1. Sales follow-up | CRM + email + calendar + quote files + company websites |
| Research each account before contact, then link the exact message and product interest to the project it produces. |
| 2. Invoice processing | Bookkeeping + email + ERP purchase orders and receipts |
| Build a history of why invoices go wrong—and identify recurring supplier errors or gaps in receiving records. |
| 3. Collections | Bookkeeping + email + CRM + delivery records |
| Connect payment delays to delivery problems, invoice errors or customer approval bottlenecks. |
| 4. Customer service | Ticketing + CRM + order system + product manuals |
| Compare customer inquiries with order and shipping events to find recurring problems that generate avoidable calls. |
| 5. Purchasing and delivery | ERP + inventory + supplier email + logistics / transportation management (TMS) |
| Use the history of promised and actual arrivals to flag unreliable lead times before making the next customer commitment. |
| 6. Field-service closeout | Field app + equipment history + parts and time records + bookkeeping |
| Find repeat failures across equipment and service visits, and flag completed work or used parts missing from billing. |
| 7. Meeting commitments | Calendar + meeting notes + task manager + document storage |
| Trace repeated project delays to missing inputs and owners, then carry those lessons into the next project’s checklist. |
| 8. Employee onboarding | HR + identity and access + IT tickets + training records |
| Pinpoint which applications or approvals repeatedly delay new hires, so those steps can start earlier for the next group. |
What this means for the owner
A leaner company starts with complete workflows.
Roles built largely around routine handling can shrink or combine. A growing company may avoid its next administrative hire. Engineering, commercial judgment and physical execution still need accountable people.
Count the workload removed across a whole role before deciding what happens to a position. Include integration upkeep, exception handling and review in that calculation.
Discuss your business with Battery Point- Choose one recurring task. Start with a process whose inputs, owner and finished result are clear.
- Measure the current work. Record handling time, errors, waiting and exceptions.
- Connect and complete it. Verify the saved outcome, including the required human decisions.
- Keep the useful history. Use it to make one operating change, then compare the next set of results.
Research scope, assumptions and sources
These are illustrative workflows, not client results or measured savings. Record numbers, quantities and outcomes are hypothetical. The examples assume the company has the named records and appropriate permissions. Some steps may already be automated. MCP supplies a connection standard; it does not independently perform the work or guarantee an integration. Full workflows may require custom tools, scheduled checks and maintained connections.
The proposed team structures are scenarios. Roles are not necessarily separate employees. A staffing decision requires measured workload, exception rates and service quality across the whole job. The dividend comes from preserving and using evidence that could previously have been scattered or unrecorded; the information was not inherently unknowable.
The research links document operating mechanisms and available product capabilities. The manufacturing scenarios and proposed improvements are BPC analysis, not measured results from those sources. Existing software may already supply the reports or rules; the agent helps connect records and complete the work. A pattern still needs investigation before changing the process. These sources do not establish an off-the-shelf end-to-end installation or its staffing outcome. The P&G study concerns defined product-innovation tasks, not robotics headcount.
- Model Context Protocol: connections and tools
- Intuit: QuickBooks Online MCP tools
- Microsoft: tools for connected agents
- Microsoft: Dynamics 365 data integration
- Zendesk: procedures, integrations and handoffs
- Asana: MCP tools reference
- BambooHR: employee-created events
- Microsoft Entra: lifecycle workflow tasks
- Research: AI and team design — P&G field experiment
- Celonis: purchasing and receiving errors create invoice rework
- Salesforce: retain product interest through lead-to-opportunity conversion
- Microsoft: use delivery history to assess future supply risk
- UPS: label creation and carrier possession are different statuses
- Asana: record which tasks block other work
- Microsoft: inspect lifecycle workflow results at task level
- Oracle: transportation management and shipment visibility
- Microsoft: authentication registration, usage and failure reporting
