Skip to content

Competency Area

Knowledge management for sales and proposal work

I help make approved product information, proposal components and specialist evidence available at the right point in the workflow. I start with a specific task: which information is missing, who can confirm it and where should it be found?

The assessment produces an inventory of sources, unresolved responsibilities, access barriers and the next decisions. New software is not an automatic consequence.

I first assess whether the CRM, file stores and existing specialist applications already cover the task. For proposal evidence, a reliable link to the valid version may be sufficient; other tasks may require changes to access or search.

Starting Point

Scattered knowledge is a structure problem, not an effort problem

More storage and more training don't solve it. As long as ownership, validity, and access remain unclear, you don't get a reliable body of knowledge — just a bigger one.

  • Knowledge sits in people's heads, inboxes, and parallel folders instead of one findable place.
  • Multiple versions of the same topic exist without a clear indication of which one is valid.
  • Proposals and tender responses are rebuilt from scratch for every opportunity.
  • Onboarding takes a long time and depends on individual people.
  • External expert sources, norms, and standards are hard to access or not connected at all.
  • Licenses, holdings, and budgets are not transparent — usage can't be evaluated.

Competency Building Blocks

Six building blocks of a defensible information architecture

The building blocks build on one another but can be engaged individually — depending on where the friction is greatest.

  1. 01

    Analyze the Knowledge Landscape and Decision Situations

    The starting point is the decisions that are actually being made — and the knowledge required for them. We map where this knowledge sits today, who holds it, and where it is missing or contradictory.

  2. 02

    Structure Internal and External Sources

    Internal policy, sales, and process knowledge is organized alongside external expert sources, norms, and standards: one valid version per topic, traceable provenance, and a structure that follows the way work actually happens.

  3. 03

    Define Ownership, Access Rights, and Approvals

    For every knowledge area, we define who maintains it, who reviews it, who approves it, and who may access it. Approvals carry a date and scope so it’s clear what any statement is based on.

  4. 04

    Integrate Knowledge into Existing Workflows and Systems

    Content is made available where the work happens — in the CRM, in proposal work, on the intranet, or in procurement. The goal is embedding into existing systems, not another portal.

  5. 05

    Make License, Procurement, and Budget Logic Transparent

    Access models, entry points, approval tiers, budgets, and cost centers are disclosed and organized. Only then do decisions about external expert sources become economically steerable rather than habit-driven.

  6. 06

    Steer Usage, Currency, and Ongoing Development Measurably

    Maintenance becomes a process with a cadence and clear ownership. Measurable usage shows which knowledge is actually needed — and which holdings should be revised or retired.

System Logic

How a question becomes a reliable basis

Each stage has an outcome and an accountable role. The last stage feeds the first: feedback from usage determines what gets revised, extended, or retired.

  1. Schritt 01

    Decision Situation

    The pending decision is named: who decides, about what, with what level of validity required. This produces the precise question.

  2. Schritt 02

    Relevant Sources

    Internal policies and licensed external expert sources are drawn on deliberately — with traceable provenance instead of arbitrary hits.

  3. Schritt 03

    Review and Approval

    Relevance, currency, and scope are checked. A named person approves; outdated versions are retired.

  4. Schritt 04

    Delivery in the Work Context

    The approved version is placed where it’s needed — with an owner, a date, and a validity period.

  5. Schritt 05

    Usage and Feedback

    Usage and feedback are made measurable and feed back into maintenance, structure, and procurement decisions.

Decision situation → relevant sources → review and approval → delivery in the work context → usage and feedback.

Application Areas

Where a clear information architecture pays off

The same system works across different areas — with the same goal every time: a valid, current, and findable version.

Sales and Argumentation Knowledge
Value argumentation, reference logic, and pricing and objection handling in a maintained, findable version.
Proposal and Tender Management
Vetted text modules, evidence, and answers instead of reinventing the wheel for every opportunity.
Onboarding New Employees
Orientation without months of piecing information together from individual conversations — less dependency on people.
Process and Policy Knowledge
Binding procedures, approvals, and responsibilities documented, findable, and kept current.
External Expert Sources, Norms, and Standards
Targeted access to licensed holdings, embedded in day-to-day work rather than in a separate system.
License, Holdings, and Procurement Management
Access models, entry points, holdings, and budgets run as a managed process — traceable and measurable.

Advisory Offerings

Three clearly scoped formats

The formats can be agreed individually or in sequence. Scope, required contributions and expected deliverables are defined for the specific engagement.

01

Knowledge assessment

Where is knowledge missing from a proposal or sales decision?

I examine a selected task and record sources, outstanding approvals, responsibilities and the next decisions.

  • Scope, required contributions and deliverables are agreed in the individual engagement before work begins.
02

Knowledge architecture and ownership

Which version is valid and who may change it?

I organise the agreed sources and describe roles, access, maintenance and approvals for the knowledge collection in scope.

  • Scope, required contributions and deliverables are agreed in the individual engagement before work begins.
03

Introduction and adoption

How does knowledge reach the workflow?

I plan with the responsible people how approved content can be found in existing tools and how maintenance and usage will be reviewed.

  • Scope, required contributions and deliverables are agreed in the individual engagement before work begins.

My professional background

