Novrith

Revenue Engine

How Juo unified partners, sales, and product usage into one Revenue Engine on Attio

A conversation with Alina Prelicz, Co-founder

Challenge

Juo ran two motions at once, a partner-and-sales motion and a product generating rich subscription data, but they lived apart. Attio held contacts and deals while shops, MRR, and usage sat in Metabase, so customer health couldn't be read next to the commercial relationship.

Solution

We built an Attio Revenue Engine that treats subscription data as a first-class citizen: cleanly segmented companies, a real lead-to-client lifecycle, product usage modeled as native objects, and event-driven workflows, with Metabase and Intercom bridged via n8n.

Results

  • Attio became the single source of truth across partners, leads, and clients, with product usage sitting next to the commercial relationship.
  • The funnel follows an explicit lead-to-deal-to-client lifecycle: leads enter only when qualified, and a won deal moves the client straight into onboarding.
  • MRR, active subscriptions, and new-subscription momentum at 30, 60, and 180 days flow from Metabase into Attio, so customer health and expansion timing are visible from the CRM.
  • The partner channel has a defined lifecycle and Bronze/Silver/Gold tiering, turning scattered referrals into a managed growth channel.
  • Intercom conversations land against the right company and person, and event-driven workflows move the funnel automatically, so the team manages exceptions instead of chasing handoffs.
We needed a CRM to serve as a single source of truth across our product, support, and go-to-market teams. Marco grasped our account structure immediately and was a genuinely engaged partner from start to finish, handling the full setup and automation while guiding us toward solutions that fit our culture and the way we work with clients. In a fast-growing company, having a partner like this is invaluable.
Alina Prelicz, Co-founder

Needs and objectives

Juo didn't need another disconnected dashboard. They needed Attio to become the backbone of their revenue model, one that reflects how a subscription business actually grows across partners, sales, customers, and product usage.

  • Turn Attio into the single source of truth across partners, leads, clients, and the product itself.
  • Cleanly segment one Companies object into Partners, Leads, and Clients, without duplicating company records.
  • Define a real lead-to-deal-to-client lifecycle with a structured sales pipeline that starts only once a lead is qualified.
  • Bring the product's subscription data, shops, MRR, active subscriptions, and subscription trends, into Attio so customer success and expansion decisions are grounded in real usage.
  • Give the partner channel a lifecycle and a tiering model, so informal referrals become a managed, rewardable channel.
  • Connect Intercom support conversations to the right company and person, with full thread history stored in the CRM.

From two disconnected worlds to a single Revenue Engine

Juo's story isn't about bolting another tool onto the stack. It's about recognizing that a subscription business has two halves, the commercial relationship and the product usage, and that the value compounds only when both live in the same model.

Before this work, Juo had strong raw material on both sides: a real partner and sales motion, and a product generating detailed subscription data shop by shop in Metabase. But those halves never met. Simple questions like "which clients are scaling and ready to expand?" or "which partners actually drive qualified pipeline?" meant digging across Attio, Metabase, and Intercom by hand.

For B2B SaaS and subscription businesses, the lesson is straightforward:

  • Product usage and the commercial relationship belong in one model. When MRR and subscription momentum sit next to the deal and the client lifecycle, customer health stops being a guess.
  • A channel without structure isn't a channel. Giving partners a lifecycle and tiering turns informal referrals into a managed, measurable source of growth.
  • Event-driven handoffs beat manual checks. When qualification creates deals and wins trigger onboarding, the funnel moves on real events instead of someone remembering to move it.

By segmenting companies cleanly, modeling shops and conversations as first-class objects, and wiring product data and support into the same architecture, Juo turned Attio into a strategic asset: one system where partners, sales, customers, and product usage finally tell a single, coherent story.

Recognize parts of Juo's story in your own SaaS or subscription business?

If you are running a subscription motion, blending partners, sales, customer success, and product usage signals across disconnected tools, with your richest data sitting in an analytics layer that never reaches the CRM, it's a sign you have a system design problem, not a tooling one.

Novrith designs and implements Revenue Engines on Attio that turn fragmented motions into decision-ready systems: clean segmentation across partners, leads, and clients; product usage modeled as native CRM data; partner lifecycles and tiering that make your channel measurable; and event-driven workflows that move the funnel on real behavior.

Let's talk about what a similar Revenue Engine for your subscription business could look like.