Setting up teams and ownership
Teams decide which targets exist, which reports scope, and who owns what. A structural decision that is cheap to make and expensive to change.
Product walkthrough
See it in RevTech
See how RevOps establishes teams, ownership, and target accountability so agent work follows the operating model.
Teams are structural, not cosmetic
Team Setup creates the teams that appear across Goals & Targets, planning and reporting. Each team carries an owner, a description, and the consequential part, the KPIs it is responsible for. The same teams are the option list behind the team filter on every report, so a team created here is a scope everywhere.
That last field is not a tagging exercise. The KPIs assigned to a team determine which team targets and individual targets are visible for it. Assign the wrong set and the targets you expect to set simply are not there, which reads like a missing feature rather than a configuration choice.
Model what you manage against
The most common setup mistake is mirroring the HR org chart. Teams here exist to scope targets and reporting, so the right structure is the one you actually manage revenue against: usually segments, territories or motions, which may or may not match reporting lines.
A useful test: if you would not run a separate forecast conversation for a group, it probably does not need to be a team. Teams that exist only to appear in a hierarchy dilute every report they show up in.
Creating and editing
Create Team opens the editor, and it is deliberately short: team name, team owner, description, and the responsible KPIs. Existing teams show owner, description, KPIs and member count on their card, and any card opens for editing. System teams cannot be edited or archived. That is deliberate, not a permissions gap.
Archiving lives inside the editor and asks for confirmation first. It removes the team from active planning, target assignment and reporting views. It is not a delete, which matters when you archive a team mid-year and later need to explain what a historical number was scoped to.
The order of operations
Set up teams and assign their KPIs first, then go to Goals & Targets and set the numbers. Doing it the other way round produces targets attached to a structure that then changes underneath them.
This is the least glamorous surface in the product and one of the few where a decision made in ten minutes shapes what every reporting surface can say for the rest of the year. It is worth the ten minutes.
What to take away
- The KPIs assigned to a team decide which team and individual targets exist at all.
- Model the teams you manage against, not the org chart in your HR system.
- Archiving removes a team from planning, target assignment and reporting. It is not a delete.
- Set teams and their KPIs before setting numbers. The reverse order creates orphaned targets.
Try the demo.
See agents carry the repeatable work of GTM across sales, marketing, customer success, and RevOps. Every action prepared, reviewed, and recorded. Fictional data, real product.
Explore the demo