Skip to content
GuideAdministrationIntermediate

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.

RRRevTech RevOpsRevenue operations team 2 minUpdated

Product walkthrough

See it in RevTech

See how RevOps establishes teams, ownership, and target accountability so agent work follows the operating model.

See how RevOps establishes teams, ownership, and target accountability so agent work follows the operating model.
Part 1 of 4

Teams are structural, not cosmetic

Teams live in Goals & Targets: the Team Setup tile there opens Teams, which needs the Manage Teams permission. Without it you can see the tile but not open it. The teams you create appear across Goals & Targets, planning and reporting. Each carries an owner, a description and its members.

The consequential part is that a team is a scope. Team targets are set per team, and the same teams are the option list behind the Team filter on every report that has one, and behind the "Your team" numbers a manager sees on Home. A team created here is a scope everywhere, and a member missing from it is a person missing from their manager's numbers.

RevTech Team Setup: the teams that scope targets and reports, with their owners and members.
Team Setup under Goals & Targets. Each team is listed with its owner and members; teams decide which targets exist, which reports a team filter scopes, and who owns what. Sample data. Screenshot of the RevTech application; sample data.
Team Setup under Goals & Targets: each team with its owner and members.
Part 2 of 4

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.

Part 3 of 4

Creating and editing

Create Team opens the editor, and it is deliberately short: Team Name, Team Owner, Description and Team Members. Existing teams show their owner, description and member count on their card, a search finds a team by name, and any card opens for editing.

Archiving lives inside the editor and asks for confirmation first. A team with members other than its owner cannot be archived until you move them, which stops a team disappearing with people still scoped to it. Archiving removes the team from active planning and target assignment, and existing reporting keeps its historical references. It is not a delete, which matters when you later need to explain what a historical number was scoped to. Restoring an archived team goes through support.

Part 4 of 4

The order of operations

Set up teams and their members 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

  • A team is a scope: it is what team targets attach to and what every report's Team filter narrows to.
  • Model the teams you manage against, not the org chart in your HR system.
  • Archiving removes a team from planning and target assignment. Historical reporting keeps it. It is not a delete.
  • Set up teams and their members before setting numbers. The reverse order creates orphaned targets.
Demo

See how the work gets done.

Explore how agents prepare work across your revenue teams, and how people review it, guide it and decide what happens next. Fictional data. Real product.

Explore the demo