Skip to content

Custom Business Software

SaaS products: many customers, one product, each kept apart

When five firms use your product, you can set each one up yourself and fix their problems by hand. At fifty, the product has to do it: create each firm's own space, keep its data away from everyone else's, enforce what its plan includes and get it started without a call. That's the difference between software and a product. We build the tenancy, plans and onboarding that let it grow without you.
Talk through your productSee what a product adds ↓
new firm · Starter planW-0143 · Startermanagercoordinatorviewergetting startedadd a propertyinvite a contractorsend the first request link+ add a 4th contractorStarter includes 3 contractors · move to Team?Move to TeamNot now46 requests this monthW-0098requests scoped to W-0143W-0098 never visible

What worked for five firms won't work for fifty

Early products run on the founders: they create each account, explain how it works, fix data by hand and remember which customer was promised what. That's right for an MVP. It stops working when the next firm signs up at 11 p.m. and expects to be using the product by morning.

A SaaS product turns those habits into software. Every firm gets its own workspace, separated in every query. Plans say what each firm can do, and the product enforces them politely. Onboarding is a path the product walks people through, and the team can see what's working, what's failing and what's being used.

Software for one customer, and a product for many

Software for one customer

  1. 01Set up by hand for each customer.
  2. 02One set of data, so everyone can see everything.
  3. 03What each customer gets is in an email somewhere.
  4. 04Problems reported by phone and fixed by the founder.

Every new customer adds work for the team, and one mistake can show one firm another's data.

A product for many

  1. 01Each firm creates its own workspace at sign-up.
  2. 02Every record belongs to one workspace, and every query is scoped to it.
  3. 03Plans set limits and features; the product enforces them.
  4. 04Errors, usage and sign-ups are measured and watched.

New customers add revenue, not set-up work.

What a product adds

Five things an internal application can skip and a product can't.

  1. 01

    Separation

    Each firm in its own workspace

    Every record belongs to one workspace, and every screen and API call is scoped to it.

  2. 02

    Onboarding

    Started without a call

    A checklist walks a new firm to its first real request, and shows the team who got stuck where.

  3. 03

    Plans

    Limits the software keeps

    What each plan includes is data the product checks. Hitting a limit offers a choice, not an error.

  4. 04

    Operations

    Problems seen first by you

    Errors, slow pages and failed jobs are watched, so the team knows before a customer writes in.

  5. 05

    Product analytics

    What's actually used

    Which features firms use, where they stop, and what the busiest firms do differently.

Plans the software enforces

Each plan is a set of entitlements the product checks on every action. Prices are yours to set; the structure is what the software needs.

Starter

Contractors
up to 3
Properties
up to 50
Request link
yes
Reports
basic
API access
no
Price
yours to set

The parts it's built from

Each part is built and tested on its own, so you can start with one and add the rest.

  1. Sign-up

    SaaS & MVP Development

    A firm creates its own account and chooses a plan.

  2. Workspace

    Backend Architecture

    • the firm
    • its plan
    • its people

    a record without a workspace → refused

  3. Plans

    SaaS & MVP Development

    Entitlements checked on every action.

  4. Operate

    Internal Tools

    An admin view of firms, usage and errors.

Underneath every stepIdentity & Access ManagementWho belongs to which workspace, and what their role allows.

What changes from one product to the next

CustomersWhat a workspace is: a firm, a team, a household
PlansWhat each includes, and how limits are offered
OnboardingThe first real result a new customer should reach
BillingWhether the product charges directly, and how

A common starting point is a Next.js application, a Postgres database with every record tied to a workspace, hosted sign-in with teams, Stripe for billing, and error and usage monitoring. These are starting candidates, not requirements.

Is it time for a SaaS product?

Good fit

  • An MVP or internal tool has proven people will use it.
  • More customers are coming than you can set up by hand.
  • You'll charge for it and support it as a product.

Avoid when

  • You haven't tested the core belief yet. Start with an MVP.
  • Only your own company will use it. Build an internal tool or platform.

How we'd approach it

Most of the early work is agreeing who your customers are, what each plan includes, and how onboarding and billing work.

  1. 01

    Understand

    As much as the problem needs

    We map how the work runs today: who does what, which systems hold the records, and where it breaks.

  2. 02

    Design

    Decided before it's built

    Ownership, rules, integrations and exceptions, agreed with you and written down with acceptance criteria.

  3. 03

    Build

    Connected to what you use

    We build the scoped system, connect it to the tools you already run, and test it on the cases that matter.

Related systems

The capabilities underneath

Questions about SaaS products

Can our MVP become the SaaS product?

If it was built on foundations worth keeping, yes. Workspaces, plans and onboarding are added to it rather than starting again.

How is each customer's data kept apart?

Every record belongs to one workspace, and every query, screen and API call is scoped to it. The separation is tested along with the rest of the software.

Do you handle billing?

We build the plan checks and connect a billing provider. The prices and terms are yours.

What happens after launch?

The product keeps changing. Usage and errors show what to fix and build next; we can keep building with you, or hand over to your team.

Turn your software into a product

Tell us how customers are set up and supported today. We'll show you what the product would need to do on its own.

Start a project