The company that got rich fixing its own mess
There is a genre of startup that exists because its founder built something so successful it created a brand-new problem, and then went off to solve that too. Prodly is a clean example. Max Rudman founded SteelBrick, a quote-to-cash tool that Salesforce liked enough to buy in 2015 and rename Salesforce CPQ. Rudman stuck around as a VP for a few years, watched the customer base grow by something like 1000%, and along the way noticed a recurring, un-fun fact: deploying the configuration rules that make CPQ work was clunky, slow, and easy to break.
This is more interesting than it sounds, so bear with me. When engineers ship software, they have a century of accumulated discipline for it - version control, testing, staged rollouts, the ability to undo a mistake. Salesforce has that too, for its metadata: the code-like stuff. What it historically did not have was a good way to move the data - the actual price books, discount schedules, product bundles, approval rules - from a test environment into production. And that data is not decorative. For a lot of companies it is the revenue engine.
The way people used to do it was to export records into a spreadsheet, re-import them by hand into production, and hope the relationships between all those records survived the trip. They frequently did not.
So Prodly's whole pitch is: treat configuration data like a first-class citizen. Its AppOps suite compares two Salesforce orgs, figures out what changed, moves the relational data across in the right order so nothing breaks, seeds sandboxes with realistic data to test against, runs regression tests, and keeps an audit trail so that when a compliance officer asks "who changed this and when," there is an answer that is not a shrug.
The elegant part - the part that makes this a real business and not a feature - is that the problem is genuinely hard and genuinely unglamorous. Nobody's going to post a viral thread about relational data deployment. Which is exactly why it's defensible. The big Salesforce DevOps names, Gearset and Copado, went after the broad CI/CD workflow. Prodly went narrow, into the CPQ-and-data gap those tools leave open, and made itself the thing teams add regardless of what else they run.
It's a small company - roughly 27 people - which is the right size for this. You don't need an army to own one sharp slice of one platform's ecosystem. In 2021 Leta Capital led a $10 million Series A, joined by a cluster of funds and the earlier backers Shasta and Norwest, bringing total funding to about $13.5 million. The stated plan was to push beyond Salesforce into other low-code platforms - the general theory being that wherever business users configure apps without writing code, they eventually need a grown-up way to deploy those configurations.
There's a nice symmetry to the whole thing. Rudman built the product that created the deployment headache, sold it to Salesforce, and then built the company that sells the aspirin. That's not cynicism - it's just how you get a founder who understands the pain in his bones, because he caused it. The best person to sell you a fix is often the person who watched you suffer without one.
What Prodly is betting on, ultimately, is that low-code doesn't mean low-stakes. The apps running your quote-to-cash flow can break in production just like anything else, and when they do, someone's commission is wrong and a deal is stuck. Bringing versioning, testing, and audit trails to that layer isn't flashy. It's the kind of thing you only appreciate the day it saves you - which, for a certain kind of Salesforce admin, is the highest praise a tool can get.