Tenancy bolted on later
The product was built for one customer, and separating each company’s data after the fact is slow, risky and hard to prove to anyone.
SaaS development company · UK
We help UK founders and software companies build SaaS products that businesses will pay for and IT teams will approve — multi-tenant from the start, with subscriptions, SSO, onboarding and admin tooling done properly, and ready for the security questionnaire your first enterprise customer sends.
Where SaaS gets hard
A SaaS demo is easy. The hard parts appear when real companies sign up, pay, invite colleagues and send their security team your way.
Foundations worth building early
The product was built for one customer, and separating each company’s data after the fact is slow, risky and hard to prove to anyone.
Mid-month upgrades, failed card payments, seat changes, refunds and invoices with the right VAT details — each one a support ticket if it was not designed in.
A promising customer asks for single sign-on, audit logs and a completed security questionnaire, and the product has none of them ready.
People sign up, land on an empty screen and leave. Without guided onboarding and sample data, the trial ends before they see the value.
With no admin tooling, every refund, plan change or locked account needs an engineer — who should be building the product.
Without usage data there is no way to tell which features matter, which accounts are at risk, or whether the plans make commercial sense.
Who it is for
Founders, established software companies and service firms turning what they know into a product — at different stages, on the same foundations.
You have early users; now you need proper tenancy, billing, onboarding and an admin panel before you can charge real companies.
An installed or single-customer product rebuilt as multi-tenant SaaS, with a migration path for the customers you already have.
A consultancy, agency or training firm turning its method, templates and reports into software that clients subscribe to.
Hospitality, education, property or professional services products built around the workflows and rules of that sector.
SSO, a billing overhaul, a public API or usage-based pricing delivered alongside your core team’s roadmap.
A tool you built for yourselves that other companies now ask to buy — made multi-tenant, billable and supportable.
Architecture
Every SaaS product has to keep one customer’s data away from another’s. There are three broad ways to do it: a shared database where every row carries a tenant ID, a separate schema for each tenant, or a separate database for each. Shared is the cheapest to run and the simplest to change; separate databases are the easiest to explain to a cautious enterprise buyer, but add operational weight.
Most B2B products start shared, with PostgreSQL row-level security enforcing the boundary in the database itself rather than relying on every query being written correctly. We add automated tests that try to read across tenants, so isolation is checked on every release rather than assumed. Where a large customer insists on its own database or a UK-only region, the architecture can accommodate them without forking the product.
Tenancy also shapes everything built on top of it: how users belong to organisations, how roles and permissions work, how data is exported when a customer leaves, and how you answer “where is our data held?” in a security review. That is why we settle it in discovery, not in sprint six.
What we build
The core workflow is what customers buy. These are what let them buy it, use it and stay — and they are far cheaper to build in than to retrofit.
Stripe Billing for plans, trials, seats, upgrades, proration and failed-payment recovery, with Stripe as the source of truth and webhooks processed idempotently.
Customer country, VAT number and tax treatment stored on every account, so invoices carry the right details and a change your accountant advises is configuration, not a rebuild.
Organisation roles and permissions from day one, then SAML or OIDC single sign-on and user provisioning when business customers ask for them.
Sign-up, invitations, sample data and a guided first session, designed around the moment a new user first gets value.
Activation, feature adoption and seat use per account — the numbers behind pricing, roadmap and renewal conversations.
Account lookup, plan overrides, audited impersonation and tenant health views, so your support team can help customers without an engineer.
Enterprise readiness
Sooner or later a large customer sends a security questionnaire — usually a long spreadsheet covering access control, encryption, logging, backups, incident response and your own suppliers. The answers need to be true, and ideally backed by evidence the platform already produces.
Many SaaS companies eventually commission a SOC 2 report, and UK customers sometimes ask for Cyber Essentials. That is your company’s journey, not ours: a SOC 2 report is issued by an independent auditor after examining your controls, many of which concern people and process rather than code, and we are not auditors. What we do is build and run the technical controls those frameworks look for — single sign-on and MFA for staff, least-privilege access, audit logs, change management through reviewed pull requests, encrypted backups that are restored in tests, dependency and vulnerability scanning — and document them so your answers are quick to write and easy to evidence.
The earlier those controls exist, the cheaper they are. Retrofitting audit logs and access reviews into a product that never had them is a project of its own; building them into version one is far cheaper.
Typical roadmap
An example of how the platform work usually sequences as a B2B SaaS product grows. The order changes with your customers; the foundations do not.
An illustration, not a fixed plan. Your roadmap is agreed in discovery and revisited as real customers show you what they need.
Tenancy, roles, Stripe checkout and the one job customers are paying for — typically planned over weeks, not months.
A product you can charge for
Seat changes, proration, failed-payment emails, invoices with VAT details, and admin tools so support stops needing engineers.
Billing edge cases handled
SSO, audit logs, data export, a documented security posture and accurate answers to the questionnaire that arrives with the contract.
Security review answered
Usage-based pricing where it fits, background jobs and caching for heavier tenants, and a public API or webhooks for integrations.
A platform that grows with revenue
How we work
The same seven stages we use for every build, with the SaaS decisions — tenancy, billing, roles — pulled forward to where they are cheap to make.
Who buys, who uses, how you will price it and what the first enterprise customer will ask for — then the tenant model, roles and billing rules that follow from those answers.
Product, pricing and tenancy decisions
We cut version one to the workflow customers will pay for, plus the foundations that are expensive to add later, and fix the price for that scope.
Version-one scope and fixed quote
Onboarding, empty states, invitations and settings designed with the core workflow, alongside the data model, API boundaries and Stripe integration plan.
Prototype and architecture decisions
Two-week sprints with a demo at the end of each, code review on every change, and a staging environment your team can use.
Working software every sprint
Automated tests on billing events and cross-tenant access, load tests for heavier tenants, and security checks before each release.
Test evidence you can show customers
Production deployment with monitoring, backups and a rollback plan, followed by a handover of code, credentials and documentation.
A live, documented product
A managed team for the roadmap, or support and upgrades on a smaller retainer — with usage data reviewed together to decide what comes next.
Roadmap cadence or handover
Engagement models
Version one is usually a fixed-price project after discovery. After launch, a SaaS product needs steady development — which is where a managed product team fits.
From £2,000 fixed fee
You have an idea or a problem, but not yet a scope you would trust a quote against.
Quoted after discovery
A defined build — an MVP, a rebuild or a feature set — with milestones and a fixed budget.
From £9,500 per month
A small cross-functional pod — engineering, QA and delivery lead — that owns an outcome.
Prices are in GBP. Every estimate is confirmed in writing after a discovery call — the figures above are where engagements start, not a quote.
Relevant work
A restaurant operations platform, a revenue analytics dashboard and a university management system. Each case study covers the brief, the approach and the stack.
All case studiesRestaurant operations platform: QR ordering, kitchen displays and loyalty.
Revenue analytics dashboard with multi-source data and automated reporting.
University management system replacing spreadsheet enrolment and timetabling.
Why Techsleight
The habits that make a SaaS platform easier to sell, support and scale — and cheaper to change.
Pricing, plans and who buys shape the data model. We ask about them before we design tenants, roles and billing, because they are expensive to change later.
A tenant model you can describe to a customer’s security team in two sentences, with automated tests that check one customer cannot see another’s data.
Stripe as the source of truth for subscriptions, and invoices your customers’ finance teams can process without querying.
Access logs, change history and restore tests you can show a customer or an auditor — produced by the platform, not written up afterwards.
Activation, feature use and seat counts tracked from launch, so pricing and roadmap decisions rest on behaviour rather than opinion.
Code, cloud accounts, the Stripe account and documentation are yours, with an NDA before discovery if you want one.
SaaS is never finished. Keep a managed team for the roadmap, scale down to support, or hand over to your own engineers with documentation.
FAQs
Straight answers on scope, cost, timelines and how we work. If yours is not here, ask us directly.
It depends on the core workflow and how many of the platform foundations — billing, SSO, admin tooling — version one needs. A discovery sprint starts from £2,000 and ends with a fixed quote for version one. After launch, a managed product team starts from £9,500 a month, or dedicated developers from £2,900 a month each.
A focused version one — one core workflow, tenancy, roles and Stripe billing — is typically planned over weeks, not months. Enterprise features such as SSO and audit logs usually follow once the first customers are live. You get a dated plan with milestones after discovery.
For most B2B products, multi-tenant with a shared database and strong isolation is the right default: cheaper to run and simpler to update. Single-tenant or database-per-tenant makes sense when customers contractually require it or the data is especially sensitive. The architecture can support a mix, which we plan in discovery.
Yes. We model plans, trials, per-seat and usage-based prices in Stripe, handle upgrades, downgrades and proration, recover failed payments with retries and emails, and give customers a self-serve billing portal. The Stripe account is yours; we build against it.
We store what the tax calculation needs on each account — country, business or consumer, VAT number — and apply rates through Stripe Tax or rules you define, including the different treatment for business customers outside the UK. Which treatment applies is a question for your accountant; our job is to make changing it a configuration change.
Yes. We add SAML or OIDC single sign-on and user provisioning against the identity provider your customer’s IT team already runs, fill gaps such as audit logs and admin controls, and give you accurate technical answers for the questionnaire — backed by evidence rather than aspiration.
Nobody can do that on your behalf. A SOC 2 report is issued by an independent auditor after examining your company’s controls, many of which are about people and process rather than code. We help with the technical side: implementing and documenting access control, logging, change management, backups and vulnerability management, and producing the evidence your auditor asks for.
Yes. We can host in AWS’s London region, keep backups in the UK, and document where each piece of data lives and which third-party services process it — the questions UK buyers ask in security reviews. If some customers need a different region, the architecture can support that.
Yes. We start with an audit of the code, tenancy model, billing integration and infrastructure, then fix what threatens customers first. Where a rebuild is justified, we replace the product piece by piece behind the existing interface, so paying customers are never asked to migrate all at once.
You do. The code, cloud accounts, Stripe account, domain and documentation belong to your company from day one, and we sign an NDA before discovery if you want one. We work inside your accounts rather than hosting your product on ours.
Start a project
Tell us about the product, who pays for it and where it is stuck — version one, billing, enterprise readiness or scale. We will reply with questions and a view on the sensible next step.
What happens next
Techsleight Labs is a trading name of Krapton IT Consultancy.
Explore