メニュー
Strategy for getting Your Project's first paying customer. Use when discussing revenue, pricing, monetization, or what to sell. Based on Minimalist Entrepreneur principles adapted for our stage.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
Translate git history and orchestrator logs into authentic social content. Use when turning recent technical work into tweets, Dev.to posts, or changelog entries without manual summarisation.
Red team the staging environment with injection attacks, rate limit probes, and auth bypass attempts. Use before major releases or when adding new user-input surfaces.
Deploy Your Project to production safely. Use before any deployment, after code changes, or when asked to push to prod.
Facilitate a structured CONVERSATIONAL meeting between department agents via claude-peers — named phases (Diverge, Clarify, Challenge, Build, Stress Test, Converge, Decide) with state machine navigation. Agents push back on each other and build on each other's ideas. Minimum path: Diverge → Challenge → Build → Stress Test. Early exit only after Stress Test. NOT for simple task dispatch (use orchestra-management). NOT for solo research (use rd-architect).
Manage the 6-department orchestra via claude-peers. Use when dispatching tasks, coordinating departments, reviewing results, or shaping department behavior.
Write emails, social posts, and newsletter submissions for Your Project. Use when creating maker outreach, blog content, social media posts, or press pitches.
SOC 職業分類に基づく
| name | first-revenue |
| description | Strategy for getting Your Project's first paying customer. Use when discussing revenue, pricing, monetization, or what to sell. Based on Minimalist Entrepreneur principles adapted for our stage. |
| metadata | {"version":"1.0.0","author":"Master Agent","category":"strategy","updated":"2026-03-30T00:00:00.000Z"} |
You are advising on Your Project's path to first revenue. The product exists (3,100+ tools, MCP server, migration intelligence). The challenge is going from 0 to 1 paying customer.
Check current state:
Skip the launch. Focus on selling. Every seemingly overnight success is built on hard work. Sell one by one, learn from each interaction, build momentum.
For Your Project this means: don't build pricing pages and payment flows. Have ONE conversation with ONE maker about what they'd pay for. Then build that.
These people engaged with us. They're warmest.
They showed interest but didn't claim.
The 24 emails we sent. More batches if earlier ones show signal.
"Your tool appears first when agents search for {category}"
"Here's what repos are migrating from your competitor to you (and vice versa)"
"See which agents recommend you, what queries surface you, daily trends"
"Programmatic access to migration data, compatibility pairs, competitive intel"
No paying customers yet. Focus on getting first conversation, not first payment.
A maker has claimed their tool. Turn that into a pricing conversation.
Someone expressed willingness to pay. Close it.
Talk to a maker. Not email them a claim link — TALK to them. When someone claims their tool, reply personally:
Hey, thanks for claiming {tool}! I'm Pat, one of the founders. Quick question —
what would be most useful to you about knowing how AI agents recommend your tool?
We're figuring out what's worth building next.
That conversation tells us what to charge for. Everything else is guessing.
| Situation | Deliverable |
|---|---|
| Pre-revenue planning | Priority list: who to talk to first |
| Maker claimed | Personal reply email draft |
| Pricing conversation | Proposed price point with reasoning |
| First payment | Stripe setup checklist |