A fresh round for an unglamorous category
Rundoo has raised $30 million in new funding, bringing its total funding to $48 million, to build software for a segment of retail that rarely makes headlines: independent paint, hardware, farm-and-feed, and building materials stores. Founder and CEO Nick Hershey is explicit about why he thinks this market has been underinvested. "It's not a tech-averse market. It's just a tech-deprived market," he said, describing operators who want better tools but have never been offered any built for their specific workflow.
That distinction is the entire investment thesis. A tech-averse market resists new software regardless of quality, which makes it a bad venture bet. A tech-deprived market simply has not had a credible option, which is a much better setup for a company that shows up with one. Rundoo's bet is that thousands of independent operators, competing against national chains with real analytics and inventory systems, will pay for parity if someone finally builds it for their category specifically.
Why the technology gap is deeper than it looks
Hershey's most striking claim is architectural. He describes many competing systems at independent supply retailers as running on infrastructure that is, in his words, pre-AI, pre-mobile, and pre-internet all at once. That framing matters for any technology leader who has underestimated a legacy migration before: this is a full-stack replacement problem, where the underlying system was never designed to talk to a browser, a mobile app, or an API in the first place, so a modern front end has nothing underneath it to connect to.
That kind of gap explains why larger horizontal platforms have mostly ignored this category. Building point-of-sale, ERP, and inventory tooling from scratch for a fragmented vertical with thin margins per customer is a hard return-on-investment case for a generalist SaaS company. It is a much better case for a founder willing to specialize deeply enough to earn trust in a market where switching costs, and switching risk, are unusually high.
Where the AI assistant actually earns its keep
Rundoo's AI assistant, Dooey, started as a reporting tool and has since expanded into ordering, email drafting, and sales assignment. That expansion path is worth studying: Rundoo did not launch a broad conversational assistant on day one and hope it stuck. It started with a narrow, low-risk use case, reporting, where a wrong answer is annoying but not costly, and only extended into transactional territory, ordering and assignments, once the underlying data model had proven itself.
Hershey ties the demand directly to staffing reality rather than a generic AI narrative: operators are "managing so many different workflows, and they're just short-staffed. Labor's the No. 1 challenge." That is a specific, verifiable pain point rather than an abstract efficiency pitch, and it explains why an AI feature aimed at reducing manual data entry and task assignment lands with an owner-operator in a way a flashier chatbot would not.
The pitch is an operating system for the store
Rundoo describes its own ambition in blunt terms: a platform spanning point of sale, ERP, inventory, commerce, and embedded financial technology, functioning as the operating system for a store instead of one more app layered on top of existing ones. Hershey compares the trust required to "performing surgery on a business," a framing that acknowledges how disruptive a full system replacement is for an operator with no IT department and no tolerance for downtime.
Crucially, Rundoo has chosen to work alongside the cooperatives, manufacturers, and distributors that already serve this market rather than compete with them for the customer relationship. The company frames integration with those existing partners as a requirement, not an afterthought. That is a pragmatic recognition that independent retailers sit inside supply relationships built over decades, and a vertical software vendor that tries to route around them picks a fight it does not need to have when the harder, more valuable fight is winning the point-of-sale terminal itself.
The build-vs-buy signal for adjacent categories
Rundoo's funding is a useful data point for any executive evaluating vertical SaaS, whether as a buyer, a partner, or a competitive threat. The pattern here, a genuinely underserved fragmented market, infrastructure old enough to require full replacement rather than integration, and a labor shortage that makes automation an easy sell, is not unique to hardware and building materials. It shows up across plenty of B2B categories that PE-backed operators and enterprise software teams touch every day: distribution, field service, specialty wholesale, and other verticals the big horizontal platforms have judged too fragmented to serve well.
The lesson is less about Rundoo specifically and more about where AI-native vertical software tends to win. It wins where the incumbent option is genuinely pre-digital rather than merely old, where the AI feature attacks a named labor constraint rather than a vague productivity claim, and where the vendor commits up front to integrating with the existing supply chain instead of trying to own it outright and alienate the partners already in the room.
What this means for your own portfolio and roadmap
If your organization touches distribution, wholesale, or any category where independent operators still run legacy or homegrown systems, Rundoo's $30 million round is worth treating as a market signal rather than just a funding announcement to skim past. Capital is flowing toward vertical operating systems that replace pre-internet infrastructure outright, rather than toward incremental add-ons bolted onto systems that were never built to be extended in the first place. Investors are pricing full replacement as the credible strategy, not integration middleware layered on top of software that cannot support it.
For CTOs and CIOs weighing whether a fragmented, unglamorous vertical is worth a build-or-partner decision, the Rundoo model offers a cleaner test than most: identify the workflow where staff are most short-handed, ship a narrow AI feature there first, and only expand into transactional territory once trust in the underlying data is established. That sequencing, reporting first and transactions second, is a more defensible rollout plan for your own roadmap than launching a broad assistant on day one and hoping adoption follows.
