> 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/intro/what-is-jimo/choose-your-first-use-case.md). # Choose your first use case Pick one use case, build one experience for it, get it live for real users, then widen. Accounts that start with three use cases at once end their trial with three drafts. Accounts that start with one end it with something live and a plan for the next two. *** ## Pick one Most teams arrive with two or three goals. Write them down, then choose the one that meets all three conditions: 1. You can describe the moment it happens in your product ("after signup, on the dashboard", "when they open Reports for the first time"). 2. You can tell whether it worked without a developer: a step completed, a button clicked, a survey answered. 3. It does not depend on user data you do not send to Jimo yet (plan, role, signup date). If it does, keep it for level 3 of the [learning path](/docs/intro/what-is-jimo/your-learning-path.md).
Several goals pass three filters, one comes out as the first goal

Three filters, one goal to start

Keep the other goals: [What to build next](/docs/getting-started/what-to-build-next.md) picks them up once the first one is live. ## From use case to experience The onboarding flow pre-generates drafts for the goal you picked at signup. This table says what to finish first and what to leave for later. | Your goal | Family | Build first | Add at the next level | Avoid at first | | ----------------------------------------------------------- | ----------------- | ---------------------------------------------------------------- | ------------------------------------------------------------------------- | --------------------------------------------------- | | Onboard new users | Guide | A short welcome tour, 3 to 5 steps, on your main screen | A checklist whose tasks launch tours, then a Resource Center | A tour with 12 steps across 6 pages | | Get a feature used | Guide | A modal or a hint on the feature, no sequence | A tour from the hint, a goal to measure | Targeting the feature to everyone with no condition | | Announce a release | Announce | A changelog post, then a banner pointing to it | A modal for admins only, a segment "has not seen" | A blocking modal for all users | | Give help in context | Guide, self-serve | A Resource Center with links and a contact, no element targeting | Blocks per page and per audience, an embedded checklist, the Agent | Hints on every control at once | | Collect feedback | Collect | An NPS or a one-question survey, triggered on a page | A survey as a branching point to the right checklist, Slack notifications | A 10-question survey on first login | | Replace another tool (Appcues, Intercom, Userpilot, WalkMe) | Any | Rebuild the one flow your users see most, as is | Parity flow by flow, then what the old tool could not do | Rebuilding everything before anything is live | {% hint style="warning" %} **Element targeting is the first thing that breaks.** Modals, banners, surveys and the Resource Center need no CSS selector, so they survive any front-end change. Tours and hints point at elements, so they depend on [stable selectors](/docs/getting-started/create-your-first-experience/stable-selectors-on-a-dynamic-front-end.md). If your front-end regenerates its classes and IDs, start with an experience that targets nothing, and bring your developer in before the first tour. {% endhint %} ## What changes with your profile | You are | Lean on | Postpone | | --------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------- | | Product, CS or ops, no developer at hand | The Chrome extension, the generated drafts, preview. Send the [Install Jimo](/docs/getting-started/install-jimo.md) page to a developer now, it takes them an hour and you will need it at Step 4. | Segments on user data: build now, target "everyone" or your own test segment, segment later | | A developer or a technical PM | [Install Jimo](/docs/getting-started/install-jimo.md) in full, with identify, attributes and events from day one | Nothing. You can run the whole Getting started in a day. | | A product whose users are not very digital | A checklist where each task launches a short tour and holds a video or a PDF in the same block, and a Resource Center early | The Agent, until users are comfortable with the product itself | | An admin who wants the Agent for a part of the users only | A Launcher filtered on an "admins" segment, or a Resource Center per audience with and without the Ask Agent block | Skills and the MCP, second level | ## Related * [Your learning path](/docs/intro/what-is-jimo/your-learning-path.md) * [First experience by goal](/docs/getting-started/create-your-first-experience/first-experience-by-goal.md): the same table, with the exact steps in the builder * [What to build next](/docs/getting-started/what-to-build-next.md)