Introduction: The “too much” vs “too little” dilemma
One of the most common B2B dilemmas is what to show on the website and what to hide from competitors. On one side there is the fear: “if we show too much, competitors will use it.” On the other, a lack of concrete information on the site lengthens sales conversations, multiplies repeated questions, and lowers the quality of first contact. The client does not know whether you are a fit for their problem, so the meeting starts with basic explanations instead of “how do we implement this for us?”
Effects of “too little”: A site full of generic claims (“we are your partner”, “we deliver solutions”) attracts both well-matched and poorly matched leads. Every first conversation requires explaining the same things again: what you do, how you work, what drives the price. The sales cycle stretches, and the team wastes time on initial qualification that the site could partly do.
Effects of “too much” (real ones): Publishing individual quotes, internal procedures, contract templates, or detailed methodologies can give competitors a ready recipe. So the key is not “how much” information but what kind – universal vs context-dependent.
In practice, the aim is not to hide everything or show everything. It is a deliberate split of content: what is universal and repeatable (and should be on the site) vs what needs individual context (and stays with sales). In client conversations I distinguish two types of information: systemic and situational. This split lets you design information architecture so the site attracts the right leads and shortens the sales cycle without giving away strategic know-how.
Systemic information: what it is and why to show it
Systemic information is universal and repeatable. It does not require individual diagnosis; it appears in much the same form in almost every sales conversation. These are the best candidates for website content.
What counts as systemic information?
- Context of the problem you solve – e.g. “who this service is for”, “in what business situation it makes sense”.
- Scenarios where cooperation makes sense (and when it does not) – e.g. “we work with you when you need X; we do not take on Y”.
- Approach to solving the problem – how you think about the project, what principles you use (e.g. iterations, prototypes, workshops).
- General implementation process – typical phases, without pricing or client-specific timelines.
- Typical risks and wrong assumptions – e.g. “clients often assume that…; in practice what matters is…”.
- Factors that affect cost – not price ranges, but what drives the price (scope, complexity, integrations, deadlines). That helps the client understand what drives the quote and prepare a better brief.
Why put it on the site?
Showing this on the site helps the client self-assess fit. It shortens the first conversation, because sales no longer starts with “what do you actually do?” but with “how do we implement this for us?”. At the same time you do not give away core know-how – no individual quotes, internal procedures, or project-specific nuances. If a given piece of information is the same for most clients and can help them understand your solution, it is worth placing it in the site’s information architecture.
Example of using systemic information
An ERP implementation company can put on the site: “We work with companies of 50 to 500 employees that already have an IT department and want to unify processes across several locations. We do not take on projects without a designated client-side project owner.” That does not reveal pricing or implementation details – but a 5-person company without IT immediately sees they are probably not in the segment. A company that meets the criteria knows it is worth getting in touch. That is the effect of systemic information: self-qualification without revealing know-how.
Situational information: the space for sales
Situational information is everything that requires context and interpretation. It cannot be sensibly captured in one universal site text, because it depends on the specific client, industry, organisation structure, or process maturity.
What counts as situational information?
- Individual business diagnosis – what exactly the problem is for this client, what the constraints and priorities are.
- Recommendation of a specific solution – e.g. “in your case we recommend option A, not B” – after analysing needs.
- Commercial terms – rates, ranges, payment model, contract terms. These are always subject to negotiation and depend on the project.
- Operational know-how – e.g. internal checklists, templates, ways of managing project risk. That is your operational advantage; you do not have to publish it.
- Nuances from industry, structure, or organisational maturity – e.g. “in industry X we usually…”, “with your kind of in-house team we suggest…”. That cannot be generalised in one article; it is conversation content.
Delivering this is the space for the sales team. The site’s job is to attract the right clients and set the stage; solution details, pricing, and terms belong to the meeting or workshop.
Why not move situational information onto the site?
First, it cannot be generalised without losing meaning. A line like “price depends on your budget and timeline” adds nothing; a real quote needs a brief and a conversation. Second, that is where you build relationship and value – diagnosis, recommendation, tailored offer is when the client sees you understand their situation. Moving all of that to the site weakens the role of sales and helps neither the firm nor the client. Third, some situational information is your advantage – e.g. how you manage project risk or internal quality standards. Publishing it is neither necessary nor desirable.
Three decision questions: should this information be on the site?
When you need to decide whether a specific piece of information should appear on the website, three simple questions help:
-
Is this information the same for most clients? If yes – e.g. “projects typically take X to Y weeks depending on scope” or “we work with companies that already have an IT department” – it is a candidate for public content. If it depends on the case (“it depends on your infrastructure, budget, deadlines”), it is better left for the conversation.
-
How often does it come up in sales conversations? If almost every time – e.g. “what do you do?”, “what does the process look like?”, “what drives the price?” – that is a sign it is missing from the site. Putting the answer in the information architecture relieves sales and improves first contact quality.
-
Does it affect how the client understands the product or service? If yes – e.g. when cooperation makes sense and when it does not, or what the typical pitfalls are – it is valuable site content. It helps self-qualification: the client knows whether it is worth contacting you at all.
Rule of thumb: if the answers to these three questions are yes and you are not revealing strategic know-how (e.g. detailed quotes, internal procedures, patents), I recommend putting that information on the site. Communication designed this way reduces repeated questions. Marketing may be less happy with the number of “for everything” form submissions, but conversation quality and conversion should compensate.
When to keep information off the site?
If the information varies by client (e.g. “for you we would suggest a different variant”), rarely comes up in first contact, or reveals methodology or data that is your advantage – better not to publish it. When in doubt, run a quick test: if a competitor copied this content onto their site, would you lose something important? If yes, it is situational and should stay in the conversation.
Practice: how to implement this split on the site
Step 1: Content and conversation audit
Review the current site and the list of questions that come up most often in first contact (email, phone, form). List them in two columns: “universal answer” vs “client-dependent answer”. The first are candidates for systemic content; the second stay in the sales domain.
Step 2: Fill in missing systemic information
For each recurring issue you currently answer in conversation, consider adding a section or page: “Who is it for?”, “How we work”, “Typical risks”, “What drives the cost?”. You do not need long essays – often a bullet list or short paragraph is enough. The important thing is that after reading, the client knows more than before visiting the site.
Step 3: Do not reveal price ranges or know-how
You can write “cost is influenced by scope, number of integrations, delivery timeline, and level of post-implementation support” – without giving specific figures. You can describe “typical project phases” – without internal checklists and templates. The line is: what helps understand the offer and process goes on the site; what is your operational or commercial advantage stays in the team.
Step 4: Prepare sales for the new lead quality
When more systemic information appears on the site, some leads will “drop off” earlier – they will conclude you are not a fit. That is good: fewer inquiries but better quality conversations. It is worth aligning with the sales team in advance and adjusting KPIs (e.g. fewer leads but higher conversion or shorter cycle).
Step 5: Regular review
Every quarter or after a major offer change, review: are the questions that come up in first contact still the same? Have new doubts appeared that could be addressed with systemic content? The site does not have to be “forever” – information architecture should evolve with the market and the team’s experience.
Examples: what on the site, what in the conversation
| Topic | On the site (systemic) | In the conversation (situational) |
|---|---|---|
| Process | General phases (e.g. brief, workshop, prototype, implementation, support). | Concrete timeline, milestones, client-side roles. |
| Cost | Factors that affect price (scope, complexity, integrations). | Ranges, quote, payment model, payment terms. |
| Fit | Who cooperation makes sense for; when you do not take on a project. | Whether this specific client and project fit – after reviewing the brief. |
| Risks | Typical wrong assumptions and how to avoid them. | Risks specific to the project after diagnosis. |
The table does not close the topic but shows the direction: universal, repeatable, educational → site; contextual, individual, commercial → sales.
Common mistakes: what to avoid
- Site as a business card with no substance – only slogans (“we are your partner”, “we deliver value”) with no answers to “who for?”, “how?”, and “what drives the price?”. Result: every conversation starts from zero.
- Publishing price ranges “to filter” – ranges often attract people who would not buy anyway (looking for the cheapest option) and put off well-matched clients who interpret them without context. Better: describe factors that affect cost and invite a conversation.
- Putting everything on the site, including internal procedures – e.g. contract templates, implementation checklists, internal SLAs. That is your operational know-how; competitors can copy it, and the client still needs a version tailored to them.
- No alignment with the sales team – if the site promises “first conversation within 24 hours” but sales has a different standard, or the site describes a 4-step process and sales talks about 6 – the client loses trust. Systemic content on the site and the sales message must be consistent.
Conclusion
The “systemic vs situational information” model works best for B2B services with a longer sales cycle and a high-value first conversation – consulting, implementations, software development, agencies. The more the offer depends on the client’s context, the more important a clear split: the site qualifies and educates, sales diagnoses and recommends.
The dilemma “what to hide from competitors and what to show to stand out?” can be structured. Systemic information – problem context, cooperation scenarios, approach, process, risks, cost factors – is worth showing on the site. It helps the client assess fit and shortens the first conversation without giving away core know-how. Situational information – diagnosis, recommendation for the specific case, commercial terms, operational know-how – is the space for sales.
The three questions – is this information the same for most clients? How often does it come up in conversation? Does it affect how the offer is understood? – help decide what goes into the information architecture. A site designed this way may generate fewer “blind” inquiries but better-quality conversations and a faster move to “how do we implement this for us?”.
