SaaS products

SaaS development from a team that runs its own SaaS.

Most agencies have only ever built software for someone else. We built OpesFlux, a multi-tenant product with real companies on it, and we operate it every day. You get the decisions we wish someone had told us about at the start.

Book a free discovery call See our work

01 Is this you?

Where founders usually are when they call

  • 01You have an idea and a budget for a first version, and need to know what to leave out.
  • 02You have a prototype that works for one customer and breaks with ten.
  • 03Your first developer has left and you need someone to take the product over.
  • 04You sell a service and want to turn the repeatable part into a product.

02 Scope

What a SaaS build covers

A first version that is small on purpose

We agree the one job the product must do well, build that, and put it in front of real users before adding more.

Multi-tenancy

Each customer’s data kept apart at the database level, not just hidden by the interface.

Sign-in, roles and permissions

Secure sessions, roles per customer, and an admin area for you to manage accounts and plans.

Plans and feature switches

Modules that can be turned on per plan or per customer, so pricing can change without a rebuild.

Different countries

Currency, tax, dates and time zones set per customer. Much cheaper to design in at the start than to add later.

Running it

Hosting, backups, monitoring, migrations and releases, so the product stays up while it changes.

03 Proof

What we learned building our own

OpesFlux

Multi-tenant, with row-level security in PostgreSQL, modules switched on per company, an offline-capable point of sale, and companies in different countries on one platform.

About OpesFlux →

How we built it

We wrote up the architecture and the decisions behind it.

Read the write-up →

Marketing it

We also built its website, comparison pages and search set-up, so we know what comes after the build.

Visit the OpesFlux site ↗

Case studies: Purchasing and Approval System · Face-Verified Staff Attendance · A Multi-Tenant ERP Across Countries

What we build with: React, Next.js, Python (FastAPI), Node.js, PostgreSQL with row-level security, Docker, AWS, Google Cloud or Azure.

04 How we work

From first call to software in use

01

Discovery

A call to understand the problem, the people who will use the software and what success looks like. You get a written scope and a fixed quote.

02

Design

Wireframes and, where it helps, a clickable Figma prototype, so you can see it and change your mind before code is written.

03

Build

Short cycles with working software to review as we go. You can see progress, not just status updates.

04

Launch and look after

Deployment, handover and 30 days of free bug fixes, then optional support and improvements.

05 Questions

SaaS development: common questions

How much does it cost to build a SaaS MVP?

It depends on what the first version has to do. We help you cut the scope first, then give a fixed quote. Larger builds are split into milestones, so you can stop or change direction after each one.

What should the first version include?

Less than you think. The one job customers would pay for, sign-in, and a way for you to manage accounts. Everything else waits until real users ask for it.

Who owns the product and the code?

You do. The code, the data and the accounts it runs on are yours.

Can you take over a SaaS that someone else started?

Yes. We start with a review of the code, the data model and the hosting, and tell you plainly what is sound and what is not.

Can you keep running it after launch?

Yes. We offer ongoing support covering hosting, updates, bug fixes and new features, so you don’t have to hire a team on day one.

Tell us what you need built.

The first call is free. You get a written scope and a fixed quote, and we reply within one business day.

Book a free discovery call See pricing