Which course is right for your role?

• Our technology is good and our business model is quietly killing it.
• We built horizontal breadth and cannot monetize it.
• We do not know which surfaces we own.
• Our roadmap only contains what we can build today.

The strongest match in the portfolio. Every axis maxes out: the job description is platform architecture plus monetization plus governance plus partner ecosystem, which is a section-by-section description of this course. Infrastructure cost engineering, model serving operations, and SRE are not covered.

• There is no definition of my role.
• I understand the concepts and cannot execute them.
• I cannot tell how the pieces fit together.
• My technical team is buried in unqualified requests.
• An executive brings me a directionally wrong idea and I cannot just say no.

Week one defines the role concretely, and weeks four through eight are implementation. If you want a lower-cost entry point first, AI Opportunity Discovery is the upstream half of this job and the two are designed to sequence. Take one, then the other, rather than both at once.

• My technical team is buried in an unfiltered request queue.
• Commitments get made before anyone checked whether the thing can be built.
• Initiatives get blocked mid-flight by data problems discovered months in.

Take this first, then AI Product Management as the eight-week continuation. The two are sequenced deliberately and buying both at the same time is not the recommended path.

• I am not in the room where it is decided.
• I get handed initiatives I know will not deliver.
• Do this with AI is an executive specifying my architecture.
• I am the only one pushing back.

Opportunity discovery is where the year of work gets chosen. If you are not in that room you inherit the results with no recourse, and reopening the decision later costs credibility rather than winning the argument. This is the entry point to the ladder.

• I cannot quantify the value of my own work.
• I have never estimated something this uncertain. Single-number estimates are impossible and ranges feel like hedging.
• The room goes silent in the workshop.
• People leave the session feeling stupid and do not come back.

A scarce and fast-growing function whose published job description is close to a restatement of lessons 6, 8, and 9: lead structured value discovery, publish executive-ready business cases that quantify results. TCO spreadsheets, MEDDIC, deal strategy, and procurement navigation are not covered.

• Consumption pricing is breaking down. Every time the model gets better, customers do not consume more.
• Institutional rigidity pulls every initiative back.
• I cannot explain why we are succeeding or failing.

The course states its own boundary: it assumes an organization with existing products, existing customers, and an existing business model rather than a greenfield startup. That assumption describes you exactly.

• We have data everywhere and cannot tell you what any of it is worth.
• Our data was built for dashboards and our models cannot use it.
• Every department defines customer differently.
• I am the only person in the building who cares about data.

Data strategy here is commercial rather than operational: the Data Monetization Catalog, the With-and-Without valuation method, and the Multi-Domain Problem. Governance mechanics, privacy compliance, MDM, and lineage tooling are out of scope.

• The ideas I get are all digital use cases.
• Someone raises a roadblock and the room stops.
• Prioritization by squeaky wheel.
• Prioritization by coolest job title.

Lesson 13 is a full toolkit for when a discovery session goes wrong: the silent room, the derailing objection, and the participant who leaves wondering why they were there. That lesson alone maps to the part of your job with no published playbook.

• I have a mandate and none of the people who have to help me do.
• I sit inside IT and structurally cannot own strategy.
• I freeze when a C-level leader challenges me.
• My CFO will not fund anything without a timeline and I do not have one.

The course covers the published job description almost line for line: enterprise strategy and roadmap, the initial assessment, workflow-level ROI, coalition building, and live pushback drills. It stops at opportunity discovery. Roadmap construction is the product management course and pricing is monetization.

• We ran the pilot, it worked, and nothing changed.
• We took one big swing at transformation and it collapsed.
• The organization feels like it is being torn apart.
• Pushing harder makes it worse.

Built around incremental delivery rather than a single transformation program, plus the change work that decides whether any of it lands. It does not teach Prosci or ADKAR vocabulary, workforce planning, or HR job families.

• We are still monetizing software when we are delivering intelligence.
• Per-seat licensing collapses when the worker is not a person.
• We have no path from where we price today to outcome-based pricing.

The pyramid supplies the intermediate steps between where you price now and outcomes: capabilities, autonomy and intelligence, domain expertise, self-improvement. Elasticity modeling, conjoint analysis, deal desk operations, and CPQ are not covered.

• Just give me a number, before anyone knows what is being built.
• Users show up and do not pay.
• Freemium is quietly destroying our business.
• I am being asked to do AI strategy and AI product management at once.

Written for someone who owns a P&L. The course is explicit that AI strategy and AI product management are two full roles and doing both means doing both badly, plus how to split responsibilities when there is no one else to hire.

• We are spending heavily on AI and cannot show what it returns.
• AI is bolted onto existing workflows and creates more work downstream.
• I have a quarter, not three years.

