Guided Onboarding and Setup

Open Setup. Follow Connect Stripe → Install your app → Funnel setup → Review and verify. Setup updates automatically while you work. You can leave and return without replacing working connections.

Use the Help link in any step header for instructions specific to that step. Help opens in a new tab so you can keep your place in Setup.

Connect StripeCopy Anchor Link

Connect the merchant that sells your application's plans. Check the merchant name shown after authorization. Products and prices must finish importing; customer and activity history may continue in the background. You can start installing your app while imports run.

Use Change account only to replace the merchant. Setup will ask for new verification where the connection changed.

Install your appCopy Anchor Link

Work through the installation panels:

1. App address: enter the URL customers use. Add localhost only if you need local development.
2. Environment values: create missing values and save them in the destinations shown. All four entries belong in one list; the discovery key is for your local installer or CI only. Values ready means the credentials exist. Copying does not mark installation complete, and SaaSFunnels cannot inspect your secret manager.
3. Install and deploy: use Copy installation instructions for your developer or coding agent. The same requirements apply to a manual installation. This includes runtime installation, trusted signed-in identity, application discovery, payment handling, and deployment. This step becomes Verified after app activity and trusted signed-in identity are received. Discovery results and review appear under Funnel setup → Features & Plans; they do not hold this installation check open.
4. Payment connection: an administrator saves the backend endpoint and its two signing secrets. Verification starts automatically. An authorized installer may save the connection through the existing management API; the discovery key cannot do this.

Connect Your App lists the configuration destinations. Never paste secret values into a coding-agent prompt or commit them to your repository.

Funnel setupCopy Anchor Link

Use the Setup navigation to move between panels. Your current panel stays open while checks update.

• Features & Plans: run or resume discovery, then review its results. If your coding agent already completed the scan, review the existing results without running it again.
• Product & Branding: review and save your product wording, then save your Brand kit. A green check appears when both are saved and the wording is current. Pricing decisions belong in Features & Plans.
• Funnel Drafts: review prepared drafts when available. Ready means drafts are prepared, not published or approved. Finish this step to turn your approved configuration into ready-to-edit Funnels.

In Features & Plans, open Review findings. If an answer is needed, Decisions opens over the plans table. Expand a row, make your choice, and save it. Saved answers remain in the same list. The plans table contains your prefilled features, access, and limits.

Decisions stays in the plans header after you finish. Open it and select any row to change its answer. Its attention count includes only unanswered questions. Back to plans preserves unfinished inputs and your table position; Save and finish later saves applied changes for your return.

When questions are resolved, choose Publish configuration. A short confirmation opens over the plans grid. Choose Back to continue editing or Publish configuration to finish. Any proposed exclusions from discovery are available as optional details in that confirmation; plans, features, and add-on settings are not listed again. Setup verifies the published result automatically.

Review and verifyCopy Anchor Link

Setup checks the Stripe connection and catalog, app activity, signed-in identity, application discovery/review, and payment readiness. The progress bar counts these verification checks; it does not count created or copied credentials.

Complete every outstanding check shown here. Payment verification alone does not unlock Funnel creation. Review and verify completes only when all required checks pass and the initial discovery review queue is resolved.

A completed scan with no findings is valid. A scan that never ran, failed, or stopped halfway is incomplete. Resume an interrupted installation from your application repository:

npx --yes saasfunnels@latest setup run --resume

If developer access is not loaded, the command asks whether the key is saved in Doppler or .env.local, or shows where to create it. It requests approval before sending structured findings. It does not upload source files or grant payment permissions. If pricing cannot be extracted safely, the developer gets a manual mapping task rather than a guessed result.

When discovery needs an answerCopy Anchor Link

Known values are filled in automatically. Missing information stays unknown. For example, a limit of 10 needs a unit and reset period; an add-on needs to distinguish total units from units above an included allowance.

Choose Copy developer questions for application behavior that cannot be resolved in Setup. Your developer submits corrected structured evidence with the installer. You review the result before it can be published. Does not apply is only for findings unrelated to your application; it does not verify unsupported behavior.

After source code or reviewed answer files change, run a fresh scan:

npx --yes saasfunnels@latest setup run

Use --resume only when continuing the same interrupted scan. Existing published settings and drafts are preserved; differences require a decision. Answers survive unrelated scans. If the application code behind a question changes, that question reopens for review. If publication succeeds but verification is interrupted, Retry verification finishes that same operation without publishing again.

Create your first FunnelCopy Anchor Link

When Setup shows Installation verified, choose Create your first Funnel. This completes installation; it does not publish a Funnel or certify a real payment transaction.

Use Stripe test data to verify payment success, failure, and retry behavior. After authoring the Funnel, test its entry, targeting, placement, and outcome before publishing. Existing Funnels remain accessible if new setup work becomes necessary.