Failure PatternDecision layer

Why Agencies Fail With Knownbase in Multi-Client Delivery

Symptom: Client A's architectural decisions appear in Client B's agent context, causing cross-project contamination and confused code suggestions. Root cause: Agencies fail to enforce per-project workspace isolation, so the Free plan's 3-project limit and shared MCP keys allow notes from one client to leak into another's agent context.

By InnovaAI ResearchPublished

Agent Memory Knowledge Connectors
How do you recognize it?
  • •Client A's architectural decisions appear in Client B's agent context, causing cross-project contamination and confused code suggestions.
  • •Agents repeatedly re-ask for the same project constraints despite notes existing in Knownbase, indicating retrieval failures or poor note organization.
  • •The agency's monthly Knownbase bill spikes unexpectedly as note counts exceed the 3,000-note limit on the $2.50 Go plan, forcing an unplanned upgrade.
  • •New team members spend hours reading stale notes that contradict the current codebase, because revision history is ignored or overwritten.
  • •Clients complain about inconsistent delivery quality when different agents handle the same project across sessions, due to fragmented memory.
Why does it happen?
  • •Agencies fail to enforce per-project workspace isolation, so the Free plan's 3-project limit and shared MCP keys allow notes from one client to leak into another's agent context.
  • •The 300-note cap on the Free tier and 3,000-note cap on the Go plan are treated as soft limits, but Knownbase's search returns all matching notes, so exceeding them degrades retrieval precision and slows agent responses.
  • •Teams skip defining a structured note taxonomy (tags, statuses) during onboarding, so agents can't filter by project or status, leading to irrelevant context being loaded into every session.
  • •The MCP server's basic search on the Free plan lacks advanced filtering, so agencies that don't upgrade to a paid plan for backup/export and more MCP keys end up with unmanageable note sprawl.
How do you fix it?
  • •In the Knownbase dashboard, create a separate workspace per client and assign unique MCP keys to each, ensuring agents only access the relevant project memory.
  • •Set up a note naming convention that includes the client code and date, and enforce it via the onboarding guide so agents can query with precise filters.
  • •Review the 'Notes' list weekly and archive or delete notes older than 30 days that are superseded by newer revisions, keeping the active set under the plan's limit.
  • •Upgrade to the Solo plan ($5/month) to get 10 projects and 4 MCP keys, which provides headroom for 3+ concurrent client codebases without hitting caps.
Open the Knownbase courseKnownbase decision recordBrowse the Academy

More on Knownbase

More for Agent Memory Knowledge Connectors