A clean room for every client.
The consultant's nightmare is bleed: client A's numbers surfacing in client B's memo. GPTree's projects scope memory, files, and instructions per client, so each engagement thinks inside its own walls.
Separate rooms, shared craft.
Client work in projects
One project per client: the brief, the reference files, the standing instructions, and a default model tuned to the engagement. Memory scoped to the project means what you learn about Alpha never colors what you write for Beta. Your methodology stays yours; their context stays theirs.
- Standing instructions and files brief every conversation
- Project-scoped memory keeps client contexts sealed
- A default model and persona per engagement
Two clean exits
When the work ships, it leaves without the mess. A read-only share link shows the client a polished thread they can read without an account and cannot branch or edit. Or export the deliverable to Markdown or JSON and drop it into their stack. One honest limit: projects cannot change owners yet, so keep engagements in the account that runs them.
- Read-only public share links, no client account needed
- Export to Markdown, plain text, or JSON
- Ownership transfer is not supported yet; plan accordingly
What this workflow leans on.
- Projects: one sealed room per client engagement
- Scoped memory: no bleed between engagements, inspectable always
- Branching: explore recommendations before committing to one
- Merge Board: Decision mode drafts the recommendation memo
- Share links: clients read without accounts or edits
- Export: deliverables in the format their stack wants
Every claim here is documented in the field guide's consulting playbook. gp-tree.com/learn
Never re-explain yourself.
Start free in under a minute. No card required. Use built-in credits or bring your own keys.