Marketing automation is the execution of content or communication steps by the system according to certain conditions. Purchasing a platform does not complete the message, user experience and visual production. As Selçuk Aker, I recommend preparing a brief on the design side that explains which component will appear, with what content, and in what situation.
Start with the use case instead of the platform name
When examining Insider or similar solutions, first describe the work to be done. Providing product information, explaining the registration process, and communicating again require different content. Current features, license and integration limits of the platform should be verified with the provider; This article is not a product catalog or vendor partnership statement.
What columns should be in the Brief table?
| Area | Question to be answered |
|---|---|
| Purpose | What task do we make easier for the user? |
| Trigger | What event initiates this content? |
| Channel | Web space, email or notification? |
| Source | Where do the text, product images and data come from? |
| Alternative | What will be shown if data or image is missing? |
| Responsible | Who will approve the content and publish it? |
For example, in the product reminder e-mail, the product name may be long, there may be no image or the price may have changed. A template designed only around ideal sample data can break in these situations. Set actual content boundaries at the beginning.
Cross-channel design does not mean duplicating the same image
Email, web banner, and phone notification differ in scope, reading time, and interactivity. While brand color and message are maintained, information density may vary. Instead of hiding critical conditions in small print, move them to the target page with the correct link. Don't automatically copy the notification title from a banner slogan.
File delivery and implementation responsibility
Figma component, image export, text field boundaries, and missing data status can be included in the design delivery. Account setup, integration, data transfer and publishing automation are separate expertise and responsibilities. Using representative data for testing reduces the need to spread real people's information across design files.
My combination of web, social media and other brand materials for Pedaş is an experience of visual integrity; It is not a claim that we use a particular automation platform. Check out email design, interface scenarios by behavior, and my portfolio.
Frequently asked questions
Does an automation platform eliminate the need for a designer?
Ready-made templates can provide a start. Brand fit, real content, accessibility and different situations should again be evaluated.
Can design be done without choosing a platform?
Needs and flow studies can be done. The technical limits of the chosen platform should be known when preparing the final components.
Is Insider installation included in this service?
This page describes the design preparation. License, account setup, integration and operational delivery should also be defined by competent teams.
