IT consulting

One knowledge base per client for a small consultancy

A small Dynamics 365 consultancy runs projects for several clients and wanted each client kept in its own knowledge base.

Phase by phase

1. Phase 0 · Free demo

   Remote demo

   A knowledge base for his practice was built live on the call from his public profile. In the same session the assistant drafted starting code, documentation and diagrams for his integration project. He decided to go ahead during the call.

2. Phase 1 · Goal

   One knowledge base per client

   The goal was a separate knowledge base for each client, connected to that client's cloud platform and project board.

3. Phase 2 · AI readiness scan

   Clients, tools and access

   An overview of his clients, the cloud platforms and project tools each one uses, and the access he has to each. He also chose how to record meetings so the notes end up in the right client's knowledge base.

4. Phase 3 · Connecting

   Setup pack

   On the day of the demo he received global settings, safety rules for what the assistant may and may not do, and the knowledge base for his practice. He installed them himself before the setup session.

   Setup session

   In one session he was shown how to set up the knowledge base for his first client and its connections: read-only access to the client's project board, and cloud access with daily permission activation. The assistant then read the board's user stories, updated the project brief and drew the architecture from the existing code.

   The next three

   With the first knowledge base as the example, he set up three more himself. A guide covers syncing his meeting notes into them.

5. Phase 4 · First project

   Not part of this engagement

Results

A technical client needs less support. After the demo, the setup pack and one session, he builds and runs his knowledge bases himself.