Ownership of Product Usage Data

Diving deeper into

Thomas Schiavone, co-founder and CEO of Calixa, on the PLG data pipeline

Interview
if you can't do this product-led motion well because the tool can’t handle it, and top-down sales is not the primary motion
Analyzed 3 sources

The real shift is that the team owning product usage data starts to matter more than the team owning pipeline fields. In a product led company, the most valuable question is not who did the rep log a call with, it is which users, workspaces, or accounts are suddenly activating, inviting teammates, or showing buying intent. That makes warehouse connected tools like Calixa more native to the motion than a classic CRM built around top down deal stages.

  • At Twilio, the internal tool that inspired Calixa existed because Salesforce did not show the product signals that mattered. Teams needed one place to see who was using the product, prioritize those accounts, and act on them, instead of waiting for reps to manually create the picture.
  • This is a workflow change as much as a software change. In PLG, sales often starts after users are already active, so reps need alerts on usage spikes, team invites, and account level momentum. Census describes this as collapsing messy usage into signals that tell a rep exactly where to look and when to reach out.
  • The tradeoff is clear in the market. Calixa argues startups should optimize first for bottoms up selling, especially before they are locked into Salesforce. Arrows makes the opposite design choice, pushing data into HubSpot so teams stay in one familiar inbox. The split is between building a new operating surface and extending the old one.

The next stage is tools that turn raw event streams into recommended actions automatically. As warehouses get faster and more teams run PLG plus sales assist together, the winning systems will not just store customer records. They will tell sales, success, and product which account is breaking out, why it matters, and what to do next.