The final assignment is a Parallel Maturity roadmap for your own business, which is the artifact a P&L owner can take straight into a planning cycle.

• A former student asked me to run an initial assessment and I do not know what it includes or what to charge.
• I keep landing at the wrong level.
• I am one person with a team of one more.

You leave with a repeatable assessment and strategy engagement you can sell. If your clients are SMB or mid-market and the deliverable is a use case portfolio rather than a strategy document, start with AI Opportunity Discovery instead. Practice marketing, lead generation, and contracting are not covered.

• Our pricing metric has no structural connection to value.
• Adoption is high and payment is low.
• Our pricing changes keep getting reversed.
• We charge the same price across domains with wildly different value.

Eighteen pricing frameworks, the AI Monetization Pyramid, and the Salesforce pricing journey treated as a listening exercise rather than a launch. Experimentation platforms, funnel analytics tooling, and conversion-rate tactics are not covered.

• Executives do not see what it takes to produce an insight, so they do not fund it.
• We are drowning in reporting.
• Frontline teams cannot articulate opportunities.

Bottom-up discovery is built for someone without C-suite access: start with frontline teams, stack two or three wins, and earn the meeting. If you want the full mandate path and the strategy document, step up to the Data & AI Strategist Certification afterward.

• Leadership announced a huge investment and the stock dropped.
• We cannot calculate ROI, so finance is cutting us.
• We are stuck between proof of concept and production.
• A competitor will make us obsolete before we finish transforming.

One caveat worth knowing before you buy: most CAIO job descriptions include governance, ethics, and model risk, and this course teaches none of them. Agent governance is taught in Platform Monetization. Pair the two if governance is a real part of your mandate.

• I cannot telephone-game my way up from a director.
• My clients are not ready to hear where they actually are.
• I am being asked to prove ROI on something whose ROI arrives later.

Route by what you own. If you facilitate the workshop, AI Opportunity Discovery is the tighter fit. If you own the engagement and have to hold the client C-suite, take this one. Proposal writing, SOW pricing, and practice economics are not covered.

• Most of our data cannot be used for models or even analytics.
• Agents hallucinate because there is no information structure underneath them.
• We have far more data than we know and no way to capture it.

Take this if you build the data product. If you commercialize it, Platform Monetization is the better fit. Data mesh implementation, data contracts, catalog tooling, and quality frameworks are not covered.

• I cannot translate in either direction.
• I do not know how to define a problem without prescribing the solution.
• The customer wants AI and cannot say what for.

Roughly half of the FDE job is discovery, and it is the half with almost no training available. Nothing technical is taught here, which is the point: this is the non-engineering half. Lessons 2, 8, 9, and 13 map to walking into a customer, finding the workflow worth changing, and proving it created value.

• I have a quarter, not three years.
• Costs scale with success.
• I need funding before I can do the work that justifies the funding.

Named in the syllabus audience: founders building AI-native products who need a business model, not just a model. Note that Platform Monetization assumes existing products and customers, so it is the wrong course for a greenfield startup. Fundraising, cap tables, and sales motion design are not covered.

• Small-business CEOs demand execution detail immediately. AI magic does not survive thirty seconds.
• I do not know how to scope or price an engagement.
• My clients want to cut headcount and I know that is the wrong answer.

The course is opinionated that discovery is a growth function rather than a cost-reduction function, which is the exact argument you need with a client reaching for layoffs. If your clients are enterprise and the deliverable is a strategy document, take the strategist certification instead.

• Every team believes it has the agent to rule all agents.
• Our platform works and no one uses it.
• Initiatives are evaluated in isolation instead of as a compounding sequence.

Covers surfaces, platform strategy, and the Roadmap Layer Cake. For agent governance specifically, Platform Monetization section 20 is the only place in the portfolio that teaches it.

• I am the only person in the room who can see this coming.
• I cannot tell how the pieces fit together.
• Everything I learn is obsolete in six months and I want durable structure.

The frameworks are the durable layer. Model releases every three to six months do not change the Roadmap Layer Cake, Parallel Maturity, or how an opportunity becomes an initiative.

• I came from a technical background and I keep meddling.
• Strategy means giving up the tools that made me successful.
• I am stuck between staying technical and going advisory.

The course states this upfront: if you come from a technical background, expect the first two weeks to be uncomfortable, because strategy is shoulders up and the weapons you have used to be successful get set aside. This material is harder for technical people, not easier.

• I understand the concepts and cannot get anyone to act on them.
• Our KPIs have no owner.
• Our engineers are maintaining data infrastructure they never wanted.

Nothing technical is taught, and that is the point. One participant described the first weeks as the first time on a surfboard. Strategy has nothing to do with your hands, and the material is built to teach you through that discomfort rather than around it.

