| Best when | You need a complete personal Meter without client or team workflows. | You need to explain selected client work without exposing its content. | Multiple engineers need shared consent, budget, and allocation decisions. |
|---|
| Data boundary | Accountless use stays on one Mac; signed-in personal metadata can sync across your devices. | Personal usage can sync; client mappings and free-text notes stay in this browser. | Only metadata each engineer explicitly agrees to share enters team rollups. |
|---|
| What you get | Provider runway, full personal history, period comparisons, goals, and own-device composition. | One reviewed snapshot to copy, print/save as PDF, and export as CSV. | Coverage, reference-cost forecast, budget status, project/model breakdowns, and a copyable operating brief. |
|---|
| Progress loop | Review history and follow goals you chose without a productivity score. | Turn reviewed project facts into client-facing evidence and a reusable report workflow. | Turn coverage, freshness, cost, and allocation signals into a decision queue—never a people ranking. |
|---|
| Portable output | Personal Meter history and MCP answers; no client handoff snapshot. | A client-selected evidence snapshot with one report ID across text, PDF, and CSV. | A monthly operating brief with the observed scope, forecast, allocation, and next actions. |
|---|
| Choose this tier | Start here for your complete personal Meter. | Choose Solo when measurements need to become client proof or reporting. | Choose Team when shared operating decisions begin. |
|---|