Intercom · Strategy · Mid · 45 to 60 minutes
How should Fin for Sales be priced?
Intercom makes customer communication software, including AI agents that help businesses talk with prospects and customers. Answer this product management case and get it graded line by line against a weighted rubric.
- pricing_strategy
- product_judgment
- customer_empathy
- analytical_reasoning
- written_communication
The situation
You are the PM for Fin at Intercom. Fin already works in a service role, where pricing is tied to customer outcomes rather than raw activity. Now Intercom is preparing a sales role for Fin. It can engage website visitors, answer product questions, ask qualification questions, and route promising prospects to a sales rep. Before launch, leadership wants a recommendation for how this sales use case should be priced. The team agrees on the principle that pricing should reflect customer value, not vendor inputs like tokens or conversations. But the right value signal is unclear. Some people favor a simple usage model that is easy to meter. Others want a tighter link to business impact, even if that creates attribution and implementation challenges. There is also a fairness question: pricing should make customers feel Intercom shares performance risk, but should not hold Fin responsible for things outside its control after a handoff to a human rep. Your task is to propose a pricing approach that can work across different customer segments, different sales motions, and mixed conversations where Fin may also handle support questions.
What to produce
Write a 1 to 2 page pricing strategy memo for Fin's sales role.
Your answer must
- Recommend a primary pricing model and define the billable event or unit clearly.
- Compare at least three plausible pricing approaches, including their trade offs on value alignment, customer trust, measurability, and ease of launch.
- Explain where Fin's responsibility starts and ends, and how that boundary affects what Intercom should charge for.
- Describe how your approach can support customers with different definitions of a good sales opportunity.
- Explain how you would handle conversations that mix sales and support, and what you would instrument or test after launch to validate the model.
Constraints
- The initial launch should not depend on heavy CRM integration or complex revenue attribution across every customer.
- The model should fit Intercom's existing belief that buyers prefer paying for results rather than activity.
- Fin may hand off to human reps, so the pricing metric should avoid charging Intercom for downstream outcomes it does not fully control.
Format
Use short sections with headings such as goal, options, recommendation, trade offs, and validation plan.
How Intercom actually played it
When Fin took on a sales role, the team had to redefine what value means for outcome-based pricing and settled on paying when Fin qualifies a lead. The post explains how the principle stays the same while the outcome changes. A compact example of adapting a pricing model to a new use case.
- Keep the pricing principle, change the definition of value per use case.
- Choose an outcome the customer already counts.
- Align your revenue with the customer's success moment.
Built from Building outcome-based pricing for Fin for Sales by Aisling O'Reilly.
Related case studies
- How should Intercom win its first paying SMBs?Intercom · Go-to-market · Senior
- How should Intercom launch an ML support bot?Intercom · AI product · Senior
- How should Intercom prove support drives revenue?Intercom · Metrics · Mid
- How should Fin handle support email?Intercom · AI product · Mid
- Should Fin still be priced per resolution?Intercom · Strategy · Mid
- How should Fin be priced at launch?Intercom · Strategy · Senior