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.

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, 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.

Each plan includes a set number of projects and members:
| Free trial | Starter | Team | Growth | |
|---|---|---|---|---|
| Price | Free | $49 a month | $149 a month | $299 a month |
| Runs included | 10, once | 100 a month | 500 a month | 1,200 a month |
| Extra runs (packs of 50) | — | $30 | $20 | $15 |
| Web runs at a time | 1 | 5 | 10 | 20 |
| App runs at a time | 1 | 1 | 3 | 10 |
| Android and iOS app tests | Yes | Yes | Yes | Yes |
| Members | 1 | 5 | 25 | 100 |
| Projects | 1 | 2 | 5 | 15 |
| Tests | 20 | 300 | 1,000 | 5,000 |
| Assistant drafts a day | 40 | 300 | 300 | 300 |
| Phone number and endpoint calls | — | Yes | Yes | Yes |
| Invite people | — | Yes | Yes | Yes |
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. For one result, a share link shows just that run.
This post is part of Find the bug before your client does.
Filed underWebClient sitesSharing and alerts