Launch a small SaaS

This is a design starter, not a verified live automation. The example output is illustrative. No provider run has been verified for this pack.

• Planning needs no external app connection. Generation uses the selected model and its funding path.
• Launch checks need a reachable preview URL and hosted Browser availability. Private previews may require a saved session.
• Publishing, billing changes, and outbound messages require separate scoped access and approval. This pack does not deploy a product.

Create a Product Plan for a client approval portal for freelance designers. Start with one workspace, client invitations, design uploads, comments, and approval history. Include a two-week MVP, non-goals, acceptance criteria, a launch checklist, and an activation metric. Keep payments in test mode. Ask me about unknown constraints before assuming them.

An MVP with five core features, a client-invitation-to-first-approval journey, and a launch checklist covering access, billing tests, failed uploads, and recovery. Sample activation metric: a workspace receives its first client approval within seven days; validate the target with real users.

• An invited client can view only authorized projects
• An approval records the actor, version, and timestamp
• Duplicate payment webhooks do not duplicate entitlements
• Failed uploads preserve the draft and offer retry

Adapt the existing launch workflow after reviewing the plan. Connections and live checks are still required.

1. 1Review the Product Plan and replace the sample scope with your own requirements.
2. 2Inspect the connected Architecture starter. Ask Codelit to adapt it to your approved scope; these starters do not automatically synchronize edits.
3. 3Try one bounded task with your real inputs. Review connections, costs, permissions, and evidence before enabling recurring work or approving any external action.

Keep the existing evidence and resolve the specific blocker before retrying.

• If scope is too broad, ask to keep only invitations, uploads, and approvals for the first milestone.
• If a preview cannot be reached, check access and retry a read-only inspection. Do not mark the launch check as passed.
• Before retrying a write with an unknown outcome, check the provider receipt to avoid duplicate actions.

These are proposed measures, not claims about observed customer results.

• Measure time from workspace creation to first client approval
• Track invited clients completing a review
• Track weekly returning workspaces; establish a baseline before setting targets