If TAM shows the full possibility space, SAM shows the part of that space that aligns with your product as it exists right now. It reflects the real world boundaries created by your features, platforms, languages, pricing, regulatory environment and any other constraints that define who your product is truly built for.

Using the fitness app example:

• TAM is everyone who wants to get fitter.
• SAM is the group who can actually use your current product. For instance, English-speaking iPhone users if that’s what you support today.

Inside Decidr, SAM becomes a structured expression of design intent. Because your markets, segments, workflows and constraints all live inside schema, SAM isn’t a slide in a pitch deck. It’s a computable object that shows how your product logic intersects with your market logic. It tells your apps, “These are the customers we’re able to support with the capabilities we’ve already built.”

SAM sits in the “capability” layer of Decidr’s goal structure. It describes what’s feasible based on your existing architecture. This helps your agentic apps reason about where to focus, which opportunities make sense now and where additional capabilities would be needed to expand.

In a networked organisation, SAM also stops being static. When you launch new features, expand into new regions or shift pricing, your schema updates and SAM shifts with it. It becomes a living indicator of your reachability, not a once-a-year estimate.

This makes SAM a powerful strategic signal. It highlights capability gaps, exposes market misunderstandings and shows you where your product decisions limit or unlock opportunity. It also gives your apps a grounded understanding of what’s genuinely available to them so their reasoning stays aligned with reality.

In short, SAM shows capability. It’s the slice of your full opportunity that your current product can actually serve, expressed in a structure your AI apps can use to guide smart, aligned decision making.