Heavy Customer Success Platforms vs CRM-Native Onboarding
Daniel Zarick, CEO of Arrows, on the problem with customer success platforms
The hard part in customer success software is not buying the product, it is forcing a company to redesign its post sales workflow around a new system. Tools like Gainsight ask teams to define health scores, lifecycle stages, playbooks, alerts, ownership, and data flows across CRM, support, and product systems before value shows up. Arrows is positioned around a much smaller starting point, a customer facing onboarding plan that can sit on top of HubSpot and get used immediately, then deepen over time.
-
Dedicated customer success platforms tend to become an operating system for the whole CX team, not a lightweight add on. That is why setup is heavy. The product only works well once customer data, reporting, and workflows are modeled correctly, and comparable commentary on Gainsight also describes teams deciding whether to work from it as their primary system.
-
Arrows deliberately removed much of that implementation burden by treating the CRM as the source of truth. In practice, the CSM or onboarding manager launches a plan from a closed won deal in HubSpot, sends the customer a checklist, and syncs task status back into HubSpot for reports and automations. That avoids a second inbox and makes rollout much faster.
-
This tradeoff also explains market size. Customer success platforms sell to a relatively narrow group that is willing to run a specialized post sales stack, while HubSpot alone reported more than 205,000 customers at the end of 2023 and more than 268,000 customers are referenced in its current ROI materials. Arrows is aiming at the broader CRM installed base instead of only mature CS teams.
The category is moving toward CRM native post sales tools that start with one visible workflow, then pull more automation and reporting into the existing system. As HubSpot keeps expanding its customer base and platform depth, products that can be installed quickly and prove value inside the CRM should keep taking share from slower, full stack rollouts.