Portfoliodemo
New
PortfolioLiveFindingsSurprisePersonasDocs
Demo build. All companies, metrics, messages, and tasks are placeholder data. Nothing connects to a backend; nothing you click writes to a database.

SaaS surface

Internal-only admin view of the Sovi-as-SaaS infrastructure. Built but dark-launched - public surfaces stay dormant until Nate flips per-surface flags. portfolio

1/3 surfaces enabled
5 subscribers · 3 connect accounts

Dark-launch surfaces

LIVE

DARK

Flip to live: UPDATE saas_dark_launch SET enabled=true, enabled_at=now(), enabled_by='nate' WHERE surface='marketplace_listings'
DARKPublic Signup

Lets non-Nate users sign up to use Sovi as a SaaS. Stays dark until Nate is ready to onboard outside users.

Flip to live: UPDATE saas_dark_launch SET enabled=true, enabled_at=now(), enabled_by='nate' WHERE surface='public_signup'

Subscribers

  • first@example.com - active - 2026-06-26T22:34:26.924Z
  • two@example.com - active - 2026-06-26T18:34:26.924Z
  • three@example.com - active - 2026-06-25T23:34:26.924Z
  • four@example.com - active - 2026-06-24T23:34:26.924Z
  • five@example.com - unsubscribed - 2026-06-18T23:34:26.924Z

Stripe Connect accounts

  • - charges: no - payouts: no
  • - charges: no - payouts: no
  • - charges: no - payouts: no

How the dark-launch pattern works:

  • Each public-facing SaaS surface has a row in saas_dark_launch with enabled=false by default.
  • The surface route (e.g., /signup, /marketing) checks the flag at request time. If false, returns a "coming soon" page.
  • Flipping enabled=true takes effect on next request - no redeploy needed.
  • Nate can flip surfaces independently. E.g., enable the marketing site for lead capture before enabling actual signup.

Per Nate's lifted-gates directive: all SaaS infrastructure is BUILT and stays dark until he explicitly says "Sovi, flip the X surface." Optionality is the deliverable.