Mercury
Mercury is a US-based fintech platform delivering digital-first business banking, treasury, credit, and financial operations software for startups, tech-focused SMBs, founders, and VC-backed companies, operating on top of partner banks rather than as a chartered bank itself.
40 live briefs
Select recurring-spend control engagement outcomes
The wrong interpretation of growing card usage could create more setup work without improving oversight. A focused experiment can reveal which control moment customers actually value
Design high-value wire payee confirmation
A mandated control can prevent costly payment errors, but poorly designed friction can disrupt payroll and critical vendor activity. The decision must hold under real urgency
Improve first ACH payment setup completion
A confusing first payment experience can delay real operating activity. A clearer flow can turn funded accounts into active payment accounts faster
Prompt PIN setup before first card use
A card that cannot work at first use creates avoidable urgency for both employees and finance teams. Better readiness can reduce declines without weakening credential protections
Reconcile available cash after card authorizations
A misleading balance can turn a routine payment day into an avoidable cash surprise. Accurate visibility protects customer confidence and payment continuity
Migrate unclaimed funds with auditable compliance
The cutover affects customer property, legal treatment, and the reliability of financial records. A wrong classification may be costly to unwind after migration
Streamline approvals for on-time vendor payments
Late payments create supplier friction and force costly last-minute work. A reliable approval rhythm improves cash planning without weakening controls
Identify behaviors that deepen account engagement
The wrong interpretation can turn promising usage into a misleading roadmap. A better hypothesis creates a focused path to more durable account engagement
Migrate international-wire beneficiaries before retirement cutoff
A fixed transition deadline puts recurring cross-border payments at risk; customers need verified readiness before their next payment run
Reengage newly issued virtual card first use
A missed first payment can turn a newly issued card into an unused control rather than a recurring spend workflow
Choose reporting outcome for cohort retention
Choosing the wrong adoption goal could create busywork while customers continue solving financial visibility elsewhere
Broaden role-based payment workflows beyond one admin
If responsibilities remain concentrated, payment delays become a recurring operating problem and product value stays narrow
Rank merchant-test sequences within review capacity
Missed early signals can turn into larger card losses. Over-alerting, however, can disrupt legitimate company spending and overwhelm review teams
Correct check amount extraction before deposit completion
Incorrect prefills create avoidable repair work at the moment customers are trying to deposit funds. A reliable fix improves completion immediately
Calibrate application review before manual intake retirement
A fixed transition date creates pressure to use model prioritization before its uneven error patterns are fully understood. The decision affects both risk controls and how quickly legitimate founders can start operating
Prioritize assistant outcomes for cash-management workflows
Assistant usage is rising, but the reason customers return is unclear. Choosing the wrong proxy could create polished interactions without durable workflow value
Identify sustained multi-card usage driver
High-growth accounts are using team cards in incompatible ways. The right learning agenda can prevent a large roadmap from optimizing for the wrong behavior
Retain recurring ACH schedules through first 45 days
Routine vendor payments should reduce work, not create a new monitoring burden. Improving completion protects customer trust and payment continuity
Execute domestic-wire screening cutover with continuity
A fixed retirement date makes delay costly, but the remaining exceptions cannot be waved through. The cutover affects high-value payments and the controls around them
Streamline failed RTP payment recovery
A failed urgent payment can create duplicate attempts and missed vendor commitments. A clear recovery path reduces uncertainty at the moment it matters most
Establish programmatic workflow outcome for testing
The team must distinguish meaningful workflow reliability from superficial tool usage. A focused experiment can reveal what technical finance teams will rely on repeatedly
Prevent reissues for time-sensitive vendor payments
Late vendor payments erode trust and add operational cost. A better decision path can improve completion without removing checks where they remain necessary
Balance card-authorization migration controls and spend completion
The migration can improve approval rates, but only if controls remain trustworthy in real transactions. A wrong scope choice is costly to unwind once routing changes
Unblock physical-card activation after delivery
Employees need a usable company card when work starts, not after a support exchange. Restoring activation also keeps controlled spend on-platform
Rework acquisition routing for funded active accounts
A channel that looks productive at approval is creating weak operating-account activation downstream. The next-quarter commitment must improve quality without simply turning off a major source of demand
Test an emerging founder acquisition thesis
A promising cohort may represent durable new demand—or a misleading artifact of incomplete tagging. The task is to decide what deserves a small, reversible bet
Increase first ACH funding after instruction views
If founders do not fund promptly, the account is less likely to become their operating center. A small clarification could recover hundreds of active accounts each month
Convert temporary virtual cards into recurring spend
The team needs to separate a real retention opportunity from normal card churn. Better guidance could deepen spend-control adoption without inflating unnecessary card creation
Mitigate rapid ACH-to-transfer cash-out exposure
Returned ACH funds can leave the platform before risk is understood. A calibrated policy reduces loss exposure while preserving legitimate operating velocity
Gate transfer access on beneficial-owner verification
A small exception pattern can turn into unverified money movement. Success restores a clear control without creating avoidable onboarding delays
Prioritize safe account-recovery assurance outcomes
Recovery friction can leave legitimate founders unable to act, but weak recovery can hand control to the wrong person. The first decision is what outcome to optimize
Establish digital-asset account eligibility guardrails
A fixed examination deadline requires defensible account classifications. Overreach disrupts legitimate businesses; underreach leaves material compliance exposure
Improve team-card activation from accountant referrals
A simple referral can either become an operating relationship or stall after account opening. Restoring activation makes the partner channel more credible to both firms and founders
Negotiate procurement-platform referral alliance before conference
A conference deadline creates a rare distribution moment, but public commitments can lock in economics and data expectations for years. The agreement must make the channel valuable without compromising trust or viability
Shift payroll referrals to operating balances
If payroll-partner referrals remain shallow, both sides carry the cost of fragmented customer operations. A successful motion links partner trust to a tangible cash-management behavior
Test vertical-platform partnerships for qualified opportunities
Platform interest creates optionality, not proof. A strong thesis focuses exploration on the customer workflow where a partnership could earn durable relevance
Diagnose webhook gaps limiting repeat consumer activity
More integrations are being configured than sustained. A focused experiment can reveal whether trust or breadth is the actual barrier to recurring use
Prove financial-event migration reconciliation accuracy
A required storage cutover has little room for reversal. Success preserves accurate balances and history; a missed discrepancy can become a customer and audit event
Streamline domestic wire creation during peak demand
Payroll-window delays can turn a compliance dependency into customer abandonment. The right architecture preserves control coverage while restoring a usable payment path
Eliminate duplicate ACH submissions after timeouts
A small retry defect can become an overpayment and reconciliation problem for customers. A dependable fix restores confidence at the moment money leaves an account