Project Management Tool Comparison — Scored JSON Matrix

<role>
Senior agency operations consultant specializing in software stack architecture, workflow optimization, and profitability engineering for service-based businesses.
</role>

<context>
A boutique digital agency with 12 team members operating on an hourly billing model is selecting a unified project management platform. The agency leadership requires a rigorous, structured comparison matrix ready for inclusion in an internal executive decision document. The tool must balance billable hour tracking, client collaboration, integration flexibility, and administrative overhead during migration.
</context>

<task>
Perform a comparative evaluation of 5 leading project management tools tailored specifically for a 12-person hourly-billing agency. Format the output as a structured JSON object containing tool metrics, official links, evaluation criteria, and a definitive winner recommendation with business rationale.
</task>

<objective>
Provide an objective, data-rich decision framework that enables agency leadership to select and execute a migration to the optimal project management tool, maximizing billable hour capture while minimizing setup friction and operational cost.
</objective>

<requirements>
- Scope: Evaluate 5 distinct project management platforms suited for creative/digital agencies (e.g., Teamwork, ClickUp, Monday.com, Asana, Wrike).
- Team Scale: 12 active paid seats.
- Billing Context: Hourly client billing model requiring strict time tracking, billable/non-billable distinction, and budget tracking.
- Evaluation Criteria per Tool:
  - Canonical product URL (`url`)
  - Monthly price per seat (standard plan tier providing time tracking & client access)
  - Time tracking capability (native vs integration, billable rate controls)
  - Client access features (guest seat pricing model, permission controls)
  - API and ecosystem maturity (REST API, webhooks, native integrations)
  - Migration friction score (1-5 scale) and key operational risks
- Executive Summary: Declared winning platform with explicit rationale tied to agency profitability and efficiency.
</requirements>

<instructions>
1. Role — Act as a senior agency operations consultant evaluating software for an hourly-billed team of 12.
2. Instructions — Evaluate 5 top project management platforms against the operational constraints of an agency requiring billable hour tracking, client transparency, and low administrative friction.
3. Steps —
   1. Select 5 relevant project management platforms widely adopted by digital service agencies.
   2. Identify the exact plan tier required for a 12-person team to access guest permissions, API access, and time tracking.
   3. Document exact seat pricing (monthly equivalent billed annually) and calculate total team cost.
   4. Detail time tracking mechanics, specifically highlighting billable vs. non-billable toggles, hourly rates, and reporting depth.
   5. Detail client portal capabilities, distinguishing between free guest users and paid client accounts.
   6. Evaluate API depth (REST endpoints, webhooks, rate limits) and rate migration difficulty on a 1-5 scale (1 = seamless, 5 = high operational friction).
   7. Provide the canonical official URL for each tool's platform or pricing page.
   8. Select one single tool as the overall winner and articulate a 3-4 sentence justification based on margin protection, tracking efficiency, and agency overhead.
4. End-goal — Deliver a single, fully populated JSON structure adhering to the specified schema, ready to drop into a decision document without further editing.
5. Narrowing — Do not evaluate enterprise tiers requiring custom sales calls; stick to published self-serve tiers. Do not output vague feature lists; frame every evaluation point around hourly billing efficiency, client management, or migration pain.
</instructions>

<output_format>
Return valid JSON matching the following schema shape:

```json
{
  "comparison_matrix": [
    {
      "tool_name": "string",
      "url": "https://...",
      "plan_tier_evaluated": "string",
      "price_per_seat_monthly": "string",
      "total_monthly_cost_12_seats": "string",
      "time_tracking": {
        "type": "Native | Integration Required",
        "billable_rates_support": boolean,
        "details": "string"
      },
      "client_access": {
        "free_client_seats": boolean,
        "details": "string"
      },
      "api_and_integrations": {
        "has_rest_api": boolean,
        "details": "string"
      },
      "migration_pain": {
        "score_1_to_5": number,
        "primary_bottleneck": "string"
      }
    }
  ],
  "decision": {
    "winning_tool": "string",
    "rationale": "string"
  }
}
```
</output_format>

<examples>
```json
{
  "comparison_matrix": [
    {
      "tool_name": "Teamwork",
      "url": "https://www.teamwork.com",
      "plan_tier_evaluated": "Deliver",
      "price_per_seat_monthly": "$9.99",
      "total_monthly_cost_12_seats": "$119.88",
      "time_tracking": {
        "type": "Native",
        "billable_rates_support": true,
        "details": "Native timers, billable/non-billable flags, project budget tracking against logged hours."
      },
      "client_access": {
        "free_client_seats": true,
        "details": "Unlimited free client users with granular privacy controls per task and milestone."
      },
      "api_and_integrations": {
        "has_rest_api": true,
        "details": "Full REST API v2/v3 access, native integrations with QuickBooks, Xero, and Harvest."
      },
      "migration_pain": {
        "score_1_to_5": 2,
        "primary_bottleneck": "CSV re-mapping of existing task dependencies and billable historical logs."
      }
    }
  ],
  "decision": {
    "winning_tool": "Teamwork",
    "rationale": "Built specifically for client services, offering native billable time tracking, custom rate cards, and free client guest seats out of the box, offering the lowest operational friction for an hourly agency."
  }
}
```
</examples>

<verification>
- [ ] Each metric has an explicit definition; no ambiguous names left.
- [ ] Null / duplicate / outlier handling is stated, not implicit.
- [ ] Query respects the performance budget and uses the correct schema / column names.
- [ ] No PII or excluded fields appear in the output.
- [ ] All schema fields populated with realistic example values
- [ ] Field types match the spec; no extra fields beyond schema
- [ ] No required field is null or placeholder text
- [ ] Output meets the success criterion: can drop straight into a decision doc
- [ ] Language and depth fit the audience: 12-person agency decision makers
- [ ] JSON validates and parses without errors
</verification>