# Matt Barnard

Matt Barnard is a finance leader at Vertice who writes about managing software purchasing and AI costs. They draw on finance-team problems to explain how companies can track spending, negotiate software contracts, and build purchasing workflows.

- Profile: https://b2binfluencer.marketing/creators/matt-barnard/
- LinkedIn: https://www.linkedin.com/in/mattbarnard1
- LinkedIn followers: 2,733
- Topics: artificial-intelligence
- Based on 11 dated posts, latest 2026-10-07

## Summary

Matt Barnard is useful for practical finance-operator posts on software purchasing, procurement, and AI cost visibility.

- Best for: A B2B FinTech vendor selling enterprise spend management for finance-leader thought leadership.
- Not for: Consumer savings apps seeking broad US consumer awareness or app-install campaigns.
- Check first: Confirm audience job function, seniority, company size, region, and paid or co-marketing availability.

### Takeaways

- AI spend is a visibility problem before it is a cost problem
- Token-based pricing breaks the annual budget, so steering beats restricting
- Buying rules should live inside the workflow, not in more approval gates

## Main ideas

- **AI spend is a visibility problem before it is a cost problem**: Barnard says the question they hear most from finance peers is "what's our AI spend, and what do we do about it?" The first half is usually answered with "more than we thought," and by then it's too late to act. Their position: the goal isn't to make the number smaller, but to understand what drives it, whether it's a good investment, and where there's room to optimize. That means tying spend to teams and commitments in real time, with an alert before a threshold is crossed.
- **Token-based pricing breaks the annual budget, so steering beats restricting**: Barnard argues the fastest-growing line a CFO should track is AI token spend, not headcount or per-seat cost, because it keeps moving after signature. Annual budgets were built for a world where a contracted number stayed put; token spend shifts across teams and tools, largely without central visibility, and reaches finance only after the money is gone. Restricting consumption, they argue, limits adoption instead of fixing the forecast.
- **Buying rules should live inside the workflow, not in more approval gates**: Barnard describes a purchasing model that worked at 50 employees—every purchase went through them—but broke at 500: a $5k tool became an approval bottleneck while a $50k commitment went on a corporate card that finance saw only when the statement arrived. Both failures trace to the same gap: no process between "someone needs a tool" and "the company is now paying for it." Adding approvals and sign-offs, they argue, just moves the bottleneck to a committee and leaves engineers chasing a Slack thread to get a design tool upgraded. The alternative is routing logic inside the workflow: low-risk, low-value requests approved automatically; high-value contracts flagged to the right person with context for a fast decision; and compliance checks run inline rather than after the fact.
- **Negotiate on benchmark data, not gut feel and old spreadsheets**: Barnard repeatedly argues that software negotiations should draw on pricing data, not instinct. They describe buyers entering negotiations with exact pricing from a large vendor set and a large volume of processed spend, and point to company datasets as the source of benchmarks and savings recommendations. The figures are Vertice's own, presented as evidence of scale rather than independent research.

## Work to read

- [When we were 50 people, every software purchase came through me](https://www.linkedin.com/posts/mattbarnard1_when-we-were-50-people-every-software-purchase-activity-7453003798073061377-YAbI)
- [The era of reactive software purchasing is dead](https://www.linkedin.com/posts/mattbarnard1_the-era-of-reactive-software-purchasing-is-activity-7464957180341841920-Et4R)
- [The most common question I've been getting as a CFO this year](https://www.linkedin.com/posts/mattbarnard1_the-most-common-question-ive-been-getting-activity-7493681073420234752-x8Zz)
- [The fastest-growing line a CFO should be tracking this year](https://www.linkedin.com/posts/mattbarnard1_the-fastest-growing-line-a-cfo-should-be-activity-7490685397224706048-hZri)
- [Vertice acquires Vendr](https://www.linkedin.com/posts/mattbarnard1_vertice-acquires-vendr-vertice-blog-activity-7467274837187579904-OqVx)

## Brand relationships

- **Vertice** (employment)
- **Vendr** (mention)

## Partnerships

Barnard's posts do not set out a partnership offer. They write as a finance leader at Vertice, promoting the company's AI spend tracking and cost optimization, software purchasing workflows, and acquisition of Vendr. The posts cover procurement problems—fragmented buying, auto-renewals with inflation adjustments, and token spend that moves daily—and link readers to Vertice pages. They are company promotion, not disclosed sponsorships. No rate card, format list, audience package, deliverable specification, or inquiry route for outside brands appears in the posts. Brands considering a paid collaboration should ask Barnard directly whether sponsored work is available.

## Alternatives

- Justin Etkin: Choose Justin Etkin when the campaign angle is procurement negotiation and sourcing tactics rather than CFO-level spend governance. Etkin's posts show a buyer negotiating with a vendor that had stopped moving and using benchmark intelligence to find another 21% savings on a Carta deal. A second post argues AI buying works more like buying steel than software because token spend, pricing, and demand move constantly, positioning procurement to connect usage, forecast, and price. That fits a vendor selling negotiation intelligence, sourcing capacity, or procurement workflow better than a finance-led AI cost-visibility campaign, especially if the brand wants an event hook around procurement when the deal never closes.
- Omer Menashe: Choose Omer Menashe when the campaign's buyer task is trustworthy finance AI and source-trail reporting rather than top-line spend optimization. The posts argue finance AI is useless without lineage: which ledger entry, contract, vendor file, supplier change, or assumption moved the forecast. One example describes a CFO cutting a forecast cycle from three weeks to five days after the system surfaced a supplier pricing shift that spreadsheets would have missed. A second post lays out a narrower operational step: sync unapplied cash into a reporting store, route exceptions to a daily queue, cut month-end reconciliation by two days, and prove one high-value sync before expanding. That fits a vendor selling finance data pipelines, close automation, reconciliation, or AI with audit trails.
- Sarah Toomey: Choose Sarah Toomey when the campaign needs a procurement-operator voice on autonomous source-to-pay and AI-native procurement adoption. Toomey's posts describe 15+ years in sourcing and running procurement inside a finance team, then introduce an autonomous source-to-pay platform that routes requests, pulls supplier and contract data, checks policy, and moves work toward a decision. The other post frames AI buying as slow and expensive because of security reviews and extra stakeholders, arguing teams need visibility to keep pace without skipping rigor. That suits a vendor selling source-to-pay automation, procurement orchestration, or an AI-native procurement platform, particularly when the audience is procurement leaders rather than CFOs.

---
AI-assisted summary of public posts. Audience demographics are not available. Engagement appears only where we checked recent posts. Method: https://b2binfluencer.marketing/methodology/