SaaS Products
From validated idea to a product that scales.
Almost every SaaS rewrite traces back to two decisions made in month one. We make those two decisions deliberately, then ship something small enough to learn from.
01When this applies
Signs you are in this territory.
If two or three of these are true, this is usually the right place to start.
- An internal tool that customers keep asking to buy
- A prototype that proved the idea and cannot carry the second customer
- Billing modelled as a payment rather than as entitlements
- Tenancy added after the first ten customers
- A roadmap longer than the team that has to build it
02Approach
How we run it.
01
Decide tenancy first
Shared database with row-level security, or isolated per tenant. Every later feature inherits this decision whether or not anyone revisits it.
02
Model entitlements, not payments
What a plan unlocks is product logic. Getting that separation right is what lets pricing change without an engineering ticket.
03
Ship one paid workflow
End to end, in production, that a real customer would pay for. Everything else is a hypothesis until that exists.
04
Instrument before you scale
Logging, tracing and alerting configured before traffic arrives, so 'is it us?' takes minutes rather than an afternoon.
03Deliverables
What you end up with.
- Multi-tenant architecture and isolation strategy
- Subscription billing, plans, trials and entitlements
- Roles, permissions, invitations and audit logging
- Customer and internal analytics
- Infrastructure as code, CI/CD and observability
- Security review, backups and recovery plan
What good looks like
- A tenancy model that holds as the customer base grows
- Pricing changes made in configuration, not code
- An on-call story that does not depend on one person
Delivered by
04Relevant work
Software we have built along these lines.
ProductGrowth Pilot
An AI growth workspace: find local businesses that need work done, prove it with an audit, then win and deliver the job.
Live toolProject Cost Calculator
An honest estimate of what a website, application, SaaS product or mobile app will cost, and how long it will take.
05Questions
Before you ask.
Yes. We build to be handed over — your repositories, your cloud accounts, documented decisions.
Through an established provider, with the entitlement layer in your product so pricing and permissions stay yours to change.
A first release is usually a three to five month engagement. The cost calculator on this site gives an honest range before you speak to anyone.
Keep exploring
Other solutions.
- Business SoftwareReplace the spreadsheets, shared inboxes and manual handoffs holding your operation together.
- AI SolutionsPut a language model to work on your documents, your support queue and your internal knowledge.
- AutomationConnect the systems you already pay for and take the repetitive steps out of the middle.
- Digital TransformationModernise a legacy estate in sequence — without stopping the business while you do it.
Start here
Good software starts with a straight conversation.
No pitch deck, no discovery fee. Describe the problem and we will tell you what it would take to solve it — and what it would cost.