I connect an understanding of institutional professional information with my experience in B2B and enterprise sales. The same questions matter: which source is valid, who may use it and which information is missing for the decision?

My profile explains my professional background and my role at Frohberg GmbH

Frequently Asked Questions

Short answers

Isn't knowledge management just part of sales enablement?

It also supports onboarding, process knowledge, internal policies and work with external professional sources. Sales and proposal knowledge are possible applications.

Do we need new software for this?

In most cases, no. The starting point is structure, ownership, and access. Only once those are clarified can you assess whether existing systems are sufficient or an addition makes sense.

What's a sensible way to start a collaboration?

I record which information is needed for the task under review, which sources exist, which approvals are missing and who can resolve the open questions. I use this to agree the next steps with you.

What role do external expert sources play?

External sources are optional and remain subject to their access and licence terms. Approved internal knowledge can be the starting point. Access to a document does not automatically permit AI processing; permitted uses must be clarified separately.

Guide: Knowledge as a Decision Basis

A German-language guide to the assessment, a fictional source inventory and three consulting formats with defined deliverables, accompanying the current German knowledge-management consulting page.

PDF · German · 4 pages · 27 KB

PDF content updated:

Request a confidential intro call

Describe a situation where a proposal, customer or internal approval decision is held up by missing information. In the introductory conversation, I assess with you whether an inventory is the right next step.

  • Confidential
  • No obligation
  • Direct with Moritz Wagener

Intro Call

Let's place your starting position

The more concretely you describe the situation, the more targeted the first conversation can be.

Das Formular wird vorbereitet …

01 / 03

Worum geht es bei Ihnen?

Wählen Sie den Bereich, der Ihrem Anliegen am nächsten kommt. Eine erste Idee genügt.

Worum geht es bei Ihnen?
Passendes Thema

Wo fehlen verlässliche Informationen, klare Zuständigkeiten oder aktuelle Wissensstände? Beschreiben Sie ein Beispiel aus Ihrem Arbeitsalltag.

Bitte keine Passwörter, Zugangsschlüssel, Patientendaten oder vertraulichen Dokumentinhalte eingeben.

0/1400

Ein gewünschtes Ergebnis genügt; Kennzahlen oder ein fertiges Konzept sind nicht erforderlich.

Kein Newsletter. Kein automatischer Termin. Keine Beauftragung durch das Absenden.

Datenschutzhinweis

Wir verwenden Ihre übermittelten Angaben, um Ihr Anliegen zu beantworten und eine mögliche Zusammenarbeit vorzubereiten. Der Wechsel zwischen Formularschritten versendet keine Anfrage. Das Formular speichert keinen Entwurf im Browser-Speicher und übermittelt Ihren Text nicht an einen KI-Dienst.

Kontakt: service@mwcstrategy.com

  • Angaben: Erforderlich sind Name, E-Mail-Adresse, Beschreibung Ihres Vorhabens, Thema und Kontaktwunsch. Unternehmen, Position, Gründungsplanung und gewünschtes Ergebnis sind freiwillig; der Zeitraum kann offen bleiben. Eine Telefonnummer ist nur für einen gewünschten Rückruf erforderlich. Ohne die erforderlichen Angaben kann dieses Formular die Anfrage nicht senden; der direkte E-Mail-Kontakt bleibt möglich.
  • Rechtsgrundlage: Art. 6 Abs. 1 lit. b DSGVO, wenn Ihre Anfrage vorvertragliche Maßnahmen zu einem Vertrag mit Ihnen betrifft. Bei sonstigen geschäftlichen Anfragen, auch im Namen einer Organisation, gilt Art. 6 Abs. 1 lit. f DSGVO: unser berechtigtes Interesse an der Beantwortung der Anfrage. Die Bestätigung der Kenntnisnahme ist keine Werbeeinwilligung.
  • Speicherung: Ihre Angaben werden in einer zugriffsbeschränkten Datenbank für die zuständigen Personen gespeichert. Technische Hosting- und Datenbankdienstleister verarbeiten Daten zur Bereitstellung des Dienstes. Ihre Anfrage löst weder ein Newsletter-Abonnement noch eine automatische Terminbuchung aus.
  • Aufbewahrung: Die Dauer richtet sich nach der Bearbeitung Ihres Anliegens, einem möglichen Vertragsverhältnis, gesetzlichen Aufbewahrungspflichten und der erforderlichen Geltendmachung, Ausübung oder Verteidigung von Rechtsansprüchen. Nicht mehr erforderliche Daten sind zu löschen; dieser Hinweis verspricht keine automatische Löschung nach einer festen Frist.

Unter den gesetzlichen Voraussetzungen haben Sie Rechte auf Auskunft, Berichtigung, Löschung, Einschränkung und Datenübertragbarkeit sowie auf Beschwerde bei einer Aufsichtsbehörde. Bei einer Verarbeitung aufgrund berechtigter Interessen können Sie aus Gründen Ihrer besonderen Situation widersprechen. Nutzen Sie dafür den oben genannten Kontakt. Details finden Sie in unseren Datenschutzhinweisen.

Knowledge management supports my work on Sales Excellence and AI implementation. Klinik Wissen 360 is my own beta development project for such a knowledge architecture.

View all services