Skip to main content

​
What You’ll Learn

  • What Master Projects do differently
  • When to use one
  • How cross-project knowledge works
  • Practical use cases

​
What Is a Master Project?

A regular project is isolated - its knowledge, files, and memory stay within that project. A Master Project breaks that boundary. It can draw on knowledge from all your other projects. This means you can ask questions that span your entire body of work across all initiatives.

​
When to Use a Master Project

​
Strategic Planning

You have separate projects for Product, Marketing, Sales, and Engineering. You need to make a decision that considers all four perspectives.

​
Cross-Initiative Patterns

You notice similarities across projects and want to identify patterns or contradictions.

​
Executive Reporting

You need to summarize progress across all active initiatives in one conversation.

​
Knowledge Synthesis

Your research across multiple projects has overlap. A Master Project connects the dots.

​
How It Works

  1. Create a project and enable the Master Project setting
  2. Start a conversation in the Master Project
  3. Ask cross-project questions - the AIs search across all project knowledge
  4. Get synthesized answers that draw from multiple sources

​
Examples

​
Cross-Project Strategy

"Based on what we've discussed across all my projects, what are
the three biggest risks to our company right now?"
The AIs pull from Product (technical debt), Marketing (competitive pressure), and Sales (pipeline concerns) projects.

​
Pattern Recognition

"Have I made any contradictory decisions across projects?
For example, am I planning to grow the team in one project
while cutting costs in another?"

​
Progress Overview

"Give me a status update across all active projects.
What's on track, what's at risk?"

​
Knowledge Reuse

"In my competitor research project, I analyzed pricing.
In my product project, I discussed our value proposition.
How do these connect? Are we priced appropriately?"

​
What a Master Project Can Access

  • Knowledge Graph entities from all projects
  • Key decisions stored in project memory
  • File content uploaded to any project
  • Conversation insights extracted across projects

​
What It Can’t Do

  • It doesn’t give other projects access to each other (only the Master Project has cross-project visibility)
  • It doesn’t merge projects together
  • It doesn’t change or update information in other projects
  • It won’t access projects you’ve archived or deleted

​
Tips

  • You probably only need 1-2 Master Projects. They’re for strategic, cross-cutting work.
  • Keep your individual projects focused - the Master Project handles the synthesis.
  • Master Projects are especially powerful if you’ve been building knowledge across multiple initiatives over time.
  • Use Master Projects for quarterly reviews, strategic planning, and big-picture thinking.

​
Still Need Help?

Reach out to us at [email protected] or use the feedback button in the app.