How do I count how many slots we need, is every page a slot?

Pages are not slots. The pricing FAQ defines it well: components are the reusable building blocks (like a hero section) while slots are the specific placeholders (like a home hero) where those components are rendered. A slot is a context-specific placeholder in your application, not a page.

So the counting question is: how many distinct places on the site do you want to personalize or test? A home hero, a pricing FAQ list, a checkout banner, that is 3 slots, even if your site has 40 pages. And one slot can serve many experiences and variants over time without consuming more quota. Quotas are 3 slots on free and 20 on Growth, which covers most rollouts if you start with the highest-traffic placements.

For your doc, list the placements you plan to touch in the first six months, not the site map. That number is usually much smaller than the page count.

Adding two details that helped us size correctly:

Each slot binds to exactly one component, so when you map placements, note which component type each one renders. If two placements render the same hero component in different contexts, they are still two slots (a home hero and a landing hero, say), but the component itself is defined once and reused.

Once you are live, the dashboard shows status dots per slot: grey means no requests yet, green means active, red means no requests for 7+ days. That is handy when auditing quota use later, because slots someone set up and abandoned show up red and can be reclaimed.