Team features

Run outbound as a team. Not as a row of solo reps.

Workspaces, shared ICPs, manager view, Slack alerts, SSO — Mama's team layer turns a personal SDR tool into a team-wide outbound operation. White-label and API on Pro for teams running multiple ICPs, segments, or brands.

5 seats included on Team · Manager view standard · SSO on Team+
signalmama.com/team/settings
Team plan
Team configuration · NA Outbound
5 seats used / 5 · 3 workspaces · 8 integrations connected · last sync 4m ago
Audit log + Invite seat
Seats used
5 / 5
Add a seat at $35/mo
Workspaces
3
Each with own ICP
Roles
3
Admin · Manager · Rep
Integrations
8
All connected, last 4m
NA Outbound
Mid-Market SaaS · NA
Active
217 briefs / wk
5 reps active · ICP locked 4d
EMEA Outbound
Mid-Market SaaS · EMEA
142 briefs / wk
3 reps · separate ICP
Customer Expansion
Existing customers · upsell
68 briefs / wk
2 CSMs · own playbook
Team members · NA Outbound
5 seats · 3 roles · workspace-scoped permissions
A
Admin
All workspaces
Active now
P
Manager
NA + EMEA
12m ago
M
Marcus T.
Rep
NA only
2h ago
J
Rep
NA only
38m ago
D
Rep
EMEA only
4h ago
Connected integrations
8 active · per-workspace scope on Pro
Salesforce HubSpot Slack Outreach Salesloft Apollo Lemlist Smartlead
Six pieces of the team layer

Everything a team needs that a solo rep doesn't.

When you go from one rep to five, six things have to change about how your outbound runs. We built each of them into the Team layer so you're not duct-taping permissions, shared docs, and Slack alerts together yourself.

Team+
Workspaces
Isolated spaces, each with its own ICP, brief library, integration credentials, and member list. Run NA + EMEA from one account, or split by Enterprise / Mid-Market / SMB. No data leakage between workspaces, ever.
  • 3 workspaces on Team, unlimited on Pro
  • Per-workspace ICP rubric & locked-by-manager flag
  • Per-workspace integration credentials on Pro
Team+
Shared ICP rubric
Manager defines the ICP rubric once. Every brief on the workspace scores against it. Reps can filter their queue but can't change the definition — so variance across the team drops to zero. Consistency stops being a meeting and starts being the default.
  • 4-dimension scoring (fit / recency / strength / intent)
  • Locked by Admin or Manager role
  • Version history with rollback on Pro
Team+
Roles & permissions
Three roles, each scoped per workspace. Admin owns billing and seat invites. Manager owns the ICP and team data. Rep owns their own queue and history. Permissions inherit through workspaces — Marcus can be a Rep in NA and a Manager in EMEA.
  • Admin · Manager · Rep (built-in)
  • Per-workspace scoping
  • Custom roles on Pro
Team+
Manager view
A second screen built only for managers. Every brief generated by every rep, filterable by signal type, ICP fit, reply outcome, or meeting booked. Drill into any rep, any account, any signal — without scheduling a 1:1. Same data your VP wants every Friday, packaged.
  • Per-rep KPI strip + drill-down
  • Signal-to-meeting attribution charts
  • One-click weekly export to your VP
Team+
Slack alerts & routing
Push high-fit signals straight into #buying-signals, or DM the right rep when their accounts fire. Filter rules let you scope alerts by signal type, ICP fit, territory, or watchlist — so the channel stays signal, not noise.
  • Native Slack + Microsoft Teams
  • Per-rep DM rules & per-channel routing
  • Webhook on Pro for custom destinations
Pro
White-label, API, SSO
The pieces a multi-ICP, multi-segment, or multi-brand team needs. White-label briefs with your logo and colors. Full API + webhooks for custom workflows. SSO via Google, Okta, Microsoft. SOC 2 Type II under NDA. Custom DPA available.
  • White-label exports (PDF + web)
  • Unlimited workspaces & per-workspace API keys
  • SSO standard on Team+ · audit log on Pro
Three workspace patterns

How teams actually structure their workspaces.

Most teams start with one workspace and grow. Three setups account for ~90% of the customer base — pick the one closest to your shape, or mix and match. None of them require an admin meeting to figure out.

