Onboarding

New Velocity X customer lands at the dashboard at 9am Monday. By Tuesday, they're uploading logos. Wednesday, Stripe Connect wires up. Thursday, calendar sync pulls first appointments. Friday morning, 2,000 leads ship in via CSV. By Monday week two, they flip the DNS switch and Velocity X replaces their old system. No Slack threads asking "how do I...?", no waiting for onboarding calls, no "we'll email you a setup guide later." The flow is guided, visible, and self-explanatory — because the best onboarding is the one users don't skip.

Why Structured Onboarding Wins Over "Here's Your Dashboard"

Most SaaS products dump users into the UI and hope they figure it out. "Explore the features" is polite for "we didn't design this moment." Velocity X takes the opposite angle: onboarding is a directed flow with exactly seven steps, each one unblocks the next. No rabbit holes, no optional toggles to ignore.

Users who skip onboarding churn higher. Users who follow a checklist feel like progress is being made. By day seven, when that DNS cutover happens and "Velocity X is now live", the customer doesn't feel like they're starting from zero — they feel like they've built something. That shift in ownership is worth more than a polished demo ever will be.

The Seven-Day Flow (One Step Per Day)

Day 1: Brand Prefill & Logo Upload

Customer signs up, confirms email, lands on the onboarding home. First page: "Let's set up your brand." Three inputs: company name, industry (dropdown: Sales, Insurance, Real Estate, Field Services, Other), and logo upload. These three fields are the only required fields on day one — everything else is pre-wired or can wait.

The logo uploads to Supabase storage and gets cached on the CDN. The company name auto-fills every branded email, every report header, every dashboard title going forward. Industry selection gates which template category pages light up first (a Real Estate company sees neighborhoods before insurance adjusters see territory rules). By 11am, the brand is set. Checkbox: ✅.

Day 2: Asset Finalization & Theme

Day-two users see an optional step: upload 2–3 brand colours (or pick from a palette). Velocity X uses these for dashboard accent elements, charts, and email templates. Dark mode is auto-enabled if the logo background is light. Users can customise their app's feel in under 5 minutes. Most skip this — defaults are solid. Checkbox: ✅.

Day 3: Stripe Connect (Billing & Seat Management)

Velocity X redirects to Stripe Connect auth. User signs in, approves permissions, comes back. Now Velocity X can read the account's invoice history and seat usage. Users never see a card form in Velocity X — seat billing is synced from Stripe. First-week customers get 7-day free trials on all tiers, so this day-three step often feels premature. But it's there: frictionless, non-blocking, done in 90 seconds. Checkbox: ✅.

Day 4: OAuth Integrations (Calendar, CRM Sync Start)

Calendar sync is Velocity X's killer feature for field-facing teams. Day-four step: "Connect your calendar." OAuth to Google or Outlook, grant read access, Velocity X ingests appointments and cross-references with territory/lead data. The importer starts pre-populating "next meeting dates" from real calendar pulls, no manual typing.

CRM syncs (Salesforce, HubSpot, Pipedrive) are optional on day four but appear in the checklist. "Not yet? You can always hook these up later — or skip if you're moving to Velocity X as your primary CRM." Non-blocking. Checkbox: ✅.

Day 5: Territory & Team Setup

By now, the brand is live, Stripe is connected, and calendars are syncing. Day-five step: structure the team. Input: how many sales reps? Who owns which region/territory? Velocity X has a "fast team builder" form that auto-generates territory cards and assigns reps in bulk. Upload a CSV with name, email, territory — 2 minutes, done. Or manual entry for teams under 10. Checkbox: ✅.

Day 6: CSV Lead Import (The Big Move)

By day six, the infra is ready. Teams have uploaded their logo, synced calendars, structured the team. Now comes the moment that decides whether onboarding feels like "seamless handoff" or "we're starting from scratch": import existing leads. Velocity X's CSV importer handles 50K rows in under an hour. Columns auto-detect, mapping is visual, validation is per-row, upserts are batched. Teams import 80% of their old CRM data without a single support ticket. Checkbox: ✅.

Day 7: Domain & DNS Cutover

Final step. "You're live — cut over your domain." Velocity X generates custom DNS records (CNAME for the API, MX records for inbound emails). Customer updates their domain registrar, waits for propagation (usually 1–6 hours), and Velocity X becomes the source of truth. Inbound emails to `sales@company.com` now route to Velocity X. Territory updates hit the rep's calendar. Deal wins auto-log to activity feeds. The old system becomes read-only. Checkbox: ✅.

The Checklist UI — Showing Progress at Every Step

Each day's step is one line in a persistent progress checklist that lives in the sidebar. Grey uncompleted, green when done. "Day 1: Brand setup (2m)" → ✅ "Day 2: Theme colours (5m)" → ✅ "Day 3: Stripe Connect (2m)" → ✅. Users see the light at the end of the tunnel and feel ownership. The checklist is the entire onboarding UX — no modals, no hidden steps, no "there's more stuff but we're not telling you yet."

Behind the scenes, each checklist item maps to a dashboard page (brand settings, integrations, team builder, CSV importer, DNS). Unchecked items have a "start" button. Checked items show "edit" or stay locked green. The checklist auto-refreshes every time a step completes — no page reload, no manual checking. React + Zustand watches the onboarding state store and updates the UI in real-time.

Frequently Asked Questions

Do we have to follow the 7-day flow?

No. The checklist is recommended, not mandatory. Power users can skip days 2–5 and jump straight to CSV import. But data shows: teams that complete all seven steps by day seven have 40% lower churn in month two. The flow works because it sequences setup from simplest (logo) to hardest (DNS). Skipping days is tempting but leaves gaps that support has to fill later.

What if we already have all our data in Salesforce?

CSV export from Salesforce, skip to day six, run the importer. If you want bi-directional sync after import, wire up the Salesforce integration on day four. Either way, you're live in a week.

Can we do onboarding faster?

Technically yes, but why rush? Seven days is the speed limit before users start forgetting why they signed up. If your team wants to skip the daily pacing and blast through in one session, the importer, Stripe, and OAuth all work in parallel — everything except DNS cutover (which needs time to propagate). Fast-track teams can go live in 2–3 days if they power through.

What happens if we don't complete the checklist?

Velocity X keeps working. Day three without Stripe Connect? The account goes into "trial extension" mode and features stay available. Day five without team setup? Territories are created as-needed when you log leads. Only DNS cutover at day seven is a hard blocker — without it, your domain still points to your old system. Everything else has a graceful fallback.

Can we white-label this onboarding for our customers?

Enterprise plans get a self-hosted onboarding page. Agency partners can rebrand the checklist and send it to end users as part of their own setup docs. The flow, step names, and copy are all configurable via the brand.json schema.

What if customers get stuck on the CSV import?

The importer catches 90% of data problems — bad emails, phone format mismatches, missing required fields. Error messages are row-specific: "Row 47: email 'john.at.company' is not a valid email." Users fix the CSV and re-run. If you're stuck after that, Velocity X's support team does a free ETL pass during onboarding week (included in all plans).

The Bottom Line

Best onboarding is the one you don't skip. Velocity X's seven-day flow is designed to be blindingly obvious: Day 1 is the logo. Day 7 is go-live. Everything else slots between, each step unblocking the next. No hidden settings, no "here's an admin panel, figure it out" — just a checklist that feels like progress. Teams that follow it land live and running. Teams that don't often call support asking why their calendar sync isn't working (because they never enabled it). The structure isn't just nice — it's the difference between "onboarding took three weeks" and "we cut over Monday morning."