Integrations

Integrations is how SaaS Founder OS connects to the outside tools a builder uses every day: the places you look for design inspiration, the AI platforms that build your app, and the payment providers that hold your revenue numbers.

What it is (and what it isn't)

The catalog lives in Settings → Integrations and every service sits in one of three categories:

• Research & design services — where you find real screens and flows (Mobbin, Page Flows, UI Sources, Screenlane, Nicelydone, Refero, UX Archive). These feed the product research prompt that external AI tools use.
• Build platforms — where the app gets built (Claude Code, Cursor, Warp, Lovable, Replit, v0, OpenHands, Devin, Cursor Cloud Agents, and more). These are the targets of the Build It prompts.
• Payment & data providers — where your revenue lives (Stripe, RevenueCat, Paddle, Polar, Lemon Squeezy, Chargebee). These feed the Live Data Feeds and the Stripe pull connection.

Every service shows how it can be connected, in plain terms:

A yellow "verify before connecting" badge means the capability was researched but not confirmed against the vendor's docs — it still gets the prompt handoff, but SaaSFO won't claim more than it knows.

Workspace catalog vs product selection

Two levels, two jobs:

• Workspace (Settings → Integrations) — the catalog you curate: toggle services on/off, and set credential pointers. Toggling a service off hides it from every product's selection.
• Product (Settings → Integrations) — the selection for that product: which research service its research prompt uses, which build targets are available (only the checked ones appear in Build It's Prompts tab), and your prompt rules (one per line, appended to every build prompt — e.g. "Mobile apps use Expo"). New products can inherit all of it from a template.

Best practice: keep everything enabled at the workspace level unless a service is truly off the table, and do the per-product narrowing on the product. Templates then carry the rules and preferences (never data) — that's what makes a "mobile app template" behave differently from a "web app template" while the numbers always come from the live product.

Credential pointers (never secrets)

Add pointer records where the credential lives — env:MOBBIN_KEY, a 1Password item, a password-manager note — never the secret itself. Same rule as Build → Connections: secrets stay in your environment or your password manager; the catalog only remembers the pointer so nothing lives only in one founder's head.

Stripe pull (beta)

Per product (Settings → Integrations): connect a restricted read-only Stripe key and SaaSFO pulls MRR, customers, and one-time sales daily — the same honest snapshots and provenance as the push webhook, with zero plumbing in your app. "Pull now" refreshes immediately; the stored key is encrypted at rest and only its last 4 characters are ever shown. Requires INTEGRATIONS_ENCRYPTION_KEY to be set on the server. See Live Data Feeds for the push alternative — both write the same ledger and can coexist.

Best practices

• Start with prompt handoff. It costs nothing, works with every service, and is the honest baseline — the PRD URL + prompt is a complete handoff.
• Fill the Playbook first. An incomplete playbook produces an incomplete PRD regardless of which services you enable — the readiness score in Build It tells you exactly what's missing.
• Restrict keys. When a provider connection needs a key, create a read-only restricted key scoped to the minimum resources.
• Re-verify before wiring connectors. Vendor APIs move; entries marked "verify before connecting" were researched, not confirmed.