{"id":1096,"date":"2026-11-03T15:42:04","date_gmt":"2026-11-03T23:42:04","guid":{"rendered":"https:\/\/embedded.gusto.com\/blog\/?p=1096"},"modified":"2026-11-03T19:29:49","modified_gmt":"2026-11-04T03:29:49","slug":"embedded-fintech-workflow-vertex-sf-2026","status":"publish","type":"post","link":"https:\/\/embedded.gusto.com\/blog\/embedded-fintech-workflow-vertex-sf-2026\/","title":{"rendered":"Embedded Fintech Belongs in the Workflow: What We Learned at Vertex SF 2026"},"content":{"rendered":"

A year ago, AI and the \u201cSaaSpocalypse\u201d hung over vertical software, and by association embedded fintech as well. We didn\u2019t hear that once at Vertex SF Fall 2026.\u00a0<\/span><\/p>\n

Consistently across twelve sessions speakers and panelists noted that the vertical platforms pulling ahead own the workflow, the money that moves through it, and the trust of the customer. They treat each embedded product as its own business, with its own go-to-market plan, instead of a line on a feature list. Vertical SaaS platforms win by becoming the system of action for the businesses they serve, and doing so requires deep vertical-specific product depth, which serves as the moat against vibe coded solutions.<\/span><\/p>\n

We were on stage with our partner BQE, and we spent the rest of the day taking notes. Here\u2019s what we learned.<\/span><\/p>\n

 <\/p>\n

Put the product at the moment of need, not in a settings page<\/b><\/h2>\n

The strongest stories of the day had one thing in common: the financial product showed up exactly when the customer was thinking about the problem it solves.<\/span><\/p>\n

In a session with Kanmon, a former UPS Capital executive described how the team embedded cargo insurance directly into the shipping manifest step. A Shopify seller shipping a package could add coverage per shipment, with no contract and no separate sales process. He compared it to the insurance offer at a rental car counter. Cargo insurance is a complex product, but offered at the right moment, it became simple enough for anyone to buy, and he credited that program with much of the value behind a business that grew to more than $4 billion.<\/span><\/p>\n

BQE CEO Matt Cooper made the same point about payroll. BQE serves architecture and engineering firms, and its software already records time and expenses. Those now flow straight into payroll, and journal entries post automatically to BQE’s general ledger. He also noted that about 70% of payroll workflows are the same across verticals, and BQE\u2019s payroll succeeded with ~30% customized for construction, such as subconsultant payments and prevailing wage reporting.\u00a0<\/span><\/p>\n

That 70% is the iceberg<\/a>: tax calculation across 11,000+ jurisdictions, fund movement, filings. BQE built its differentiated 30% on top of it. This is where embedded payroll shines: BQE offers a vertical-specific payroll tailored to the architecture and engineering industries but backed by Gusto\u2019s money movement and tax remittance \u2013 a vertical-specific solution built on top of underlying financial services rails.\u00a0<\/span><\/p>\n

 <\/p>\n

Surveys tell you what customers say. Behavior tells you what they’ll buy.<\/b><\/h2>\n

Several speakers described products their customers said they didn’t want, and then adopted.<\/span><\/p>\n

For example, when the Heard team surveyed therapists, banking ranked last on their list of needs. But a referral partnership had quietly produced about 500 sign-ups over three years even though the partner disqualified roughly 20% of Heard’s prospects. So, Heard launched embedded banking. Within about three months, it had added almost half as many accounts as the referral program did in three years. Early banking users retained at 100% in their first 30 days, against a 93% average.<\/span><\/p>\n

Shopmonkey got to the same place a different way. If they had asked auto shops whether they wanted Shopmonkey to take over their accounting, shops would have said they already had accounting software. So the team asked about accounting problems instead, heard about broken syncs and double entry, and built the product around those.<\/span><\/p>\n

The opposite case came from Cents, which serves laundromats and dry cleaners. Its team embedded an insurance product in about three days, but customers pushed back. Laundromat owners do buy insurance, but they weren’t looking to Cents for it. WorkWave’s GM of fintech shared a similar contrast: instant business bank accounts reached 25% attach at a UK point-of-sale company serving first-time business owners, but he said the same offer would get almost no attach with a $5 million pest control company.<\/span><\/p>\n

The right test for any embedded financial service is “what does my customer need to do next, and do they expect it from me?” The answer depends on the segment, and it\u2019s inferred from behavior and not a survey.<\/span><\/p>\n

 <\/p>\n

The go-to-market plan matters as much as the integration<\/b><\/h2>\n

The Shopmonkey session made this case most directly: the integration doesn’t matter if your team can’t sell the product. Their advice:<\/span><\/p>\n