Finding is not the same as knowing
Search returns files. It does not tell the writer why that engagement is comparable, what the firm learned, or which parts are still the firm's current view.
Consulting knowledge reuse
Reuse firm knowledge without copying client-confidential work.
Solon draws on approved methodologies, templates and prior engagement structure when a proposal is written, shows where each element came from, and keeps client-specific material out of cross-client reuse.
How firms reuse knowledge today.
Almost every consulting proposal starts from a previous one. The method is the problem.
- 01Someone remembers a similar engagement from two years ago
- 02They search the drive by filename and open several candidates
- 03The closest one is duplicated and renamed
- 04Client names, numbers and specifics are edited out by hand
- 05Whatever they missed travels into the new proposal
Storing documents is not knowledge management.
The firm's knowledge is real. The retrieval, the judgement and the safeguards around it are what is missing.
Nobody knows what is reusable
A prior proposal mixes firm methodology with a client's commercial terms and internal detail. Without that distinction, teams either copy too much or refuse to reuse anything.
Copying carries the client with it
Manual redaction is the only safeguard, and it depends on a tired person spotting every client name, figure and identifying detail under deadline.
Judgement stays with the partner
The reasoning that made the prior engagement work is in someone's head. It does not survive into the next proposal unless that person is in the room.
Why the usual approaches fall short.
Each of these solves part of the problem and leaves the important part to the individual.
- Drive or SharePoint search
- Optimised for finding a document you already know exists. It cannot tell you which precedent is relevant to this client, or whether reusing it is appropriate.
- Proposal templates
- Templates carry structure, not judgement. They standardise the shape of a proposal and leave the reasoning — scoping, sequencing, pricing — to whoever fills them in.
- A content library of approved blocks
- Useful for boilerplate. Consulting proposals turn on the engagement architecture, which is rarely a reusable paragraph.
- A general AI assistant with uploaded documents
- It will happily reuse whatever it was given, including a previous client's confidential terms, with no notion of what was approved for reuse or where a claim came from.
How knowledge reuse works in Solon.
- 01
Classify the source
Knowledge is held per workspace, client, permission and reuse policy — separating firm methodology and templates from client-confidential material.
- 02
Retrieve with permission in mind
When a proposal is written, Solon draws on what the firm has approved for reuse and leaves restricted material out of cross-client work.
- 03
Show the provenance
Each element points back to the methodology, prior structure or transcript it came from, so a reviewer can judge whether it belongs here.
- 04
Flag the uncertain cases
Where reuse is ambiguous — client names, commercial terms, internal metrics, identifying detail — Solon surfaces it for a person to decide.
Sources for this proposal
- Approved
Firm methodology
Approved for reuse
- Approved
Proposal template
Workspace standard
- Restricted
Prior engagement structure
Restricted summary
- Confidential
Client transcript
Confidential
Client commercial appendix
Excluded from cross-client reuse
What the firm gets back.
Approved for reuse
An explicit distinction between reusable firm intellectual property and content a client owns.
Precedent with reasons
Relevant prior engagement structure surfaced against the current opportunity, not a filename match.
Source traceability
Which documents, conversations and firm rules informed an output, visible at the point of review.
Confidentiality controls
Client names, commercial terms, internal metrics and identifying details flagged before anything is reused elsewhere.
Methodology applied, not pasted
The firm's approach shapes the engagement architecture for this client rather than arriving as a copied section.
Delivery becomes knowledge
Approved frameworks and reusable structures from finished work can return to the knowledge base without client specifics.
When this matters most.
- Most proposals begin as a copy of a previous proposal
- The firm has real methodology worth reusing
- Prior work sits across drives, inboxes and individual laptops
- Client confidentiality makes teams cautious about reuse
- Proposal quality depends on who happens to be writing
- The firm wants to use AI without leaking client material between engagements
Questions about consulting knowledge reuse
- What is consulting knowledge management for proposals?
- It is the practice of making a firm's methodologies, prior work and partner judgement retrievable and reusable when a new proposal is written — with enough control that client-confidential material does not travel between engagements.
- How is this different from a proposal content library?
- A content library stores approved blocks of text, which works for boilerplate. Consulting proposals turn on engagement architecture — objectives, workstreams, sequencing, assumptions — which is judgement applied to a specific client rather than a paragraph to paste.
- Can we reuse a previous client's proposal?
- The firm's methodology and engagement structure are usually the firm's to reuse. The client's commercial terms, internal metrics and identifying details usually are not. Solon holds that distinction explicitly and flags uncertain cases for a person to decide rather than guessing.
- How does Solon prevent cross-client leakage?
- Knowledge sources are classified by workspace, client, permission and reuse policy. Material marked client-confidential is kept out of cross-client reuse, and content that cannot be classified confidently is surfaced for human review.
- Do we have to move our documents into Solon?
- Solon is designed to work around the systems a firm already uses rather than replace them. Which sources are connected, and how, is part of what we configure with beta firms.
- Does this replace our partners' judgement?
- No. It makes prior judgement visible at the moment a proposal is written. Partners still decide what is appropriate for this client, and approve what goes out.