AP Card Line of Credit
Bill & Divvy tech stacks

Overview
Our target segments are offline spenders w/o virtual card spend as well as existing BILL+Divvy Accounts Payable customers. As a customer, I want to choose how I fund payments to my vendors while maximizing on rewards.
Goal
All funding options are available to me and Bill helps me choose the best method to deliver the payment timely while benefiting me. Target APs with offline spend to AP Card — using balance from Divvy LOC.
Target Customers
All vendor direct opted out users who have an existing Divvy account
BILL accounts who are about to opt out of vendor direct
Divvy AP spenders who don’t qualify for Divvy payment services
Divvy payment services accounts (and non-qualifying accounts)
Role
Discovery, Service Design, Cross team collab, User Research, Prototyping, iXD, Visual Desigmn
Tools
Figma, FigJam, Notion, Confluence
Team
Bill PMs (2), Divvy PMs (2), 8 developers from both teams, PMM, Analytics, Content
Dual platforms solution
Currently there’s 2 tech stacks. Bill’s core product and acquisition stack.

Workshop Activity
I led a workshop with all stakeholders to take part in collective understanding of requirements and constraints of Bill and Divvy code base.

Service Map Design
Desktop Designs
Payment type UI logic
Webhook touchpoints
Being a 2-sided market, the payer and the payment recipient user journey needs to be solved for. Webhooks triggers specific activities allowing push to emails, notifications as well as dashboard updates.

Payment recipient email for virtual card.

Dashboard variants based on payment status.
Demo of AP Card product on development box.
Learnings
How much and what Divvy experience is necessary within BILL.
Does the BILL software help “sell” Divvy Payment Services.
Does the BILL software help reduce the manual support of Divvy Payment Services.
Does the BILL software help bring more TPV/spend from customers who don’t quite qualify for Divvy Payment Services.














