Consulting workflow
How to Build a Client Project Knowledge Base for Consulting
Keep one consulting engagement's sources, research, decisions, deliverables, and handoff context in a traceable client-project knowledge base.
Article packet
Workflows
Independent consultants, boutique consulting teams, and research analysts delivering client engagements
8 min read
01
Keep each client in a separate source boundary instead of mixing engagements.
02
Trace findings, decisions, and deliverable claims back to current client-approved sources.
03
Leave a reviewable handoff that records open questions, stale evidence, and the next owner.
01
Quick answer
Create one client-scoped knowledge base per engagement. Register only the approved project sources, keep a decision and open-question log, distill reusable findings into a source-backed Page, and verify every deliverable claim before handoff.
Wenlan can keep Sources, atomic Memories, and maintained Pages inside a client Space, with source references, revisions, stale state, lint, and review. It does not provide CRM ingestion, email or calendar sync, role-based access control, automatic redaction, legal compliance, billing, or project management.
02
When this problem appears
A consultant often starts the next proposal, workshop, deliverable, or handoff by reconstructing context from folders, interview notes, slide decks, chats, and personal memory. The risk is not only wasted time: evidence from another client can leak into the engagement, an old decision can look current, and a polished claim can lose its source.
03
Build one client-to-handoff loop
Start with a non-sensitive sample engagement. Use the client's contractual and security controls before adding confidential material.
- Create one Space and one source folder for a single client engagement; never use a shared catch-all client corpus.
- Register the approved proposal, scope, research, interview notes, source documents, decisions, and current deliverables with `wenlan sources add <path>`.
- Record each important decision with its date, owner, evidence, alternatives, and what would reopen it; keep unanswered questions separate.
- Distill one repeated project question into a maintained Page, then verify the cited source and revision before copying a claim into a deliverable.
- When a source changes, resync it and review only the affected Pages; mark unresolved claims stale instead of silently preserving them.
- Before handoff, record current scope, accepted decisions, open questions, deliverables, source boundaries, risks, and the next responsible person.
- Run lint and review before sharing. Keep confidential or regulated material out unless the engagement's approved controls permit it.
After Wenlan and the AI client are configured
wenlan status
wenlan sources add ~/Clients/acme-approved-sources
# In a Wenlan plugin client:
/distill <client project question>
/pages <client project question>
/lint
/curate
/handoff04
What to check next
Local-first storage does not replace a consulting agreement, client consent, access control, retention policy, redaction, or a secure document system. Start with non-sensitive sample data, keep each client isolated, and withhold any claim whose current source cannot be verified.
Build one inspectable client handoff
Create a client-scoped source boundary, verify one deliverable claim, and leave a handoff another consultant can reproduce.
FAQ