How Weights & Biases ships a new purchase signal in 2 days on Cargo
Frederic PinchonBefore Cargo, taking an idea from concept to execution could easily consume a month, considering the briefing, development, and integration phases. Now, we're looking at a turnaround of just two days. This has changed our operational tempo.Frederic Pinchon
Before Cargo
Signal ideas arrived faster than anyone could ship them
Weights & Biases finds enterprise buyers among its free users by watching for usage patterns that predict a purchase. When a rep acts on the right signal at the right time, it works, and the sales team is always asking “what if we try this?” about new ones.
"The pace at which our teams generate ideas, challenging us with 'What if we try this?' moments, demands equally fast delivery of supporting data or processes. If we fail to act quickly, these ideas slip away pushing our executives to seek alternative solutions, such as creating dormant dashboards in Tableau."
The data was already centralized. A new signal usually meant joining CRM, email marketing and product analytics data, then acting on the result across several sales tools. Nothing sat between the warehouse and those tools, so each signal became a bespoke script requested from engineering, and that took weeks.
"My priority was to maintain agility and control over the entire solution process, from design to implementation. The challenge was finding a way to achieve quick results without extensive coding, given our tight timelines and the lack of additional manpower to delegate tasks. We needed a straightforward, swiftly adaptable solution."
Most ideas were dropped before anyone tested them. Off-the-shelf GTM tools were considered and ruled out. Each one comes with fixed use cases, and covering the range of ideas would have meant buying and running workflows across a long list of tools.
What runs on Cargo
Weights & Biases built one data model in Cargo over its warehouse (product data), Salesforce (sales data) and Stripe. Metrics on that model decide when an account deserves a rep’s attention. When a metric changes, a change-based trigger starts a play that acts in Salesforce, Slack and the other sales tools. A new signal is a new metric and a new play, not a new pipeline.
Play 1: Recontacting accounts that engage with content
The model tracks how several users from the same account engage with content across marketing campaigns. When an account crosses the threshold, an allocate node finds the AE who owns the relationship and sends them a message with the context to start the conversation.
"Cargo gives a rapid turnaround of just a couple of days, bypassing the need to involve infrastructure teams or navigate complex operations. Now, I can independently drive projects from ideation to execution, delivering tangible results within days."
Play 2: Telling AEs when a free account nears its limit
Hitting a free usage limit is an upsell signal. The play finds leads approaching each threshold and summarizes their usage so a rep can read it at a glance. It uses the system prompt and output formatting of Cargo’s OpenAI integration, so every digest has the same shape.
Play 3: Matching leads to accounts by product usage
Highly engaged users were slipping through because they could not be enriched enough to match to an account. The play runs a waterfall across several data sources using Cargo’s branching logic. Where the other sources come back thin, Cargo’s native LinkedIn integration fills in company size, industry and location, the minimum needed to match a lead to an account.
The outcome
"Before Cargo, taking an idea from concept to execution could easily consume a month, considering the briefing, development, and integration phases. Now, we're looking at a turnaround of just two days. This has changed our operational tempo."
2 days from idea to a running signal
The time to stand up a new sales trigger fell from weeks to an average of two days. Ideas that work turn into good sales conversations, so the sales team brings more of them, knowing they will ship.
"I'm excited about Marketing ops’ involvement because it signifies a broader interest from our operations team in exploring new possibilities with Cargo. However, I'm eager for our head of customer success and head of strategy to start bringing their use cases and ideas."
The same data model now takes use cases from marketing and customer success, starting with platform usage and customer health monitoring.
Hundreds of leads matched to accounts every day
The data model catches hundreds of leads a day that used to go unmatched.
Two thirds less prep time per lead
Reps read the usage digest instead of researching the lead, and get to the conversation sooner.
Weights & Biases (WandB) is a developer-first MLOps platform that simplifies the machine learning workflow by enabling engineers to track experiments, manage dataset versions, evaluate model performance, and reproduce models with ease.
- Signal ideas arrived faster than anyone could ship them (1 min)
- Play 1: Recontacting accounts that engage with content (2 min)
- Play 2: Telling AEs when a free account nears its limit (1 min)
- Play 3: Matching leads to accounts by product usage (1 min)
- 2 days from idea to a running signal (1 min)
- Hundreds of leads matched to accounts every day (1 min)
- Two thirds less prep time per lead (1 min)
Build the self-driving GTM engine
Your coding agents build it on Cargo.Or our team builds, operates and improves it with you.