Email Studio
- ROLE
- Builder
- SCOPE
- AI Workflow
- Product
- INDUSTRY
- Marketing Ops
- Financial Services
- TYPE
- Digital Product
Written Brief to Working Email
Building an email meant writing a brief in Word, handing it to an outside vendor, and working through rounds of revisions. I built Email Studio so channel marketers could create and review emails directly. Shared components give them control over content while keeping the design consistent. Average design-to-delivery speed increased 40%.
- DESIGN TO DELIVERY
- 5 days → 2 days
- SUPPORTED CHANNELS
- Advisor Forum, In Person Events, Webcasts, Product Launches, Thought Leadership, and Subscriptions.
- WORKFLOW
- Drag and drop editor
- BUILT WITH
- GitHub Copilot CLI, Angular
Components at Scale
New components still needed to ship on time, even with a smaller build team. I built an inspection view that puts the actual code, spacing, typography, colors, and assets in one place. Designers and developers can check the same details as the system grows. The team maintained its previous component delivery timeline despite reduced headcount.
- DELIVERY
- One new component per week
- TEAM CAPACITY
- Reduced from 4 to 1
- (Components ship at previous pace)
- INSPECTION
- Bundled code, design variables, and assets
- DESIGN DECISION
- Provide shared design reference for implementation
Type to Build
What if making an email started with saying what you need? I built a conversational prototype around the drag and drop editor. A brief becomes a live email, then follow-up requests add event details, funds, and legal copy. The component system holds the design rules while the marketer reviews and refines the result.
- STATUS
- Beta release
- OPPORTUNITY
- Draft emails, websites, and social through conversations
- RISK
- Token cost associated with creation and refinement
- TESTING
- Determine user preference and effectiveness







