← all use cases
for consultants & agencies ·one memory layer

Every client, cleanly kept apart.

Juggling many clients means many sets of context that must never mix. Scopes keep each engagement's memory isolated and instantly recallable.

start free ↵how it works →
how it shows up ·memories your assistant keeps
  • preference

    Acme prefers weekly async updates, not standing calls.

    claude · −6d · scope: acme
  • decision

    Lindqvist approved rebrand direction B; proceed to assets.

    chatgpt · −3d · scope: lindqvist
  • fact

    Meridian's fiscal year starts in April; plan reviews around it.

    claude · −12d · scope: meridian
what changes ·with the loop closed
  • One memory layer, cleanly scoped per client
  • Ramp back into any account in seconds
  • Nothing bleeds between engagements
why it matters ·the shape of the problem

Each engagement carries its own decisions, preferences, and facts. 3ngram scopes memory per client, so your assistant ramps back into any account in seconds and context from one engagement never surfaces in another.

Consulting is context switching as a business model. Every client carries its own decision history, working preferences, and facts on file, and the cost of mixing them up is trust.

3ngram gives each engagement its own scope. While you work, your assistant captures the approvals, preferences, and facts that matter into the client’s scope, and recalls only from that scope when you are back in the account. Ramp-up time shrinks to the question “where were we with Meridian?”, and the answer arrives with sources instead of a scroll through last month’s threads.

friction points ·what breaks, and what 3ngram does instead
01

Switching clients costs an hour of re-reading

Ramping back into an account means scrolling old threads, decks, and email to reconstruct where the engagement stands before you can do anything billable.

3ngram: The engagement's memory is a scope away. Ask your assistant where things stand with the account and the decisions, preferences, and open items come back at once.

02

Client context bleeds across conversations

One assistant, ten clients. A detail from one engagement surfacing in another is at best embarrassing and at worst a confidentiality problem.

3ngram: Scopes are hard boundaries. Recall respects them, so memory captured under one client's scope never surfaces while you are working in another.

03

Working styles get re-learned every cycle

Acme wants async updates, Lindqvist wants decks, Meridian plans around an April fiscal year. Those preferences live in your head until the day they do not.

3ngram: Preferences are captured once as typed memory in the client's scope. Every later session with that client starts already knowing how they like to work.

faq ·the questions we hear most
How do scopes keep clients separate?
A scope is a namespace for memory. Each engagement gets its own, and recall respects the boundary, so context from one account never surfaces in another. Deleting a scope removes only the label; the memories that carried it stay intact.
Which tools does this work with?
Any MCP-compatible client: Claude Desktop, Claude Code, ChatGPT, Cursor, Codex, and more. The same scoped memory is available wherever the engagement's work continues.
Is there a free tier?
Yes. The Free plan requires no credit card. It includes the MCP server, web dashboard, and unlimited memories and search under a fair-use usage budget. Upgrade to Pro for a higher budget and priority support, with AI answers and daily digests coming soon.

Keep Every Engagement's Memory Separate and Ready

3ngram scopes memory per client, so decisions, preferences, and facts stay isolated and come back the moment you switch accounts.

get started free ↵