Choose whether pricing should live at the client level, the project level, or both.
Overview
Client pricing is best for standard terms that apply across many projects. Project pricing is best for exceptions, special scopes, fixed packages, or project-specific negotiations.
The goal is to put the rate where the business rule lives. If the client has standard role pricing, start at the client. If one project is different, override the project.
Client vs project pricing
| Use | When | What it affects |
| Client rate card. | The same role prices should apply to most or all projects for a client. | Projects can inherit the client's rate card and billing roster. |
| Client member rate. | One member has client-specific pricing across that client's work. | That member's work for the client can use the client-specific override. |
| Project rate card. | One project has its own role pricing. | The project resolves role rates from its own card first. |
| Project member rate. | One member has a special rate for one project. | That member's project work uses the project-specific override. |
Set up standard client pricing
- Create the roles your team bills by in Profitability → Settings → Rates → Roles.
- Create a client rate card in Profitability → Settings → Rates → Rate cards.
- Add role entries and bill rates to the card.
- Attach the rate card to the client.
- Add members to the client's billing roster and select their billing roles.
- Let projects inherit the client's billing roles when the same roster and role setup should apply.
Set up project-specific pricing
- Decide whether the whole project has special role pricing or only one member has an exception.
- If the whole project has special role pricing, create or select a project rate card and attach it to the project.
- If only one member has an exception, create a project member override instead of changing the card.
- Add project members before configuring project billing roles.
- Open the project billing roster and assign the billing roles each member can use on that project.
- If the project was inheriting client billing roles, confirm the project-level override when prompted.
Inheritance and overrides
- Inherited client setup keeps projects aligned with the client roster and client pricing.
- Project override lets a project use different members, roles, or pricing than the client default.
- Project rate cards should be used when the project's role prices differ from the client standard.
- Project member overrides should be used when one person's project rate differs from the project standard.
Examples
| Scenario | Recommended setup |
| Acme Co uses the same UX Designer and Project Manager rates for every project. | Attach Standard Services to Acme Co and use client billing roles. |
| Website Redesign has a special launch package with different role prices. | Attach a project-specific rate card to Website Redesign. |
| Alex has a negotiated rate only for Website Redesign. | Create a project member override for Alex on Website Redesign. |
| Most Acme Co projects should use the client setup, but one project has a different roster. | Keep client pricing, but configure project billing roles for the exception project. |
Troubleshooting
| Problem | How to fix it |
| A project is not using the client rate card. | Check whether the project has its own rate card or project-level override. Remove the project card if the client card should apply. |
| A member appears on the client but not on the project. | Confirm the project inherits client billing roles, or add the member to the project billing roster. |
| A project needs different billing roles from the client. | Configure project billing roles and confirm the project-level override. |
| Only one person has a different project price. | Use a project member override instead of creating a new project rate card for everyone. |