SaaS development
We build SaaS products from the first paying release through to scale, with multi-tenancy, SSO, billing and AI features designed in from the start. You reach customers sooner and avoid the rebuild that hits products whose foundations were rushed.
What it is and when it fits
SaaS development covers the product your customers use and everything underneath it: tenant isolation, authentication and SSO, roles and permissions, subscription billing, audit logs, admin tooling and the deployment pipeline. We work in TypeScript and Python on Postgres. In our own work we build with AI agents: coding agents do scoped tasks and we review every change. That keeps the pace up without cutting corners on code quality.
We are a good match for founders and product teams who have validated demand and need the product built or rebuilt properly, and for established companies turning an internal tool or service into a subscription offering. If you are still testing whether anyone will pay, a landing page and conversations with buyers will teach you more for less. We'll tell you that straight on the first call.
What we build
Multi-tenant architecture
Tenant isolation at the data layer, per-organisation settings and a structure that supports shared or dedicated hosting as enterprise customers ask for it.
Authentication, SSO and roles
Email and social login, SAML and OIDC single sign-on for enterprise buyers, and role-based permissions that match how your customers organise teams.
Subscription billing
Plans, trials, seats and usage-based pricing in Stripe, with invoices, dunning and entitlements wired into the product.
AI features inside the product
Search, summaries, assistants and document handling built into your workflows, with evals and cost controls per tenant.
Admin and support tooling
Internal dashboards to manage accounts, impersonate users safely, adjust plans and see product usage without touching the database.
Delivery pipeline
Preview environments, automated tests and CI checks on every change, so releases stay frequent and predictable.
How it works
- 01
Product discovery
We work through your users, pricing model and must-have features, and agree what the first release needs to prove.
- 02
Architecture and foundations
Tenancy, auth, billing and deployment are set up early, because they are the parts most expensive to change later.
- 03
Build in short cycles
Features ship to a staging environment every week or two, and you review working software as the product takes shape.
- 04
Launch and grow
After launch we monitor, fix and keep building, or hand over to your in-house team with documentation and a transition period.
Related work
Built with
All technologiesA guide to start with
Further reading
Vibe coding vs agentic engineering explained
Vibe coding means asking an AI tool for software and accepting the code without reading it. Where that works, what breaks once real users and data arrive, how agentic engineering differs, and what to do if your business already runs on a vibe-coded app.
9 min read
Agentic engineering: how we ship SaaS with Claude Code and Codex
How experienced developers use coding agents to build SaaS while keeping control of architecture, quality and security.
4 min read
When custom software beats off-the-shelf
A practical way to decide between off-the-shelf software and custom development, covering total cost of ownership, integrations and risk.
5 min read
Common questions
The main drivers are the number of user roles and workflows, integrations, enterprise requirements such as SSO and audit logs, and any AI features. We scope a first release that can win customers, then price the build in phases so spend follows traction.
You own the code and intellectual property once invoices are paid. Repositories, cloud accounts and third-party services are set up in your name, so you can bring development in-house or change partners whenever you choose.
Coding agents handle well-scoped tasks such as tests, migrations and repetitive features, while we own the architecture and review every change before it merges. We agree the tools and data handling with you up front.
Usually Next.js and TypeScript on the front end, TypeScript or Python services, Postgres as the database and Stripe for billing, hosted on Vercel, Railway, AWS or Azure. If you already have a stack and a team, we work within it.