Finance Ops Is Still Running on Excel, and Nobody Knows What Their AI Costs

Two patterns dominated the pain signal feed this week. One is old — finance processes that were manual in 2005 are still manual in 2026. One is new — AI API costs are scaling faster than anyone's visibility into them.

Neither has a clean solution yet.

The Excel Problem That Won't Die

Accounts payable teams are doing three-way matching in 2026. That means: purchase order arrives, invoice arrives, receipt arrives — someone manually compares all three in a spreadsheet to confirm they match before releasing payment. Bill.com partially automates this. Mostly it doesn't.

The Reddit and small business community posts on this are uniform: "We have 200 invoices a month and three people doing nothing but matching." The volume is low enough that enterprise tools are overkill, high enough that it's a part-time job.

The same pattern shows up in bookkeeping. Freelance bookkeepers report spending 3+ hours per week matching bank transactions to QuickBooks entries by hand. The transactions are already in both systems. The data exists. The matching doesn't happen automatically because the mapping rules are ambiguous enough that existing tools won't commit to them.

What's being built: LedgerMatch — a reconciliation copilot that learns a bookkeeper's matching rules from their historical decisions and applies them automatically. And MatchLine — a lightweight three-way matching engine designed for the SMB AP teams that Bill.com ignores.

The market pattern here is worth noting: both are wedge plays into workflows that large players (QuickBooks, Bill.com, Xero) handle badly at the SMB tier. The enterprise version costs $50k+/year. The solo bookkeeper version doesn't exist. That gap is real and monetisable.

The AI Cost Explosion Nobody Planned For

A signal that started appearing in r/SaaS and r/LocalLLaMA this month: teams whose AI API bills tripled in 90 days with no clear visibility into which workflows caused it.

The failure mode is consistent: someone builds a Claude/GPT integration, it goes into production, usage grows, costs grow, and the only reporting available is a monthly invoice line that says "API calls: $1,847." No breakdown by workflow, no alerting, no routing logic.

The specific frustration: Claude Sonnet is the right model for complex reasoning. Haiku is right for classification and simple extraction. Most teams are using Sonnet for everything because setting up routing logic is annoying and not on anyone's sprint. When usage scales, that's a 5x cost difference on every call.

What's being built: ModelSwitch — a drop-in router that sits in front of your AI calls and routes to the cheapest model that can handle the task, with real-time cost dashboards and spend alerts. The pitch: "You told Claude Sonnet to classify 40,000 customer tickets this month. That cost you $400. Haiku would have done it for $18."

The pain here is sharp. Anyone building AI-powered products is going to hit this. The tools to manage it are either enterprise-priced or DIY.

The Autonomous Hiring Agent Pattern

A third cluster worth watching: sourcing managers describing their week as "running the same 6 LinkedIn boolean searches, sending the same 30 InMails, and copy-pasting results into a spreadsheet." The sourcing workflow at most companies is a series of identical manual steps with no automation in place.

This is the autonomous agent pattern at its clearest. The job isn't intellectually difficult — it's just repetitive and time-consuming. An AI agent that runs sourcing searches, drafts personalised outreach, and surfaces candidates has a story that writes itself: "I automated my sourcing workflow and sourced 3x more candidates in half the time."

What's being built: SourceAI — an autonomous sourcing agent that runs candidate searches and personalises outreach without a human in the loop.

The catch: LinkedIn's API restrictions make this harder than it looks. Several tools in this space have been shut down or throttled. The builders who win here will either work through approved channels (LinkedIn Talent Solutions API) or build for job boards that don't have the same restrictions.

Other Pain Signals This Week

Figma automation for design variants — Design teams producing 12 size variants of the same ad template, manually, every week. Playwright-based automation breaks on Figma's canvas rendering. No clean solution exists.

WhatsApp automation for small businesses — Local businesses know they should automate appointment reminders and order updates via WhatsApp but hit a wall with Twilio APIs. The friction is in setup, not capability. Demand signal is strong in r/smallbusiness and Latin American entrepreneur communities where WhatsApp is the primary business channel.

Extreme uptime alerting — Uptime Robot sends an email. Developers who've lost revenue to undetected downtime want phone calls, SMS, and Hue light changes. The gap between "email notification" and "wake me up at 3am" is surprisingly unaddressed by current monitoring tools.

---

Pain signals sourced from Reddit, Hacker News, and job boards. Idea scores based on market demand, competition level, and estimated time to ship. Browse the full idea database →