Private SaaS Platform

🔒 Confidential🚧 In active development

A production SaaS platform I design, build and operate solo: it automates the repetitive operational workflows of a service-based industry, combining authentication, subscription billing, third-party integrations and scheduled automation across a multi-application architecture.

Confidential case study

This is a real product with paying infrastructure behind it, so its identity stays private. Product branding, implementation details and screenshots are available to authorized viewers.

  • Product name, brand and live URL
  • The industry and the customer it serves
  • Dashboard and onboarding screenshots
  • Architecture, integration and data-model specifics
  • Technical decisions, trade-offs and results

Private project access

This case study contains confidential product and implementation information. Enter the access code you were given to view it.

Recruiters: ask me for a code, or use the private link I sent you.

Problem

Operators in a service-based industry lose hours every week to coordination work that is manual but entirely predictable — the same sequence of messages, follow-ups and small decisions, repeated per customer. It is exactly the kind of workflow software should own end to end.

Solution

I build and run the whole product alone, from schema to deploy: a monorepo holding two independently deployed Next.js applications — a public marketing surface and an authenticated product dashboard — on top of shared internal packages. Authentication, subscription billing, transactional messaging and scheduled automation all run in production.

Tech stack

  • TypeScript
  • Next.js
  • React
  • Supabase (PostgreSQL)
  • Stripe
  • Turborepo
  • Vercel

Architecture

Two independently deployed Next.js applications in one monorepo. The public application owns marketing, content and lead capture; the dashboard owns authentication, the business APIs and the product itself. Shared packages hold the database clients (server and browser, with cross-subdomain cookies), the messaging and AI integrations, plan configuration, feature flags and the design tokens — so both applications evolve and deploy separately without forking any logic.

Technical highlights

  • Monorepo with two independently deployed Next.js applications sharing internal library, UI, types and i18n packages
  • Cross-subdomain authentication with a shared cookie domain between the public site and the authenticated dashboard
  • Subscription billing gated behind a single feature flag, so the complete paid flow is exercised on staging while production runs a restricted launch
  • AI-assisted onboarding that provisions a fully configured workspace from one input instead of a long manual setup
  • Transactional email, SMS and scheduled cron automations running in production
  • Delivery discipline of a real product: protected main branch, staging previews per pull request, deploy checklists and runbooks