Onboarding screen for collecting company information including name, team size selector chips, and industry dropdown. Perfect for B2B SaaS apps that need organizational context during setup.
Company-details form combining a text input for company name, a row of team-size chips, an industry dropdown, and a role input, though only the team-size chips are backed by real component state.
Pro blocks install through the shadcn CLI with your license key and ship their full source. Docs and live previews stay open to everyone, so you can read every block's details first.
Swap YOUR_EMAIL and YOUR_KEY for the email and license key on your account. Find your license key on your account page.
Radix flavor
npx shadcn add "https://ui.beste.co/r/onboarding29?email=YOUR_EMAIL&license_key=YOUR_KEY"Base UI flavor
npx shadcn add "https://ui.beste.co/r-base/onboarding29?email=YOUR_EMAIL&license_key=YOUR_KEY"This installs the block to components/beste/block/onboarding29.tsx and the badge, button, input, and select shadcn/ui primitives it depends on.
The installed file exports onboarding29Demo alongside the block: the exact props behind the preview above. Spread it to get a working company-info step in one line.
import { Onboarding29, onboarding29Demo } from "@/components/beste/block/onboarding29";
export default function OnboardingPage() {
return <Onboarding29 {...onboarding29Demo} />;
}Then replace the demo with your own props. Written out, a trimmed setup looks like this:
import { Onboarding29 } from "@/components/beste/block/onboarding29";
export default function OnboardingPage() {
return (
<Onboarding29
badge={{ label: "Company", variant: "secondary" }}
heading="Tell us about your company"
description="This helps us tailor the platform to your organization's needs."
teamSizes={[
{ id: "solo", label: "Just me" },
{ id: "small", label: "2-10" },
{ id: "medium", label: "11-50" },
]}
industries={[
{ value: "saas", label: "SaaS / Software" },
{ value: "ecommerce", label: "E-Commerce" },
{ value: "other", label: "Other" },
]}
primaryButton={{ label: "Continue", href: "/setup/next" }}
secondaryButton={{ label: "Skip for now", href: "/dashboard" }}
/>
);
}| Prop | Type | Default | Description |
|---|---|---|---|
badge | { label: string; variant?: "default" | "secondary" | "outline" } | – | Small badge above the heading |
heading | string | – | Main headline |
description | string | – | Supporting copy below the heading |
teamSizes | TeamSize[] | [] | Team-size chip options |
industries | Industry[] | [] | Industry dropdown options |
primaryButton | { label: string; href: string } | – | Primary CTA link, always enabled |
secondaryButton | { label: string; href: string } | – | Secondary CTA link, always enabled |
labels | { stepOf?: string; companyName?: string; companyNamePlaceholder?: string; teamSizeTitle?: string; industryTitle?: string; industryPlaceholder?: string; roleTitle?: string; rolePlaceholder?: string } | – | Field labels, placeholders, and the step template |
currentStep | number | 1 | Current step number, used only to fill the step-of label |
totalSteps | number | 4 | Total step count, used only to fill the step-of label |
className | string | – | Extra classes for the outer <section> |
type TeamSize = { id: string; label: string };
type Industry = { value: string; label: string };selectedSize state, single-select, toggled via setSelectedSize); the company-name Input, industry Select, and role Input are all uncontrolled and unbound to any state, so nothing typed or picked in them is captured by the component.Select has no value/defaultValue, so it always opens empty even though industries provides a full option list to choose from.primaryButton and secondaryButton are always-enabled links regardless of whether a team size, industry, or any text field has been filled in; there is no validation gating on this screen.currentStep/totalSteps only feed the static "Step of " label above the form; there is no wizard state transition tied to form completion.Wiring the form up
This block ships the form markup only; state, validation, and submit are yours to add. Our guide wires the shadcn Field primitives to React Hook Form, TanStack Form, and Formisch on one field system.
onboarding26
Onboarding screen with import options from other platforms, CSV upload, and manual entry. Perfect for SaaS migration flows that help users bring existing data into the platform.
onboarding22
Onboarding screen showing current plan details with visual usage bars for storage, seats, and API calls. Perfect for SaaS post-signup flows that introduce plan limits and upgrade paths.
onboarding19
Onboarding screen with a form card for setting up user profile including avatar, display name, bio, and timezone. Perfect for the personal details step in any SaaS onboarding flow.
onboarding23
Onboarding screen for configuring account security including two-factor authentication, recovery email, and backup codes. Perfect for apps that prioritize security during onboarding.
onboarding27
Onboarding screen with a quick survey asking how the user discovered the product, with selectable options and an optional text input. Perfect for marketing attribution during signup.
onboarding20
Onboarding screen with a grid of starter templates to choose from, each with a preview thumbnail, title, and description. Perfect for project creation flows in design tools and project management apps.