Company Context

Rippling is a multi-product workforce management platform serving SMBs and mid-market companies across HR, IT, payroll, benefits, device management, and spend management. The company grows by expanding customers from one core product into adjacent products inside the same admin experience.

Problem

Rippling's growth team wants to improve cross-sell performance for Rippling Spend among customers already using Rippling Payroll and Rippling HRIS. Today, cross-sell messaging is mostly based on account eligibility and firmographics. Conversion from qualified accounts to activated Spend customers is only 3.8% within 90 days, and sales feedback suggests many offers feel like feature promotion rather than a solution to an urgent customer problem.

Customer interviews show mixed signals: some admins struggle with employee reimbursements, card controls, and policy enforcement; others say their current finance workflow is "good enough" and do not want another rollout. Leadership wants a clearer way to determine whether Rippling Spend solves a real pain point for a given segment before investing in more in-product promotion.

Deliverables

1. Explain how you would identify the underlying customer pain point that a cross-sell product like Rippling Spend should solve.
2. Define which customer segments you would prioritize first and why.
3. Describe what evidence would tell you the pain point is strong enough to justify a cross-sell motion.
4. Recommend the MVP product or growth interventions you would test inside Rippling to validate demand.
5. Define success metrics and key trade-offs.

Constraints

• You have one quarter to recommend and validate an approach.
• Engineering support is limited to lightweight in-product surfaces and basic CRM/data instrumentation.
• You cannot rely on a full sales-led motion; the solution should work through product-led discovery and qualification.
• You must avoid creating a spammy admin experience across Rippling surfaces.