# Organise testing for many client sites: one project per client

> How agencies keep tests, sign-in accounts, schedules and run usage separate per client, when to use a project and when a separate workspace with its own billing.

By Jason Nguyen, Founder, Testsy. Published 2026-11-21. https://testsy.dev/blog/organise-client-sites-one-project-per-client/

## The mess to avoid

Tests for ten clients in one list, with sign-in accounts named "admin" and "admin2", a schedule nobody remembers creating, and no idea which client the month's runs went to. It happens by the third client if nothing is decided up front.

## A project per client

In Testsy a **project** holds tests, [sign-in accounts](https://testsy.dev/docs/sign-in-accounts/), files, endpoints and app builds. Make one per client site:

- Tests are grouped by client, and **Run all** runs one client's tests.
- Sign-in accounts belong to the project, so "admin" means that client's admin.
- Slack subscriptions can follow selected projects, so one client's failures go to one channel.
- **Plan and usage** shows where the runs went, by project, so you can see what each client costs you.

![Projects: one per client site, each with its tests and last results.](https://testsy.dev/docs/img/projects-light.webp)

Each plan includes a set number of projects and members:

The plans and their prices: https://testsy.dev/docs/plans-billing/

## When a separate workspace is better

A **workspace** has its own projects, team, plan and billing. Make one per client when:

- the client pays for testing directly, on their own card,
- the client's team will write or run tests themselves,
- you need more client projects than your plan includes, and the client should carry the cost.

New workspaces start on the free trial. You can belong to many, and switch between them.

## Naming that survives

- Project: the client's name and site ("Harbour Dental · harbourdental.com.au").
- Tests: what a user does ("Book a check-up and receive the confirmation").
- Sign-in accounts: the role ("staging admin", "member").

The project name appears on run pages; the workspace name appears on share links, so name the workspace after your agency.

## Who sees what

Invite your team as members. Give a client a **viewer** seat in your workspace and they see results only, for every project in it, so use a separate workspace for a client who must not see other clients: [Give clients a viewer seat](https://testsy.dev/blog/give-clients-a-viewer-seat-to-see-test-results/). For one result, a [share link](https://testsy.dev/blog/show-clients-proof-not-screenshots/) shows just that run.

This post is part of [Find the bug before your client does](https://testsy.dev/blog/find-the-bug-before-your-client-does/).
