Step 1
Understand the lane
See what the product does, who it fits, and what is live right now.
Guided Signup
Start the founder workspace with clear pricing, guided signup, and a visible next step.
Founders can evaluate the lane, stage the workspace, and know what happens next before self-serve and checkout are fully opened.
Activation Posture
Register the workspace now and complete activation through the available path.
This path records the founder, workspace, and plan choice now, while activation continues through reviewed access or a later self-serve step.
This environment stages the founder workspace first and completes activation through reviewed access or a later self-serve rollout.
Signup should create clarity, not ambiguity. This route stages the founder identity, the workspace, and the commercial lane first, then hands off into either activation or reviewed follow-through based on the live environment.
Step 2
currentChoose the path
Pick pricing, signup, or reviewed intake without losing the same founder context.
Step 3
Open the workspace
Use the active identity path without duplicating the workspace or resetting the journey.
Step 4
Run with signal
Operate research, validation, launch, and billing from one accountable surface.
Plan context
Growth
Signup keeps plan choice attached to the workspace from the first step.
Founder email
Recovery anchor
The same founder email should carry through signup, activation, login, and billing follow-through.
Activation
Readiness-gated
This environment stages the founder workspace first and completes activation through reviewed access or a later self-serve rollout.
Fallback
Invite path primary
Duplicate founders should recover the existing workspace instead of creating a second one.
Launch readiness
Activation and commercialization posture stay visible during signup.
Signup inherits the same launch truth as the rest of the public funnel. Founders should see why staging, activation, or reviewed access behave differently across environments.
Public pricing
liveFounders can evaluate the current plan and understand the commercial lane clearly.
Public signup
liveFounders can stage the workspace from the current public path.
Self-serve activation
stagedSelf-serve activation stays staged while the identity and provisioning path are still being finalized.
Checkout
stagedCheckout stays staged until billing credentials, price mapping, and webhook handling are fully connected.
Permanent HTTPS redirect
reviewBefore calling launch complete, confirm the public edge permanently redirects HTTP traffic to HTTPS.
SPF + DKIM + DMARC + CAA
reviewBefore full launch, confirm sender-domain email authentication and certificate-authority records.
Signup
Register founder intent
Use this path to reserve the founder, workspace, and plan now. The same record can later continue through reviewed access or self-serve activation.
Before you continue
Use the real founder email
The same email carries through signup, activation, and recovery, so duplicate-workspace mistakes stay visible instead of getting silently reprovisioned.
Before you continue
Choose the workspace name you plan to keep
Signup creates a reusable onboarding record first. If the founder already exists, the flow should recover the existing workspace instead of creating another one.
Before you continue
Expect activation to follow live readiness
Public signup does not guarantee immediate self-serve. The next step stays tied to the live identity and access posture for the environment.
Plan context
Growth
$99 monthly / $990 annual
The commercial lane is staged here first so activation and billing never detach from the workspace.
Single-founder workspace
Operator-reviewed signup and invite conversion
Research, spec, launch gate, and portfolio views
Founder details
Record the founder intent clearly.
The goal is a reviewable onboarding record that can convert into invite or later self-serve without losing context.
Current Mode
Workspace details are staged first, and activation follows the active rollout path.
This form creates a reusable onboarding record without changing public routes or removing the invite fallback.
Recovery model
Signup should explain the next step before the founder commits.
A polished signup flow makes staging, recovery, and activation posture obvious instead of forcing the founder to infer them after submission.
Workspace continuity
The route should preserve one founder record.
When the founder already exists, the product should route to recovery instead of silently creating duplicate workspace ownership.
Commercial continuity
The plan should stay attached.
Signup should stage the commercial context early so pricing, activation, and billing return states all point back to the same lane.
Activation continuity
The next step should stay explicit.
Whether activation is self-serve or reviewed, the page should make the supported next move obvious.
FAQ
Signup questions founders should not have to guess at.
This flow should explain the supported path, the fallback, and what happens when a workspace already exists.
What happens after I submit signup details?
The workspace is staged first. From there, the same route can continue into activation or stay in reviewed mode, depending on the live rollout posture.
Why not create a second workspace for the same founder email?
That would erode trust and make billing, recovery, and founder identity ambiguous. The flow now favors recovery to the existing workspace instead.
Do I need Firebase configured to use signup?
No. Signup can still stage the founder record publicly while activation remains deliberate. Firebase only matters when self-serve activation is actually ready.
When should I use the waitlist instead?
Use waitlist when you want reviewed intake first, when your fit is still unclear, or when a slower handoff is the better path.
Activation discipline
Public signup should feel clear even when activation is still staged.
The product should explain what happens next, why it happens, and how the founder recovers if a workspace already exists.