/ Industry · E-commerce

Peak-ready teams.
Lean tool spend.

Ops, fulfilment and customer-service teams ride seasonal peaks on a stack of tools. Compass unifies tasks and signals across the apps you use, sharpens CS and ops teams with aggregate signals, and recovers idle seats between peaks.

Aggregate signals, source attribution always shown. Decision-support — you stay the decider.

/ 01   Ops workspace

One unified
ops workspace.

During a peak period, ops and CS teams context-switch between Asana, Slack, Notion, Google Calendar, and half a dozen other apps. Compass unifies the task surface — source attribution always shown — so your team sees what needs to happen without hunting across tabs.

Compass does not replace any of those tools; it surfaces signals from them in one place. The origin of every task or signal is always visible.

compass · ops workspace · unified task view

Today’s ops surface — source attribution shown

Resolve escalated ticket #4421 Slack
Review fulfilment SLA report Notion
Peak prep sprint planning Calendar
CS capacity check — Black Friday Asana
Update returns workflow doc Notion
Carrier SLA review call Calendar
Source badge always shown — every item traces back to the tool it originated from. No black-box aggregation.
Illustrative data. Tasks shown are sample items. Real view depends on which tools you’ve connected and their live data.
compass · saas spend · off-peak idle report

Recoverable spend estimate — off-peak period (90d)

≈$1,850
per month recoverable (illustrative)
CS platform seats (0 tickets last 45d) 9 idle
Ops tool seats (<1 session/wk) 6 idle
Fulfilment reporting seats (dormant) 4 idle
Idle detection uses login frequency and session counts only — Compass never reads ticket content, customer data, or messages.
Illustrative data. Figures are sample values. Real estimates depend on your tool stack, seat pricing, and seasonal observation window.
/ 02   Seasonal spend

Recover seasonal
idle spend.

E-commerce teams scale up for peak seasons and forget to scale the SaaS bill back down. Compass tracks login frequency and session counts across your CS, ops, and fulfilment tools, surfaces seats that have gone idle in the off-peak period, and gives your ops lead the evidence to consolidate.

No content is read. Compass tracks usage signals only. You stay the decider on which seats to cut and when.

/ What Compass is not

Honest about
what it doesn’t do.

Aggregate — not per-person surveillance
Workforce signals are aggregate. Compass does not surface an individual team member’s usage patterns to management. It shows where the team as a whole is concentrated.
Source attribution always shown
Every task or signal in the unified workspace carries its source badge. There is no black-box aggregation that obscures where data came from.
Decision-support, not a verdict
Compass surfaces signals and recoverable spend estimates. Your ops team makes all decisions — which seats to cut, how to staff peak periods, how to triage CS queues.
Never reads customer data or ticket content
Compass reads usage metadata — login frequency, session counts, calendar signals. It never reads customer records, ticket conversations, order data, or any operational content.

Aggregate and source-attributed. Compass reads usage and calendar metadata — never customer data, ticket content, or order records. Decision-support; you stay the decider.

Compass