Single team
3–10 reps · one ICP
Team
Main outbound
Mid-Market SaaS
5 seats
Workspaces
1
Total seats
5
What it solves: shared ICP, manager visibility, Slack alerts. The simplest version of "stop being a row of solo reps."
Multi-region
10–25 reps · regional ICPs
Team
NA Outbound
SaaS · NA
5
EMEA Outbound
SaaS · EMEA
4
APAC Outbound
SaaS · APAC
3
Workspaces
3
Total seats
12
What it solves: region-locked ICPs, regional manager visibility. The setup most teams land at once they cross 10 reps.
Multi-segment / Multi-brand
25+ reps · segment or brand split
Pro
Enterprise
5K+ employees
8
Mid-Market
200–2K
6
SMB
< 200
4
Expansion / CS
Existing
4
Workspaces
4+
Total seats
22+
What it solves: segment-locked playbooks, per-segment KPIs, separate brief libraries. Pro unlocks unlimited workspaces and per-workspace integration credentials.
You don't pick a pattern at signup — you grow into one. Start with a single workspace. Add a second when the ICP needs to fork. Move to Pro when your workspace count crosses 4.
Manager view

The dashboard your VP keeps asking you to build. Already built.

Every brief, every rep, every signal, every meeting booked — attributed back to its trigger. The manager view turns Mama into the reporting layer your team has been faking with Google Sheets.

Signal-to-meeting attribution · NA Outbound · last 30 days
Every meeting traced back to the signal type that triggered its brief
Manager view only
4,872
Signals fired
across 247 accounts
868
Briefs sent
17.8% high-fit
124
Replies
14.3% reply rate
58
Meetings
46.8% reply→mtg
Meetings booked, by signal type 58 total · all attributed
Hiring
18.4% reply 24
Funding
15.1% reply 16
Tech change
12.3% reply 10
Exec move
9.8% reply 5
Voice
8.4% reply 3
Per-rep KPI strip
Briefs, reply rate, meetings booked, signal mix — per rep, drillable in one click. The metric panel your VP would ask you for on Friday.
Brief audit
Open any brief any rep generated. See what they saw before they sent. Coach from real briefs, not retrospective stories.
ICP drift detection
When converting signals stop matching the locked ICP, manager view flags it — so you tighten the rubric before reply rates drop.
One-click weekly export
PDF or CSV. Pre-filtered for the format your VP/board expects. Stop assembling the weekly outbound deck by hand.
The Pro layer

For teams running multiple ICPs, segments, or brands.

Pro is for teams whose outbound complexity outgrew "one ICP, five seats" — multi-brand parent companies, consultancies running outbound services, RevOps teams orchestrating multiple plays at once. Four capabilities make Pro Pro.

White-label briefs — your brand on every export.
Pro
Replace Mama's logo and colors with yours on every brief, PDF export, and shared public URL. Useful when your team ships briefs to internal stakeholders, executives, or external partners who shouldn't see vendor branding. Two clicks to configure per workspace.
Default
Signal Mama
White-labeled
YourBrand
Full API + webhooks.
Pro
Every brief, signal, theme, and tech change available programmatically. Per-workspace API keys so you can wire Mama into your own apps, internal tools, or customer-facing products. Webhooks push events to wherever you want them.
# Get briefs for an account curl https://api.signalmama.com/v1/briefs \ -H "Authorization: Bearer sm_live_..." \ -d '{"domain": "notion.so", "workspace": "na-outbound"}' # Webhook: new high-fit signal fires { "event": "signal.fired", "icp_fit": 94, "signal_type": "funding" }
Unlimited workspaces & per-workspace credentials.
Pro
Team caps at 3 workspaces. Pro is unlimited — and each workspace can have its own Salesforce instance, HubSpot account, Slack channel, and ICP rubric. Run truly isolated outbound for each segment, brand, or client engagement without cross-contamination.
Enterprise NA
SF · Slack #ent-na
Mid-Market EMEA
HubSpot · #mm-emea
Brand B Outbound
Separate SF org
+ unlimited more workspaces…
Audit log + custom DPA.
Pro
Every admin action, permission change, ICP edit, and integration credential rotation logged with timestamp and user. Required by enterprise security reviews. SOC 2 Type II under NDA. Custom DPA available. Data residency on request.
12:04
Asif M. locked ICP rubric · workspace "NA Outbound"
Admin
11:47
Priya R. invited 1 seat · role: Rep
Manager
09:32
Asif M. rotated Salesforce credentials
Admin
Team features by plan

