# ECC v2.0.0-rc.1 Partner, Sponsor, and Talks Pack

This pack turns the rc.1 release surface into outbound-ready copy for sponsors,
partners, consulting conversations, conference talks, podcast bookings, and
community announcements.

It is not a publish action. Use it after the release URL ledger, video suite,
and publication gates are current.

## Current Business Baseline

| Metric | Current | Target | Gap |
| --- | ---: | ---: | ---: |
| MRR | `$1,728/mo` | `$10,000/mo` | `$8,272/mo` |
| Core revenue lanes | Sponsors, ECC Tools Pro, consulting, talks | Repeatable growth loop | Approval-gated outbound |
| Launch proof | rc.1 preview pack, video suite, queue-zero audit | Public release package | Final URLs and human approval |

## Positioning Line

ECC 2.0 is the harness-native operator system for agentic work.

Use this short version in partner and sponsor messages:

```text
ECC gives teams one reusable layer for skills, hooks, rules, MCP conventions,
release gates, and operator workflows across Claude Code, Codex, OpenCode,
Cursor, Gemini, Zed, GitHub Copilot, and terminal-only workflows.
```

## Offer Ladder

| Motion | Best fit | Starting point | Primary ask |
| --- | --- | ---: | --- |
| Pilot sponsor | OSS-friendly team that wants early signal | `$200/mo` | GitHub Sponsors |
| Business sponsor | Tooling or AI infra company that wants logo and case-study surface | `$500/mo` | GitHub Sponsors or direct invoice |
| Strategic partner | Platform, marketplace, security, or developer-tool company | `$1,000+/mo` | Sponsor plus launch or integration plan |
| Consulting sprint | Team adopting agent harnesses internally | Scoped quote | Harness audit, rollout plan, and operating loop |
| Talk or podcast | Devtools, AI engineering, security, OSS, or founder audience | No fee required for high-leverage reach | Recording slot, demo slot, or conference proposal |

## Partner Targets

Prioritize partners that already benefit from a harness-agnostic operating
layer:

- AI coding platforms and IDEs;
- hosted agent and workflow orchestration tools;
- code review, security, and supply-chain vendors;
- model and inference providers;
- developer education, podcast, and conference organizers;
- teams adopting multiple harnesses at once.

## Sponsor Outbound

Subject:

```text
ECC 2.0 sponsor slot for cross-harness agent workflows
```

Body:

```text
Hey [name],

I am getting ECC v2.0.0-rc.1 ready for release review.

The project is now positioned around one reusable operator layer for agentic
work across Claude Code, Codex, OpenCode, Cursor, Gemini, Zed, GitHub Copilot,
and terminal workflows.

The sponsor fit is pretty direct: ECC reaches the exact builders who are
standardizing their AI coding stack, security posture, and workflow automation.

The current public sponsor ladder is:

- Pilot Partner: $200/mo
- Business Sponsor: $500/mo
- Strategic Partner: $1,000+/mo

Business sponsors get logo placement and release visibility. Strategic partners
can turn it into a deeper integration or launch motion.

Repo: https://github.com/affaan-m/ECC
Sponsor: https://github.com/sponsors/affaan-m
Release notes: https://github.com/affaan-m/ECC/blob/main/docs/releases/2.0.0-rc.1/release-notes.md

If useful, I can send the short sponsor packet and a proposed first 30-day plan.

Affaan
```

## Platform Partner DM

```text
ECC 2.0 is getting close to rc.1.

The release is centered on cross-harness agent workflows: reusable skills,
hooks, rules, MCP conventions, release gates, and an optional Hermes operator
shell.

The partner angle is not "another prompt pack." It is a tested operating layer
for teams using more than one AI coding harness.

I think there is a real integration or co-launch angle here if your team wants
better setup, policy, security, or workflow portability for agent users.

Repo: https://github.com/affaan-m/ECC
```

## Consulting Intro

