Priority 1
Choose the smallest entry path
Use pricing, signup, waitlist, or founder login based on whether the founder needs validation, review, or recovery.
Open pathPublic Help Center
Find the right next step: validate, upgrade, or recover.
Use this guide to choose between the $9 validation, a Growth upgrade, and recovery when a founder already has a record.
Read this first
This Help tab is the public operating map: confirm the validation-first path, preserve founder identity, and keep recovery instructions easy to find.
Quick start
Choose between validation, Growth, and recovery.
The public Help Center shows when to buy the $9 report, when Growth makes sense, and how founders recover the same workspace.
Start
Priority 2
Preserve the same founder email
Return with the same email if signup says a workspace already exists, so ownership does not fork.
Open pathPriority 3
Keep recovery visible
Even when the public path is direct, recovery and reviewed intake stay visible for founders with more context.
Open pathCurrent plan
Single Validation
The public commercial lane founders can evaluate before opening a workspace.
Pricing
Two plans
Pricing explains the validation-first path before a founder upgrades.
Validation
$9 first
The single validation report is the first paid checkpoint.
Workspace
Upgrade later
Growth is the workspace path after a credible report.
Workspace map
What each area is for
Use the same map whether you are evaluating the product publicly or already working inside a founder workspace.
Workspace area
Dashboard
Capabilities
- Review portfolio evidence, launch gates, revenue context, and recent activity in one place.
- Create or reopen product lanes without losing the workspace context.
- Decide whether the portfolio can support another product lane.
Recommended next steps
- Start every work session here before changing scope or revenue assumptions.
- Use active, archived, and ready-for-next counts to decide where attention goes first.
- Open the product lane that has the clearest next operating move.
Workspace area
Workspace CRM
Capabilities
- Track due, overdue, snoozed, and pending validation work across active products.
- Review transcript analyses, objections, pain points, and follow-up tasks.
- Keep repeated customer signals close to product and launch decisions.
Recommended next steps
- Check overdue and due-today work before creating new research.
- Review pending analysis when CRM insight looks incomplete or stale.
- Use objection clusters to sharpen positioning and scope.
Workspace area
Opportunity Intelligence
Capabilities
- Upload PDF, PPTX, DOCX, XLSX, and structured notes as founder-owned opportunity evidence.
- Review cited scorecards, SWOT, warnings, fallback state, benchmarks, Scout rankings, and decision memos.
- Import provider-neutral records into the Evidence OS module registry without enabling live external adapters.
- Convert the strongest evidence report into a product lane with validation tasks, spec anchors, and launch criteria.
Recommended next steps
- Start with source material before creating a product lane from a hunch.
- Use confidence, warnings, and citations to decide whether to advance, validate, or park.
- Use the Opportunity Quality Guide and Trust page when you need the public evidence policy.
- Convert only after the next validation move is clear.
Workspace area
Product lanes
Capabilities
- Move one product through research, validation, spec, build, ops, and launch.
- Keep the product thesis, target user, pricing, and launch checklist together.
- Archive lanes without losing their operating record or recovery path.
Recommended next steps
- Open the lane with the largest launch, evidence, or integration gap.
- Use the stage navigation instead of jumping across unrelated forms.
- Archive lanes that should not affect active portfolio decisions.
Workspace area
Pricing and billing
Capabilities
- Compare the $9 validation and Growth workspace paths.
- Keep paid upgrades tied to workspace ownership and plan context.
- Move eligible workspaces into Growth without losing the commercial context.
Recommended next steps
- Use public pricing to understand the active commercial lane.
- Upgrade only when the workspace is eligible and the founder is ready.
- Treat unavailable upgrade buttons as workspace guidance, not a second pricing path.
Workspace area
Connected operations
Capabilities
- Inspect GitHub, Cloud Run, Stripe, and Resend connection context inside product lanes.
- Refresh integration snapshots before trusting stale launch evidence.
- Keep deployment, revenue, and onboarding signals attached to product decisions.
Recommended next steps
- Connect only the systems needed for the current lane stage.
- Refresh stale integrations before evaluating launch evidence.
- Resolve provider warnings before treating a launch gate as complete.
Workspace area
Recovery and access
Capabilities
- Return to an existing workspace through the supported sign-in or invite-token fallback.
- Recover signup work without creating duplicate founder ownership.
- Keep the supported access path visible while direct access remains available.
Recommended next steps
- Use founder login if signup reports an existing workspace.
- Keep invite-token fallback visible for reviewed recovery.
- Use the same founder email across signup, login, pricing, and recovery.
Workflow map
How MicroSaaS Factory behaves end to end
The product is intentionally sequential: validate first, keep founder identity stable, and upgrade only when the report supports the next step.
Step 1
StartChoose the entry path
Use pricing, signup, waitlist, or founder login based on whether the founder needs validation, review, or recovery.
Open related surfaceStep 2
Preserve one founder identity
Use the supported identity path and keep validation, upgrade, and recovery tied to one founder email.
Open related surfaceStep 3
Create a product lane
Capture the product thesis, target user, pricing hypothesis, core problem, and moat.
Open related surfaceStep 4
Run opportunity intelligence and validation
Upload source material, review evidence reports, capture leads, analyze transcripts, and keep follow-up work visible.
Open related surfaceStep 5
Spec, build, and connect ops
Turn evidence into a spec, then connect GitHub, Cloud Run, Stripe, and Resend where applicable.
Step 6
Make the build/no-build call
Use customer proof, scope limits, revenue context, and CRM pressure before opening the next lane.
Buyer path
Current public path decisions
Public Help explains when to validate, when to upgrade, and when to recover an existing founder record.
$9 validation
GuideStart with the single validation report when the founder needs evidence before workspace commitment.
Growth workspace
GuideUse the Growth workspace after a report shows enough buyer signal to keep building.
Founder recovery
GuideReturn with the same founder email when a workspace or signup record already exists.
Path questions
When to validate, upgrade, or recover.
Public Help keeps the commercial path simple enough to choose without reading internal launch notes.
Validate first
Use the $9 report when the next decision is whether the idea deserves a build cycle.
Upgrade later
Use Growth when the report shows enough buyer evidence to need the founder workspace.
Recover instead
Use founder login when the same email already has a workspace or signup record.
Troubleshooting
Common issues and the fastest recovery path
Use the recovery path that preserves workspace identity, report proof, and the existing operating record.
Signup says a workspace already exists.
Use Founder login with the same founder email. MicroSaaS Factory recovers the existing workspace instead of creating duplicate ownership.
Growth upgrade is not the right next step.
Open Pricing and start with the $9 validation when the idea still needs proof. Growth belongs after a credible report.
CRM insight looks incomplete.
Open Workspace CRM, review pending analysis, then return to the product validation lane if a transcript needs retry or more context.
A launch gate is blocked.
Review the launch checklist, integration status, revenue metrics, support load, and critical blockers before re-running the launch gate.
GitHub, Cloud Run, Stripe, or Resend data looks stale.
Refresh the specific integration inside the product ops or build stage before trusting the snapshot in a launch decision.
A product is no longer part of active work.
Archive the lane to remove it from active rollups while preserving the URL, activity record, and restore path.
FAQ
Help Center questions founders should not have to guess at
Help is meant to shorten the path to the right workspace surface without changing data or creating a support workflow.
Both. Public Help explains the product path before a founder signs in, while workspace Help adds current portfolio, CRM, launch, and revenue context.