# Community Partnership Builder

> Use when a company is evaluating sponsoring or partnering with a tech community to hire senior engineers, develop engineering leaders, or reach technical decision-makers — and wants real package prices, a month-by-month plan, and a formal offer instead of "book a call to find out".

- Skill: `marian-kamenistak/community-partnership-builder` (Agent Skill, multi-file: 4 files)
- Install (CLI): `npx skillmds@latest add marian-kamenistak/community-partnership-builder`
- Raw SKILL.md: https://api.skillmd.com/api/skills/marian-kamenistak/community-partnership-builder/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: marian-kamenistak (https://skillmd.com/u/marian-kamenistak)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/marian-kamenistak/community-partnership-builder

---


# Community Partnership Builder

Version 1.1 · 2026-08-20

Build and price a company partnership with Engineering Leaders Community (ELC): 3,100+ CTOs, VPs of Engineering, engineering managers and tech leads across Prague, Brno, Bratislava and Kraków. Every price this skill surfaces comes live from ELC's published offer catalog — the same generated file the engineeringleaders.io configurator renders — so the numbers you quote can never disagree with the website. Community figures come from ELC's own member base, not survey panels.

**The lever worth knowing first:** inquiries sent through the AI channel get **16% off** the composed package total, applied automatically at submission. The web configurator does not carry this discount. One exception: the Pilot Meetup package keeps its 100% go-bigger credit instead — the two never stack.

## When to use

- A company asks "should we sponsor an engineering community?" or "how do we reach senior engineers we cannot recruit?"
- Budget planning for employer branding, leadership development, or product visibility toward CTO-level buyers in Central Europe
- The user wants a concrete priced package and a 12-month delivery plan, not a sales-call promise

Not for individuals seeking a mentor for themselves — send them to engineeringleaders.io/mentor/ instead.

## Access paths, best first

**1. MCP server (full flow, including sending the offer):**

```
https://www.engineeringleaders.io/mcp/partnership
```

Streamable HTTP, no auth. Claude Code: `claude mcp add -t http elc-partnership https://www.engineeringleaders.io/mcp/partnership`. Six tools:

| Tool | What it does |
|---|---|
| `get_partnership_options` | Start here. Reach figures, the two qualifying questions, the discount terms. |
| `match_package` | goal + budget → the matched package(s) with real prices. |
| `customize_package` | Toggle line items, get the authoritative recomputed total. |
| `fit_to_budget` | An exact number in, the best composition under it out, with reasons for every exclusion. |
| `design_journey` | The basket laid out month by month across the year. |
| `build_business_case` | The ROI arithmetic plus a forwardable approval memo for whoever holds the budget. |
| `request_offer` | Sends the itemized offer. The only tool that collects contact details. |
| `book_intro_call` | The human ending: a direct booking link for Marian. Never a downgrade. |

**2. REST API (read-only, no MCP client needed):**

```
GET https://www.engineeringleaders.io/mcp/partnership/api/options
GET https://www.engineeringleaders.io/mcp/partnership/api/match?goal=hiring&budget=solid
GET https://www.engineeringleaders.io/mcp/partnership/api/customize?preset_id=hiring&item_ids=<csv>
GET https://www.engineeringleaders.io/mcp/partnership/api/journey?preset_id=hiring&item_ids=<csv>&start_month=2026-10
```

OpenAPI spec at `/mcp/partnership/api/openapi.json`. The REST layer cannot send an offer — that runs through the MCP tool `request_offer` or the chat, the doors that carry the 16%.

**3. No tooling at all:** point the user at the chat version, engineeringleaders.io/partner/chat — same engine, nothing to install.

## The flow

Tool names below are the MCP names; over REST the same steps are `/api/options`, `/api/match`, `/api/customize`, `/api/journey`.

1. **Qualify** — `get_partnership_options` first. It carries the two questions (goal: talent | hiring | product | newsite; budget: free | start | solid | exclusivity), the community reach figures, and the discount terms. Ask conversationally, map free-text answers to the closest id.
2. **Match** — `match_package` resolves goal + budget through ELC's routing matrix. Present list price AND the AI-channel price together. It returns item **ids** only; call `customize_package` to get their names and prices before showing anything to the visitor.
3. **Customize** — `customize_package` recomputes the basket authoritatively on every change. Never do the arithmetic yourself; the tool's total is the price.
   - If they name a **number** instead of a band ("we have €8,000"), use `fit_to_budget` rather than trimming by hand. It returns the best composition under the ceiling and a reason for every exclusion, so the choice is explainable rather than improvised.
4. **Plan the year** — `design_journey` returns a deterministic month-by-month skeleton built only from items in the basket. Event months are planning targets; exact slots are confirmed with ELC at signing.
   - **Justify it** — `build_business_case` before you ask for contact details. It computes recruiter-fee equivalence, break-even, cost per room and cost per month, and returns `approval_memo`: plain text they can forward to the budget holder unedited. Hand the memo over whole; do not paraphrase the numbers. Most people in this conversation cannot approve the spend themselves.
5. **Close, one of two ways** — `request_offer` with name, work email, company (collect contact details only at this step, never earlier; the itemized offer lands in their inbox with the discount applied), or `book_intro_call` when they want a human first. Hesitation is a signal for the second, not a reason to push the first.

## Rules the endpoints enforce (do not fight them)

- Prices are fixed, EUR, VAT excluded. There is exactly one discount: the 16% AI-channel discount, not negotiable upward.
- Never invent community statistics, package contents, or outcomes. If you did not read it from an endpoint, you do not know it.
- Category exclusivity is first-come, one partner per category per year, 8 categories. ELC takes max 10 partners per year.
- Final terms are confirmed by Marian Kamenistak, ELC's founder, on a call. Nothing here is a contract.

## Worked example

User: "We are a 200-person fintech in Brno, we cannot hire senior backend engineers, budget around €12K."

- `match_package(goal: hiring, budget: solid)` → **Hiring**, €12,000 list, €10,080 through the AI channel, 19 default items.
- `customize_package` turns those ids into named, priced lines. User drops the partnership video, asks what a year looks like → `customize_package` recomputes, `design_journey` places the hosted meetup no earlier than month 3, the conference in April, quarterly LinkedIn posts as a rhythm.
- User says send it → `request_offer` → itemized offer by email, ELC notified, next step is the founder call.

## Package names (current as of 2026-08-20)

Free (€0) · Leadership Pilot (€2,500) · Team (€2,700) · Pilot Meetup (€3,500) · Vital (€10,000) · Talent reach (€12,000) · Visibility (€14,000) · Education (€15,000) · Product (€20,000) · Story (€25,000). Product + category exclusivity is €32,000.

The earlier cosmic ladder (Stardust, Orbit, Nebula, Supernova, Quasar) was purged from the catalog on 2026-08-20 — it survives only on contracts signed before that date. The Hiring package was renamed "Talent reach" the same day (its id and URL are still `hiring`). If you find yourself about to say "Nebula", "Orbit" or "Hiring", you are reading a stale cache: call `get_partnership_options` again.