Blacksky activation playbook v1.
The operating doc we ship against. Weekly posting cadence across five platforms, reusable Monday-through-Sunday rituals, and the exact four-touch founder-intro verbiage — copy-paste-ready from this page.
Source of truth for the team and for future teammates. Updates land in src/lib/business/playbook.ts and the deploy ships the doc.
#Blacksky
Where founders and early backers are already talking.
“Blacksky is the room where the founders we're building for are already talking about what they wish existed. We listen there first — then we ship.”
Weekly cadence
Five platforms, one week, one rhythm.
Each row is a slot we commit to before the week starts. Volatility is in the reply threads, never in the schedule.
| Platform | Days | Cadence | Angle |
|---|---|---|---|
| X | Tue + Fri | 2x / week | Short, punchy narrative — what we shipped, what we heard. |
| Wed | 1x / week | Long-form founder voice — the why behind the work. | |
| Bluesky | Mon + Thu + Sun | 3x / week | Live-in-the-room listening — quotes founders, asks questions. |
| Wed + Sat | 2x / week | Visual proof — screenshots, carousels, founder quotes. | |
| Fri | 1x / week | Plain-spoken update — clearest place for the longer backstory. |
Rituals
One ritual per weekday. Copy the body, ship the post.
Each card is a copy-paste template. Fill the brackets, post it, and we'll see it land in #Blacksky.
Founder note
Open the week in a public, founder-voice voice. No metrics, just the lens.
Hey everyone — opening the week with a short note. This week we're shipping [one thing]. It came out of [one conversation] in #Blacksky. If you've been wondering why we built it, that's the answer. Reply if it's wrong. Reply harder if it's right. We ship what we hear. — The NestVest team
Education drop
Teach one concept the audience asked about — never gated, never jargon.
Wednesday education drop: [one concept]. What it is: - 1 line of plain English. - Why it's the term a first-time allocator hears first. - The one mistake to avoid. - One NestVest surface that touches it (or "not yet — tell us if it should"). We refuse to gate education. If something here is wrong, the comments are open and we read every one.
Trade-floor screenshot
Show real product use — paper or live — to anchor trust in the work.
Friday trade-floor screenshot. [one screenshot] — this is what a paper-trade rehearsal looks like in NestVest Pro. $100 of virtual dollars, the same 7 exchanges, no commission, no real money on the line. If you've been hesitating to place a trade because you weren't sure how it would feel — paper mode removes that worry. → Try Pro for $5 → nestvest.app/pricing
Community recap
Close the week by naming what we heard in #Blacksky and what we'll do about it.
Sunday #Blacksky recap. This week in the room: - [one quote or thread] — [what we heard]. - [one quote or thread] — [what we heard]. - [one quiet DM] — [what we heard]. What we're doing about it: - [one ship or change]. - [one question we're still sitting with]. Reply if it's wrong. We ship what we hear.
Founder intro sequence
Four touches, one founder, the exact verbiage.
The sequence we run the first time we meet a founder who's sharing the kind of feedback that should change what we ship. Tap a touchpoint to expand the script. The copy is plain text on purpose — select it, copy it, send it.
1The first DMDay 0 — within 24 hours of the public conversationBluesky DM
Hey [first name] — I'm one of the NestVest founders, and I caught your [post/comment/DM] in [#Blacksky | elsewhere] this week. We aren't pitching anything. We just wanted to say your framing of [their one idea] is the kind of thing we keep coming back to when we're deciding what to ship. A few questions for you, only if you have a minute: - What's the first thing you'd want a tool like NestVest to do for someone in your shoes? - What's the first thing it should refuse to do? No wrong answer. We read everything here. — [founder name] NestVest
2The public replyDay 2 — land on a thread they're already inX reply (or Bluesky reply)
[quote their message verbatim] This is exactly the question we keep coming back to at NestVest. The honest version of where we are today: [one sentence — what we already do about it, plainly]. The honest version of where we're not: [one sentence — what we haven't shipped yet, no spin]. If you have a second, the thing that would change how we build next is: [one open question]
3The founder voice inviteDay 5 — if touch 1 + 2 got a responseLinkedIn message
Hey [first name] — following up on the thread from earlier this week. Quick context on us: NestVest is a small team building long-horizon investing tools alongside the Black founders, investors, and first-time allocators we want in the room. We're not at scale yet — we're at the stage where one conversation can change the next thing we ship. Two reasons I'm writing: 1. We open-sourced our reasons here: [link to /community/mission] — short version: we ship what we hear and we explain what we ship. 2. We're putting a small group of founder-voice advisors in front of a 30-minute conversation about [one specific topic from their thread] — no slides, no pitch, just the conversation. If a 30-min slot in the next two weeks is interesting, here's the calendar: [link]. If not, reply with the one thing you'd want us to hear and we'll log it the same way. — [founder name] NestVest
4The thank-you that closes the loopDay 10 — after they ship / reply / drop offSame channel as touch 1 (Bluesky DM preferred)
Hey [first name] — short thank-you, no ask. Two things we shipped this month that started with [their one idea/sentence]: - [ship 1, with link]. - [ship 2, with link]. You don't owe us anything, and we're not following up with a pitch. If you ever want to pick the thread back up, the door is open — reply here and it lands in my inbox. — [founder name] NestVest
Maintaining the playbook
One source of truth: src/lib/business/playbook.ts.
Cadence, rituals, and the four-touch verbiage all live in a single compile-time file. Edit a row, open a PR, and the next deploy serves the new doc. No database, no migration, no staging pass required — the playbook is the source, the page is the rendered artifact.