YC growth framework - identify One Metric That Matters, commit to 7% weekly growth, install public accountability. Focus-forcing system for early-stage startups.
Applies YC's three-pillar growth system when users discuss metrics or accountability. Identifies One Metric That Matters, sets 7% weekly growth targets, and installs public accountability mechanisms.
/plugin marketplace add majesticlabs-dev/majestic-marketplace/plugin install majestic-marketing@majestic-marketplaceThis skill inherits all available tools. When active, it can use any tool Claude has access to.
Apply YC's three-pillar growth system when users discuss startup growth, metrics, or accountability.
Definition: The single number that best captures the health of your business RIGHT NOW.
Selection Criteria:
OMTM by Stage:
| Stage | Typical OMTM | Why |
|---|---|---|
| Pre-launch | Waitlist signups | Demand validation |
| Pre-revenue | Active users | Engagement before monetization |
| Early revenue | Weekly revenue | Direct business health |
| Product-market fit | Net revenue retention | Sustainable growth signal |
| Growth | MRR growth rate | Scalability proof |
OMTM by Business Type:
| Business | OMTM | NOT This |
|---|---|---|
| SaaS | Weekly active users OR MRR | Total signups |
| Marketplace | Weekly GMV | Registered users |
| E-commerce | Weekly revenue | Traffic |
| Content | Weekly engaged readers | Pageviews |
| B2B Services | Pipeline value | Proposals sent |
OMTM Anti-Patterns:
The Math:
7% weekly = 1.07^52 = 33x annual growth
5% weekly = 1.05^52 = 12x annual growth
10% weekly = 1.10^52 = 142x annual growth
Why 7%:
Weekly Growth Calculation:
Growth Rate = (This Week - Last Week) / Last Week × 100
Example:
Last week: 100 users
This week: 107 users
Growth: (107-100)/100 = 7%
Tracking Template:
| Week | OMTM Value | Growth % | Cumulative | Notes |
|---|---|---|---|---|
| 1 | 100 | - | 100 | Baseline |
| 2 | 107 | 7% | 107 | [What drove it] |
| 3 | 114 | 6.5% | 114 | [What drove it] |
When You Miss 7%:
Why Public:
Accountability Mechanisms:
| Method | Effort | Pressure | Audience |
|---|---|---|---|
| Twitter/X updates | Low | Medium | Public |
| Investor updates | Medium | High | Investors |
| Mastermind group | Medium | High | Peers |
| Public dashboard | High | Very High | Everyone |
| Blog posts | High | Medium | Followers |
Weekly Update Template:
Week [X] Update:
OMTM: [Metric Name]
Last Week: [Value]
This Week: [Value]
Growth: [X]%
What worked:
- [Specific action → result]
What didn't:
- [Specific action → result]
Next week focus:
- [Specific action with expected impact]
Accountability Partner Selection:
| User Says | Red Flag | Response |
|---|---|---|
| "We track DAU, MAU, revenue, NPS..." | No focus | Help identify THE one |
| "We're growing 2% monthly" | Too slow | Reframe to weekly, increase ambition |
| "I review metrics quarterly" | Too infrequent | Suggest weekly rhythm |
| "Nobody knows our numbers" | No accountability | Suggest public sharing |
"7% weekly is unrealistic" → "What's your current weekly growth? Even 5% = 12x annual. The number matters less than the weekly discipline."
"We can't share numbers publicly" → "Share with one accountability partner. The point is external pressure, not public disclosure."
"Our business doesn't work that way" → "Every business has a leading indicator. What number, if it went up, would guarantee future success?"
growth-audit for comprehensive assessmentfirst-principles to identify true OMTMfounder-mode for execution disciplineidea-validator for post-validation trackingApplies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.
Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.
Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.