• I cannot tell hype from a real opportunity. The executive saw a demo and arrived enthusiastic.
• I am asked to prescribe a solution before anyone defined the problem.
• Deals die on adoption, not technology.

The four hype-resistant questions filter enthusiasm without dampening it: is the technology ready, is the business model ready, is it feasible for us, are we too late. Three-space feasibility keeps you from committing to something no one has checked.

• Downstream breakage no one anticipated.
• Everything reaches the technical team and most of it should not.
• I build what I am handed and absorb the blame when it produces nothing.

The lowest-cost way to move from receiving requirements to shaping them. Qualification and feasibility is the densest part of this course at 9 frameworks, and it is the skill that changes what reaches your team.

• I am seen as a cost center. If it is not broken, why fix it.
• Our systems do not talk to each other, so agents break.
• Every team bought a different tool and runs a different process.
• We cannot hire the skills we need.

The reframe puts everything technology delivers in top-line and bottom-line terms, which is the argument that moves a technology function out of the cost column. Expect the strategy material to feel unfamiliar if you came up through engineering.

• We are defending against the last disruption.
• Our best internal capability is trapped inside the company.
• Any business without a platform will not survive.

Route by mandate. If you own a product P&L, take this. If your mandate is enterprise transformation, the Data & AI Strategist Certification is the better fit.

• Our pricing changes keep getting reversed.
• A business model over-fitted to one technology wave cannot adopt the next.
• Our AI feature adds incremental value and incremental cost.

Week eight covers pricing and the go-to-market sequence. If pricing and packaging is the majority of your job rather than a slice of it, Platform Monetization goes considerably deeper with 18 pricing frameworks against 7 here.

• Our controls do not cover the agents we are about to deploy.
• Customers will not trust agents enough to pay for their output.
• Shadow AI is spreading and we are losing control and visibility.

Read this before you buy. Section 20 is the only governance content in the portfolio and it is written as the commercial case for trust architecture, not as a compliance curriculum. There is no EU AI Act, NIST AI RMF, ISO 42001, audit procedure, model card, or red-teaming content. If you need regulatory frameworks, this is not the course.

• We are giving data away and a partner captures the value.
• Data is treated as exhaust rather than an asset with a revenue path.
• We cannot teach customers to measure the value we are claiming a percentage of.

Take this if you commercialize the data product. If you build it, AI Product Management is the better fit. Privacy and consent for external monetization, clean rooms, and licensing law are not covered.

• We cannot justify R&D spend that might return nothing.
• No one will staff an innovation project.
• We are stuck between proof of concept and production.

Innovation economics is a full third of this course: the Profitability Tax, Phases equal Gates, and incentive design treated as part of strategy rather than an HR afterthought. If you are the individual contributor finding the opportunities rather than the director funding them, start with AI Opportunity Discovery.

• Our partnerships are transactional rather than compounding.
• We cannot see where we fit in the big platform ecosystems.
• We are fighting for share of a shrinking pie.

Eight ecosystem and partnership frameworks, more than any other course in the portfolio: the ecosystem triangle, partnership monetization, and circular partnership. Partner program design, channel economics, co-sell mechanics, and tiering are not covered.

• Innovation with no adoption journey. No killer app, friction too high, payoff too thin.
• Technology in search of a problem.
• Incumbents do not innovate until a startup forces them to.

Take this as the individual contributor finding the opportunities. If you are the director who has to fund them through gates, the Data & AI Strategist Certification carries the innovation economics. Design thinking, prototyping methods, and venture scouting are not covered.

• Clients do not know what they want or what would help them.
• Small-business CEOs demand execution detail immediately.
• I do not know how to scope or price an engagement.

Engagement scoping, typical length, and where opportunity discovery sits inside an assessment are covered in session and in office hours. Bottom-up discovery is reframed as teaching clients the two triggers, complexity and uncertainty.

• We are trying to skip to advanced technology without the foundation.
• The distance from our current platform to a modern one looks impossible.
• Every technical decision is made in isolation from the business consequence.

The L0 to L5 maturity model gives you the visible path, and the SAP case study runs twelve years without ever taking the ERP offline. The architecture content is the deepest in the portfolio at 17 frameworks.

• Every technical decision is made in isolation from the business consequence.
• We are trying to skip to advanced technology without the foundation.
• I came from a technical background and I keep meddling.

Route by what you own. If you own a product platform, Platform Monetization is the stronger fit and carries 17 architecture frameworks against 11 here. If you own enterprise architecture, take this one.

• I have to write the pricing page and no one can tell me what we are charging for.
• Our AI feature launched and conversion is single digits.

A partial fit and worth saying so. Most of the PMM job is messaging, launch, competitive intel, and enablement, and this course touches only pricing and go-to-market sequence. Week eight alone can justify it. If you own pricing outright, take Platform Monetization instead.