SaaS Product Development
The architectural decisions that define a SaaS product — how tenants are isolated, how usage is metered, how data is separated — are made early and are expensive to revisit once customers are live.
- Reply within one business day
- NDA on request
- No obligation
Constraints specific to saas
The problems that shape software here, and that generic engineering tends to discover late.
Tenant isolation is decided once
Shared schema, schema-per-tenant or database-per-tenant each carry different cost, isolation and operational trade-offs, and migrating between them after launch is genuinely difficult.
Billing has to match what actually happened
Usage-based pricing requires metering that is accurate, reconcilable and explicable to a customer disputing an invoice.
Enterprise buyers audit before they buy
Security questionnaires, SSO requirements, data residency and audit logging arrive during procurement. Retrofitting them delays deals; anticipating them shortens cycles.
One noisy tenant affects everyone
Without deliberate limits, a single customer's heavy usage degrades service for the rest — which is a multi-tenant problem that does not exist in single-tenant software.
Software we build for saas
Multi-tenant architecture
Tenancy models chosen against your actual isolation, cost and customer-size profile rather than by default.
Metering and billing
Usage capture that reconciles with invoices, supporting seat, consumption and hybrid models with proration handled correctly.
Enterprise readiness
SSO and SAML/OIDC, role-based access, audit logging, data export and residency controls — the checklist procurement produces.
Onboarding and self-service
Sign-up, provisioning and administration flows that reduce the manual work each new customer costs you.
Standards that apply to software in this sector
What the software has to be built to satisfy. Which of these apply to you depends on your jurisdiction, your data and your customers.
[ 01 ]
Service assurance
- SOC 2
- ISO/IEC 27001
[ 02 ]
Personal data
- GDPR
- CCPA
- Data Processing Agreements
[ 03 ]
Data residency
- Regional hosting
- Cross-border transfer mechanisms
[ 04 ]
Identity
- SAML 2.0
- OIDC
- SCIM
[ 05 ]
Accessibility
- WCAG 2.2
- VPAT
These are the standards we design and build to meet. Certification or attestation of your organisation is a separate exercise, carried out by a qualified assessor — we can support that process with documentation and evidence, but we do not certify it.
Tell us where the product is straining
Discuss a SaaS projectHow we'd approach it
The service lines this sector most often needs.
Web Application Development
Scalable web applications on modern frameworks, engineered for first-load performance and sustained load.
Cloud & DevOps
Migration, deployment automation and infrastructure on AWS, Azure and Google Cloud, built to be operated.
Custom Software Development
Bespoke systems shaped around your operations, integrated with the tools and data you already run on.
Product Design & Discovery
Discovery, UX and interface design that resolves the expensive questions before implementation starts.
Projects in this space
Financial Research
The Cytadel
A subscription market intelligence platform built on Supabase and Stripe.
Trading
OptionTeller
An options analytics platform querying 70+ million daily trades, built on Next.js and Rust.
HR Technology & Staffing
Crowdstaffing
A hiring platform managing the contingent-workforce pipeline for employers and staffing agencies alike.
SaaS: common questions
Something specific to your operation?
Send it over — sector questions are the ones we most like getting.
Ask us01
Which multi-tenancy model should we use?
Shared schema with a tenant identifier is cheapest and scales to many small customers, but places the entire isolation burden on application code. Database-per-tenant gives strong isolation and simple per-customer restore at higher operational cost, which enterprise buyers often require. The deciding factors are your customer size profile and what your buyers demand contractually.
02
When should we start worrying about SOC 2?
Before your first enterprise prospect asks, because by then it is blocking a deal. The controls themselves — access management, change management, logging, incident process — are ordinary good practice, and building them in early costs far less than reconstructing evidence during an audit window.
03
How do you handle usage-based billing?
By separating metering from billing. Usage events are recorded immutably as they happen, and invoices are derived from them, which means a disputed charge can be traced to the specific events behind it rather than defended by assertion.
04
Can you add SSO to an existing product?
Yes, and it is a common request once enterprise deals appear. The work is usually less about the protocol than about reconciling an existing user model with externally-managed identities — deciding what happens to existing accounts, and how provisioning and deprovisioning work.
Adjacent sectors
Tell us where the product is straining
Whether it's tenancy, billing or an enterprise security questionnaire you can't answer yet — describe it and we'll come back with an assessment.
- Reply within one business day
- NDA on request