```text
I am open to a small number of ECC 2.0 implementation sprints for teams that
are standardizing AI coding workflows.

The useful scope is usually:

1. audit the current harness setup;
2. turn repeated workflows into ECC skills, hooks, and rules;
3. add release, security, and CI gates;
4. create a team operating loop that works across Claude Code, Codex, OpenCode,
   Cursor, Gemini, Zed, GitHub Copilot, and terminal workflows.

This is not generic AI consulting. The output is a working harness operating
system your team can keep using.
```

## Talk And Podcast Pitch

Title options:

- Building a Cross-Harness Operating System for AI Coding
- From Prompt Packs to Operator Systems
- What Breaks When Teams Adopt Too Many AI Coding Harnesses
- Security and Release Discipline for Agentic Coding Workflows

Short pitch:

```text
ECC started as an open-source workflow layer for Claude Code and is now moving
toward a cross-harness operating system for agentic work.

The talk is about the practical problems teams hit after the first AI coding
honeymoon: scattered prompts, duplicated setup, weak release gates, fragile
security posture, and no clear operating loop across tools.

I can show how ECC uses reusable skills, hooks, MCP conventions, release gates,
AgentShield-style security checks, and an optional Hermes operator shell to make
agentic work more measurable and portable.
```

## GitHub Discussion Announcement

```text
ECC v2.0.0-rc.1 preview pack is ready for final release review.

The main point: ECC 2.0 is a meta-harness for agentic work.

It is the portable layer that keeps skills, hooks, MCP conventions, release
gates, security checks, and team workflows reusable across the AI coding tools
people actually use.

It now has a reviewed public surface for:

- reusable skills, hooks, rules, and MCP conventions;
- Claude Code, Codex, OpenCode, Cursor, Gemini, Zed, GitHub Copilot, and
  terminal workflows;
- Hermes as the optional operator shell;
- release, security, queue, discussion, Linear, observability, and video-suite
  gates.
- a gated Itô prediction-market skill pack for research, comparison, planning,
  and risk review, with Itô API access kept separate and approval-based.

The GitHub prerelease and npm `next` package are live now. The release remains
approval-gated for plugin paths, video URLs, final outbound URLs, and billing
claims that have not been freshly rechecked.

Feedback wanted: install friction, cross-harness gaps, partner integrations,
sponsor fit, prediction-market research use cases, and examples of teams using
multiple AI coding harnesses.
```

## Video CTA Hooks

Use these with the release video suite:

- "If your AI coding setup only works in one harness, it is not an operating
  system yet."
- "ECC 2.0 is the shared layer: skills, hooks, MCPs, release gates, and team
  workflows across the tools people actually use."
- "OSS stays free. Sponsors, Pro, and implementation work fund the public
  layer."
- "Start with one workflow lane: engineering, research, content, or outreach."

## Do Not Send Or Publish If

- The release URL ledger still has stale or placeholder links.
- `npm run release:video-suite -- --format json` is not green against the
  intended video roots.
- The GitHub prerelease or npm package readback is contradicted, or a plugin
  path, video URL, billing claim, or official directory listing is described as
  live without evidence.
- The message claims native payments are ready before ECC Tools billing readback
  passes.
- The recipient needs a custom promise that is not covered by `SPONSORS.md`,
  `SPONSORING.md`, or a separate consulting scope.
- The user has not approved outbound sponsor, partner, consulting, or media
  messages.

## Routing Links

- Repo: <https://github.com/affaan-m/ECC>
- Release notes: <https://github.com/affaan-m/ECC/blob/main/docs/releases/2.0.0-rc.1/release-notes.md>
- Quickstart: <https://github.com/affaan-m/ECC/blob/main/docs/releases/2.0.0-rc.1/quickstart.md>
- Sponsor: <https://github.com/sponsors/affaan-m>
- Sponsor tiers: <https://github.com/affaan-m/ECC/blob/main/SPONSORS.md>
- Sponsoring guide: <https://github.com/affaan-m/ECC/blob/main/SPONSORING.md>
