Product signals and pipeline in the same place.
SaaS revenue teams don’t lack data, they lack it in one place: usage in the product database, pipeline in the CRM, tickets in a third tool. This pack models the account lifecycle end to end and treats product signals as ordinary fields — so “trials with high usage and no scheduled call” is a view, not a data request.
What lands in your workspace on day one.
Not a template gallery — objects with real relationships, a pipeline with real stages, and automations already running.
- Accountplan, ARR, seats, health score, usage trend, owner
- Trialstart/end, activation events, seats invited, conversion likelihood
- Subscriptionterm, renewal date, seats, expansion opportunity
- Opportunitytype (new/expansion/renewal), value, stage, close date
- Contactrole, champion status, last product login, engagement
Rename, reorder, or retire any stage. Add a second pipeline for a different motion.
Automations, not suggestions.
These are live the moment the pack installs. Every one is editable, and every run keeps a step-by-step trace.
Activation nudges
A trial that signs up but never completes the key activation step gets targeted help, and the AE is told which step they’re stuck on rather than just that the trial is quiet.
Expansion signals
When an account crosses a seat or usage threshold, an expansion opportunity is created and routed with the usage trend attached.
Churn-risk escalation
Declining usage, a departed champion, or a support spike moves an account into an at-risk segment and creates a task before the renewal conversation, not during it.
Renewal runway
Renewal opportunities open on a schedule relative to term end, with the account’s usage and support history summarised for the owner.
The problems this pack was shaped around.
Usage as a field, not an integration project
Push product events in through the API and they become fields and related records — filterable, reportable, and usable as automation triggers. That’s the difference between knowing an account is quiet and having a workflow that acts on it the day it goes quiet.
New, expansion, and renewal are different motions
Forcing all three through one pipeline is why SaaS forecasting is so often wrong. Multiple pipelines on the same object let each motion keep its own stages and still roll up into one revenue picture.
One record for the whole lifecycle
Marketing, sales, onboarding, and renewal touching the same account record means the renewal owner can see the promises made during the trial. It also means attribution is a report rather than a reconciliation between two databases.
The same platform, whatever you sell.
A pack is configuration on top of one shared data model, one filter engine, and one automation engine. That is why you can change any of it without losing the parts that work.
B2B SaaS, answered.
How do product usage events get in?
Through the API. Events can update fields on the account, create related records, and trigger workflows — the same paths the UI uses, so validation and permissions still apply.
Can I model product-led and sales-led motions together?
Yes. Separate pipelines with their own stages on the same Account object, reporting together or separately.
Does this replace a customer success platform?
For health scoring, at-risk segmentation, and lifecycle automation, usually yes — because those are filters and workflows on data you already have here. Deep in-app messaging is a different category and stays with your product tooling.
Can I sync to my warehouse?
Yes — everything is available through the API, and views export to CSV for ad-hoc analysis.
Start with the b2b saas pack already installed.
Free workspace, the objects and automations above set up at onboarding, and every price published. Customise from something that works.
Free trial · no card required · every price published