Back to Skills
Strategy/ai-product-strategy

AI Product Strategy

Develop AI product strategy and identify AI opportunities for your product. Build, buy, or partner?

Time Saved

3-4 hours → 45 min

Compared to doing it manually

Slash Command

/ai-product-strategy

Type this in Claude to run the skill

The Problem

Everyone says "add AI" but you don't know where it makes sense for your product. You don't want to build AI for AI's sake, but you also don't want to miss the boat. You need a framework to identify real opportunities vs hype.

What You Get

  • ✓High-impact AI opportunities ranked by feasibility
  • ✓Build vs Buy vs Partner analysis with recommendations
  • ✓Data moat assessment (do you have defensibility?)
  • ✓Model selection guidance
  • ✓UX considerations for AI features (transparency, control, trust)
  • ✓Implementation roadmap with phases and success metrics

How to use this skill

  1. 1Download the skill file using the button on this page
  2. 2Add the file to your .claude/skills/ folder in your project
  3. 3Type /ai-product-strategy in Claude to run the skill

Best For

Evaluating where AI can add real value to your productMaking build/buy/partner decisions for AI capabilitiesAssessing if your data creates a competitive moatPlanning AI feature rollout with user trust in mind

Related Skills

Strategic Roadmap Review

/strategic-roadmap-review

A facilitated thinking exercise: look back at what happened, then look forward to set strategic direction — before building the tactical roadmap.

Prioritization Engine

/prioritization-engine

Score and rank features using RICE, ICE, or weighted scoring with clear documentation.

North Star Finder

/north-star-finder

Identify and validate your product's North Star metric with supporting input metrics.

Go-to-Market Strategy

/go-to-market-strategy

Creates a complete GTM plan with channels, messaging, timeline, and success metrics

Frequently Asked Questions

AI product strategy identifies where AI can add real value to your product (not just "AI for AI's sake"), evaluates build vs buy vs partner options, and assesses if your data creates a competitive moat.

No. Add AI where it solves a real user problem better than alternatives. If your product works fine without AI, or if AI adds complexity without clear benefit, skip it. AI should be a means to an end, not the end itself.

Building gives you control and potential data moat but requires ML talent and data infrastructure. Buying (3rd party APIs) is faster and cheaper but limits differentiation. Partner when you need capabilities you can't build but want more control than an API.

Ask: Is your data unique (not publicly available)? Does more data make the product better (data flywheel)? How long until competitors catch up? If you have proprietary data that improves with usage, you likely have a moat.