Independent portfolio concept developed for the Janus Henderson Head of Automation & AI Enablement opportunity. Not affiliated with or endorsed by Janus Henderson Investors. All workflows, contracts, data and outcomes are illustrative.
CAO IntelligenceAI Enablement & TransformationExecutive Brief

Investment decision

Build vs. Buy vs. Existing Tools

Choose the simplest approach that solves the problem. These transparent rules favour process redesign and licensed tools before custom builds.

Load an example

Recommended approach

Workflow automation (buy / configure)

  • · Documented steps translate directly into workflow rules.
  • · Intake, routing and approvals are deterministic — best handled by rules, not models.
  • · Existing workflow tooling in the productivity suite may suffice.
  • · High volume rewards consistent automation.
#1Workflow automation (buy / configure)score 7
#2Microsoft 365 Copilot (existing tools)score 2

Work already lives in Microsoft 365 — leverage existing licences before buying.

#3Custom AI agent (build)score 2

Stable process makes agent behaviour testable. High volume can repay build and maintenance cost. Privileged content raises the validation burden for custom models.

#4Traditional process redesignscore 0

Required guardrails

  • · Named human owner accountable for every automated output.
  • · Attorney-client privilege review by Legal before any AI processing; restrict to privileged-matter workspaces.
  • · Attorney sign-off required on every AI-assisted output.
  • · Information Security and Compliance review before pilot launch.
Illustrative

Rule-based demonstration. No real Microsoft or vendor integration is implied.