OverviewStart briefPlansCheckoutWorkspace

SaaS Onboarding

Use a guided brief instead of asking users to describe a website from zero.

This is the front door for the site-building SaaS. A usable public product does not push customers directly into a complex admin system. It first narrows the scenario, scope, package direction, and delivery constraints in a way normal customers can finish quickly.

Start the wizardView packages first

What the user decides here

Business scenario, conversion goal, page scope, content source, domain path, and launch timing.

What the platform should output

A structured requirement brief, a recommended package, and a clean handoff into account, order, and site setup.

Why this matters

A clear SaaS intake is the difference between guided site building and forcing users to explain everything from scratch.

Build Flow

Keep the user oriented from requirement intake to package choice.

0/5 required sections completed

  1. 01Choose the build scenario
  2. 02Describe the business
  3. 03Define conversion goals
  4. 04Select pages and content
  5. 05Confirm launch constraints
  6. 06Review the requirement brief

Recommended package

体验版

This is a good low-friction entry point while the business scope and package choice are still being clarified.

Compare packages

Delivery lane

Standard launch

Guide the customer through requirements, package choice, content preparation, editing, and go-live.

Current brief

ScenarioNot selected
BusinessNot filled
GoalNot selected
LaunchNot selected

Step 1

Start with the scenario so the rest of the flow stays constrained.

Site scale