# Can we adopt Croct gradually, starting with one Strapi component?

Asked by aliciav on 2025-01-28. Tags: strapi, adoption, best-practices.

I am the tech lead at an agency. Client site runs on Strapi and the whole thing is
stable, so I want the lowest-risk pilot possible: personalize only the homepage
hero and leave every other page exactly as it is.

Is that a supported way to work or does the integration expect you to wire up the
whole site? Also any best practices for an incremental rollout would help, we want
to prove value on one component before commiting to more.

## 2 answers

### Answer from Ricardo Nunes (2025-01-28)

One component is exactly how you are supposed to start. The overlay works at
component level: you map the homepage hero to a slot in the frontend, and every
other page keeps rendering Strapi content directly, untouched. There is no
site-wide wiring step and no migration, the rest of the site does not know Croct
exists.

For rollout, the pattern we follow with clients is hero first (highest traffic,
easiest to measure), let it run a few weeks, then expand slot by slot only where
there is a hypothesis worth testing. Mapping a slot is small enough that adding
the next one is never a project.

### Answer from hbergmann (2025-01-29)

Worth knowing for a pilot: the free plan covers up to 3 content slots and 1
experience or experiment, no credit card, so a one-hero proof of concept fits
inside it comfortably. That also gives you a natural scope limit for the pilot,
one slot, one experiment, one clear result to show the client before anyone
spends money.