SaaS Development

One product,
many customers

We design and build software you sell by subscription, with sign-in, plans and billing, tools for your team and each customer’s data kept apart, so a new customer is one more account, not one more project.

Thanks, we’ll be in touch soon.

{{ heroStatus }}

{{ heroSay }}

You’re in good company

A few of the companies we’ve worked with.

{{ wallSay }}

From first customers to many

A product that works for its first customers isn’t always ready for many. Each new customer brings its own people, data and plan. Larger ones send a security review before they sign: can our people use our own sign-in, are they removed when they leave, can we see who did what, and is our data kept apart from everyone else’s. Each answer is a part of the product, and each one touches every customer’s data.

Here, a customer is a company that pays for your product, and each one has an account of its own.

What we build

The parts a product sold to many companies runs on, built in from the start.

  • Each customer’s data kept apart

    On every path to it, not only the screens, decided from who is signed in.

  • Sign-in for every customer

    Passwords with multi-factor authentication, or single sign-on, so people sign in through their own company’s system.

  • People from your customer’s directory

    Joiners, movers and leavers kept in step with the customer’s own list of people, roles included.

  • Roles each customer sets

    Owners, admins and members, set by each customer for its own people.

  • Plans, trials and billing

    Plans and their limits kept in one place, with upgrades, downgrades and canceling as simple as signing up.

  • Use counted, and limited

    Use measured for each customer, with limits on requests and queued work, so a busy customer’s work waits its turn.

  • An audit log your customers can read

    Who did what, and when, in each customer’s account, kept and ready to export.

  • Tools for your own team

    Find a customer, see its plan and settings, and help, each visit made with a reason and recorded in its audit log.

  • Taking data along, and closing an account

    A customer can export its data, and a closed account’s data is deleted on the schedule you set.

An idea that isn’t built yet? Discovery & MVP →

Software for your own team, not for sale? Custom Software →

Hosting, releases and uptime? Cloud, DevOps & Security →

Kept apart on every path

A customer’s data can be reached through more than its screens: the API, background jobs, caches, file links, exports, logs and backups. We make every one of them pass the same check on whose data it is, decided from who is signed in and the accounts they belong to, never on a request’s word alone. Then we test it the way it would fail: one customer’s account asking for another’s records, through every path, before every release.

Separate databases, separate schemas or shared tables: we choose with you, by the data and what your customers ask for →

Run as another customer

An example

One customer asks for another customer’s invoice

  • On screenNot found
  • Through the APINot found
  • In an exportNot found
  • By a shared file linkNot found
  • From a cacheNot found
  • In a background reportNot found

When someone leaves your customer’s company

When someone leaves one of your customers, the customer takes them out of its directory. Single sign-on then stops them signing in again, but it doesn’t by itself remove their account, end a session that’s already open or stop the access keys they made.

For that, your product needs a directory connection (SCIM, an open standard for adding and removing people), and code that acts on what it’s told: ending their sessions, stopping their keys, and handing what they owned to someone the customer chooses.

An exampleOne person leaves a customer’s company.

Your customer’s directory

  • Designer
  • Analyst Left the company
  • Account manager

Single sign-on only

  • Can’t sign in again
  • A session already open stays open until it times out
  • Their access keys still work
  • Their work stays assigned to them
  • Still counts as a seat

With a directory connection

  • Account deactivated
  • Open sessions ended
  • Access keys stopped
  • Work handed to a teammate
  • Seat freed

Single sign-on decides who can sign in. A directory connection tells your product when someone joins, moves or leaves. Your product still has to act on it, and that’s the part we build.

Some customers’ sign-in systems can also tell a product when a person’s session should end, through newer open standards for sharing those signals.

Start with the customer you want next

If the product isn’t built yet, we start with a discovery. If it’s live, we read it against the customer you want next: how each customer’s data is kept apart, how people sign in and leave, how plans and limits work, and what your team can see. You get a written plan of what to build first, in the order we’d build it, and a test customer account that every later check runs as.

Work with us as a dedicated team, on a fixed price project or a mix of both. Compare engagement models →

How each is paid for: Pricing →

Questions worth asking

Should each customer have its own database?

It depends on the data, on what your customers ask for and on what each choice costs to run. Separate databases, separate schemas and shared tables can each keep customers apart when they’re set up and tested with care, and they can be mixed, giving a larger customer its own where it needs one. We choose with you, and the rest of the product works the same way whichever you pick.

Can we add single sign-on later?

Yes. We design each account so its people can later sign in through the customer’s own system, and be added from its directory, without changing how the rest of the product works.

Should single sign-on and audit logs cost extra?

That’s your decision. CISA’s Secure by Design pledge, a voluntary pledge for software makers, says products should have multi-factor authentication, logging and single sign-on available at no extra cost. We build them in for every plan, so how you offer them stays a pricing choice, not an engineering one.

What happens to a customer’s data when it leaves?

It can export its data first. Then that data is deleted on the schedule you set, and only that customer’s: from the product, its files and its caches, and from backups as they age out.

Will one busy customer slow everyone else down?

Each customer has limits of its own, on what it sends and on the work it can queue, so a burst from one waits its turn. A customer that needs more can be given capacity of its own.

Do you build the billing yourselves?

We connect your product to a billing provider you choose, and keep your plans and their limits in your own code, so the provider can change later without your plans changing with it.

Can you work on a product that’s already live?

Yes. We start by reading it, as Start with the customer you want next describes. If you’re preparing a raise or a sale: Technical Due Diligence →

Do you run the product for us, or hand it over?

Either. Once it’s live, we can run it with you: keep it patched and up to date, watch it, respond when an alert needs a person, and review access and costs on a regular rhythm. Or we hand it over to your team, with the runbooks and the knowledge behind them. Where we run it, our engineers reach your customers’ data only for a task you’ve agreed, and each time is recorded. Cloud, DevOps & Security →

What does it cost to build?

It depends on which of these parts the first release needs and what it connects to. The first call is free. Your proposal sets out the scope, the price or rate, and how you pay, before any work starts. Pricing →

Let’s build it better

Tell us about the customer you want to win next. We’ll suggest where to start.

Thanks, we’ll be in touch soon.

{{ ctaStatus }}