---
title: "Understand Memo’s current product boundaries"
description: "Know exactly what Memo does and does not do today."
canonical: "https://memo.ly/docs/product-boundaries"
updated: "2026-07-31"
---

# Understand Memo’s current product boundaries

Know exactly what Memo does and does not do today.

**Who this is for:** Anyone evaluating Memo’s fit.

Memo is intentionally focused. Knowing the boundaries up front helps you decide where it fits in your stack.

## Supported today

- Branded email design and workspace template libraries
- Brand Kits and reusable blocks
- Editor-based composition with versioning and approvals
- Preflight quality checks and quality profiles
- HTML and plain-text export, and controlled internal test sends

## Not supported today

- Bulk campaign sending and scheduling
- Email automation and lifecycle journeys
- Audience segmentation and CRM
- Pamphlet workflow sync
- Email-client rendering certification or guaranteed inbox placement

> These boundaries are deliberate. Where useful, Memo hands off clean output to the platform you already use to send.

## Expected result

You can confidently describe Memo’s scope.

## Related
- [What is Memo?](https://memo.ly/docs/what-is-memo.md)
- [Compare Memo](https://memo.ly/compare)
- [Pricing](https://memo.ly/pricing)

[View HTML version](https://memo.ly/docs/product-boundaries) · [Documentation home](https://memo.ly/docs)