Arrows removes admin blockers via HubSpot

The real product advantage here is speed of change, not just lower cost. In many Salesforce setups, basic changes like adding fields, editing workflows, or exposing new data to a team often run through a dedicated admin or operations owner. HubSpot is more often configured so the people running marketing, sales, or onboarding can make those changes themselves, which makes it much easier for a tool like Arrows to go live fast and fit into an existing PLG motion.

• Arrows built around this by removing its own dashboard and pushing onboarding data back into HubSpot. That lets a team trigger an onboarding plan from a closed won deal, report on overdue tasks inside the CRM, and automate follow ups without making users learn a second operating system.
  1 sacra 2 sacra
• The contrast with dedicated customer success software is setup burden. Gainsight and similar tools can take months to configure, and other operators describe those systems as useful but heavy. Arrows is positioning around a same day start, then deeper workflows later, which only works when the base CRM is easy to edit.
  1 sacra 3 sacra
• This also explains the ecosystem bet. HubSpot ended 2023 with 205,091 customers, and Arrows describes a large partner and solutions channel around it. A product that depends on fast self serve adoption benefits more from a CRM where teams can install, tweak, and expand usage without waiting on a central admin queue.
  2 sacra 4 hubspot

This is heading toward a CRM native post sales stack. As HubSpot keeps moving upmarket and adds more customers, the winning apps are likely to be the ones that leave reporting, automation, and core workflow inside the CRM, while only owning the narrow layer that the CRM still does not do well, in Arrows case, the customer facing onboarding experience.