docs: add demand execution pack

.docs/demand-execution-pack.md

@@ -0,0 +1,102 @@
+# Demand Execution Pack
+
+## Objective
+
+Book 20 qualified conversations, recruit five active design partners, and obtain two explicit $29/workspace/month willingness-to-pay confirmations. Do not build Phase 2 until this gate is met.
+
+Use this preview in every CTA: <https://openapi-studio-tanstack-preview.pibin.workers.dev>
+
+## Prospect Criteria
+
+Contact only people who meet all four conditions:
+
+1. Work on a software team of roughly 2–30 engineers.
+2. Maintain an OpenAPI 3.0/3.1 file today.
+3. Participate in editing, reviewing, publishing, or consuming that contract.
+4. Can describe a recent workflow problem or introduce its owner.
+
+Prioritize founders, backend leads, platform engineers, API designers, and developer-experience leads. Exclude students, inactive projects, generic API enthusiasts, and teams seeking only free documentation hosting.
+
+Useful public signals: an OpenAPI file in a repository, API-documentation complaints, manual YAML review, generated-client drift, broken documentation, or recent API platform work.
+
+## Public Posts
+
+### X
+
+```text
+Small API teams: what is the most painful part of maintaining your OpenAPI file—editing, review, drift, or publishing?
+
+I’m testing a focused OpenAPI workspace and looking for five design partners. No checkout; honest pilot conversation first.
+
+https://openapi-studio-tanstack-preview.pibin.workers.dev
+```
+
+### Threads
+
+```text
+I’m speaking with small software teams that maintain OpenAPI 3.0/3.1 contracts.
+
+Where did your last API-spec change slow down: editing YAML, reviewing the diff, keeping implementation aligned, or publishing useful docs?
+
+I’m recruiting five design partners for a focused workspace. The proposed post-pilot price is $29/workspace/month. Details: https://openapi-studio-tanstack-preview.pibin.workers.dev
+```
+
+### LinkedIn
+
+```text
+I’m researching how small API teams maintain OpenAPI contracts in practice.
+
+I want to understand the last real change your team made: where review stalled, what drifted, and which workaround you used. I’m recruiting five design partners for OpenAPI Studio. This is an early pilot—not a finished product or self-serve signup. The current post-pilot hypothesis is $29 per workspace per month.
+
+If you actively maintain OpenAPI 3.0/3.1, I’d value a 20-minute workflow conversation: https://openapi-studio-tanstack-preview.pibin.workers.dev
+```
+
+### Facebook Groups
+
+```text
+Research request—not a promotion: I’m looking for small teams that actively maintain an OpenAPI 3.0/3.1 document.
+
+What happened during your last spec change? I’m especially interested in editing, review, implementation drift, and publishing problems. I’m recruiting five design partners for an early OpenAPI workspace and will be transparent about its pilot status and proposed $29/workspace/month price.
+
+Details: https://openapi-studio-tanstack-preview.pibin.workers.dev
+```
+
+Follow each group’s rules. Do not post where research or product links are prohibited.
+
+## Direct Outreach
+
+Initial message:
+
+```text
+Hi [first name]—I noticed [specific OpenAPI signal]. I’m researching how small teams handle real spec changes. Could I ask how your last change moved from edit to review and publish? I’m not asking you to buy anything; I’m looking for a concrete workflow conversation.
+```
+
+If they confirm the problem:
+
+```text
+That is exactly the workflow I’m testing. I’m recruiting five design partners for an early OpenAPI workspace. Would a 20-minute walkthrough next week be reasonable? Pilot details: https://openapi-studio-tanstack-preview.pibin.workers.dev
+```
+
+One follow-up after four business days:
+
+```text
+Quick follow-up, then I’ll close the loop: is OpenAPI maintenance an active problem for your team, or not a priority now? Either answer is useful.
+```
+
+No further follow-up without a reply.
+
+## Daily Operating Loop
+
+- Identify 10 qualified prospects from public evidence.
+- Send 10 personalized messages; never mass-send identical DMs.
+- Publish at most one channel-appropriate post.
+- Reply to interested prospects the same day.
+- Record private notes outside Git; update aggregate counts only in `design-partner-operating-ledger.md`.
+- After five conversations, report repeated problems and objections before changing copy.
+
+## Stop Rules
+
+- After 50 qualified messages with fewer than five replies: rewrite the opening message.
+- After 10 conversations without one repeated urgent problem: narrow or change the buyer.
+- After 20 conversations without two $29 confirmations: revise the offer or price before building more.
+- Never interpret likes, impressions, or unqualified signups as demand.