- Regulated enterprises with strict vendor risk management
- If procurement requires SOC 2 Type II, ISO 27001 documentation, data residency commitments, or detailed security whitepapers, Postcards may not meet vendor due-diligence requirements based on publicly available materials.
- SaaS companies needing an embedded white-label editor
- For an embeddable editor inside a customer’s product, vendors that explicitly offer SDKs and OEM editor integrations may be a better structural fit.
- Teams that cannot tolerate any HTML-level fixes
- Teams without anyone capable of performing HTML-level adjustments should note there are reported cases where exported templates required manual fixes for certain clients.
- High-volume email operations constrained by export limits and credit models
- Organizations that require frequent exports and heavy AI credit consumption should model expected volumes against export limits and credit pricing to avoid unexpected costs.
- Email client CSS limitations (acknowledged)
- Background images are poorly supported by some clients (including some Outlook clients). This is a general constraint for HTML email but affects perceived consistency when users expect identical rendering across clients.
- Export and sending constraints
- Some send-from-inbox workflows require additional tooling beyond the builder; vendor materials reference plugins/extensions for inserting HTML into Gmail/Outlook.
- Rendering / code edge cases (from reviews)
- Reported instances of Gmail-specific adjustments required in exported code have been noted by reviewers.
- Roadmap / future features
- No formal public roadmap was located in the accessible sources; buyers should request roadmap details if future feature timing is procurement-critical.