Improve the way you work once. Reuse it deliberately.

Firm methodology, specialist roles and working standards are the parts of your practice worth maintaining once. Keep reusable material in shared knowledge and client facts in their project room, with scope and permissions deciding where each can be used.

Why copied projects accumulate configuration debt

The usual way to reuse an AI setup is to copy the last project and edit it. Every copy is a fork: an improvement made in one does not reach the other nine, and after a few months no two engagements are running the same method. The debt is invisible until someone asks which version of the approach a deliverable was built on.

What counts as reusable firm capability

Specialist definitions — a role, its expertise, the standards it holds and what it should always question. Team definitions — who is in the room and how they work together. And approved general knowledge: the material that is true of your practice rather than of one client.

How methodology is added and maintained today

You define a specialist or a team once, and it is available to use in engagements from then on. Knowledge is uploaded and scoped to where it belongs. Both are edited in one place rather than re-described per engagement.

How scope works across engagements

Knowledge and memory carry explicit scopes alongside their workspace and room containment. Workspace material can be used across rooms by authorised members; room material follows that room’s access rules. A guest does not inherit access to workspace material merely by entering a room.

How updates reach work in flight

An update to a specialist, a team or firm knowledge applies to work done from that point on. It does not reach back into engagements already delivered, and it does not silently rewrite an approved report. If you need an old engagement brought up to the current method, that is a piece of work you do, deliberately.

How a lesson becomes firm capability

Review the lesson, remove client-specific or sensitive details, and decide whether its intended readers should receive it. Promotion into shared knowledge is a human decision; a label such as “general lesson” is not proof that the content is safe to share.

Limits

What this does not do

Stated here rather than discovered later. If a claim is not on this site, assume we are not making it.

Improvements do not propagate automatically into every engagement. An update applies to work done from that point forward.
Nothing becomes reusable firm capability by itself. A lesson becomes firm knowledge only when a human decides it should and puts it there.
Screening helps identify sensitive or client-specific material, but it can make mistakes. Review a proposed lesson and its intended readers before making it shared knowledge.
There is no version-pinning that ties a delivered document to the exact state of a method at the time it was written.

Review security and data handling →

Also in this section

The rest of the detail

Client context & isolation
What is contained inside one engagement, what may cross between them, and how that line is enforced.
Quality & review
What the critic and validator actually do, and where accountability stays.

See it working.

Free recorded demo · No live AI calls

Try the interactive demo Go to Launchpad Live Walk through your use case with us