Answer product questions before planning stalls.
Explore product usage, calls, support, and warehouse data in one thread without turning data into a ticket queue.
Ryan O'Connor
@compass What latent demand shows up across Gong, support, and product usage?
Turn product questions into shipped decisions.
Launch readouts, metric definitions, customer signals, and next steps stay in the thread where the work is already happening.
Launch readouts without the wait
Ask what changed while the launch conversation is live, then decide in-thread with context everyone can see.
Shared answers in Slack or Teams
Compass brings curated data context and approved business context into the channel so PMs, data teammates, and leaders work from the same answer.
Curated context
WAU = users with a core workspace event in the trailing 7 days. Login-only activity is excluded.
with wau_events as (
select user_id,
date_trunc('week', event_time) as week
from product_events
where event_name in ('project_created',
'query_run', 'teammate_invited',
'shared_answer_viewed')
group by 1, 2
)
select week, count(*) as weekly_active_users
from wau_events
group by 1No more metric archaeology
Stop chasing the data team for which WAU, activation, or retention definition won last quarter.
Show-your-work answer paths
Compass answers like an analyst and shows the datasets, SQL, and approved definitions behind the result.
Gong
18 calls
Pylon
42 tickets
Snowflake
product usage events
Open-ended exploration
The best product signals are already in your data. Compass helps teams mine them without a new pull for every hunch.
Find signal across messy sources
Compass connects behavior, calls, tickets, and warehouse data so repeated patterns become evidence your team can use.
Notion
Linear
Jira
Google DocsOne thread for inputs, answers, and follow-through
Pull context from other agents or work apps, validate the answer, and turn the decision into real work without copy-paste.
MCP Servers and Skills as context and action
Compass can read MCP Server context, then write back to Notion, Linear, Jira, or Google Docs from the same thread.
How product teams adopt Compass
Pick one concrete product workflow: measure adoption of a recently released feature, or mine latent demand from calls, support, and product behavior. Then expand once the questions, context, and review loop are working.
Pick one released feature
Data teams connect the product events, warehouse tables, calls, and support context behind one feature adoption workflow.
Answer adoption questions in-thread
PMs ask who adopted it, where drop-off happens, and which segments are showing demand, with curated data context behind the answer.
Review threads and missing data
Data teams see which answers worked, where definitions were unclear, and which missing fields or tables belong on the data roadmap.
Self-serve starts to stick
The product team can self-serve common adoption questions while data teams monitor quality and approve reusable context.
