Skip to content

[Due for payment 2025-04-10] Allow NewDot collect customers to add one third-party card feed #55898

@joekaufmanexpensify

Description

@joekaufmanexpensify

Problem

Coming from here, if a lead with company cards qualifies for NewDot but won't upgrade to control, we push them to OldDot and either convert them there or not at all. This harms growth and undermines our broader NewDot strategy by unnecessarily adding additional OldDot customers.

Solution

Allow NewDot collect customers to add one third-party feed before requiring them to upgrade. This simplifies the onboarding experience for smaller customers using company cards alongside otherwise simple use cases, hopefully increasing conversion in NewDot. It also recognizes that having multiple card programs is a more complex use case and a more natural point to require upgrading. To do this, we'll:

  • Remove the existing collect > control upgrade path when enabling Company cards in More features of the workspace. This will allow collect customers to enable Company cards without needing to upgrade to control.
  • Add a new upgrade path when a customer already has a card feed (commercial or direct) and tries to add a second one.
    • After upgrading, you land on the existing upgrade confirmation page we use.
    • Clicking Got it, thanks! or < on the upgrade confirmation page lands you on the Who's your bank? page, which is the first step of the flow to add a new card feed.
    • The Expensify Card would not count as the one feed. So you could have an Expensify Card feed AND a third-party feed. We'd only require you to upgrade if you tried to add a second third-party feed.
    • This upgrade path is applied only per workspace. So a collect customer could create two workspaces and add one third-party feed on each of them before needing to upgrade. We don't expect this to be common, but we'll revisit this if many people do this.
  • Make Company cards more discoverable by enabling it on all new workspaces (so it appears in the workspace editor by default).
Issue OwnerCurrent Issue Owner: @
Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~021905280862522047139
  • Upwork Job ID: 1905280862522047139
  • Last Price Increase: 2025-03-27
Issue OwnerCurrent Issue Owner: @joekaufmanexpensify

Metadata

Metadata

Labels

Awaiting PaymentAuto-added when associated PR is deployed to productionExternalAdded to denote the issue can be worked on by a contributorNewFeatureSomething to build that is a new item.Waiting for copyUser facing verbiage needs polishingWeeklyKSv2

Projects

Status

Done

Status

Done

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions