PalladiumPeak
Back to blog

Operators

Your Industry Runs on Spreadsheets. That's the Opportunity.

If an industry runs a critical workflow on a shared spreadsheet, there may be a company in it. Four signs to check, and two examples from our portfolio.

Peter EkhatorUpdated 3 min read

If a whole segment of an industry runs a critical workflow on a shared spreadsheet, there's probably a software company in it. The spreadsheet is evidence that the work is real, repeated and poorly served. The person best placed to build the replacement is usually the one who has maintained it the longest.

An earlier version of this post credited one of these gaps to a company that isn't part of our portfolio, and we've removed that example. The two examples that remain are companies in the Perizer portfolio.

Four signs a spreadsheet is a company

Most spreadsheets are just spreadsheets. The ones worth building on pass a few tests:

  • Many people depend on it. Dozens of teams, offices or organizations use a version of it to do the same job.
  • It breaks regularly. Version conflicts, bad data entry, broken formulas, and no control over who sees what.
  • It touches money, compliance or safety. Errors have consequences, so the people using it will pay for something better.
  • Nobody has built the replacement. What exists is either too generic for the workflow or priced for enterprises.

A spreadsheet that passes all four is a market with a workaround in place of a product.

What it looked like in two of our companies

Healthcare credentialing. CRNAs, anesthesiologists and other providers track licenses, certifications and contracts across email, shared documents and spreadsheets, and they resubmit the same documents to each facility that credentials them. Providers have little control over who sees what. That gap is what Dolorvia is built for.

Property management. Small and mid-size property managers use separate tools for leases, maintenance, accounting and tenant messages, and a spreadsheet of who paid what holds them together. That gap is what Trurentra is built for.

In both cases the workflow was obvious to people who do the job every day, and close to invisible from outside it.

Why the operator sees it first

A common startup pattern is to fund a smart generalist to enter an industry they've never worked in. The hard part, though, is rarely the code. It's knowing what the software has to do: the workflows, the edge cases, and why the last three attempts failed.

Industry operators bring years of that context, and it can't be hired. The tradeoff is that context alone doesn't ship software. An operator still needs engineering, infrastructure and someone who has built companies before, and that's the gap most ideas die in.

From spreadsheet to company

PalladiumPeak partners with operators who see a problem clearly. We bring the engineering, infrastructure and operating support, and we build the company together. You don't need to learn to code or find a technical cofounder first.

If you maintain the spreadsheet everyone in your field hates, tell us about it.

Know an industry inside out?

Tell us the problem you’ve watched for years. If software can fix it, we’ll build the company with you.

Build with us