Customer City exists because revenue teams deserve the same observability that engineering teams have had for years. We built the platform we always needed.
Every revenue team uses Salesforce or HubSpot and 5-10 tools on top of it. Email, calendar, contracts, call recordings, sales engagement. Each one captures a fragment of the picture. But no tool shows you the full picture.
The result? Deals die in the gaps between tools. Champions go silent. Proposals go unopened. Critical stakeholders never get engaged. And your pipeline dashboard says everything is fine.
We defined the Revenue Observability category: the missing layer that sits on top of your entire stack and cross-references every data point to surface what your team is missing right now.
The Opportunity
$20B+
What Datadog proved observability is worth. Revenue teams are next.
68%
Of deals have at least one undetected blind spot
0
Tools that monitor deal health across your full stack
CEO & Founder
I spent years in RevOps leadership watching the same pattern repeat: deals would slip, forecasts would miss, and everyone would wonder what happened. The warning signs were always there, buried across disconnected tools that nobody had time to cross-reference. I built Customer City to connect the dots across the entire revenue stack so teams stop being surprised by pipeline failures.
Before founding Customer City, Jay led revenue operations at high-growth SaaS companies where he saw firsthand how blind spots in the pipeline led to missed forecasts and lost deals. That experience, watching deals die in the gaps between tools, became the founding insight for the Revenue Observability category.
Four principles that shape every decision at Customer City, from product design to how we communicate with customers.
We tell you what is happening in your pipeline. No fluff, no vague scores. Specific warning signs, specific deals, specific actions.
Every alert points to a real deal with a real risk. We don't surface noise. If we flag it, it matters.
Built by people who ran revenue teams. Every feature exists because an operator needed it, not because an analyst imagined it.
Pipeline risks compound daily. Blind spots surface in real time, not in next week's QBR deck.
Revenue Observability is changing how teams protect their pipeline. Whether you want to see it in action, explore a partnership, or join the team, we want to hear from you.
Interested in joining the team? We'd love to hear from you