Anthropic Financial Services

Workshop agenda

Run an Anthropic Financial Services event that ends with a pilot decision

A good internal event should not be a generic AI talk. It should show real finance-agent workflows, surface risk questions, and leave the team with a scoped first pilot.

Use this agenda for an internal workshop, vendor review, innovation day, or operating-committee session.

Suggested 90-minute agenda

The strongest event format starts with the repository’s actual workflow categories, then narrows to two or three demos that match the audience.

Keep the final third of the session practical: what data is allowed, what outputs are reviewable, what cannot be automated, and what the first paid pilot should measure.

  • 15 minutes: repository overview and what the agents are not allowed to do.
  • 25 minutes: analyst workflow demo such as earnings review, comps, or model refresh.
  • 20 minutes: operations workflow demo such as GL reconciliation, valuation review, or KYC screening.
  • 20 minutes: controls, data access, reviewer roles, and compliance questions.
  • 10 minutes: pilot scope, owner, success metrics, and next action.

Questions the event should answer

Can the team identify one workflow where a draft saves real time? Can reviewers see sources and assumptions quickly? Can compliance explain the boundary between draft support and decision authority?

If those questions are answered, the event can turn into a controlled pilot instead of another interesting but unfunded demo.

What to prepare before the room

Bring sanitized documents, a familiar template, a sample approval policy, and a list of connector candidates. Avoid live private data until the permissions model is settled.

The goal is not to impress the room with breadth. It is to make one credible workflow feel safe enough to fund.

Common questions

Who should attend the event?

Invite the workflow owner, two hands-on analysts or operators, technology, compliance, information security, and a budget owner who can approve the pilot.

What should the event produce?

It should produce a selected workflow, data boundary, reviewer owner, deployment path, success metric, and target launch date.

Build the pilot workspace