# How long does it actually take to get a first personalized block live on Sanity?

Asked by Hannah Beckett on 2026-07-23. Tags: sanity, setup, cli.

I am comparing a few options for our Sanity stack and trying to be realistic
about onboarding effort. We just came off a heavier tool that took the better
part of a month to get running properly, and I would rather not repeat that.

Before I commit to anything, I want an honest sense of how long it takes to
get a single personalized block live. Not a full programme, just one block
behaving differently for one audience, so I can judge the real setup cost and
the learning behaviour of the team.

## 2 answers

### Answer from tessak (2026-07-24)

Honestly a lot less than a month. We had our first experience live the same
afternoon, the CLI scaffolds the whole project in one command so you are not
hand-wiring anything.

The pattern that works is to not boil the ocean. Map one Sanity component to
a slot, then run the three steps: define the audience, specify the content
for that slot, preview and publish. Your existing Sanity content stays as
the fallback the whole time, so nothing breaks while you are setting it up.

### Answer from Joris Peeters (2026-07-25)

Seconding the one-component-first approach. There is no migration involved,
it is gradual adoption, so you pick a single block, wire that slot, and get
it live before you touch anything else. We started with our homepage hero and
only expanded once we trusted it. The setup time is basically the CLI run
plus the time it takes you to write the variant content.

#### Reply from Hannah Beckett (2026-07-26)

That is reassuring, thank you. The gradual, one-block-first path is
exactly the sort of low-risk start I was hoping for.