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.
Login Posture
Founder re-entry is available now, while new workspace activation still follows live rollout posture.
New founders can register publicly, while provisioned founders and invite recipients can return through this login surface.
Firebase sign-in is not configured in this environment yet, so invite-token access remains the supported founder return path.
Returning founders should see the fastest supported path first, the fallback path second, and a clear explanation of why both still exist in this 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.
Primary path
Invite token
Public signup is open, but founder workspace access still reopens through invite links or existing provisioned identities.
Fallback
Always preserved
Invite-token recovery stays visible even when Firebase is available, so workspace access never depends on one path only.
Founder identity
Workspace-aware
Recovery should reinforce that founder access is tied to the real workspace and founder email.
Recovery goal
Fast return, no duplicate setup
Returning founders should reopen the same workspace instead of restarting onboarding.
Launch readiness
Recovery posture stays visible, not buried.
The login surface should stay honest about launch posture. Founders need recovery that works even when self-serve or checkout are still partially staged.
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.
Founder access
Sign in with your invite.
Public signup is open, but founder workspace access still reopens through invite links or existing provisioned identities.
Authentication Mode
Signup is public, while founder re-entry still stays tied to existing provisioned identities.
Public signup can capture demand, but workspace activation still completes through reviewed access or an existing provisioned identity.
Firebase sign-in is not configured in this environment, so invite-token access remains the supported founder return path.
Recovery model
Founder recovery should feel coherent across the whole public surface.
Login is not a detached support page. It should explain the supported path, the fallback, and what the founder should do next if the workspace already exists.
Recovery principle
Return through the same product story
Founder recovery should not feel like a hidden support flow. Login stays linked to pricing, signup, and waitlist so the path remains coherent.
Recovery principle
Keep fallback visible, not buried
Invite-token access remains a first-class recovery option whenever the faster identity path is incomplete, staged, or simply not the right fit for this founder.
Recovery principle
Match identity to the real workspace
The recovery path should reinforce that founder access is workspace-aware and identity-bound, not a detached marketing login.
FAQ
Recovery questions should be answered before founders get stuck.
A polished login page tells the truth about rollout posture while still giving provisioned founders a fast path back into the workspace.
Should returning founders use Firebase or invite-token access?
Use the path the environment actually supports. When Firebase is fully available it is the faster re-entry path, but invite-token access remains valid for fallback and recovery.
Why does login still mention rollout posture?
Because founder trust improves when the login page explains the current access contract instead of pretending every environment is already fully self-serve.
What if the founder already completed signup but not activation?
The founder can return here and use the supported activation or fallback path rather than trying to restart onboarding from scratch.
Founder recovery
Re-entry should feel deliberate, not improvised.
The login surface should make the supported path obvious while preserving a safe fallback whenever self-serve is incomplete.