메뉴
Business Model and Architecture Design methodology for aligning technical architecture with business model sustainability and scalability
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Expert in Three.js, 3D graphics, and interactive 3D visualizations
Implement accessibility (a11y) best practices to make applications usable by everyone. Use when building UIs, conducting accessibility audits, or ensuring WCAG compliance. Covers screen readers, keyboard navigation, ARIA attributes, and inclusive design patterns.
Expert in web animations, transitions, and motion design using Framer Motion and CSS
Design REST and GraphQL APIs. Use when creating backend APIs, defining API contracts, or integrating third-party services. Covers endpoint design, authentication, versioning, documentation, and best practices.
Build reliable third-party API integrations including OAuth, webhooks, rate limiting, error handling, and data sync. Use when integrating with external services (Slack, Stripe, Gmail, etc.), building API connections, handling webhooks, or implementing OAuth flows.
Master Archon MCP for strategic project management, task tracking, and knowledge base operations. The strategic layer (WHAT/WHEN) that coordinates with Skills (HOW). Use when managing projects, tracking tasks, querying knowledge bases, or implementing the Archon+Skills two-layer architecture.
| name | BMAD Method |
| description | Business Model and Architecture Design methodology for aligning technical architecture with business model sustainability and scalability |
| version | 1.0.0 |
| category | business-architecture |
| triggers | ["bmad-method","bmad method","business model architecture","business architecture design","align architecture with business model"] |
| dependencies | {"required_mcps":[],"required_tools":[],"required_integrations":[]} |
The BMAD Method bridges business strategy and technical architecture. It ensures your technical decisions support long-term business sustainability, not just immediate feature delivery.
Core Insight: Your architecture IS your business model in code form.
Use BMAD when:
Understand the Revenue Engine:
Key Questions:
Map Business Model to Architecture:
Subscription SaaS (B2B):
Usage-Based (API/Platform):
Marketplace/Network:
Freemium/Consumer:
Infrastructure Cost Analysis:
Calculate Unit Economics:
Example (SaaS):
Target: $20/user/month subscription
Acceptable costs:
- Infrastructure: <$2/user/month (10% COGS)
- Support: <$4/user/month (20%)
- Sales/Marketing: <$60 CAC (3-month payback)
Architecture decisions:
- Shared infrastructure (not dedicated per customer)
- Self-service onboarding (reduce sales cost)
- In-app support tools (reduce support tickets)
- Efficient database design (reduce storage costs)
Design for Growth Stages:
Stage 1: MVP (0-100 users)
Stage 2: Growth (100-10k users)
Stage 3: Scale (10k-1M users)
Stage 4: Enterprise (1M+ users)
Evaluate Core vs. Context:
Build when:
Buy/Use SaaS when:
Examples:
| Capability | Decision | Rationale |
|---|---|---|
| Payment processing | Buy (Stripe) | Commodity, compliance heavy |
| Core algorithm | Build | Competitive moat |
| Email delivery | Buy (SendGrid) | Commodity infrastructure |
| Analytics | Buy (Mixpanel) | Faster than building |
| Custom AI model | Build | Unique to your data |
| Auth infrastructure | Buy (Auth0) initially | Build later at scale |
Capture Non-Negotiable Requirements:
Regulatory/Compliance:
Business Commitments:
Financial Constraints:
Business Model:
Architecture Decisions:
Build vs. Buy:
Outcome: $2.50/customer/month COGS, 83% margin
Business Model:
Architecture Decisions:
Build vs. Buy:
Outcome: $0.0025/call COGS, 75% margin
Business Model:
Architecture Decisions:
Build vs. Buy:
Outcome: Scales to 100k users at <$35k/month
Don't choose React/Node/AWS first. Choose after understanding:
Build for where you are now, but don't lock yourself out of next stage.
Bad: Hard-coded single-tenant that can't scale Good: Multi-tenant from day 1 (even at 10 users)
If you can't calculate cost per user, you can't predict profitability.
Track monthly:
If feature doesn't drive revenue/retention, defer expensive architecture.
Example: Don't build multi-region before proving PMF.
Know when you'll need to refactor:
Building for 1M users when you have 100 wastes time and money.
Antipattern: Microservices + Kubernetes at MVP stage Better: Monolith on Railway/Heroku, scale later
Not building multi-tenancy in B2B SaaS kills margins at scale.
Antipattern: Dedicated database per customer Better: Multi-tenant architecture from day 1
Not tracking cost per user means surprises at scale.
Antipattern: "We'll figure out costs later" Better: Model costs before building
Commodities don't need custom solutions.
Antipattern: Build custom auth, payments, email Better: Buy Stripe, Auth0, SendGrid; build differentiation
Spending on features that don't drive business value.
Antipattern: Perfect CI/CD before proving PMF Better: Ship fast, optimize later
When using BMAD Method, produce:
Business Model Canvas
Architecture Alignment Document
Build vs. Buy Decision Matrix
Architectural Roadmap
You've successfully applied BMAD when:
Remember: The best architecture is the one that makes your business model sustainable and profitable.