Subscription products,
built to operate

Most SaaS stalls not at launch but two quarters in, when admin, billing and identity still aren't there and every new customer is a support ticket. We build the six surfaces together, so the product can actually be run.

See the six surfaces Scope a build
Stacked SaaS product surfaces with identity, billing and event flow to a shared warehouse saas.product.map build · ship · operate customer · admin · billing · identity Customer app Admin Billing plan · seat · usage · tax stripe · recurly adapter Identity · RBAC SAML · OIDC · SCIM roles · sessions Public API · webhooks rate · version · idempotency · changelog Warehouse · analytics plane events · funnels · exec dashboards

SIX SURFACES

What ships when we ship a SaaS product

A SaaS product isn't the customer app alone. Admin tooling, billing, identity, analytics and a public API decide whether the product survives its second quarter.

01

Customer app

The surface every user sees. Sign-up, product shell, empty-state flows, feature-flag routing, in-app assistance. Built for keyboard users, screen readers and tight CLS budgets, not just the happy path.

02

Admin console

Where your team actually operates the product. Customer search, impersonation, feature flags, pricing overrides, manual refunds, audit trails of every admin action.

03

Billing layer

Plans, seats, metered usage, proration, dunning, tax. Stripe or Recurly under a thin domain abstraction so you can swap later without rewriting checkout.

04

Identity & RBAC

SSO (SAML, OIDC), SCIM provisioning, fine-grained roles, per-workspace isolation, session policies. The ceiling enterprise buyers check first.

05

Analytics plane

Product events, funnel reporting, experimentation guardrails, exec dashboards. Routed to the warehouse in a schema the data team can query in SQL.

06

Public API

First-party API and webhooks. Rate limits, versioning, idempotency keys, a changelog the customer-success team can link to.

LIFECYCLE

Six stages, reviewable at each boundary

No black-box delivery. Each stage ends with named artefacts the whole team can read — ADRs, runbooks, acceptance notes — not a verbal status update.

01 · Discovery

Discovery

Problem frame, competitor teardown, wedge strategy. Out of the week with a crisp product thesis and a named first customer.

02 · Architecture

Architecture

Domain model, data schema, auth boundary, deployment topology. Decisions documented as ADRs, reviewable by a second engineer.

03 · Vertical slice

Vertical slice

End-to-end thin path: auth → core feature → billing → admin. Real users, real edge cases, real money movement.

04 · Harden

Harden

RBAC, SSO, audit, rate limits, CWV gates, staging eval. Observability wired before GA, not after.

05 · Launch

Launch

Phased rollout, feature flags, runbooks, cost guardrails. The first 90 days carry a rollback budget.

06 · Operate

Operate

Release train, customer feedback ingest, drift detectors, quarterly tech review. Ownership stays named.

Billing is half the product

Subscriptions fail on the edges: proration, dunning, tax, promo codes, annual vs monthly. The tier table below is the scaffold we ship under every SaaS we build.

See tier scaffold ↘

TIER SCAFFOLD

Four-tier template we start every subscription product on

Starter self-serve, Team pro-sumer, Business mid-market, Enterprise signed. Price points are placeholders; the shape is not — it covers 90% of B2B SaaS we've shipped and maps cleanly to feature flags.

Starter

Self-serve individual

$0
  • 1 seat
  • Core feature set
  • Community support
  • API rate 60/min

Team

3–50 user teams

$39
  • Up to 25 seats
  • Admin console
  • SSO via Google
  • API rate 600/min
  • Email support

Business

50–500 user orgs

$149
  • Unlimited seats
  • SAML SSO + SCIM
  • Audit log export
  • API rate 6k/min
  • Priority support

Enterprise

Regulated + residency

Talk
  • Custom residency
  • Dedicated infra option
  • Signed SLA
  • Named delivery lead
  • Security review

STACK

Default stack, swapped per engagement

Our default toolkit across product, backend and platform. Choices are driven by team fluency and the problem's latency, residency and compliance profile.

Product

  • Next.js · Remix · SvelteKit
  • Tailwind · CSS modules
  • Radix · shadcn · Ariakit
  • Playwright · Vitest

Backend

  • Node · Go · Python
  • Postgres · Redis
  • Temporal · BullMQ
  • OpenAPI · tRPC

Platform

  • Vercel · Fly · AWS ECS
  • Cloudflare · Fastly
  • Datadog · Sentry · Posthog
  • Stripe · Recurly

Adjacent disciplines

Where SaaS connects

Growth

Growth Analytics & SEO/GEO

Tracking architecture, conversion events and AI-search readiness so the product actually gets found and measured.

 Revenue

CRM & Revenue Operations

Lifecycle, pipeline and quote workflows that surround the product once it has paying customers.

 Platform

DevOps & Cloud Infrastructure

CI/CD, autoscaling, reliability and cost guardrails that keep the subscription product alive at scale.

 Quality

QA & Release Governance

Automated tests, regression guards and human approval gates on every release cut.
Build · launch · operate

Turn a product idea into a running subscription business

Share the wedge, the user, the pricing intuition and the target ARR. We come back with a feasibility note, tier scaffold and first-90-day delivery plan inside ten working days.

Start a SaaS engagement Or wire the growth layer