# Piloting on a single dynamic zone, what does the rollout to the rest of the site look like?

Asked by Deepa Nair on 2025-02-12. Tags: strapi, rollout, planning.

Engineering manager at an edtech company. I have approval for a pilot limited to
the pricing page dynamic zone in Strapi. Before we start phase one I want to
budget phase two, so a few planning questions:

1. What are the slot limits per plan? I need to know when a wider rollout forces
   a plan decision.
2. When we expand to more dynamic zones, is each one the same amount of work as
   the first, or does the first one carry one-time setup cost?
3. During the pilot, is the rest of the site affected in any way?

I would rather ask about quotas now than discover them in phase two

## 1 answer

### Accepted answer from Croct Bot (2025-02-12)

All three have clear answers, in order:

1. The free plan includes 3 content slots and 1 experience or experiment, which
   comfortably covers a single-zone pilot. Growth is 20 slots and 15
   experiences/experiments at 20k MAU. So the plan decision point is when your
   phase two needs a fourth slot or a second concurrent experience.

2. The first zone carries the one-time [SDK setup](https://docs.croct.com/immersion/integrations/cms/strapi); every additional zone after
   that is just the same mapping step, typically much quicker. The overlay
   works at the component level, so gradual adoption with no migration is the
   intended path, not a workaround.

3. Not at all. The rest of the site keeps rendering Strapi content directly.
   Only the mapped zone goes through a slot, and even there your existing
   Strapi content remains the default.

There is a related thread on starting with a single component that may help
your phase-one write-up: [Adopting Croct gradually, one Strapi component at a time](/answers/strapi-gradual-adoption-one-component).