Onboarding Data Collection for Personalization

You are improving an existing product surface for this audience: SaaS founders, product designers, and builders improving existing onboarding or setup flows.
Do not redesign the whole product. Add or refine only the form, survey, widget, or intake flow described here, and preserve the current brand, layout system, components, typography, color tokens, spacing scale, icon style, and content voice unless a change is required for usability or accessibility.

Goal:
Improve an existing onboarding, setup, or profile-completion flow so it collects the minimum useful data needed to personalize the product without delaying the user from reaching value.

Existing context to inspect first:
- Identify the current primary task, where the user has just come from, and what they still need to do after this form or feedback moment.
- Reuse existing form controls, buttons, field validation patterns, banners, sheets, dialogs, toasts, loading indicators, and analytics/event naming where available.
- Keep the visual treatment subordinate to the task. The enhancement should feel native to the current app or site, not like a pasted-in third-party widget.

Layout and content hierarchy:
- Start with a short value statement explaining how answers will tailor setup, recommendations, templates, or defaults.
- Group questions into concise steps such as role, goal, team size, current tools, and first task, but only include groups that change the product experience.
- Show progress as steps or answered count, and provide Skip for now or Finish later where data is not legally or operationally required.
- Use examples and helper text for specialized fields such as integrations, workflow type, or workspace size.

Interaction behavior and states:
- Save progress after each step and restore it if the user leaves onboarding.
- Use answers to preview the immediate product change, such as recommended template, default dashboard, or setup checklist.
- Avoid asking demographic or firmographic questions that can be inferred from account context or are not used.
- After completion, show what changed and provide an edit path in settings.
- Include these states with explicit UI copy and behavior: first visit, step complete, skipped, saved progress, restored progress, submitting, personalized result, validation error, offline retry.

Mobile and responsive behavior:
- Use one question group per mobile screen when the form is more than three questions.
- Keep progress, back, skip, and continue actions consistent and reachable with the keyboard open.
- Avoid wide option grids; use stacked cards, radio rows, or chips that wrap cleanly.

Accessibility requirements:
- Each question must have a clear label or legend, visible helper text, and properly grouped option controls.
- Progress indicators need text equivalents and cannot rely only on color or position.
- Skip and continue controls must have predictable focus order and copy that clearly explains the result.
- Errors must explain how to fix input and preserve selected answers.

Implementation constraints:
- Map each question to a product decision such as template recommendation, default setting, workspace setup, or lifecycle segmentation.
- Do not block users from the product for nonessential personalization fields.
- Persist answers to existing profile, workspace, or onboarding state models without introducing a new data store requirement.
- Emit events for step viewed, option selected, skipped, completed, restored, and edited later.

Quality checklist before finalizing:
- Every question has a visible product benefit or is removed.
- The user can skip nonessential data collection and still reach product value.
- Progress is saved and recoverable.
- Mobile steps are sized for touch and keyboard behavior.
- The final state explains what was personalized and where to edit it.

Output format:
- Return the proposed UI as an implementation-ready brief or code update appropriate to the existing project.
- Include component structure, field labels, validation copy, success/error copy, analytics events, responsive behavior, and handoff notes.
- Do not use placeholder text, fake image boxes, a new design system, a new framework requirement, or broad phrases like "make it modern".