Arrows combines digital sales rooms and customer onboarding plans, giving customers a focused, login-light sequence of phases, tasks, resources and forms.
The headline for 2026 is not a feature, though: Arrows is pivoting to an entirely new product. Everything below describes a product that is no longer the company’s development priority, so read the feature detail with that in mind.
Arrows is pivoting to a new product
This is the most important thing to know about Arrows in 2026, and it outweighs every feature comparison below.
In July 2026, Arrows publicly announced that it is building and launching an entirely new product, hiring “first-of-their-kind” roles for it and running a multi-week launch campaign. Co-founder and CEO Daniel Zarick has since said the company’s marketing, product development and sales energy is all going into that new product.
The existing Arrows product is not being shut down. But it is no longer where the company is investing, and buyers should not expect meaningful further development of it.
The distinction between Arrows’ sales rooms and its onboarding plans does not really matter here – the pivot is away from the current product as a whole, not from one half of it. Zarick’s stated reason for building the new product is what the team saw in customer behaviour: the strongest teams “weren’t just onboarding. They were using Arrows to sell.” Arrows’ own homepage now leads with “Work every deal like your best deal”, and Zarick’s LinkedIn title reads “AI for AEs”.
Why this matters more than a feature gap. An onboarding platform is a system you run for years. Buyers should assume the gaps below will remain unless Arrows provides a committed roadmap for the current product. Feature gaps in an actively prioritized product may be a timing question. Here, the founder’s allocation of development resources makes that assumption much harder to justify.
If you are evaluating Arrows now, ask directly what is committed for the existing product over the next four quarters, and get the answer in writing before signing a multi-year term.
Who is Arrows best for?
Arrows is best for simple, standardized and mostly linear onboarding. The process should fit naturally into sequential phases containing tasks, resources, forms and file requests, with a relatively small number of stakeholders and limited need for internal project management.
This can work well for short, repeatable journeys: collect the required information, guide the customer through a known set of actions and use reminders to keep the plan moving. Templates, optional tasks and conditional inclusion rules provide some variation without turning the process into a bespoke implementation project.
Arrows’ deep HubSpot and Salesforce integrations strengthen this use case. Plans can start from CRM records, more than 60 data points can sync, and CRM fields can control tasks, phases and forms. That is useful automation, but it is not a substitute for deeper onboarding project management. Having HubSpot or Salesforce should not by itself make Arrows the preferred onboarding platform.
The fit becomes less clear once onboarding has parallel workstreams, flexible dependencies or many participants who need different project perspectives. Arrows has customizable plan lists and a central task table across plans, but its published project-management model remains primarily lists, filters, phases and tasks. It does not advertise Gantt planning or a cross-customer Kanban for operating the onboarding portfolio as a project pipeline.
Can Arrows be used for customer onboarding?
Yes. Arrows has a dedicated onboarding product with phases, tasks, owners, due dates, forms, file uploads, reminders, comments and reusable templates. Customers can access plans through secure email confirmation rather than maintaining another password.
The product goes beyond a static checklist. Teams can make tasks optional, use sequential phases, insert tasks or phases dynamically from CRM data and sync form responses back to HubSpot or Salesforce. A cross-plan task page helps internal users find overdue work, filter by assignee and complete tasks without opening each customer plan.
What does Arrows do well for onboarding?
- A focused customer plan. Customers get a clean, mobile-friendly experience with tasks, resources and next steps without navigating a heavyweight internal project tool.
- Repeatable, conditional delivery. Templates, optional tasks, sequential phases and CRM-driven inclusion rules help teams adapt a standard process to each customer.
- Customer data collection. Forms and file uploads can collect implementation information and sync it back into CRM fields.
- Cross-plan task visibility. Internal users have a centralized table for searching, sorting and filtering tasks across onboarding plans.
- Deep CRM integration. HubSpot and Salesforce can trigger plans, supply customer data, receive progress and form responses, and drive workflow or pipeline changes.
- Sales-to-onboarding continuity. The same vendor covers digital sales rooms before signature and onboarding plans afterwards.
Where does Arrows fall short for onboarding teams?
- Project management is deliberately lightweight. Arrows provides phase-and-task plans, portfolio lists and a cross-plan task table, but not published Gantt planning, flexible dependencies or a cross-customer Kanban. That limits teams managing overlapping workstreams, many stakeholders or complex internal operations.
- The customer space is deliberately focused. It works well as a clear plan with resources and forms, but it is less suited to fluid projects that need a richer collaborative workspace or multiple stakeholder perspectives.
- AI is weighted toward the sales motion. Arrows Intelligence uses CRM calls, emails and notes to build sales rooms and suggest milestones, next steps, value propositions, content and follow-up emails. Arrows does not currently publish a comparable general-purpose onboarding agent or MCP connection.
- Pricing is not transparent. The current pricing page provides no starting price, plan thresholds or example package, so buyers need a quote before they can compare total cost.
How much does Arrows cost?
Arrows currently uses quote-based pricing. Its pricing page says pricing depends on team size and how the team uses Arrows, while every plan includes full access to the platform.
That is a simpler feature-packaging message than products that gate core capabilities by tier. It also removes the information buyers need to estimate cost independently. Arrows does not publish a current entry price, included usage levels or an example total for a typical onboarding team.
Older public prices should not be treated as the current offer. Teams should ask for the total annual price, the usage assumptions behind it, renewal terms and any limits that affect the number of rooms, plans or AI actions.
How strong are Arrows’ automation and AI?
Arrows is strong at CRM-driven automation. Its HubSpot and Salesforce integrations can create plans, populate customer information, unlock tasks or phases, synchronize responses and use onboarding progress to update pipeline stages. This is a genuine product strength.
The AI story is narrower. Arrows Intelligence reads calls, emails and CRM notes to create or update sales-room milestones, next steps, value propositions, resources and follow-ups. That can save sellers time, but Arrows does not publish comparable AI breadth for post-sale onboarding operations, customer Q&A or external agent access.
Is Arrows a good choice for customer onboarding?
Not for most teams, as of July 2026 – and the reason is the pivot rather than the product.
On features alone, Arrows works when a straightforward customer plan is enough for simple, repeatable, mostly linear onboarding. The customer experience is focused, the HubSpot and Salesforce integrations are genuinely deep, and the onboarding feature set covers more than a basic checklist. That was a reasonable buy.
What changed is the trajectory. With the company’s development resources going into a new product, buyers should not assume the limitations documented below – lightweight project management, no cross-customer Kanban, sales-weighted AI – will be addressed without a specific commitment from Arrows. For a multi-year platform decision, that is hard to justify against vendors still actively building for onboarding.
Arrows may still make sense in narrow cases: a short commitment, a simple linear process that is already fully served today, and a HubSpot or Salesforce integration you specifically need. Everyone else should look at a platform whose primary product is onboarding and is still being developed.