Studio B Platform Architecture
Studio B operates as a services company with SaaS offerings — consulting engagements produce deployable software products that generate recurring revenue.
Core Stack
┌──────────────────────────────────────────────────────────────────┐
│ Claude Code + MCP Servers (150+ tools) │
│ Custom: Acumatica(26) DevOps(22) GoDaddy(15) Zoom(65) │
│ Microsoft(22) │
│ Native: HubSpot, Slack, Gmail, Chrome, Preview │
├──────────────────────────────────────────────────────────────────┤
│ Railway (Agents, Cron, BullMQ) │
├──────────┬──────────┬───────────┬──────────┬─────────┬──────────┤
│ Acumatica│ Orderful │ HubSpot │ Shopify │ Twilio │ M365 │
│ ERP │ EDI │ CRM+Call │ E-comm │ VoIP │ Mail/Cal │
├──────────┴──────────┴───────────┴──────────┴─────────┴──────────┤
│ GitHub (IaC, CI/CD, Config-as-Code) │
└──────────────────────────────────────────────────────────────────┘
Services (10 Active)
| Service | Purpose | Stack |
|---|---|---|
| webhook-router | Slack intake, error routing, Acumatica-HubSpot sync | Fastify + BullMQ + Redis |
| business-dashboard | Ops dashboard, health checker, sales intelligence | Express + EJS |
| support-agent | AI customer support | Claude + Qdrant KB |
| provisioning-agent | Employee onboarding/offboarding | Fastify + multi-system |
| devops-mcp | GitHub + Railway API | MCP SDK + StreamableHTTP |
| acumatica-mcp | Acumatica ERP API | MCP SDK + StreamableHTTP |
| note-intelligence | AI note classification | Claude Sonnet + pgvector |
| compliance-engine | Requirement enforcement | BullMQ workers |
| integration-tester | 10 test paths, weekly canary | Scheduled tests |
| PostgreSQL / Redis / Qdrant | Data stores | Managed on Railway |
Key Principles
- Config-as-code — Every system configuration versioned in GitHub
- CI/CD everything — No manual promotions; every change validated through pipeline
- Discovery-first — Field mappings extracted from live systems, not hardcoded
- Direct TypeScript — No visual workflow builders; Railway cron + BullMQ for orchestration
- MCP API first, browser last — API tools for all operations; browser only for UI validation
- Build for reuse — Everything templated for multi-tenant deployment
MCP Server Architecture
All custom MCP servers follow the same pattern:
- Runtime: TypeScript + Fastify 5
- Protocol: MCP SDK with StreamableHTTP transport at
/mcp - Auth: Token-based via query parameter (migration to Authorization header planned)
- Deploy: Railway with GitHub auto-deploy on push to main
Each server creates a new McpServer instance per session (SDK limitation: one transport per server).
Revenue Model
| Stream | Type | Margin |
|---|---|---|
| Consulting | Project-based | 75-85% |
| SaaS Products (AcuOps) | MRR | 85-95% |
| Managed IT | Retainer | 75-85% |
| Platform Licensing | MRR | 85-95% |
Infrastructure cost per client: $50-100/mo on Railway.