Skip to main content
A Project is a container for a body of work. Each Project gets its own chat history, artifacts, research requests, and (optionally) project-specific Messaging Framework. Use Projects when several conversations and outputs belong together.

​
When to create a Project

Create a Project when you’re working on something with a defined scope and a finite team:
  • A product launch
  • A campaign or content sprint
  • A competitive review or battlecard refresh
  • A market expansion analysis
  • A persona development or refresh exercise
  • A repositioning effort
For one-off queries, the personal Chat workspace works fine.

​
Creating a Project

From the dashboard, click + New Project. Give it a name and a description. The description helps your team find it later and gives GetWhys context for the work happening in the Project.

​
What lives inside a Project

Chats

All conversations started inside the Project, with full history and citations.

Artifacts

Outputs created inside the Project — drafted content, frameworks, anything saved from Chat.

Research Requests

Custom interviews scoped to this Project.

Messaging Frameworks

Project-specific frameworks that override org defaults.

​
Permissions and team

Projects inherit your organization’s permission model. Anyone in your organization with feature access can see Projects unless your admin has restricted visibility. Slack-connected Projects can be restricted to specific Slack channels or workspaces — see Slack integration.

​
Renaming, archiving, deleting

Open the Project, click the project menu, and choose Edit, Archive, or Delete. Deleted Projects are permanently removed. Archive if you might want to revisit later.

​
A pattern teams use

Create a Project at the start of a quarter for each major initiative. Set the Project’s Messaging Framework so every conversation inside it produces on-positioning output. By end of quarter, the Project is a self-contained research and content record you can hand off, archive, or build on next cycle.