Ramp
Ramp is a financial operations platform that consolidates corporate charge cards, expense management, accounts payable automation, invoice processing, and accounting automation into a single system for mid-market and enterprise finance teams, serving over 50,000 finance teams via subscription and card/cash-management revenue.
36 live briefs
Migrate multi-entity liability statements with traceability
The required outcome is clear, but the data model and customer interpretation must survive an irreversible migration. A wrong call threatens both enterprise rollout and audit confidence
Clarify unknown-category transaction hold handling
A small classification gap is turning routine card purchases into avoidable finance work. Restoring clarity protects both employee continuity and controller confidence
Identify contractor-spend control outcome to pursue
A visible pattern could indicate a meaningful customer need or several unrelated ones. The work is to choose a testable outcome before product investment hardens around the wrong explanation
Deliver close-ready card transactions to ERP
Late transaction context converts automated reconciliation into manual accrual work. A successful product bet improves close readiness without sacrificing accounting accuracy
Enforce required receipts for configured spend categories
A narrow control gap is leaving documented spend requirements inconsistently applied. A clear correction protects customer audit trails immediately
Retire expired card-spend records without audit loss
Thousands of records have outlived configured retention periods. The remedy must reduce privacy exposure without breaking finance evidence
Classify contractor-directed card-spend compliance risk
An emerging payment pattern may be legitimate spend, policy drift, or something more consequential. The value is in choosing the right question before locking in a response
Gate regulated-merchant evidence before rollout
A fixed-date compliance change must be committed or delayed. The launch decision depends on evidence that is expensive to verify and difficult to unwind
Signal card readiness from activation to wallet
Employees need a dependable signal that their card is ready, without confusing eligibility with universal acceptance
Shape governance narratives for enterprise control adoption
The visible signal is real, but the design problem is not yet settled. The work is to discover which visual narrative earns repeat use
Differentiate card purposes across physical and digital surfaces
The visual system will be costly to change once production starts. It must make purpose unmistakable without exposing or oversimplifying controls
Simplify final template review before publishing
A confusing review surface slows control activation. Clearer hierarchy can restore confidence before spending policies go live
Contain fraud signals before further authorizations
Delayed containment leaves a window for additional spend. Faster, accurate restriction limits exposure without creating unnecessary employee disruption
Prioritize customer-visible recovery outcomes
Internal uptime alone may not predict a controller’s ability to close. The right resilience objective directs effort toward the recovery experience that actually matters
Reduce card-control policy evaluation latency
A slow control decision becomes a visible card decline. Restoring latency protects both employee continuity and controller confidence
Validate cryptography cutover across critical paths
The cutover affects both payment continuity and transaction trust. A plausible report is not enough when the transition cannot be simply reversed
Detect synthetic identities while preserving approvals
A fixed production cutover must reduce fraud while keeping legitimate businesses moving through onboarding
Identify early signals of control drift
A useful signal could move controllers from late cleanup to earlier, targeted intervention
Repair fuel-station merchant resolution accuracy
Incorrect merchant identities distort spend reporting and make controls less dependable for field teams
Reduce repeat international exception submissions
Better guidance can reduce employee resubmissions and protect reviewer capacity during close
Lift controller education setup-start conversion
A clearer path to first configuration can turn high education engagement into governed card usage before early momentum fades
Increase approved card-program decisions from evaluations
Improving the path through shared approval can convert existing high-fit demand without compromising program quality
Craft defensible enterprise controller-demand campaign thesis
The campaign can create meaningful enterprise demand, but its promise and proof must survive strict scrutiny once committed
Expand controlled-card spend in mature accounts
The right learning agenda could reveal why similar programs either broaden into daily operating behavior or remain narrowly contained
Diagnose referral qualification gaps and reset intake
A partner’s trust and a reliable pipeline source are weakening at the same time. Better qualification protects both
Convert payroll customers into qualified co-sell pipeline
A high-potential partner base is visible but underactivated. A credible joint motion can create qualified demand before competing vendors fill the gap
Identify the highest-value advisory partnership thesis
Informal advocacy could become a scalable route to controllers—or a distracting set of unrelated referrals. The key decision is what to test, not what to launch
Negotiate bank distribution terms for viable launch
A major enterprise route to market is available now, but the wrong terms could constrain customer access and economics for years
Diagnose duplicate supplier-card creation growth
The visible pattern may be a legitimate workflow or hidden friction. Choosing the wrong interpretation could harden the wrong behavior
Eliminate duplicate expenses from webhook retries
Duplicate expenses undermine reconciliation and can contaminate downstream exports. A contained fix restores trust before the next close cycle
Hold card exports until approval and coding
Incomplete exports create avoidable manual corrections during close. The solution must preserve timely posting for customers who depend on it
Preserve audit lineage in card ledger migration
The launch depends on an irreversible accounting migration. A material mapping error could affect customer reporting, audit evidence, and contracted rollout dates
Identify adjacent workflows for mature card customers
The wrong expansion thesis wastes customer attention and weakens trust. A validated one creates a durable path from successful card adoption to broader operational value
Expand controlled-card coverage before customer renewal
The customer needs evidence that the program can replace reimbursable spend, not merely coexist with it. Delay makes renewal value harder to prove
Prepare legacy card migration for verified cutover
The customer has committed to a cutover that cannot be cheaply unwound. Success protects payments, controls, and the first financial close
Increase seven-day expense submission before month-end
A simple adoption gap is turning into manual close work. Success gives the controller a predictable, documented expense flow