Email headers and landing heroes, made by RUPA
RUPA makes the wide visuals for email and landing pages: an email header with the subject left and the right side clear for the headline, and a full bleed landing hero. The workspace's brand guidelines go with every render.
The presets RUPA works from
Email header
A wide ground, the subject left, the right side clear for the headline and a button.
1536 by 1024, wide, three plates, 5% safe margin
Landing hero
A full bleed ambient ground, with nothing important in the lower third.
1536 by 1024, wide, three plates, 4% safe margin
How RUPA runs it
- 01
Brief
A person writes the brief in her studio and picks Email header or Landing hero. Both fix a wide size and three plates.
- 02
Brand Lock
Brand Lock is on by default, so the workspace's brand guidelines go with the render and the bench shows the exact text sent. With the mark switched on, the workspace's own logo travels as an image to be placed, never redrawn; without it, the image model is told to draw no logo at all.
- 03
Reference
A reference image is optional. It comes from Nagent's shared set or the workspace's own uploads, with one of five intents: match the style, reproduce the layout, change the headline, localise it or remix it. Each intent says what it keeps and what it drops.
- 04
Attachments
Images that must appear, such as a product shot, are attached from the Knowledge Hub or the Asset Library. A render takes at most ten input images, the logo and the reference included.
- 05
Plan card
RUPA renders on her own where the workspace allows it. Otherwise she writes a plan card with the estimated spend, and nothing renders until a person approves it.
Waits for a personWaits for a person to approve the plan card, where the workspace has not let RUPA render on her own.
- 06
Render
Before anything is sent, her budget and a per-action cap for the batch are checked against the estimate. Over either, she refuses and names the limit. Then she renders the plates.
- 07
Brand check
A Brand check card follows the sheet. It reads the brief against the brand book's banned words and marks the rules a text check cannot confirm as "Needs your eye". It judges what RUPA was told, not what she made.
- 08
On the record
Every render that reaches the image model writes an audit row saying how it was authorised, and the plates are filed in the Asset Library, which is also the Assets tab of the Knowledge Hub.
What RUPA needs from you
Brand book
The brand guidelines Brand Lock sends with every render, and the banned words and manual rules the Brand check reads.
Logo
The workspace's own mark, sent as an image when Brand Lock and the mark are both on.
References
Nagent's shared reference set or the workspace's own uploads, for a look to borrow.
Attachments
Images from the Knowledge Hub or the Asset Library that must appear in the render.
What is governed
Brand Lock by default
The workspace's brand guidance goes with a render unless a person turns it off, and the bench shows the exact text sent.
A Brand check that reads the brief
It reads the brief for banned words and marks what text cannot show as "Needs your eye". It does not look at the plates, so a person does.
Budget before every render
Her budget and a per-action cap for one batch are checked before anything is sent, and a render over either is refused with the limit named.
An audit row per render
Every render that reaches the image model is written to the audit log with how it was authorised.
Questions about RUPA
What sizes are the email and landing visuals?
Email header and Landing hero both render three wide plates at 1536 by 1024. The email header keeps a 5% safe margin and the landing hero 4%.
Is there room for the headline and the button?
The Email header preset puts the subject on the left and keeps the right side clear for the headline, with a zone below it for the button. The Landing hero keeps anything important out of the lower third.
Will the visuals match our brand?
Brand Lock is on by default, so the brand book's guidelines go with every render and the bench shows the exact text sent. A reference from the workspace's own uploads can lend a look too.
Where do the images go?
To the Asset Library, which is also the Assets tab of the Knowledge Hub. Every render that reaches the image model also writes an audit row saying how it was authorised.
How much does RUPA cost?
RUPA works on the Content team. Nagent plans are Solo at $29.99 a month ($19.99 billed annually), Team at $299 a month ($199 billed annually) and Business at $1,499 a month ($999 billed annually). Enterprise is by quote. The pricing page shows which teams each plan includes.