Ramp
Each of these is a real decision Ramp is working through, written so you can make the call yourself — incomplete information, someone who pushes back, no answer key.
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. Its software moves real money across bill payments, corporate cards, reimbursements, accounting integrations, and travel. Ramp also sells AI-powered applications and agents for finance teams, plus infrastructure that helps companies deploy and manage AI with greater control, security, and cost efficiency. Customers include construction companies that manage spend by job and cost code, nonprofits that report by fund and grant, and public-sector organizations. Underwriting and financial products determine which businesses Ramp approves and how it manages risk. Ramp integrates with international banking systems and payment rails including SEPA, BACS, and SWIFT. It is moving to a cellular architecture to scale, reach international markets, operate in highly regulated and constrained environments such as FedRAMP, and deliver enterprise-grade SLAs.
Your first one is free. No card.
23 live right now.
The rest
Set the readiness bar for controllers without bespoke ERP launches
Twelve enterprise customers need a tested path from setup to first card spend without setup-related escalations. You must weigh fast customer validation against a readiness bar that stays repeatable across complex finance environments.
Decide how to release policies without reaching the wrong groups
Some enterprise controllers are finding card policies attached to the wrong employee groups after setup changes. You must weigh a reversible onboarding interruption against controls that may govern the wrong cards.
Untangle entity setup before new hires miss their first spend
Only 68% of invited employees make a first card purchase within 48 hours. You have to weigh faster activation against keeping entity assignment and spend controls accurate.
Cluster reconciliation feedback without letting AI choose the roadmap
Repeated controller friction is being treated as isolated feedback, slowing discovery of reconciliation problems. You have to weigh faster evidence synthesis against the review needed before a theme influences product choices.
Connect card charges to purchasing evidence before close
Card charges can reach accounting while the purchase order, receipt, and invoice remain scattered across workflows. You have to weigh faster exception resolution against the evidence and approval boundaries controllers rely on.
Rank savings signals before controllers rebuild the close
Controllers are rebuilding spend explanations from exports instead of acting on card data before close. You have to weigh useful recommendations against the evidence required for finance to trust them.
Route cloud findings so engineers set severity in 30 minutes
Cloud-deployment findings are waiting while engineers rebuild AWS and Terraform context, and severity calls differ. You must weigh faster evidence assembly against the human review needed before an engineer acts.
Bound virtual-card access without reopening manual reconciliation
Enterprise controllers are keeping card requests manual because outside finance systems lack a safe, narrow way to request them. You have to weigh embedded payment flow against the risk of granting more card authority than the workflow needs.
Build a feed of Canadian spend over SFTP so close skips spreadsheets
Canadian employee spending is being rebuilt outside the reconciled US card workflow each month. You must weigh a fast customer-specific bridge against a pattern future multinational deployments can operate.
Hold the cutover until 500 closed receipts match in Sage Intacct
Closed card receipts no longer match some records in Sage Intacct, putting the month-end cutover at risk. You must weigh a reusable reconciliation path against evidence that can withstand audit review.
Align card controls before field hires start spending
New field hires are receiving default card limits until finance corrects them by hand. You must weigh uninterrupted Workday onboarding against controls that arrive with the card.
Trace failures in spend controls without trusting the first AI answer
Some restricted purchases are passing after policy changes, and engineers are reconstructing each failure from scattered records. You have to weigh faster investigations against the evidence engineers need before they ship a fix.
Tie card controls to job codes without blocking valid purchases
Pilot controllers are reviewing policy exceptions after purchases because controls cannot use the job, fund, or cost-code context. You have to weigh tighter pre-purchase governance against the risk of interrupting legitimate field spend.
Choose a statement model for twelve entities
Parent-level liability and entity-level detail cannot live in the same view, and the migration is hard to unwind. You have to settle the design, the evidence behind it, and the order of rollout under heavy review.
Decide whether the evidence holds before rollout
Automated testing reports 99.9% documentation coverage, but hand samples found 14 missing evidence links in 3,200 transactions. You have to judge whether that gap is small enough for a rollout you cannot undo.
Lock the card identity before production starts
Testers confused restricted-purpose cards with ordinary employee cards, and production preflight flagged inconsistent color rendering. You have to lock an identity system that stays clear and printable before production starts.
Decide whether the processor cutover can go ahead
Automated readiness reports say the new key path is fine, but sampled replays disagree for some wallet and recurring-payment flows. You have to judge what evidence is enough before a move you cannot undo.
Stop the synthetic identities before cards ship
Losses have risen 2.6-fold from synthetic identities that pass today's onboarding rules, and a blunt fix would reject real founders. You set the thresholds and the review evidence before a cutover date that is already fixed.
Pick a campaign promise you can prove
Close-efficiency proof moves finance leaders, but reviewers read the same wording as playing down oversight. Contracts and suppression rules get costly to unwind, so you have to weigh demand against claims risk before launch.
Settle terms with the bank before signing
The bank wants exclusivity, plus pricing that limits how far you can expand on your own. Its deadline is fixed, so you have to weigh 84 eligible accounts now against terms that shape your route to market for years.
Prove the migration keeps its audit trail
The shared mapping path cannot meet the reporting terms you signed, and generated reports show a few lineage mismatches nobody can explain. The migration runs one way, so you have to check the evidence yourself.
Decide if the card cutover can go ahead
Readiness sits at 72%, and the credential-mapping reports still disagree with the vendor records the customer validated. You have to weigh a fixed date against gaps you cannot unwind later.