Public Help Center

Operational guidance for every founder using MicroSaaS Factory.

Use this guide to understand the public launch path, workspace workflow, product-lane stages, readiness labels, and the fastest recovery route when something is staged or blocked.

Start founder workspace See pricing Founder login

Read this first

This Help tab is the public operating map: confirm the supported entry path, preserve founder identity, and treat staged states as recovery instructions.

Quick start

Understand the current path before you create or reopen a workspace.

The public Help Center shows what is live now, what stays staged, and where to go when a founder needs signup, pricing, recovery, or reviewed intake.

Priority 1

Confirm the supported entry path

Start

Use pricing, signup, waitlist, or founder login based on the launch posture shown today.

Open path

Priority 2

Preserve the same founder email

Identity

Return with the same email if signup says a workspace already exists, so activation does not fork ownership.

Open path

Priority 3

Read staged states as instructions

Recovery

Controlled checkout, staged activation, or review labels mean the next safe step is visible, not missing.

Current plan

Growth

The public commercial lane founders can evaluate before workspace activation.

Pricing

Visible

Pricing visibility stays tied to public launch posture.

Activation

Guided

Signup can be live while final activation remains readiness-gated.

Checkout

Controlled

Checkout stays visible only when billing readiness and workspace eligibility align.

Workspace map

What each area is for

Use the same operating map whether you are evaluating the product publicly or already working inside a founder workspace.

Workspace area

Dashboard

Open

Capabilities

Review portfolio health, launch gates, billing posture, 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 billing.
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

Open

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

Product lanes

Open

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

Open

Capabilities

Compare the public Growth lane and current checkout posture.
Keep billing eligibility tied to workspace state and runtime readiness.
Return to the workspace without losing the commercial context.

Recommended next steps

Use public pricing to understand the active commercial lane.
Start checkout only when workspace eligibility and runtime posture allow it.
Treat controlled checkout as a readiness signal, not as missing navigation.

Workspace area

Connected operations

Capabilities

Inspect GitHub, Cloud Run, Stripe, and Resend connection status inside product lanes.
Refresh integration snapshots before trusting stale launch evidence.
Keep deployment, billing, and onboarding signals attached to product readiness.

Recommended next steps

Connect only the systems needed for the current lane stage.
Refresh stale integrations before evaluating launch readiness.
Resolve provider warnings before treating a launch gate as complete.

Workspace area

Recovery and access

Open

Capabilities

Return to an existing workspace through Firebase or invite-token fallback.
Recover staged signup work without creating duplicate founder ownership.
Keep the supported access path visible while self-serve rollout evolves.

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 billing.

Workflow map

How MicroSaaS Factory behaves end to end

The product is intentionally sequential: keep entry, workspace activation, product evidence, connected operations, and launch readiness in the same rhythm.

Step 1

Start

Choose the entry path

Use pricing, signup, waitlist, or founder login based on the launch posture shown now.

Open related surface

Step 2

Open the founder workspace

Activate through the supported identity path and keep one workspace tied to one founder email.

Open related surface

Step 3

Create a product lane

Capture the product thesis, target user, pricing hypothesis, core problem, and moat.

Open related surface

Step 4

Run research and validation

Score opportunities, capture leads, analyze transcripts, and keep follow-up work visible.

Open related surface

Step 5

Spec, build, and connect ops

Turn evidence into a spec, then connect GitHub, Cloud Run, Stripe, and Resend where applicable.

Step 6

Evaluate launch readiness

Use launch checks, billing posture, CRM pressure, and operational blockers before opening the next lane.

Launch posture

Current readiness signals on the public path

Public Help explains the same readiness language founders will see on pricing, signup, and recovery surfaces.

Public pricing

ready

Founders can evaluate the current plan and understand the commercial lane clearly.

Public signup

ready

Founders can stage the workspace from the current public path.

Self-serve activation

attention

Self-serve activation stays staged while the identity and provisioning path are still being finalized.

Checkout

attention

Checkout stays staged until billing credentials, price mapping, and webhook handling are fully connected.

Permanent HTTPS redirect

manual

Before calling launch complete, confirm the public edge permanently redirects HTTP traffic to HTTPS.

SPF + DKIM + DMARC + CAA

manual

Before full launch, confirm sender-domain email authentication and certificate-authority records.

Status and analysis notes

What the processing and readiness states mean

These labels are operational signals. They help a founder decide the next action without treating missing buttons, pending analysis, or provider errors as mystery states.

Product stages

Stages describe where a product lane is in the factory workflow, not whether the idea is good.

Research

Capture opportunity evidence, pain, audience, competition, and pricing signals.

Validate

Log leads, touchpoints, transcripts, CRM tasks, objections, and buying signals.

Spec

Turn evidence into scope, exclusions, launch criteria, and definition of done.

Build

Track repository, delivery, and connected-ops posture before calling the product launch-ready.

Launch

Evaluate integrations, revenue, support load, blockers, and final readiness checks.

Stabilize

Keep support load, revenue, blockers, and ops calm enough to consider the next lane.

CRM states

CRM state explains what validation work needs founder attention across all active lanes.

Due today

A follow-up is ready for action now and should be handled before new outreach.

Overdue

A validation task missed its intended window and may be damaging follow-through.

Snoozed

A task was intentionally delayed and will return when its reminder window arrives.

Pending analysis

A transcript was captured, but CRM intelligence extraction is not complete yet.

Launch and billing posture

Readiness labels explain what is live, staged, controlled, or blocked in the current environment.

Live

The surface is available in the current environment and can be used directly.

Staged

The route or workflow exists, but final activation depends on readiness checks.

Controlled

The action is intentionally hidden or gated until credentials, webhooks, policy, or readiness proof is complete.

Blocked

A concrete issue must be resolved before the product should claim launch readiness.

Integration states

Integration state tells you whether external proof can be trusted for launch decisions.

Connected

The provider has an active snapshot or configuration that can support workspace evidence.

Pending

The setup path exists, but a refresh, provider response, or missing value is still needed.

Error

The provider call or saved configuration failed and should be fixed before launch review.

Not connected

The product lane has not attached that provider yet, so the related proof is unavailable.

Troubleshooting

Common issues and the fastest recovery path

Use the recovery path that preserves workspace identity, launch 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.

Checkout buttons are not visible.

Open Pricing and the workspace billing section. Checkout stays controlled until workspace eligibility and runtime billing readiness are both true.

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.

Is Help public or workspace-only?

Both. Public Help explains the product path before a founder signs in, while workspace Help adds current portfolio, CRM, launch, and billing context.

Why does Help mention staged or controlled features?

MicroSaaS Factory keeps launch truth visible. If activation, checkout, or provider proof is staged, Help should explain the next recoverable step.

Where should a founder start after opening the workspace?

Start on the Dashboard, review CRM pressure and launch posture, then open the product lane with the clearest evidence, integration, or billing gap.

Does Help create support tickets or change workspace data?

No. The Help Center is read-only guidance. It links back to the existing workspace, CRM, pricing, login, and product-lane surfaces.