Introduction
Metalyde is the operating system for a marketing agency — not a PM tool, not a CRM, not a PSA.
What is Metalyde
Metalyde is the OS for a marketing agency. It owns every operating surface an agency runs on: briefs, delivery, billing, reporting, AI execution. Not adjacent to it — the layer those things run on.
This is a deliberate category bet. "Marketing Agency OS" is language that exists in market but has not been claimed vertically. We are claiming it. Metalyde is not a project management tool you can use at an agency. It is not a CRM with a retainer view bolted on. It is not a PSA that happens to know what a brief is. It is purpose-built for how agencies operate, priced on agency economics, and opinionated about what profitability looks like in practice.
At this stage, Metalyde is a proof-of-concept. The positioning, design system, multi-tenant stack, and CI/CD pipeline were assembled in roughly 2-3 hours from our in-house SaaS boilerplate. The infrastructure is production-grade. The product features are what comes next.
The problem
The operator persona: a 2-10 person marketing agency running 50K-500K USD in client revenue. The owner wears every role. They are actively hostile to generic all-in-one bloat. They identify as operators, not users.
What that operator loses today:
| Pain | Measure |
|---|---|
| Scope creep they never bill | 57% of agencies lose 1,000-5,000 USD per month |
| Untracked time | 32,000 USD average annual loss |
| Bridging disconnected tools | 4-6 hours per week |
| Utilization below healthy range | ~60% actual vs 65-80% healthy |
These are not workflow inefficiencies. They are margin leaks with a dollar amount attached.
What is already shipped
| Capability | Status |
|---|---|
| Design system (Shadcn/UI + CVA + design tokens) | Built |
| Multi-tenant architecture (PostgreSQL RLS, tenant isolation) | Built |
| Authentication (Better Auth, sessions + OAuth) | Built |
| i18n (Paraglide JS, compile-time, type-safe) | Built |
| Email templates (dev preview on port 3001) | Built |
| CI/CD on Vercel (main -> production, staging -> preview) | Built |
| Quality gates (Biome, TypeScript strict, Vitest, Playwright) | Built |
| Product features | Next |
| Dashboards | Next |
Start here
- How We Built It — the ~2-3 hour build, and what it proves
- Product — the product, the brand, and the positioning artifacts
- Architecture & Stack — stack decisions and technical architecture
- Development Process — how we work day to day