Email header & content blocks
Create reusable visual sections for a client’s existing email platform.
Design files and agreed exports. Implementation is a separate scope.
Once the individual request becomes active. Content readiness and feedback can affect timing.
What you can request
Create reusable visual sections for a client’s existing email platform.
Typical handoff
An approved email header & content blocks direction, refined for the agreed use and supplied in the formats we confirm in the brief. Editable source files, alternate sizes, or additional versions can be included when agreed at the start.
What to bring
Supply the audience, offer, approved copy and claims, channel specifications, and brand assets. This offering covers creative design; campaign management, publishing, media spend, and performance outcomes are separate.
How it fits the partnership
Request this on its own or as a stage within a larger module. We confirm scope and timing, then work through one active request at a time. Related formats and variations are prioritized in the queue rather than assumed to be a single small task.
Typical specifications
Files & handoff. Figma layout with JPG/PNG image assets. A platform template or coded HTML email is supplied only when separately included.
Setup. Responsive design direction for the agreed email platform, content blocks, and mobile layout.
Limits. A design file is not a sent campaign. Automation setup, subscriber management, delivery testing, and HTML implementation are separate scope.
Ready to start
0 of 4 reviewedUse this to prepare your request. We confirm scope and readiness together.
Before this becomes active
Can follow at the agreed stage
- Refinements after the first direction is reviewed.
- Inputs for later stages, only when we agree they are not needed yet.
Personal checklist only. Ticks are not saved or sent, and do not start the delivery estimate.
Copying a template does not submit a request.