​
What Are Projects?

Projects represent specific initiatives (e.g. “New Onboarding Flow”). Macroscope automatically groups code activity into projects, which serve as the building blocks for reports and productivity insights. Occasionally you may need to rename a project to better reflect how your team clusters work, update a project’s description to provide more context, merge projects that belong together, or delete a project that is too granular. For most customers, though, this runs on autopilot most of the time and only needs occasional steering.
FAQ: What happens when I edit a project?→ Editing a project doesn’t reclassify past commits, but it does affect classification going forward. Over time, Macroscope learns and improves as it sees more commits.
Project Graphs

​
What Are Areas?

Areas are high-level groupings that organize related projects under broader business units (e.g. Consumer Team, Revenue Team). The more context added to an Area description, the more accurately Macroscope can assign projects to it.
Add a detailed description to each Area so that Macroscope can categorize projects into them more accurately.
For large organizations that divide work into distinct units, Areas are a powerful way to bring structure and clarity. We recommend using Areas to mirror the way your organization naturally thinks about work—not by technical surface (like Frontend vs. Backend), but instead by business units. This way, you can ask Macroscope questions in your own language and get updates that align with your company’s existing mental model.
FAQ: Does my team need Areas?—> If your engineering team is small (fewer than 10 developers) or your roadmap is already straightforward, you likely don’t need Areas. But once your company grows or you begin segmenting work by business units, Areas can add real leverage. They deliver value when they mirror meaningful business distinctions, enabling Macroscope to scale insights alongside organizational complexity. If that structure doesn’t exist for your company—or if introducing Areas feels forced—we recommend skipping Areas and sticking with Projects.