paybondpaybond
Sign in

Self-serve signup and plan selection

Which plans use `/signup`, which ones route to sales, and what buyers should expect during self-serve onboarding.

/signup is the entry point for creating a new self-serve Paybond workspace. It is available for Free Developer, Starter, Team, and Business. Enterprise buyers should begin with /contact/sales.

Which plans use signup

PlanEntry pointBest fit
Free Developer/signupSandbox-only first guardrail integration
Starter/signupOne production workflow with predictable monthly cost
Team/signupMultiple agent products that need operator workflows, disputes, and audit exports
Business/signupProduction teams that need SSO / RBAC and managed policy workflows
Enterprise/contact/salesProcurement review, custom terms, and bespoke support expectations

The routing rule is straightforward: self-serve plans start at /signup; Enterprise starts with sales.

When to use signup

Use /signup when:

  • you are creating a new Paybond workspace on Free Developer, Starter, Team, or Business
  • you want the published self-serve onboarding path without a sales process
  • you have already chosen a self-serve plan and are ready to start

Use another entry point when:

  • /console/login is needed because the workspace already exists
  • /contact/sales is needed for Enterprise onboarding, custom terms, or procurement review

In short:

  • /signup creates a new self-serve workspace
  • /console/login opens an existing workspace
  • /contact/sales starts Enterprise onboarding

What buyers should expect during signup

The self-serve flow is designed to stay simple:

  1. Choose a self-serve plan.
  2. Enter the details needed to create the workspace.
  3. Verify the owner email address.
  4. If the plan is paid, complete checkout.
  5. Activate the workspace.
  6. Continue into onboarding in the console to finish setup.

Two plan-level behaviors matter most:

  • Free Developer completes without paid checkout and is intended for sandbox-only guardrail integration.
  • Starter, Team, and Business require checkout before the workspace is fully activated for production use.

After signup

After activation, the workspace owner is taken into the console onboarding flow to complete setup for the new tenant.

From that point on:

  • future access uses /console/login, not /signup
  • available console features depend on the selected plan
  • tenant-specific business configuration is completed inside the workspace after signup

Entry-point guidance

  • Landing page CTAs for self-serve plans should lead to /signup.
  • Pricing is the public plan comparison page and the source of plan-specific CTAs.
  • Enterprise CTAs should lead to /contact/sales, not to the self-serve form.
  • Public Sign in actions should lead to /console/login.