> For the complete documentation index, see [llms.txt](https://help.usejimo.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.usejimo.com/docs/getting-started/what-to-build-next.md).
# What to build next
Your first experience is live. The Get Started page stops here; this page does not. It says what the next level is for each goal, in the order that has worked for other accounts: tours, then a checklist, then a Resource Center, then measurement, then the Agent.
**You will have at the end:** a plan for the next two weeks, one experience at a time.
***
## Two things first
#### Watch the first one for a week
Open its [Analytics](/docs/analyze/analytics.md): views, completion, where users drop. A tour that loses half its users at step 3 needs a shorter step 3, not a second tour.
#### Get identify and attributes in, if they are not
Everything below that says "segment" needs them. See [Attributes and events](/docs/getting-started/install-jimo/attributes-and-events.md).
## The next level, by goal
| You started with | Build next | Then |
| ------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------- |
| A welcome tour | A checklist whose tasks launch short tours, opened by the welcome tour's last button. [Checklist and tours together](/docs/getting-started/create-your-first-experience/checklist-and-tours-together.md) | A Resource Center that holds the checklist, so users find it after closing it |
| A modal or a hint on a feature | A [Goal](/docs/publish/mesure-outcomes-goal.md) on the feature's event, to see whether the nudge changes anything | A tour launched from the hint's button for users who click "show me" |
| A changelog post and a banner | A modal for admins or one plan, with a "has not seen" condition in Who | A changelog trigger in your app's header, so users browse updates on their own. [Changelog](/docs/experiences/changelog.md) |
| A Resource Center | Blocks that change per page and per audience, a checklist embedded in it. [Resource Center components](/docs/experiences/resource-center/components.md) | The Agent inside it, for the questions your links do not answer. [Bring in the Agent](/docs/getting-started/what-to-build-next/bring-in-the-agent.md) |
| An NPS or a survey | A survey as a branching point that sends each answer to a different checklist. [Patterns that work](/docs/getting-started/what-to-build-next/patterns-that-work.md) | Slack notifications on answers, [exports](/docs/analyze/users-and-segments/data-management/exports.md) |
## Measure before you multiply
A [Goal](/docs/publish/mesure-outcomes-goal.md) on an experience compares users who saw it with users who did not, on an event you choose. A [Success Tracker](/docs/analyze/success-tracker.md) follows a sequence of events across experiences, your activation funnel. [A/B tests](/docs/analyze/a-b-test.md) settle whether a modal or a tour works better. Set one of these up before the fifth experience, or you will never know which ones to keep.
## Organize as you grow
* One [Space](/docs/build/spaces.md) per journey or per release, so the dashboard stays readable past twenty experiences.
* A [theme](/docs/build/theme.md) saved from your best experience, applied to all the others.
* [Multiple languages](/docs/build/multiple-languages.md) on the experiences your users see most, before the ones they see once.
* [Rate limiting](/docs/publish/trigger-at-the-right-time-when/rate-limiting-prevent-overwhelming-users.md) tuned once you have more than three experiences on the same page.
## Drive it from your tools
The [Jimo MCP](/docs/integrations/mcp.md) lets Claude, Cursor or another AI assistant read your analytics, draft and edit any experience, wire experiences together, set where and when they show, translate them, run A/B tests, and train the Agent, from a chat. Every change your users would see is previewed first. Useful once you have enough experiences for "which tour has the worst completion rate" to be a real question. See [What to ask](/docs/integrations/mcp/what-to-ask.md) for examples.
{% hint style="info" %}
**Keep a human in the loop.** During the trial, a follow-up call with the Jimo team is the right moment to map your second and third use case onto these building blocks. Book it from the chat before the trial ends.
{% endhint %}
## Go further
* [Patterns that work](/docs/getting-started/what-to-build-next/patterns-that-work.md): the combinations we see succeed, with the settings to copy.
* [Bring in the Agent](/docs/getting-started/what-to-build-next/bring-in-the-agent.md): when, for whom, and how to contain its usage.
* [Your learning path](/docs/intro/what-is-jimo/your-learning-path.md), levels 4 and 5.