Team unlocks the layer. Pro unlocks the complexity.

Solo is for one rep evaluating. Team is the moment outbound becomes a team operation. Pro is for teams whose org chart needs more than three workspaces, or whose security review needs more than the basics.

Solo
$49 / month
1
Seat · personal use
  • Single user, no workspace layer
  • 100 briefs / month
  • Personal watchlist + alerts
  • 30-day brief history
Start free
For most teams
Team
$199 / month
5
Seats · 3 workspaces
  • Workspaces, roles & shared ICP
  • Manager view + signal attribution
  • Slack alerts & team routing
  • SSO (Google · Okta · Microsoft)
  • Add seats at $35/mo · cancel anytime
Start Team trial

Specific use cases for Pro: consultancies running outbound for clients, multi-brand parent companies, RevOps teams orchestrating multiple plays. See the full pricing page →

Team feature questions

What every Admin asks before they roll it out.

Specifically about workspaces, seats, roles, and the Pro layer — pricing details live on the pricing page.

Team is fully self-serve — sign up, invite 4 more seats, create a workspace, lock your ICP. Most teams are live in under 15 minutes. Sales gets involved only when you need a custom contract, annual billing terms, or are evaluating Pro for security review (we send a SOC 2 Type II report, fill out vendor security questionnaires, and arrange a 30-min DPA review). Pro is technically self-serve too, but most teams that need Pro want a 30-min call first.
Admin owns billing, seat invites, workspace creation, integration credentials, and audit log access — typically held by 1–2 people per account (often the team lead and a backup). Manager owns the ICP rubric, team data, manager view access, and Slack routing rules within their assigned workspaces — typically held by sales managers or team leads scoped to specific regions/segments. Rep sees only their own queue and brief history. Each role can be scoped per-workspace, so the same user can be Manager in one workspace and Rep in another.
Yes — per-workspace role scoping is core to how the system is designed. Common pattern: someone leads NA outbound (Manager role on NA workspace) but is also a contributing rep on the Customer Expansion workspace (Rep role there). They see the manager view for NA, but only their own briefs in Expansion. Each workspace's permissions are independent — changing a role in one workspace doesn't affect others.
SSO is included on Team and Pro (no extra cost). We support Google Workspace, Okta, Microsoft Entra ID (formerly Azure AD), and any SAML 2.0 provider. Self-serve setup takes about 10 minutes — paste a metadata URL or upload a metadata XML, test with a single user, then enforce SSO for the whole account. SCIM provisioning (auto-add/remove seats based on directory group membership) is on Pro and adds ~30 min of setup with your IT team. We've done it ~200 times — happy to jump on a call to walk through it.
Every admin-level action and every permission change. That includes: seat invites and removals, role changes, workspace creation/deletion, ICP rubric edits (with diff), integration credential rotations, SSO config changes, API key creation/revocation, manager-view exports, and any data access by support staff (we log it when we look). Each entry has timestamp, user, IP, and the before/after delta where applicable. Audit log is retained for 12 months on Pro, exportable to CSV or pushable to your SIEM via webhook. Full security details →
One bill, per account. Workspaces are an organizational feature, not a billing unit — you pay for seats and the plan tier, not per workspace. So a Team account with 5 seats spanning 3 workspaces pays the same $199/mo as a Team account with 5 seats in 1 workspace. The invoice breakdown shows usage per workspace (briefs generated, signals fired, integration calls) for internal cost allocation, but the bill totals at the account level. Pro is the same — flat $599/mo regardless of workspace count.
Yes. Per-workspace white-label config replaces the Mama logo, primary brand color, and footer attribution on briefs, PDF exports, public shared URLs, and email digest exports. Mama branding is removed entirely from the brief itself — only the workspace owner's brand remains visible. We do keep a small "powered by" footer link on shared public URLs by default (helps with discovery), but that's also removable on Pro. Custom domains for shared URLs (e.g., briefs.yourbrand.com) are available on request — adds ~1h of DNS setup.

Specific Pro questions? Email [email protected] — we typically reply within 4 hours.

Bring your team in

From a row of solo reps. To one outbound operation.

Start a 14-day Team trial. Invite four teammates. Lock the shared ICP. See the manager view by Friday. Worst case, you keep the briefs and cancel.

14-day Team trial · 5 seats included · SSO standard · Cancel anytime