Pomio Insights

InsightsCompare·Author: Pomio·

Should CRM teams follow the org chart or the way you sell?

Direct answer

Follow the way you sell. In a CRM a team is not just a box on the org chart: it decides who sees which deals, whose pipeline a sales manager reviews and which target a result counts towards. So build teams around the people who work the same pipeline and answer to the same sales manager, for example new business, account management or a regional sales group. Keep everything else that describes people or customers, such as office, region, product line or segment, as a location or a label, so you can filter on it without changing who sees what. Give every team one responsible manager, give every salesperson one home team for targets and reviews, and change the structure only at a natural moment such as the start of a quarter. Pomio CRM has teams and locations, permissions with an own, team or organisation scope enforced on the server, targets per user or team and a scoreboard by period.

Pomio CRM lets a sales team share one pipeline while each person keeps a clear scope. The moment you set up teams in a CRM, you are making decisions about visibility, reviews and targets, often without noticing. Many SMEs simply copy the org chart: one team per department or office. That feels tidy, but the org chart answers a different question from the one a CRM asks.

Why teams matter more in a CRM than on paper

On the org chart, a team says who reports to whom. In a CRM, a team usually also decides three practical things. First, visibility: with a team scope, people see the deals of their own team and not those of others, as explained in how own, team and organisation scope works. Second, management: the sales manager reviews the pipeline of a team, so the team defines which deals end up in that review. Third, results: targets and the scoreboard are often read per team, so the team decides where a won deal is counted. Get the teams wrong and all three go wrong at once.

The org chart answers a different question

An org chart is built for line management, budgets and HR: who approves leave, who does the appraisal, which cost centre pays the salary. Sales rarely follows those lines exactly. An account manager may sit in the customer service department but work the same renewals pipeline as the sales team. A sales manager in one office may coach salespeople in two locations. The managing director may report to nobody but still own a handful of key accounts. If the CRM copies the org chart, the sales manager reviews deals they do not steer and misses deals they do.

Build teams around a shared pipeline and one manager

A practical rule for most teams of five to fifty people: a CRM team is a group of people who work the same kind of deals and whose pipeline is reviewed by the same sales manager. Typical examples are new business, account management for existing customers, partner or reseller sales, or a regional sales group when regions really are managed separately. Each team has one responsible manager who runs the weekly pipeline review and answers for the team target. Each salesperson has one home team, so a result is never counted twice or not at all, in line with the choice described in targets per person or per team.

Use locations and labels for the rest

Not every grouping needs to be a team. Office, country, product line, customer segment or industry are useful for filtering and reporting, but they do not have to change who sees which deals. Record the office as a location and the product line or segment as a label from a fixed list of labels. That way you can still answer the question “how is the Utrecht office doing?” or “how many deals do we have for our service contracts?” without creating extra teams that complicate access and targets.

When the org chart and the sales structure do match

In many small businesses there is nothing to choose: one sales manager, one team, one pipeline. Then the org chart and the CRM are the same and there is no reason to invent extra teams. The choice only matters once there are several managers, several offices or several kinds of selling. A good test: if two groups would be discussed in the same pipeline review by the same manager, they are one CRM team, whatever the org chart says.

Visibility follows the team, so check it

Because a team scope decides what people see, every team change is also an access change. Moving a salesperson to another team can hide their old deals from their former manager or show them a pipeline they never worked on. Decide beforehand whether salespeople see only their own deals, their team’s deals or everything, as discussed in whether salespeople should see each other’s deals. When someone moves, check that every open deal still has one clear owner, and include team membership in the quarterly access review.

Change teams at a natural moment

Team changes in the middle of a period make targets and the scoreboard hard to read, because half of the results sit in the old team and half in the new one. Where possible, change the structure at the start of a month or quarter, agree what happens to open deals, and tell the people involved before it happens. When a salesperson leaves rather than moves, the approach in reassigning open deals when the owner leaves applies.

How Pomio CRM helps

Pomio CRM has teams and locations, filterable labels and four roles: sales rep, sales manager, viewer and organisation admin. Each permission carries a scope, own, team or organisation, which is enforced on the server, so a team structure really determines who sees which deals. Targets can be set per user or per team for a month, quarter or year, and the scoreboard shows revenue, won deals, funnel, sources and a leaderboard by period. Sales managers see team and organisation figures according to their role, while sales reps see their own scope by default. An overview of the capabilities is on the features page.

A practical checklist

Build teams around people who share a pipeline and one sales manager; do not copy departments or cost centres one to one; give every team one responsible manager; give every salesperson one home team for targets and reviews; record offices as locations and products or segments as labels; start with one team when there is one manager; decide what a team scope lets people see; check deal ownership when someone moves; include team membership in the quarterly access review; change the structure at the start of a month or quarter.

Further reading

Can someone belong to two teams?

It can be useful for a manager who coaches two groups, but for targets and reviews every salesperson should have one home team. Otherwise a won deal is easily counted twice or argued over.

Should the managing director be in a sales team?

Only if they own deals in that pipeline. If they mainly look at figures, a role with organisation-wide read access fits better than a team membership.

Should each office be its own team?

Only when each office has its own sales manager and pipeline review. Otherwise record the office as a location and filter on it.

How often should the team structure change?

As rarely as possible, and preferably at the start of a month or quarter, so targets and the scoreboard stay comparable.

FAQ

Short answers you can cite. Indicative for this mockup.

Should CRM teams follow the org chart or the way you sell?

The way you sell: a CRM team is a group of people who share a pipeline and answer to one sales manager, because the team decides visibility, reviews and targets.

What should be a team and what a label?

Make a team of people who are reviewed together by one manager. Record office as a location and product line, segment or industry as a label.

Does a small business need several CRM teams?

No. With one sales manager and one pipeline, one team is enough. Extra teams only make sense with several managers or several kinds of selling.

When should the team structure change?

At a natural moment such as the start of a month or quarter, after agreeing what happens to open deals and checking who will see what.

How does Pomio CRM help?

Pomio CRM has teams and locations, labels, an own, team or organisation scope per permission enforced on the server, targets per user or team and a scoreboard by period.

See Pomio CRM in your own tenant.

Start a 14-day trial or request a demo. This preview site has no purchase flow.