To keep up with the pace of development, 800+ product teams (and counting) are already using Novus, the first-of-its-kind product agent, to automatically set itself up, monitor product data, and tell you what to do next.

It reads your analytics, GitHub history, and customer conversations, so 100% of your roadmap decisions are based on the most up-to-date information.

It's live, free, and ready today. Whether you’re getting started today or you’re one of the many already using it, here are 23 creative ways teams are already using Novus.

Your primary mode of using Novus: Slack (or wherever else you’re working) 

Before we jump into the use cases, it’s worth noting that the prompts for each Job To Be Done (JTBD) listed here were sent via Slack. 

Novus has a dashboard, goals, guides, flags, memory, replays, and more—but you don’t have to log in to access its data or insights. We simply @Novus in Slack, and Novus does the heavy lifting for us. These use cases and prompts are informed by this. 

1. Informing strategy and finding product-market fit 

PMs spend hours each week on questions that already have answers in their product data. Novus pulls from your analytics, your product context, and your GitHub history to answer them in seconds, so you’re fully briefed and on-strategy before every meeting.

Use Case Prompts
Use case Prompt
Finding product-market fit We're iterating toward product market fit (PMF). Can you give me 5 reasons why you think we haven't found PMF yet? What should we focus on getting right to ensure new users find value?
Finding sticky moments What are the activation moments in my product? What specific actions or behaviors predict whether a new user will stick around?
Updating leadership on progress What did we improve in the product this week, and how would I demo/describe it to exec audiences? Reference the wiki to describe the features, GitHub for when it shipped, and Novus to prove adoption.
Preparing for customer calls Prep me for a call with [customer/account name]. Where are they stuck, and what should I make sure to cover?
Summarizing your progress What problems did we solve for customers this week? Focus on recently merged product improvements this week, and connect them to our product's value prop and existing user friction.
Roadmap prioritization I'm considering whether to prioritize improvements to FeatureA or FeatureB. Which one matters more right now, and why?

2. Shipping product updates for you

When Novus has your product context and Pendo’s tools, it opens the PR, creates the track event, and enriches the ticket without being asked. These kinds of moments make it feel less like software and more like a teammate.

Use Case Prompts 2
Use case Prompt
Surfacing errors Set up a track event to fire whenever a user encounters an error while sending an invitation.
Enhancing tickets Look at some of our newly created Linear tickets. Is there an opportunity to add additional detail to ensure our coding agents have the context they need to build with high accuracy? I realize some of our tickets aren't well-defined.
Fixing issues Can you fix this tracking gap? Create a PR for a new track event to monitor [FeatureA]
Preparing for launch We're releasing to open beta next week. What should I be tracking for the launch? Track it for me and update this channel daily at 12 pm EST.

3. Surfacing behavioral insights 

Ship fast enough, and your tagging falls behind your codebase. That means events and features are going untracked, and your retention analysis runs on data that doesn't reflect the most updated product. We’ve used Novus to catch what our own instrumentation misses, and you can do the same with these prompts: 

Use Case Prompts 3
Use case Prompt
Understanding churn Examine customers who used Novus once but never returned. Tell me about their behavior in their last sessions. Analyze those journeys.
Improving retention Finish this sentence: customers who use _____ (insert feature) retain at a higher rate than customers who don't.
Understanding feature engagement Which features are driving deep engagement vs. shallow, exploratory clicking? Show me the features with the most depth.

4. Getting everyone up to speed

Onboarding a new PM takes weeks, and briefing an exec takes an hour they don't have. Novus has read everything across your codebase, analytics, GitHub history, and customer conversations, so you can hand someone everything they need to know without building it from scratch. 

Here’s how you can do this in your own organization: 

Use Case Prompts 4
Use case Prompt
Onboarding customer engineers Create a demo talk track and outline for new customer engineers who need to ramp up on Novus and demo it to customers. They need to be able to speak to existing functionality and also answer follow-up questions about how current customers are succeeding in the product today.
Onboarding PMs I'm onboarding a new PM onto the team. It's [insert Slack username]. Walk them through everything they should know about the product, our customers, beta usage so far, and key issues we should be focused on solving from a product perspective.

5. Always-on data analysis

Novus posts your daily health digest, tracks GTM goals, routes customer feedback, and flags friction before you think to ask. Instead of going to your data, you can pull it right into where you’re already working: Slack. 

At Pendo, we have Novus connected in a Slack channel with the entire product team. That means we all see its insights daily, from who signed up in the past 24 hours to how often they’re logging in. 

Use Case Prompts 5
Use casePrompt
Daily briefings Alert me on the information below daily at 9 am EST. @ mention me in each message. [full digest spec: active accounts, new signups, growth signals, engineering progress, qualitative context]
Analyzing user feedback Can you send the verbatim response in Slack every time someone responds to our feedback guide?
Tracking goals Give me an update on Novus account signups and our pace toward our EOQ goal.
Spotting friction Show me replays of anyone stuck linking their GitHub.
New user attribution How many new accounts came from our Mind The Product hackathon [insert UTM details]

6. Set your preferences once, and Novus remembers

Tell Novus what "activation" means for your business, which accounts to exclude, which pages matter most, and Novus commits it to Memory. 

Use Case Prompts 6
Use casePrompt
Defining "activation" I want you to define activation as any 3 actions taken in ProductAreaName within 1 week.
Segmenting customers From now on, only show me data from paying customers. Exclude free tier and trial accounts.

7. Upleveling your analytics expertise

Tell Novus what you want to learn, and it builds a curriculum from your real data, explaining concepts in plain English, anchoring every lesson in what's actually happening in your product, and giving you the words to use in your next meeting.

Use Case Prompts 7
Use case Prompt
Building analytics fluency Teach me the fundamentals of product analytics using our real data. Start from the basics, don't assume I know the vocabulary, and anchor every lesson in what you see in our product. Set this up as a daily report in this channel at 12 pm ET

Novus is free and live today. Try it now.