Offer 01 · AI agents and automation
AI agents that handle repeat work in your tools, and ask a person before they act
Routine steps run on their own. Anything that changes money, records, or customers waits for approval.
- 01Request
- 02Understand
- 03Act
- 04Approve
- 05Record
Read-only steps run on their own. Anything that changes money, records, or customers waits for a person.
Types we have built
Six kinds of agent, each built around one job
- 01
Customer Service Agent
Customers wait hours for answers that should take seconds.
Build this agent- Customer asks
- Agent checks the order
- Reply sent, refund waits
Example workflows
- Checks order status, answers delivery questions, categorizes complaints, and prepares refund requests for approval.
- Reads a returned item's details, confirms eligibility against policy, and books the pickup once a person signs off.
- 02
Back-Office Agent
Your team retypes invoices into systems all day.
Build this agent- Invoice arrives
- Agent matches the PO
- Record posted, gaps flagged
Example workflows
- Extracts information from invoices, checks it against purchase orders, flags discrepancies, and prepares records for accounting.
- Chases unpaid invoices on a schedule, logs each reminder, and escalates overdue accounts to the finance lead.
- 03
Sales Follow-Up Agent
Never lose a lead again.
Build this agent- New lead
- Agent drafts follow-up
- Rep approves, CRM updated
Example workflows
- Enriches incoming leads, drafts personalized outreach, updates CRM records, and reminds reps when a prospect needs attention.
- Notices a quote that has gone quiet for a week, sends a follow-up draft for the rep to review, and logs the response.
- 04
Voice and Chat Agent
Calls after hours go to voicemail and leads go elsewhere.
Build this agent- Call or chat
- Agent books or answers
- Hands off when complex
Example workflows
- Answers common questions, collects appointment details, checks availability, and transfers complicated enquiries to a human.
- Takes after-hours calls, captures the caller's details, and creates a callback task for the team at opening time.
- 05
Internal Copilot
Staff lose hours hunting for the right policy or file.
Build this agent- Staff question
- Agent searches approved docs
- Answer with sources
Example workflows
- Searches internal documentation, summarizes policies, retrieves project information, and drafts answers from approved company sources.
- Pulls the status of an open project, lists blockers from recent notes, and drafts a weekly update for the owner to edit.
- 06
Workflow Automation Agent
Work stalls waiting for someone to pass it along.
Build this agent- Request comes in
- Agent runs the steps
- Pauses before payment
Example workflows
- Receives a maintenance request, checks the property details, contacts the right contractor, coordinates the booking, and pauses before payment.
- Moves a new hire through account setup across three systems, then waits for a manager to approve access to finance tools.
Where agents save the most time
Five situations, and what changes in each
01
Work that only happens when someone remembers it
- Agent does
- Checks open items on a schedule and creates the next action.
- Person approves
- Changes that affect money or customer terms.
BeforeAfterRenewals and unpaid invoices get noticed when someone happens to scroll past them.
- Renewal due in 30 days, noticed Thursday
- Invoice unpaid 14 days, no reminder sent
- Contract missing signature, found at audit
Open items · checked every hour- Renewal due in 30 daysdone
- Invoice unpaid 14 daysdone
- Contract missing signaturedone
- Follow up after quotedone
02
Requests that go cold in a shared inbox
- Agent does
- Routes each request and drafts a reply in minutes.
- Person approves
- The reply, for new or high-value cases.
BeforeAfterRequests sit in a shared inbox until the next person checks it, and some never get a reply.
- Quote request, 3 pages, sitting two days
- Pricing question, no reply yet
- Partner intro, lost in the inbox
Inbound requests · liveQuote request, 3 pages
Routed to owner
Pricing question
Reply drafted
Partner intro
Waiting for you
03
The same data re-keyed between tools
- Agent does
- Writes one record to each system and logs every write.
- Person approves
- Any change to a figure already marked final.
BeforeAfterOne order is typed into three systems by hand, and the numbers drift apart by Friday.
- Order typed into the CRM on Monday
- Typed again into billing on Tuesday
- Copied into a sheet, totals do not match
One record, written once per systemSource order formCRM recordmatchedBilling systemmatchedShared sheetmatched04
A pilot that never reaches production
- Agent does
- Tests against your real past cases before anything ships.
- Person approves
- The release, and any expansion to a new process.
BeforeAfterThe demo impresses, then nobody can say when it is safe to switch it on for real customers.
- Demo approved in March
- Still no production date
- Nobody owns the rollout
Test cases from your real workPassingrun 1 of 3- Edge cases: covered
- Failures: logged
- Rollback: tested
- Release: after sign-off
05
An agent that acts when it should ask first
- Agent does
- Scores each decision and escalates the uncertain ones.
- Person approves
- Every escalated case, with the sources beside it.
BeforeAfterAutomation fires on every case, including the ones that should have gone to a person.
- Refund of 620 sent, over the 500 limit
- Customer escalates after the fact
- Finance sees it at month end
Decision · confidenceRefund 620 against a policy limit of 500
Above limit, sent to a person
Audit trail
Every action leaves a record
- One line per step: input, decision, tools called, outcome.
- Escalations show the reason and the sources beside them.
- Any outcome traces back to the step that caused it.
- receiverequest logged
- classifyrefund, 0.94
- readorder + carrier status
- policyabove limit, held
- escalatesent to approver
Where an agent sits between scripts and copilots
Scripted automation
Runs fixed rules. Stops on anything the rules did not anticipate.
Chat-only copilot
Helps a person answer. Does not act in your systems.
AI agent
Chooses steps within limits you set. Acts through approved tools. Asks when unsure.
Pricing and ownership
Priced by phase, owned by you
Fixed
One price per phase, approved before it starts.
4 to 8 weeks
Average launch for one workflow.
Yours
Code, models, data, and deployment transfer at handover.
Questions buyers ask first
- What can an agent do in our tools?
- Only what its permissions allow. We start with read access and add write access per action during scoping.
- How long does a launch take?
- 4 to 8 weeks on average for one workflow. The number of systems to connect sets where in that range you land.
- How is it priced?
- A fixed price per phase, approved before that phase starts. No rate card and no open-ended hours.
- Who owns it at the end?
- You do. The code, the models or configuration, the data pipelines, and the deployment.
- How is our data protected?
- Each agent sees only the tools it needs, every action is logged, and we review data handling with you before access is granted.
- What happens when the agent is wrong?
- It escalates when confidence is low or a case falls outside policy. Every run is logged, so the error can be traced.
Case studies
Writing
- 01AI agent architecture patterns, and when each one fits
- 02AI agent vs workflow automation: which to build
- 03What Is an AI Agent, and How Is It Different From an LLM?
- 04Reliability Engineering for AI Systems
- 05How to evaluate AI systems: a practical guide to evals
- 06What 'pilot with guardrails' actually means (and why most teams get it wrong)