The setting
's let companies issue physical and virtual cards, set spending limits, and match transactions to their records.
Faster underwriting depends on assembling evidence without pre-judging the applicant.
The queue needs less reconstruction, while every credit outcome still requires accountable human judgment.
Who you’d be doing this for
“Our invoice is due this week, and I’m still answering questions we sent documents for yesterday.”
Manish Menon · Controller · a character in this brief
Leads finance for a growing business applying for card capacity to manage employee and vendor spend.
What is at stake
Corporate-card applicants are repeating documents when reviewers cannot reconcile conflicting signals. You must decide which evidence gaps in the underwriting queue justify a prepared case before an underwriter opens the file.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- applicant document burden vs. case completeness
- prepared evidence vs. source traceability
- fewer rework loops vs. false-positive load
- threshold flexibility vs. template consistency
Why Ramp
Corporate-card underwriting determines how quickly businesses can access spend capacity while protecting the card program from avoidable loss.
Written with these in mind
Not your kind of problem? 31 more at Ramp, or browse every organization.
Where the organization context comes fromThe postings this brief was written from, and the reporting read before it.
The organization context comes from public information. The situation and characters are written for the brief.
Job postings it was written from
Public descriptions of the work at Ramp. They are listed as sources, not as openings. The lines under a posting are its own words, where it meets this brief.
- Compliance Innovation Senior Strategist (opens in a new tab)
- Credit Risk Associate (opens in a new tab)
- Build AI into credit risk workflows: feature exploration, policy monitoring, case review, exception handling, decision support, documentation, and human-in-the-loop QA.
- Senior Credit Underwriter | UK (opens in a new tab)
- Analyze financial statements, bank data, bureau information, and other risk signals to assess business health and repayment ability.
- Recommend the appropriate outcome, including approval, decline, a lower limit, or a request for additional information.
- Physical Security Lead (opens in a new tab)
- You size controls to the actual threat, explain the tradeoffs, and lead with "here's how we do this safely" rather than "no."
- KYB Operations Lead, UK (opens in a new tab)
- You'll manage our UK operators, own the queue, make the hard calls on complex cases and escalations, and keep improving how the operation works as volume grows.
- Own overall queue management and resourcing for UK onboarding: what gets worked first, who works it, and how we keep cases moving through leave and spikes in volume
This is the setup. The work is inside.
Running it puts you in the room: the full situation and its constraints, stakeholders who push back in their own words, and the decisions that are yours to make. What you produce becomes a Day One Plan — work you can show someone instead of describing.
Where similar work appears
Other live briefs connected to this one, and what connects them.
Similar problems at other organizations
Like this one, each of these is about money moving incorrectly, late, or twice.
Credit-thin Pay in 4 approvals are shifting in smaller cohorts while overall approvals look stable.
You have to decide at what point a rule-triggered shift stops being the monitor's case and becomes a manager's finding to confirm from the source data.
Billing-query cases lack a single, reviewable payment story, so merchants repeat details while cases move between teams.
You must decide how far the AI carries a case brief between the Salesforce case notes and the SQL payment results, and which explanations the Finance analysts still reconstruct themselves.
Cardholders are waiting longer when settled transactions produce account outcomes engineers must reconstruct from scattered evidence.
You decide where the AI's ranked causes stop and the engineer's own confirmation of which event started the chain begins.
The same setting, from another role
Each is set around Ramp’s Corporate cards and spend management, written for a different role. They’re separate briefs, not the same scenario.
Multinational controllers are reconciling non-US employee spend through a second card program.
You must decide which eligibility proof belongs in the launch flow and which cases require compliance review.
Enterprise discovery details are being lost between Gong calls and Salesforce records, slowing qualified follow-up.
You have to decide which parts of the record the AI fills from the call and which the seller still writes, such as the next step and what is said to the buyer.
Enterprise finance programmes are reaching advisors before a direct spend-platform evaluation begins.
You have to weigh a focused first wedge against the trust advisors need to protect with their clients.
Other problems with a similar purpose
In each of these, as in this one, the aim is to make complicated, high-stakes systems feel simple to navigate without quietly removing the protections people depend on.
Cross-surface tasks take a median of 7.4 navigation actions, and support data ties the confusion to delayed production changes.
You have to decide how developers move between workflows, evaluations, connections and deployed agents before deep links and permissions migrate and set that path.
Admins stall at permission validation and destination selection, and many misread what happens when a connection is committed.
You have to settle the interaction model now, because changing it after rollout is costly.
In audit samples, interviewers saw context that some customers do not permit, and the migration runs one way.
You have to keep scorecards structured and auditable while narrowing what interviewers see.
