Skip to main content
Engagement archetype, fund services

AI for Product Management in a Fund Services Firm

A representative engagement pattern, not a named client. A fund and corporate services firm wants its product managers and business analysts to use AI well in daily product work, inside the strict data rules its clients expect.

Sector, fund and corporate services People, product managers and analysts Format, private programme Delivery, online or in person

The situation

Firms of this kind provide fund administration, corporate services and reporting for clients in many countries. Their product teams own client portals, reporting tools and internal platforms. The work is detailed and full of documents, and client data is sensitive.

Product managers already use AI tools informally, mostly for writing. Leaders want more: a shared way to use AI in discovery, requirements, prioritisation and stakeholder updates, with rules that everyone understands.

What we usually see

1. AI used for writing, not for product work

People use AI to tidy emails, but not yet to synthesise client feedback, test assumptions or draft acceptance criteria.

2. Caution about client data

Teams are unsure what they may put into an AI tool, so many avoid it for the work where it would help most.

3. Time lost to documents and updates

Requirements, release notes and status reports take hours that could go to clients and decisions.

4. No shared method

Each person keeps private prompts. Little is reused, so the team does not get faster together.

How the engagement usually runs

A short conversation with the sponsor sets the goals and the data rules. The programme then draws on our AI Product Management course and, where the team wants a credential, the short ICAgile AI micro-credentials for product roles.

People practise on their own kind of work, using sample material that is not confidential: turning interview notes into insights, drafting user stories and acceptance criteria, preparing stakeholder updates and comparing roadmap options. The team agrees simple rules for data and review, and keeps a shared library of prompts and templates.

What this kind of programme aims to change

We describe aims rather than results, because results belong to each client.

  • Faster discovery and clearer requirements.
  • Safer, consistent handling of client data.
  • A shared library of prompts and templates.
  • Product managers who brief AI tools with confidence.

Lessons that transfer

  • Start from product work, not from the tool. The value shows up in discovery and requirements, not in tidier emails.
  • Agree the data rules on day one. People use AI more, and more safely, once they know what is allowed.
  • Reuse beats cleverness. Shared templates make the whole team faster.
  • Keep a person accountable. Every output a client sees has a named owner.

Honest framing. This page describes a type of engagement, not a named client. We do not publish client names, people, venues, dates, group sizes or programme details. If your organisation is exploring something similar, Founder and Director Prashant Shinde is happy to talk it through.

Talk to us about your product team

A direct conversation about your goals, your tools and your data rules.

Request a private discovery

Frequently asked questions

Who is this kind of programme for?

Product managers, product owners and business analysts, and the leaders they report to.

Do people use real client data in the sessions?

No. Practice uses sample material that looks like the team's real work, so nothing confidential is shared.

Can people earn a credential?

Yes, where the team wants one. The ICAgile AI micro-credentials for product roles are short live classes, assessed in the session and held for life.

Explore more