Why We Don't Have a Talk-To-Sales Wall
8 June 2026
When I started looking for a knowledge management tool a couple of years ago, two things annoyed me into eventually building this one.
The first was that no single product did everything I needed. Internal knowledge for the team. Customer-facing content. Something AI agents could read from. I would have needed to wire together two or three different services to cover the full shape. Most companies were good at one piece. Almost nobody was building the whole substrate.
The second was that I couldn’t tell what any of them cost.
Pages and pages of marketing. Feature lists. Customer logos. “Get a Demo.” “Contact Sales.” Pricing nowhere on the site. I wasn’t ready to sit through a discovery call to find out whether a tool was a hundred dollars a month or several thousand. I just wanted to know.
That story is familiar enough from other people to know it isn’t only me.
This piece is about the second annoyance.
What’s actually behind the wall
When you click “Contact Sales” on most SaaS sites, you don’t get pricing. You get scheduled into a discovery call. Someone from the sales team qualifies you, asks how many seats you need, what your budget looks like, what other products you’re considering. Then a quote comes back. Usually anchored high, with an offer to discount it.
The whole thing is a negotiation, dressed up as a service.
This isn’t a moral problem. It’s a business model. Enterprise software pioneered it because enterprise customers had procurement teams, complex requirements, and the patience for a long sale. The vendor’s job was to navigate that process. The salesperson was useful. The wall was load-bearing.
Then the model crept down-market. Mid-market SaaS adopted the same scripts. Tools that should be obvious commodity buys started gating their prices too. You can’t find out what a forty-dollar-per-seat help desk tool costs without booking a meeting. That’s where the model tips from service into performance.
Why we don’t do it
The page on our site that says “Pricing” actually has prices on it.
Three tiers. Startup, Business, Enterprise. Per-user pricing for the first two with a five-user minimum. Flat-rate Enterprise plan up to a hundred users. Bring-your-own AI keys at no extra cost on Business and above. Localised for Australia, the US, and the UK so the maths works in your currency.
Take a look at knowledgescout.io/pricing. Four seconds and you’ll know whether KnowledgeScout fits your budget. You don’t need a call. You can decide while drinking your coffee.
That’s the point.
What “talk to sales” actually costs the buyer
It looks free because nobody invoices the buyer for the time. But the buyer pays in a few places.
Time. You have to find a slot. Attend the call. Sit through whatever script gets read. Often it’s thirty to sixty minutes you didn’t need to spend.
Cognitive friction. Most people browsing tools aren’t ready to talk to a salesperson. They’re early in the decision. Forcing a conversation kills the curiosity before it has time to become intent.
Hassle afterwards. Once you’ve talked to sales, you’re in the CRM. The follow-ups start. The “just checking in” emails for six months. Some companies are restrained about this. Many aren’t.
Anchor bias. Whatever number the salesperson quotes becomes the reference point. If they discount it, you feel like you won something. The price was never really fixed. It’s whatever they think you’ll pay.
What not having a wall costs us
This is the honest part.
We can’t price-discriminate. If a five-hundred-person company finds the Enterprise plan and pays $600, they get the same deal a fifty-person company gets. Some vendors would charge that bigger company several times more, because they could. We can’t.
We can’t qualify leads before they sign up. Sometimes prospects who would benefit from a conversation never get one, because the path is “read the page and sign up.” If their needs are genuinely complex, that’s a missed connection we’d have caught.
Some buyers want a relationship. Especially in enterprise, the procurement team is used to negotiating, and a “the price is the price” stance feels like the vendor isn’t taking them seriously. We’ve lost a few prospects to that.
Those are real trade-offs. We’ve made the call that the buyer time and goodwill we save by being transparent is worth more than the price discrimination we forgo.
When the wall is actually justified
To be fair, some products genuinely need it.
If the product is complex enough that a buyer can’t tell whether it fits without a conversation. If the implementation requires custom integration and the price legitimately varies by scope. If the buyer is enterprise-tier and expects a procurement process anyway.
Most SaaS isn’t in that category. Most SaaS is a software product with predictable usage and a price per user. Hiding that price behind a wall isn’t service. It’s negotiation infrastructure.
What we expect buyers to do
Read the pricing page. Start the one-month free trial. Use it with your team. Ask questions over email if you have any. Buy when you’re ready. Cancel anytime.
If you want a call, you can have one. It just isn’t a prerequisite for finding out what we cost.
What this signals
Transparent pricing is a way of saying we trust the buyer to make a decision. You can see what it costs. You can see what’s included. You can compare it to the other options. We’re not trying to anchor you or qualify you or chase you down through a sales pipeline. We’re trying to make it easy for you to figure out whether the product is a fit.
A wall sends the opposite signal. It says: the price is what we can extract from you, not what the product is worth.
We don’t think that’s a healthy way to start a relationship.
The first thing I needed when I was buying software, before all the features and the case studies, was to know what it cost. So we tell you.
The KnowledgeScout Team