Legacy RFP UI is the moat — for the incumbents
Clunky enterprise software isn't a bug for the legacy RFP vendors. It's a switching cost. A founder's note on why the worst UX in B2B is also the most defensible — until something breaks the spell.
Here is something I have stopped being surprised by. Every time I open a public review of a legacy RFP product, the same words show up. Clunky. Slow. Hard to find what I’m looking for. Public verbatim quotes from G2 and Capterra:
- “sooooo clunky, impossible to locate exactly what you’re trying to find.” (Responsive, on G2.)
- “very slow” and “the dashboard hard-caps at 10 pursuits so teams can’t see the big picture.” (QorusDocs, on Capterra.)
- “the UI could be more modern” and “new users have trouble fully utilizing it.” (Upland Qvidian, on G2.)
The reviewers are not whining. They are describing software that takes weeks to learn, hides the answer they need behind three clicks, and runs at the speed of a 2014 enterprise SaaS. They’re describing the second-largest category of B2B software they touch every week, and they sound like they want out.
So why don’t they leave?
The thesis
I’m going to argue something I think is unfashionable but defensible: clunky UX is not a bug for the legacy RFP vendors. It’s a feature. It is the most reliable switching cost in enterprise software. And it works because the people who feel the pain are not the people who buy the contract.
The proposal manager who lost her morning to “where did the answer to question 47 go” is not the procurement officer renewing the seat license. The procurement officer sees a working tool, an integrated workflow, an SOC 2 letter, a dedicated CSM, and a 4.4 G2 score that aggregates a thousand barely-tolerable user experiences into a number that looks fine on a vendor scorecard. The renewal goes through.
This is what makes incumbent RFP software different from incumbent CRM software. Salesforce is also clunky, but Salesforce’s user is the buyer. The buyer of Salesforce feels the slowness directly. The buyer of Loopio or Responsive does not. There’s a layer.
Why the layer protects the incumbent
Three reasons.
Switching cost is paid by the buyer; switching pain is paid by the user. Migrating a 30,000-block knowledge base, retraining 40 proposal writers, re-integrating with Salesforce, updating the SOC 2 vendor list, securing a new DPA — that’s a six-month, eight-figure project for the buyer. Twenty minutes of “I can’t find this answer” per writer per day, multiplied by 40 writers and 250 working days, is a real cost too. But it is borne by people who don’t see the contract, don’t sign the DPA, and don’t have a line in the next budget cycle that says “switch RFP vendor.” The buyer’s pain shows up at signature time once every three years. The user’s pain shows up daily and is invisible to the buyer.
Procurement loves boring. A vendor that has been around since 2015, has a dedicated CSM, has a published security posture, and answers DDQs with a published DPA template is procurement-shaped. A vendor that has been around since 2024, ships every Tuesday, and prices in public on its site, is not. Procurement does not optimize for the user’s experience. Procurement optimizes for risk reduction, vendor consolidation, and a renewal motion that doesn’t require legal review. Clunky-but-stable wins.
Training as a moat. Once a team has trained 40 writers on Loopio’s interface — its tab structure, its search syntax, its review widget — that training is a sunk cost the company will not retire lightly. The company has hired a “Loopio admin” role internally. They have written internal documentation against the Loopio UI. They have integrations against the Loopio API. None of that is product value. All of it is exit cost. The vendor knows.
What I take from this
Two things, for us.
The market is not stable. It is locked. A locked market and a stable market look the same from outside. From inside they feel different. Stable means users are choosing the incumbent. Locked means users have stopped trying to leave. Public review sites are the audit trail of the difference. Read a hundred Loopio and Responsive reviews and tell me with a straight face this is a market full of users choosing the incumbent. They are choosing not to fight their procurement office about it, which is not the same thing.
The opening isn’t a better product feature. It’s a lower-friction migration. If the moat is switching cost, the lever is reducing switching cost. Self-serve onboarding. Public pricing. KB import that runs in an afternoon, not a quarter. A free analyzer that shows the user value before procurement is in the loop. A six-month rip-and-replace migration is the wrong unit of work; an “upload your last RFP, see if our extraction works on it, decide” is the right one.
I think this is why we priced in public on day one. (Separate post on that this Wednesday.) Not because public pricing converts better — most of the public-pricing literature is from PLG categories that aren’t enterprise. We did it because it removes a step from the buyer’s mental model where the friction is highest: the moment they have to ask for a quote and brace for the disclosure conversation.
The honest counter-argument
The legacy vendors are also doing real work. Loopio’s extraction at enterprise scale is battle-tested in a way nobody else’s is. Responsive has integration depth nobody can match in 18 months. Qvidian has decades of compliance investment that smaller vendors can’t replicate cheaply. The moat is not just clunkiness. The moat is also legitimate work plus clunkiness, and a new entrant has to be honest about which is which.
We try to be. Our /compare/loopio page lists where Loopio wins. The Pledge says what we will not ship even at the cost of slower drafts. The blog posts about the engineering side of the product show our work, including the parts that don’t work yet. None of that overcomes the moat by itself. But it changes who can see over it.
The thing I keep watching
Which side of the layer eventually moves. If the user side stays invisible to the buyer for another three years, the incumbents are fine. If the user side becomes visible — through a public review aggregation that procurement actually reads, through a champion at the buyer who has switched once before, through a price floor that the user can compare against — the moat erodes faster than the incumbents are pricing for.
I think this happens in 2025 to 2028. I might be wrong. I’d rather be wrong out loud than wrong quietly.