Slug
sponsorship-launch
Scope
Whole pack
File path
No response
Request
Write a four-channel pack announcing that the Nano Collective sponsorship program is now live.
The program funds the community fund that pays bounties to OSS contributors. Sponsors choose from three productised tiers — Individual ($5 / $25 / $100 per month), Supporter ($250 per month), Builder ($1,000 per month) — or open a conversation about a bespoke partnership. The full pitch, tiers, and current-sponsors empty-state placeholders live at nanocollective.org/sponsor.
Angle: this is a "new program, just launched" announcement. The sponsor wall is intentionally empty at launch — that's the framing, not a thing to apologise for. Early sponsors set the tone for the rest.
Audiences across the four channels:
- LinkedIn — companies, founders, and operators who might sponsor or know someone who would. Slightly more company-aware register.
- X — the developer community already using NC tools; lean on the credibility of what's shipped already.
- GitHub Discussion — contributors and observers of the org; technical, operational tone.
- Reddit — OSS-curious developers; explain why the model is structured the way it is (community fund, no influence over roadmap, transparent ledger).
Across all four channels: name the four shipped projects (Nanocoder, Nanotune, get-md, json-up). Mention that all funds flow transparently through Open Source Collective. Link the canonical URL on every body.
Do not paraphrase the three principles. Do not use forbidden phrases ("Sovereign AI", "Trustless AI", etc.). Operational, understated voice throughout — match the brand-voice guide.
Additional context
Source of truth and grounding references:
- nanocollective.org/sponsor — the live sponsorship page, with the full tier breakdown and empty-state framing.
- _refs/collective/organisation/support.md — recently updated to describe the productised tiers.
- _refs/collective/organisation/economics-charter.md — for how funds reach contributors.
- _refs/collective/sponsors/ — the new operational docs (operations, onboarding, offboarding) for anyone who wants the mechanical detail.
- _refs/collective/organisation/brand.md — voice and forbidden-term list. Authoritative.
The program is launching with an empty sponsor wall. Do not invent sponsors or imply momentum that doesn't exist. The honest framing is: "new program, here's the door, early sponsors lock in the rate."
Slug
sponsorship-launch
Scope
Whole pack
File path
No response
Request
Write a four-channel pack announcing that the Nano Collective sponsorship program is now live.
The program funds the community fund that pays bounties to OSS contributors. Sponsors choose from three productised tiers — Individual ($5 / $25 / $100 per month), Supporter ($250 per month), Builder ($1,000 per month) — or open a conversation about a bespoke partnership. The full pitch, tiers, and current-sponsors empty-state placeholders live at nanocollective.org/sponsor.
Angle: this is a "new program, just launched" announcement. The sponsor wall is intentionally empty at launch — that's the framing, not a thing to apologise for. Early sponsors set the tone for the rest.
Audiences across the four channels:
Across all four channels: name the four shipped projects (Nanocoder, Nanotune, get-md, json-up). Mention that all funds flow transparently through Open Source Collective. Link the canonical URL on every body.
Do not paraphrase the three principles. Do not use forbidden phrases ("Sovereign AI", "Trustless AI", etc.). Operational, understated voice throughout — match the brand-voice guide.
Additional context
Source of truth and grounding references:
The program is launching with an empty sponsor wall. Do not invent sponsors or imply momentum that doesn't exist. The honest framing is: "new program, here's the door, early sponsors lock in the rate."