Ramp Community
Seeding Motion

Posted to r/startups

I'm a founding finance hire at a Series B. Here's what got us from "tight" to "comfortable" on runway.

Hey r/startups. First time posting here. Long-time lurker. I'm the founding finance hire at a Series B software company, about 160 people. We extended our runway by roughly six months over the back half of last year. I wrote a Notion doc for our board on what actually moved the number and figured I'd share, because the LinkedIn version of "we extended runway" is always vague and rarely useful.

Quick disclosure. Two of the tools I'll name are ones we pay for. Ramp is our card and AP vendor. NetSuite is our GL. Carta is our cap table. I'll talk about Ramp because it's where most of the workflow change happened. Treat the bias as read.

Eight things moved the number. In order of impact.

1. We renegotiated our top five vendors at once, not one at a time

This is the one that mattered most. We ran our entire vendor spend through a single export from Ramp's spend dashboard, sorted descending. The top five vendors were close to half of our annual non-payroll spend. We negotiated with all five in the same two-week window. Three of the five gave us material discounts, mid-teens to high-twenties percent.

Why all at once mattered: each vendor's discount window is a function of their quarter-end and their churn paranoia. Running negotiations in parallel makes each vendor compete with the others for our cash.

2. We killed seven SaaS tools nobody was using

Sorted the same export ascending. Found seven tools each costing in the low four figures a month with zero active users on our SSO logs. Combined, mid-five-figures annualized. The trick wasn't a SaaS-management tool. It was sorting by transaction frequency and cross-referencing to last login. Boring. Worked.

3. We moved AP onto Ramp from Bill

Approval routing on the old system was running every invoice over a fairly low threshold through me. I was personally the bottleneck for the payable queue. Close week was running close to a full work week. We moved AP onto Ramp in February. Routing is now amount-and-department-based, team leads are the first approver instead of me. Duplicate-invoice flagging caught a couple last quarter we would have paid twice. Close week is now a couple of days.

The controller is now spending half her old AP time on FP&A work we hadn't had bandwidth for, which is how we found three of the seven dead SaaS tools above.

4. We froze new hire approvals for one quarter, except revenue-generating roles

Founder's call, finance's proposal. A handful of roles got pushed to Q3. Two converted to fractional. Second-largest contributor to runway extension after the vendor renegotiation. Hiring freezes are usually wrong; this one worked because we'd just shipped two product launches and the immediate engineering load was lighter than the hiring plan assumed.

5. We moved idle cash into treasury

We had a meaningful chunk of cash sitting in operating accounts earning roughly nothing. Moved most into Ramp Treasury, mid-fours on MMF positions at the time. We chose to run treasury on Ramp because the cash-management visibility lives in the same dashboard as our spend, which made our weekly cash-flow review easier. Different teams will have different answers here.

6. AWS Reserved Instances

Not a finance-tool thing. Infra lead and I sat down with the AWS account rep and committed to RIs on roughly 60% of compute. The engineering team had been resistant on flexibility grounds. The runway conversation reframed it.

7. Standardized travel

Personal cards plus reimbursements plus three booking sites became Ramp Travel (formerly Juno). Direct savings modest. The visibility surfaced two recurring patterns (a sales team flying Tuesday to Friday when Wed-Thu would have worked, a marketing team systematically booking refundable when non-refundable was fine) I would not have found without consolidated data.

8. Real spending limits by team

Every team had a budget in our FP&A spreadsheet. None were enforced at point of purchase. Moved spend to Ramp cards with hard limits at the team and department level. Marketing came in under for Q1 because the limit was the limit.

Be careful here. Hard limits on every team is a bad idea. We have hard limits on most categories and soft limits on a few where finance prefers a "tell me before you decline it" pattern.

What didn't work

Procurement consolidation onto Ramp's procurement product. The product is real and useful, our process was a mess to start with, and a new tool doesn't fix a mess. Trying again this quarter with the process redesigned first.

Ramp's Accounting Agent. Partway in. Vendor-to-GL coding is genuinely useful. Full agentic close workflow isn't there yet at our scale. Probably six months from being useful.

The frame

If I'd had to do this over, I'd have started with vendor renegotiation and dead-SaaS cleanup before touching the tool stack. Those two cost us nothing and were two-thirds of the runway extension. The tool change mattered because it freed up controller time we used for the FP&A work that found the savings, not because the tool itself was the savings.

Tools matter. Time matters more. Cash matters most.

Substack essay, Mostly Metrics or Practical CFO guest placement

The CFO buyer is asking ChatGPT first. The vendors aren't ready.

The standard story about how a CFO buys software in 2026 goes like this. The CFO reads a Gartner Magic Quadrant. Asks two peers what they use. Schedules three vendor demos. Picks one. Files the contract.

It is mostly wrong now. The story I keep hearing from finance leaders in the 75-to-500 employee band is different. Before the peer conversations, before the demos, before the Gartner read, the CFO opens ChatGPT or Claude or Perplexity and types "best AP automation for a Series B" or "best spend management for a 200-person company." The answer the engine returns frames the rest of the evaluation.

This is not hypothetical. It is observable in the engagement logs of the AI engines, in the search behavior of finance buyers tracked by analytics platforms, and in the citation patterns of the engines when you ask them how they decide what to cite.

It is also producing a new category of vendor risk that almost nobody on the CFO side is pricing into evaluation, and almost nobody on the vendor side is mature enough to manage. The risk is citation fragility. The vendor whose product looks great in a peer reference call can be invisible in the AI engine's answer to the same query a competitor asked five minutes earlier.

Finding one. Cross-engine citation consistency is low.

