Getting Started
Connect Stripe, verify your app, and build and test your first Funnel.
Use Setup to connect Stripe, install your app, and review and verify the installation before creating a Funnel. You can authorize Stripe yourself; your developer or coding agent then installs SaaSFunnels and connects payment actions in your app. Authorizing Stripe alone does not complete installation.
1. Connect Stripe
Connect the merchant that sells your app's plans. Setup shows the merchant and products/prices import progress. You can begin app installation while the import runs; historical customer activity can finish in the background. Stripe Connect Setup covers authorization and import recovery.
2. Install your app
Work through these panels in Setup:
- App address: save the URL your customers use.
- Environment values: create missing credentials and save them in the destinations shown. The browser key, installation ID, and server key configure the running app. The discovery key is for your developer's local installer or CI. Values ready means the values exist, not that they are installed.
- Install and deploy: give Copy installation instructions to your developer or coding agent. The handoff covers runtime installation, trusted identity, feature/plan discovery, payment handling, and deployment. This step becomes Verified when app activity and signed-in identity are verified. Discovery results are reviewed separately in Funnel setup.
- Payment connection: an administrator saves the endpoint and two signing secrets supplied by the developer. Verification starts automatically; use Check payment connection to retry after a repair.
Keys are shown once. Copy them into your normal secrets workflow, not into a coding-agent prompt. Installing the CLI does not save credentials in your deployed environment or verify the live app. Connect Your App explains each destination and check.
Your developer can usually reuse existing Stripe payment handling and webhook delivery. A separate new webhook is not required for every customer. Verify Payments covers the connection and payment tests.
3. Funnel setup
Open Features & Plans to run discovery or review its existing results. Review prefilled configuration, answer outstanding questions, and publish the approved result. If your developer already ran discovery during installation, do not repeat the scan. A successful scan with no findings counts; a skipped, failed, or interrupted scan does not.
Product & Branding completes when you have reviewed and saved your product wording and saved your Brand kit. Funnel Drafts lets you review prepared drafts. Complete these panels to give your generated Funnels the right wording and style and prepare them for launch. Use the navigation to move between panels.
4. Review and verify
Resolve the remaining installation checks shown here.
The Stripe connection/catalog, app activity, signed-in identity, discovery/review, and payment readiness must all pass. When Installation verified appears, choose Create your first Funnel. This completes installation; it does not publish the Funnel or certify real payment transactions. The Help link in each step opens the relevant guide in another tab.
Build and launch your first Funnel
Open Funnel Studio from Setup. Choose a template or start blank, then make these decisions explicit:
- What customer event or state starts the journey.
- Which accounts and users qualify.
- Where the experience appears in your app.
- What the customer sees and what happens after dismissal.
- Who can take a commercial action and what evidence marks the goal complete.
Use Studio Targeting to bind the exact entry and placement. Test one qualifying context and one no-render context, including the app's native fallback. Publish only after identity, viewer authority, delivery, and outcome verification are safe. Read Funnels for the full model.
After launch
Use Opportunities to follow account journeys and Results to measure reach, verified conversion, revenue, and reversals. Inspect Events and Accounts when identity or event quality needs attention. Signal Readiness and Types explains what Signals need before they can inform the next iteration.
- Setup complete — installation checks pass and discovery findings are resolved. Publishing the first Funnel is a separate action.
- Activated — a real eligible user receives the published Funnel.
- Value realized — an authoritative commercial or retention outcome is recorded.