Skip to content
Book a free 30-minute call with an engineer

SaaS Product Development

Subscription software with billing, accounts and admin built in.

StockFlow Pro screens

A SaaS product is more than the feature people pay for. It also needs sign-up, teams and permissions, plans and billing, usage limits, an admin console and a way to ship updates without breaking anyone's account. We build all of that so you can spend your time on the part customers actually buy.

We usually build on Next.js, Node.js and PostgreSQL with Stripe for billing. Tenant isolation is designed in at the database level from the start, because adding it later is expensive. We've taken products from a first paid pilot to thousands of accounts on the same codebase.

What’s included

Pick the parts you need. Most projects use all of them.

  1. 01

    Multi-tenant architecture

    Data separation per customer, designed at the schema level and tested so one account can never see another's data.

  2. 02

    Subscription billing

    Stripe plans, trials, coupons, seat-based and usage-based pricing, invoices and dunning emails.

  3. 03

    Onboarding & activation

    Sign-up, team invites, sample data and in-app guides that get new accounts to their first result quickly.

  4. 04

    Admin & support tools

    An internal console to look up accounts, change plans, impersonate users safely and see usage.

  5. 05

    Integrations & API

    A public API, webhooks and connectors for Slack, HubSpot, Google Workspace and similar tools.

  6. 06

    Analytics & reporting

    Product analytics plus in-app reports your customers can export and share.

What you walk away with

  • Product scope, pricing model review and clickable prototype
  • Multi-tenant SaaS application with authentication and roles
  • Stripe billing, plans and customer self-service portal
  • Admin console, product analytics and audit logs
  • Infrastructure as code, monitoring and a scaling plan
StockFlow Pro screens

StockFlow Pro, Multi-company retail and wholesale

Tools we use

We choose per project. These come up most often for saas development work.

app/orders/page.tsxTSX
1import { getOrders } from "@/lib/orders";​
2​
3export const revalidate = 60;​
4​
5export default async function OrdersPage() {​
6 const orders = await getOrders({ limit: 20 });​
7​
8 return (​
9 <main className="p-8">​
10 <h1>Recent orders</h1>​
11 <OrdersTable rows={orders} />​
12 </main>​
13 );​
14}​

How a project runs

Five stages, two-week sprints and a demo at the end of every one.

  1. 01  Week 1

    Discover

    A couple of workshops with your team. We map the users, the must-haves and the risks, then send a written scope with a fixed estimate.

    MVP roadmapSprint 4 of 6 · launch in 3 weeksLater2Next2Now2Done3Referral codesGrowthDark modeUIAdmin exportsBackendPush remindersMobileStripe checkoutPaymentsOnboarding flowDesignSign up & loginAuthBooking APIBackendStore listingReleasev1.0 live
  2. 02  Weeks 2 to 4

    Design

    User flows, wireframes and the visual design in Figma. You click through a prototype, and we test it with a few real users before any code.

    Home · v2StaylineLisbon, 3 nights12 to 15 May · 2 guestsFree cancellation until FridayTotal€486Book nowColourTypeAaHeading 32Body 16 / 1.5Caption 12ComponentsPrimarySecondaryToggleTested with 6 users ✓
  3. 03  2-week sprints

    Build

    Code, tests and a staging site you can open any time. Every sprint ends with a demo, so you always see what changed.

    app.yourcompany.com/ordersNorthdeskOverviewOrdersCustomersInventoryReportsSettingsOrders142 this month · $48,210+ New orderOrderCustomerStatusTotal#1042Maple StudioNew$3,400#1038Harlow LtdPaid$1,240#1039BrightwayPending$860#1040Okafor & CoPaid$2,115#1041NordlineShipped$540Order #1042 created
  4. 04  Go-live

    Launch

    Security checks, load testing, App Store and Play Store submission, then a production release with monitoring switched on.

    ~/app — zsh$ git push origin mainEnumerating objects: 14, done.To github.com:acme/app.git 4f2a1c9..b81e0d3 main → mainCI triggered: pipeline #482Instances3 / 3 healthyCPU 64% · autoscale onPipeline #482main · b81e0d3BuildTestDeploy
  5. 05  After launch

    Improve

    We watch the analytics, fix what users trip over and keep shipping features. Most clients keep us on after launch.

    Uptime · last 30 days99.98%30 days agoTodayResponse time142 msp95 · all regions09:0015:00Incident resolved · 4 minCheckout API latencyRolled back · on-call: SamDeployed to productionv2.14.1Today 09:12Latest

Recent projects

SaaS Development: common questions

How much does it cost to build a SaaS product?

A SaaS MVP with sign-up, billing and one core workflow usually costs $30k-$80k. A more complete product with integrations, reporting and an admin console is often $80k-$250k. We help you decide what has to be in version one and what can wait.

How long until we can launch?

Most SaaS MVPs launch in 10-16 weeks. We aim to get you a paid pilot as early as possible and build the rest in two-week sprints based on what those first customers tell you.

How do you handle multi-tenancy?

Usually with a shared database and tenant IDs enforced by PostgreSQL row-level security. For customers with strict requirements we can isolate them in separate schemas or databases. We pick the model based on your customers and compliance needs.

Can you add billing to our existing product?

Yes. We regularly add Stripe subscriptions, usage metering, trials and customer portals to products that started out free or were invoiced by hand.

Do you help after launch?

Yes. Many clients keep us on as their product team after launch for new features, performance work, uptime monitoring and the occasional 2 a.m. incident.

Related services