---
name: gtm-performance-scorecard
description: "Measure GTM funnel progress, channel yield and next-period priorities from reconciled evidence. Use for gtm performance scorecard tasks; select only the requested methods."
metadata:
  version: "1.0.0"
---

# GTM Performance Scorecard

Measure GTM funnel progress, channel yield and next-period priorities from reconciled evidence.

## OLLIE Runtime integration

Use relevant methods under the active OLLIE Operator. Read live Workspace Context and tenant bindings for client facts, account identity, goals, permissions and required inputs. Consume ask-ollie-authority-core for authority, outloop-access-fallback for access and recovery, email-lifecycle-core for communication, and the bootstrapper Runtime Contract for execution ownership and completion. This skill introduces no scheduler, independent permission policy or competing Runtime owner.

Discover the active Workspace’s approved capabilities before choosing API or browser access. Use Outloop for external service actions and the host’s supported tools for local artifacts. A product name in this package is not an access grant. Never import private account configuration or follow a source method that bypasses host restrictions. Apply the current task’s authorization; a library update does not grant permission to send, publish or activate a campaign.

## Required inputs

- Comparable reporting periods
- Funnel definitions and attribution rules
- Verified CRM and channel observations
- Targets and team capacity

Use for weekly reviews, channel allocation and periodic GTM recalibration. Read [measurement rules](references/measurement.md).

## Reconcile definitions before counting

Define sourced, qualified, contacted, replied, met, opportunity, won and activated for this workspace. Count unique entities or events explicitly and use the same unit in numerator and denominator. Align reporting windows, timezone, attribution and stage dates. Separate cohort conversion from period activity.

## Explain performance and decisions

Compare actuals with approved targets and previous comparable periods. Separate a measured result, an inferred explanation and a proposed experiment. Show how much activity lacked attribution or proof. Use pipeline stage ages and actual commitments to explain bottlenecks rather than celebrating outreach volume.

## Plan the next period

Allocate effort using observed yield, confidence, cost and available capacity. Keep small experimental channels separate from established channels. Define an owner, hypothesis, acceptance metric and review date for each change. Do not invent budget or revenue targets from another workspace.

## Deliver the scorecard

Produce a reconciled funnel table, channel comparison, exceptions and next-period priorities. If email delivery is requested, use the Runtime’s current communication owner and approved recipients. Report created versus delivered artifacts accurately.

## Completion

Verify findings against source evidence and read back every resulting artifact or authorized change. Distinguish a saved draft, queued job, active workflow and completed delivery. Return the requested outcome, evidence, output location and precise outstanding dependencies. Complete independent work when one dependency is unavailable. Package validation and synthetic fixtures do not establish real host import or provider execution.

Read [evaluation scenarios](references/evaluation.md) when testing this skill.