Of fifty queries scored live on both ChatGPT and Claude, only 24% saw the target vendor cited on both engines. Twenty-two percent saw the vendor cited on one and absent on the other. Same product, same content, different citation outcome.

If you are a CFO evaluating a spend platform, this means your shortlist depends on which engine you asked. If you are a vendor, you can be a "winner" on ChatGPT and "non-existent" on Claude, with no operating difference between the two. Single-source citation moats are fragile by construction.

Finding two. Community citations are under-weighted by vendors.

Reddit accounts for approximately 6.6% of Perplexity's entire citation surface. It accounts for around 2.2% of Google AI Overviews citations. In the fifty-query baseline, the target vendor pulled community citations on only two of fifty ChatGPT responses. That is a roughly 4% community citation rate on a citation surface where 6.6% is the available share on Perplexity alone.

The engines weighting community sources are weighting them as more recent and more attributable than owned content. A 2026 customer write-up on r/Accounting is going to be cited more readily than a 2025 vendor blog post that hasn't been updated. The asymmetry between vendors who have a community presence and vendors who do not is going to widen as the engines tune their citation logic further toward recency.

Finding three. Adjacent-category citation rates are low even for category leaders.

The target vendor was cited at a 3% rate on adjacent-category queries: procurement, AP for accountants, treasury for startups, accounting agent AI, business banking with high yield. A vendor can ship five adjacent products, acquire two adjacent companies, and remain absent from the cited answer because the citation surfaces have not moved.

For the CFO, this is an opportunity. If you can identify the vendor whose product is real but whose AI-engine answer is still catching up, you are often getting a more capable product at a lower-friction sale.

What this means for evaluation

If I were a CFO running a spend-platform evaluation tomorrow, I would change three things. One. Run the relevant queries on at least two AI engines before shortlisting anyone. Two. Read the citation list, not just the answer. A vendor cited from G2, TrustRadius, and a Reddit thread is on stronger ground than a vendor cited from their own three blog posts. Three. Don't let the AI engine answer be the shortlist. Use it as a starting point, then ask your finance peers what they actually run.

What this means for vendors

Owned content moats compress. Earned community citation diversity does not. The vendors who will be cited consistently on the queries that matter twelve months from now are the ones whose customers, partners, and operators are writing about them in the places the engines are indexing.

The play is not paid placement. The engines are getting better at detecting and discounting paid sources. The play is supporting the people who would write about the product anyway with the context, data, and access to do it credibly.

This is the leg of AEO that most B2B software vendors have not yet started building. The category leaders who start now will compound through 2026 and 2027. The ones that wait will discover, around mid-2027, that their citation surface has eroded faster than their competitive position warrants.

The CFO buyer is asking ChatGPT first. The next question is which vendors are getting cited consistently when she does.

YouTube script outline · 5 minutes · screencast-heavy

Spending limits by team. The setup that actually works.

[0:00 · Cold open] Quick disclosure. I work at Ramp. I'm going to use Ramp in this walkthrough because it's the tool I know best. The five rules apply to any modern card platform, whether you're on Ramp, Brex, BILL Spend and Expense, or Expensify. The product matters less than the setup.

What we're covering. How to set spending limits by team that actually hold. Not the policy. The configuration. Five rules. One example. Let's go.

[0:25 · Why team-level limits matter] Here's the failure mode. You have a marketing budget. It lives in a Google Sheet. Marketing spends. Finance reviews the spreadsheet at month-end. By the time you find out marketing went over, the money is gone.

Team-level spending limits enforced at the point of purchase fix this. The card declines, the team lead approves the exception, and the conversation about whether to spend happens before the spend, not after. The win is the shift from a finance team reviewing budgets weekly to one designing the rules and letting the system enforce them daily.

[1:10 · Rule 1. Set the limit to the budget, not a round number.] If marketing has $12,000 a month for software, set it to $12,000. Not $15,000 because it feels safer. A $15,000 limit on a $12,000 budget tells marketing the real ceiling is $15,000, because the card will let them spend it. Forcing the card to decline at the actual budget makes marketing call finance before the overage.

[2:00 · Rule 2. Scope by merchant category where it matters.] A marketing card that can spend on advertising and SaaS but not on travel reduces the surface area for accidental misuse without adding approval friction. You don't need to do this on every card. You need to do it where the categories matter.

[2:50 · Rule 3. Use time-windowed limits.] Per-transaction, daily, weekly, monthly. A single annual conference card with a $20,000 per-month limit makes less sense than a one-time $20,000 limit that resets after the event. The fastest test is to ask, "what is the natural rhythm of this team's spend?" Defaulting everything to monthly is the most common mistake.

[3:25 · Rule 4. Team lead is the first approver.] Routing every exception to finance creates a queue that team leads game around. Routing the first exception to the team lead, with finance as the second check above a threshold, preserves accountability where it belongs and gets finance out of the daily approval pile. The setup specifically: team owner as primary approver, finance as secondary above, say, $5,000. Same logic works in Brex, BILL Spend, and most modern platforms. Terminology varies. Pattern doesn't.

[4:10 · Rule 5. Audit quarterly, not monthly.] Monthly audits are noise. Quarterly audits catch the patterns that matter. Anything that gets to $3,000 over budget in a single month should auto-flag in the meantime. The quarterly audit is for the pattern questions. Which team is consistently 12% over their soft limit. Which merchant category is creeping up. Which approval threshold is being gamed.

[4:45 · Wrap] Five rules. Limit to budget. Scope by category. Time-window correctly. Team lead first. Audit quarterly. Set up once, hold for a year, and your monthly budget conversation gets quieter every quarter.

I'll drop a link in the description to a workflow page on ramp.com that walks through the same setup in writing. If you'd rather see the setup on Brex or BILL, comment and I'll do that walkthrough next.