Product Manager Bootcamp for a Singapore MAS-Regulated Fintech Scale-Up

The situation

An enterprise of this profile is a Singapore-headquartered fintech scale-up that holds, or is in the licensing pipeline for, one or more MAS regulated activities. Payment services under the Payment Services Act. Lending through a regulated subsidiary. Wealth or insurance distribution. Digital asset infrastructure under the Payment Services and Financial Services and Markets Act perimeters. The company has scaled from a Series A founding team to a population of fifteen to eighty product managers across multiple lines, often distributed across Singapore, India, Vietnam and Indonesia.

The product manager bench is uneven. Some came from banking and are strong on regulatory pattern recognition but weaker on the AI-augmented product loop. Some came from consumer tech and are the opposite. Many are first-time product managers promoted from analyst or engineering roles inside the company. A small number are senior PMs who hold the product playbook in their head and have not written it down. The CPO has decided this bench needs a structured bootcamp before the next funding milestone, when the company will be judged on the predictability of its product delivery.

The business pressure is rarely a single event. It is the compounding of a competitor launch, a MAS notice that reset technology risk expectations, an investor question on how AI is changing the unit economics of the product, and a senior leader who is tired of the same product reviews producing the same gap analysis. Engagements of this archetype begin when the CPO commissions a deliberate uplift across the entire product manager population rather than another tactical hire.

What we observed

1. Discovery is conflated with delivery

The product team treats every roadmap line item as a build. Discovery is compressed into a few interview slots. The result is a backlog of expensive builds that should have been pre-empted by a tighter discovery.

2. The regulatory brief is a separate workstream

Compliance is consulted after the PRD is written, not before. Product and compliance therefore re-litigate the same decisions repeatedly. Both teams resent the cycle.

3. AI features ship as bolt-ons

The fintech has launched at least one AI assistant. Internally, the engineering team knows it is a bolt-on. The product team has not yet learned how to write an AI-augmented feature as a redesigned workflow rather than as a chat surface on top of an existing flow.

4. The PM career ladder is unclear

The PM bench cannot answer the question of what good looks like at their level. Without a written ladder, the bootcamp risks teaching skills the company does not yet reward.

The engagement approach

Engagements of this archetype run as a six to eight week bootcamp with founder-led discovery and senior-trainer cohort delivery.

Sponsor design, week zero

The founder, Prashant Shinde, runs a one day session with the CPO, head of risk and compliance and head of engineering. Output is a written product manager capability map and a clarified PM ladder. The bootcamp is then designed to teach to the ladder, not against it.

Foundation, weeks one and two

The cohort takes the AI Product Pathway and the AI Agile for Singapore Banking module for regulatory context. The AI-Native Agile Operating Model is taught as the operating reference, not as a deck.

Practitioner, weeks three to six

Each PM brings a live feature. They rewrite the PRD, the discovery plan, the AI evaluation plan and the risk and compliance brief. The senior trainer reviews. The founder runs a fortnightly senior reviewer panel where a sample is critiqued in front of the cohort. Compliance partners sit in.

Certification and showcase, weeks seven and eight

PMs who choose certification complete ICP-APO or ICP-APM. The cohort showcase puts five PMs in front of the CPO and head of risk to present their reworked PRDs. The CPO signs off the PM capability map publicly.

What changed

1. PRD first-pass quality

The proportion of PRDs that compliance signs off without rework rises noticeably. This is the single most useful indicator a Singapore fintech can track from this engagement.

2. Discovery to commitment ratio

The ratio of features that survive a real discovery to features that get committed to the roadmap improves. The company stops building things it should have killed in discovery.

3. PM bench depth

The bench grows a layer of mid-level PMs who can independently hold an AI-augmented product loop. The CPO stops being the single point of escalation.

4. Cross-functional respect

Risk, compliance and engineering report that the conversation with product is now more productive. This is qualitative and it matters.

Lessons that transfer to other Singapore fintech scale-ups

• Write the PM ladder before the bootcamp. Otherwise you teach skills the company does not yet reward.
• Bring compliance into discovery. The cost of late compliance review is the largest hidden tax on fintech product delivery.
• Teach AI as a workflow redesign, not a chat surface. The bench has to internalise this before the next AI feature ships.
• The CPO must show up at the showcase. Without that, the cohort discounts the work.