Consultant collaboration that keeps the knowledge
What you buy from a consultant is judgement. Melp keeps the analysis, the options rejected and the reasoning in a workspace that outlives the engagement.

The engagement arc
Keep the reasoning, not only the final recommendation
An advisory engagement produces its most valuable knowledge during discovery and debate, before the final deck is written.
Consultant-owned tools
- Discovery notes leave with the consultant. Interviews and evidence stay in private tools the client cannot search later.
- Trade-offs disappear. The deck records the selected option, but not why the alternatives were rejected.
- The thinking gets purchased twice. When circumstances change, the client must reconstruct the same reasoning from scratch.
Shared workspace in Melp
- Discovery becomes shared evidence. Meeting transcripts and summaries remain in the engagement workspace.
- Decisions retain their rationale. Options, constraints, and owners are captured when the discussion happens.
- The record outlives the contract. Teams can search the engagement history and adapt prior reasoning instead of rebuying it.
What turns an engagement into institutional memory
Knowledge transfer fails for structural reasons, not because consultants withhold.


Several clients, no possibility of crossover
An independent consultant carries a specific professional risk: material from one client surfacing in another's context. That is usually managed by discipline, which works until the week someone is tired. Structural separation is a better answer than vigilance.
- Each engagement is its own workspace with its own membership
- No shared search surface across clients, so a search cannot cross a boundary
- Files scoped to a workspace's folders rather than one personal drive
- Each client sees only their own participants

Long tenure, external identity
An interim CFO is effectively part of the leadership team for six to eighteen months while remaining external. They need real depth of access and a clean, complete exit — a combination guest accounts handle badly in either direction.
- Broad access across the workspaces their role requires
- Attributable participation in decisions, for governance and their own record
- Meeting summaries documenting decisions during their tenure
- Access removed cleanly at the end of the engagement
Questions from both sides of an engagement
Clients ask about retention. Consultants ask about separation and their own material.
Related use cases
Advisory relationships overlap with other external work.
Keep the thinking, not just the deliverable
Run your next advisory engagement in a shared workspace and test the real question at handover: could a new joiner explain why, without asking anyone?