Priority 1
Understand the lane
Review who MicroSaaS Factory is for, what is live now, and how the product keeps founder work in one operating loop.
Open pathPublic Demo CenterRead-only product tour
Demo the MicroSaaS Factory loop from signal to live revenue.
Walk through the founder workflow before creating a workspace: understand the lane, choose the path, inspect readiness, validate demand, connect operations, and keep the portfolio calm enough to compound.
Read this first
The public demo is the product map before signup: see the operating loop, understand what is live or staged, and use the current route contract without hitting an auth-only dead end.
Quick start
Understand the lane before you create or reopen a workspace.
The public Demo path follows the live site: understand the lane, choose the commercial route, and preserve the same founder identity through signup and recovery.
Start
Priority 2
Choose the commercial path
Compare the visible Growth lane, then use signup, waitlist, or founder login based on the current launch posture.
Open pathPriority 3
Open or recover the workspace
Use the same founder identity through signup and login so activation, billing, and recovery do not fork the workspace.
Open pathOperating model
Guided signup
Pricing and signup can be public while final activation still follows launch readiness.
Commercial posture
Public pricing
Founders can compare the Growth lane before activation or checkout asks them to commit.
Founder access
Invite-aware
Founder login and invite-token fallback stay visible while faster identity paths mature.
Guided demo
Six surfaces, one founder operating loop.
Each step is intentionally tied to an existing MicroSaaS Factory surface, so the demo explains how the product works without adding a separate sample workspace or fake data layer.
Step 1
Signal
Start with the market thesis, target buyer, pricing hypothesis, and the one problem the founder is trying to prove.
Opportunity score
Demand, urgency, pain, and moat are reviewed before scope grows.
Capture product thesis and target user in one lane.
Keep pricing and moat assumptions visible from the first pass.
Separate real signal from founder enthusiasm before build work expands.
Step 2
Validate
Move customer discovery into a CRM lane that keeps leads, touchpoints, transcripts, objections, and follow-up work together.
Follow-up debt
Due work, objections, and buying signals stay attached to product decisions.
Track validation targets and touchpoints beside transcript analysis.
Turn sessions into CRM intelligence and follow-up tasks.
Use recurring objections to tighten positioning and scope.
Step 3
Spec
Translate validation evidence into scope, exclusions, launch criteria, and a definition of done the founder can actually operate.
One-page spec
Evidence becomes a build contract instead of a loose backlog.
Keep v1 features and exclusions explicit.
Connect launch criteria to the customer evidence already collected.
Stop unreviewed ideas from becoming hidden delivery commitments.
Step 4
Build
Attach delivery state to the same product lane so repository, Cloud Run, Stripe, and Resend posture do not drift away from the launch decision.
4 lanes
GitHub, Cloud Run, Stripe, and Resend can be reviewed beside the product.
Review implementation state without leaving the product lane.
Refresh provider snapshots before trusting old operational evidence.
Keep billing and onboarding readiness visible during delivery.
Step 5
Launch
Use launch gates, checkout posture, CRM pressure, and external verification to decide whether the product is ready for public motion.
Pass / review
Readiness is shown as an operating decision, not a marketing claim.
Inspect blockers before moving a product toward revenue.
Keep checkout controlled until workspace and runtime readiness are true.
Use final edge and sender-domain checks as explicit launch evidence.
Step 6
Operate
Return to the founder control tower to compare active lanes, support load, billing posture, and readiness for the next product slot.
Portfolio view
The workspace compounds only when current lanes are calm enough.
Review active, archived, passed-gate, and ready-for-next counts.
Use activity history to see what changed and why.
Open another lane only when support, CRM, and launch posture allow it.
Live posture
The public demo reflects what the launch funnel can safely do today.
Demo keeps the staged and live parts of the product visible so founders can evaluate the operating loop without guessing about activation or checkout.
Public pricing
readyFounders can evaluate the current plan and understand the commercial lane clearly.
Public signup
readyFounders can stage the workspace from the current public path.
Self-serve activation
attentionSelf-serve activation stays staged while the identity and provisioning path are still being finalized.
Checkout
attentionCheckout stays staged until billing credentials, price mapping, and webhook handling are fully connected.
Permanent HTTPS redirect
manualBefore calling launch complete, confirm the public edge permanently redirects HTTP traffic to HTTPS.
SPF + DKIM + DMARC + CAA
manualBefore full launch, confirm sender-domain email authentication and certificate-authority records.
Workflow spine
One operating rhythm from market signal to live revenue.
The Demo tab follows the same public product story: market signal, customer validation, scope control, connected operations, launch truth, and ongoing portfolio discipline stay in one loop.
Step 1
StartScore market demand
Use a repeatable opportunity rubric and AI-backed readouts before product scope grows.
Open related surfaceStep 2
Run validation in one lane
Keep leads, interviews, objections, transcripts, and follow-up work attached to product decisions.
Open related surfaceStep 3
Turn evidence into scope
Convert market signal into a one-page spec with launch criteria and explicit exclusions.
Open related surfaceStep 4
Attach connected operations
Review GitHub, Cloud Run, Stripe, and Resend posture beside the product instead of in side documents.
Open related surfaceStep 5
Evaluate launch truth
Use gate status, checkout posture, CRM pressure, and external verification before public motion.
Open related surfaceStep 6
Operate the portfolio
Compare active lanes, support load, billing posture, and readiness for the next product slot.
Open related surfaceWhat the demo proves
The product story stays attached to operating evidence.
Demo is intentionally read-only: it shows the workflow, current posture, and expected operating rhythm without creating hidden state.
One founder record carries the journey.
Pricing, signup, login, workspace recovery, and product lanes stay tied to one founder context instead of fragmenting into separate tools.
Launch truth stays visible.
The demo keeps staged activation, controlled checkout, and external verification in view so founders understand what is live, staged, or still under review.
Connected systems stay inside the lane.
GitHub, Cloud Run, Stripe, Resend, CRM intelligence, and billing posture are treated as product operating evidence, not a side checklist.
FAQ
Demo questions founders should not have to infer.
The Demo tab is a product tour and context bridge, not a new request-demo workflow or hidden mutation path.
Does the Demo tab create or mutate workspace data?
No. The Demo tab is a read-only walkthrough. It links to existing signup, pricing, login, dashboard, CRM, and product-lane surfaces without creating new records.
Why is there a public demo and a workspace demo?
The public demo explains the operating loop before signup. The workspace demo uses current founder context so signed-in founders can see the same loop with their own portfolio signals.
Does this replace the Help Center?
No. Help is recovery and operating guidance. Demo is a guided tour of how MicroSaaS Factory moves from signal to validation, build, launch, and ongoing operation.
Why does the demo mention staged or controlled states?
MicroSaaS Factory keeps rollout truth visible. Staged activation or controlled checkout are shown as readiness states, not hidden failures.
Why does Demo link back to existing surfaces?
The Demo tab should explain the product without inventing a second workflow. Every path points back to signup, pricing, dashboard, CRM, or product lanes that already exist.