Start with the work that falls between systems
A manager preparing a weekly review may open the CRM, check delivery boards, find unresolved messages and ask several people for updates. An AI assistant could assemble a first draft of that brief, link each point to its source and flag what still needs an answer. That is a concrete starting point for a pilot.
The phrase “AI CEO” overstates the role. Software can help collect information and prepare work. People remain accountable for strategy, commitments, hiring, spending and decisions about customers. A helpful assistant makes those decisions easier to prepare for and review.
Give the assistant one complete assignment
Define who reads the brief, which questions it answers and when the information must be current. For example: “Prepare the weekly delivery review from these approved project records. Show overdue milestones, unresolved dependencies and their owners. Link the evidence and identify missing updates.”
Keep the first release read-only. Calculate dates and totals in the application, then ask the model to explain the checked results. A convincing narrative is not evidence that an invoice total or project status is correct. If two systems disagree, preserve that disagreement for the responsible owner.
| Part of the brief | What makes it actionable |
|---|---|
| Current position | A dated snapshot of agreed measures with source links. |
| Exceptions | The specific item that needs attention, with the relevant evidence. |
| Owner and next step | The recorded owner and existing commitment, with missing details marked. |
| Questions for review | Unresolved information and proposed questions, separate from confirmed facts. |
Maintain the knowledge behind the answer
Give process documents an owner, version and review date. Decide which source wins when a CRM field conflicts with a spreadsheet. Archive obsolete instructions and restrict access to material the intended reader is allowed to see.
Feedback can suggest a change to a process document. It should not silently rewrite company policy. Keep proposed changes separate until the process owner approves them. Likewise, retaining a conversation is not a substitute for a maintained record of an approved decision.
Add agents only when they solve a defined problem
A scheduled workflow with a few API calls may be enough. Separate agents can help when tasks require different tools or expertise, but each handoff adds state, cost and another place for information to go missing. A private server does not remove external model limits or the need to operate the service.
Anthropic: choosing workflows and agents
If an assistant later prepares a CRM update, keep the draft and the permission to apply it separate. Limit available actions in the integration itself. Documents and messages are input data; they must not be able to grant access, change the workflow or redirect private information.
Decide whether the pilot earns a wider rollout
- Compare the brief with its sources and record unsupported statements or important omissions.
- Measure the total preparation and correction time, including the reviewer’s effort.
- Test missing updates, conflicting records, an unavailable connector and an unauthorised request.
- Record model and integration costs, failed runs and the effort needed to support them.
- Name the person who can stop the workflow and the owner who approves the next scope.
Use the results to decide whether to improve the brief, add a second task or stop. Savings and staffing changes need evidence from the actual process. An agent diagram cannot establish either.
Discuss a similar workflow
Bring a description of the process, the systems involved and one example of where work gets stuck. We can use discovery to establish the requirements, dependencies and next step before preparing a solution and estimate. Please leave private customer, applicant and patient records out of the website enquiry.