Multi-tenant SaaS, billing on day one
End-to-end SaaS builds with Stripe billing, multi-tenant auth, role-based access, onboarding flows, and admin dashboards — built to take real paying customers.
Most SaaS MVPs ship without billing, without admin tools, without invite flows. They look great on launch and break on first paying customer. I build with billing, tenancy, and ops from day one — because that's what survives contact with users.
8+
SaaS products shipped to paying users
Stripe
Default billing — webhooks signed, idempotent
<5s
Signup to first 'aha' moment targeted
0
Cross-tenant data leaks (RLS enforced)
Trusted by founders & teams in
Everything included in every engagement
No upsells. No surprise change orders. One scope, one price.
Multi-tenant from the data model up
Workspace/team scoping in Postgres with RLS, no leaky queries, audit log on every cross-tenant boundary, invite + role management.
Stripe billing wired correctly
Subscriptions, metered usage, proration, trials, cancellations, dunning. Webhook handlers are idempotent and signed. No silent revenue leaks.
Auth & RBAC
Supabase Auth or Auth0 with SSO, MFA, magic link, OAuth. Role-based access with permissions checked on the server, not the client.
Onboarding that converts
First-run wizard, sample data, checklist, contextual tooltips, and Intercom-style empty states. Activation is a feature, not a hope.
Admin & support tools
Internal admin to impersonate users, refund payments, view tenant health, and replay events. The tools your support team will need on day 2.
Marketing site + product on one domain
/, /pricing, /docs marketing pages sharing a design system with the product. Logged-in/out states handled cleanly.
The tools I actually use in production
Modern, battle-tested, and chosen for fit — not hype.
App
- Next.js
- React
- TypeScript
- Tailwind
Backend
- Supabase
- PostgreSQL
- NestJS
- Prisma
Billing
- Stripe
- Paddle
- Lemonsqueezy
Ops
- Resend
- PostHog
- Sentry
- Cloudflare
How we'll work together
Predictable, written-down, no surprises.
- 01
Pricing & tiers
Pricing model, feature gating, and metering decisions before writing code. Wrong tiers = wrong product.
- 02
Core flows
Signup, invite, billing, cancel, upgrade, downgrade. Boring flows that drive 80% of revenue.
- 03
Product features
Whatever your app actually does — built tenant-aware from day one.
- 04
Launch & iterate
Closed beta with 5–10 design partners, instrument with PostHog, ship to public.
Pricing that matches the work
Starting prices. Final quote in writing after a 30-minute scoping call.
MVP
Founders validating with paying users
$6,500starting
- Signup, billing, 3–5 core flows
- Single-tier pricing
- Delivered in 3–5 weeks
Production
Teams scaling past 100 paying customers
$14,000starting
- Multi-tenant + invite + RBAC
- Tiered pricing, metering, dunning
- Admin + support tools
- Delivered in 6–10 weeks
Retainer
Ongoing product growth
$3,500/mostarting
- Reserved engineering hours
- Feature flags + experiment infra
- On-call coverage
Questions I get asked first
Stripe or Paddle?+
Stripe by default for control and ecosystem. Paddle when you want a Merchant of Record (handles VAT/sales tax globally). I'll recommend based on where your customers are.
How do you handle tenancy?+
Shared schema with tenant_id on every row, Postgres RLS for hard isolation. Schema-per-tenant only when there's a regulatory reason.
Can you migrate me off no-code (Bubble, Webflow)?+
Yes — common path. I keep your data model intact, recreate flows in Next.js, and migrate data with a one-time import script.
Do you handle SOC2 prep?+
I can wire the technical controls (audit log, MFA, access reviews, encryption) and recommend a vendor (Vanta, Drata) for the policy/evidence side.
Let's scope your project
Tell me what you're building. I'll reply with a written estimate within 24 hours — no sales call required.
Related services
Often paired with saas development.
Web Development
From the database schema to the deployed Next.js frontend, I ship modern web apps designed to rank, convert, and scale. One engineer, full ownership.
Backend Development
Typed Node.js and NestJS APIs with PostgreSQL or MongoDB, Redis caching, structured logs, and the boring discipline that keeps p95 latency under 100ms.
API Development
Well-versioned, well-documented REST or GraphQL APIs with auth, rate limiting, and webhooks. Built to be consumed by partners and customers — not only your own frontend.
E-commerce Development
Headless Shopify or custom commerce on Next.js — sub-second product pages, SEO-tuned catalog, and a checkout designed around the data, not the template.