Skip to content
NagentNagent
Log inSign upHire your AI Growth Team
NagentNagent
Log inSign up

Content · Team lead · reports to CREA

Make images that match your brand. Your brand guidelines go with every one.

Describe the image you need and pick a format. RUPA makes a set of images with your brand guidelines attached, then checks your request against your brand book. You can see exactly what was sent.

AI image tools know nothing about your brand. You paste your guidelines in again every time, and the results still drift.

RUPA sends your brand guidelines with every image by default, and shows you the exact text that went with it.

a typical day

What a day with RUPA looks like Real screens from the product, as it ships today. Scroll through the day.

  1. 09:2001 of 04

    Makes images in the format you need

    Each format sets the size and how many images you get. Brand Lock sends your guidelines with the request, and your logo goes as an image to place, not redraw.

  2. 09:3402 of 04

    Checks your request against your brand book

    A Brand check follows every set. It scans the request for banned words, and flags the rules only a person can judge by looking.

  3. 11:0503 of 04

    Makes many versions at once

    One image template, many variations. You see three previews and a quote first, and a person decides before the rest are made.

  4. 15:3004 of 04

    Saves every image where your team can find it

    Every saved image goes to the Asset Library, the same place as the Assets tab in the Knowledge Hub. You can search by what each image shows.

working together

How a launch request becomes images you can use RUPA makes images when the team asks, and spends only what a person can see. Here is one launch request moving through the Content team.

  1. 01your peopleErica → CREAWe need launch images for the oak tote this week.
  2. 02ai chief of staffCREA → RUPAPlease make four paid social images with our brand guidelines, showing the tote exactly as it is.
  3. 03team leadRUPA → EricaHere is the plan and the cost estimate. Nothing is made until you approve.
  4. 04your peopleErica → RUPAApproved, go ahead.
  5. 05team leadRUPA → CREAFour images saved in the Asset Library. Two brand rules need a person to look.
  6. 06your peopleErica → RUPAMake the ad set from image two.
  7. 07team leadRUPA → EricaSquare, tall and wide versions saved next to it.

step by step

See every step RUPA takes Each job keeps a plain record: what it looked at, what it did, what it checked, and where it stopped to ask a person.

  1. 01
    Read the request

    The format, the reference images and what must appear.

  2. 02
    Attach your brand

    Brand Lock is on by default. Nobody has to switch it on.

  3. 03
    Check the budget

    Before anything is sent, however much she is trusted.

  4. 04
    Wait, or go ahead

    Approval for each request, or approval in advance, as your team chose.

  5. 05
    Make the images

    Images at the format’s size, each recorded in the audit log.

  6. 06
    Check and save

    The request checked against the brand book. The images saved to the library.

under the hood

What RUPA works with What it reads, what it knows how to do, the checks that watch it, and the approvals every action passes before anything leaves.

one shared room

Your team and RUPA work in the same room No side chats. RUPA works in the Content team room next to your people and the agents it hands work to, and every message is kept with who said it.

where it fits

Where RUPA sits in your growth team N leads the whole team. Three chiefs of staff run Marketing, Sales and Content. Your people set the direction and approve the work.

Takes work from

  • CREAImage requests from the Content team chat, passed on with who has them.
  • Your peopleThe brand book, reference images, product photos and every approval.
  • HOOKA production brief that a person sends her from the ad creative team.
  • MOXAImages for a social post, under her own checks and spending limits.

Hands work to

  • Your peopleEvery image, saved in the Asset Library.
  • HOOKCreative strategy leadImages for HOOK’s GATE to check.
  • MOXASocial media leadImages attached to the post that asked for them.
  • CREAAI Content Chief of StaffImages made from the team chat, with an "Open the image" link in the thread.

connections

The tools RUPA connects to It reads what is already in your workspace. Anything it sends goes out through your own accounts, never a shared one.

skills and tools

What RUPA knows how to do Connecting a tool turns nothing on. A person switches on each action, one at a time.

Skills

  • 01Check against brand rulesChecks the request against your brand book: banned words, and the rules only a person can confirm.
  • 02Build the ad setOne image reworked as a square, a tall and a wide version.
  • 03Restyle to a referenceKeeps the subject and borrows the light, colours and texture from a reference you pick.
  • 04Relight the subjectChanges the direction and softness of the light without touching the product.
  • 05Cut out the subjectA clean transparent background around the subject, with the shadow removed.

What it reads

  1. 01Brand guidelines Your own Brand Lock guidance, sent with every request while Brand Lock is on.
  2. 02Logo Your own logo, sent as an image when Brand Lock and the logo are both on.
  3. 03Banned words and manual rules From your brand book, used by the Brand check.
  4. 04References Nagent's shared reference images and your own uploads, for a look to borrow.
  5. 05Attachments Images from the Knowledge Hub or the Asset Library that must appear in the result.

Every tool Nagent connects to

by industry

How teams like yours use RUPA

  • 01Ecommerce

    Sale banners and ad versions from your approved product photos, with the product shown as it is, for the people who own the offer to approve.

  • 02Fashion

    A shot list for a new drop, each shot made from the product photo and in the image style your brand book sets.

  • 03FMCG

    Images for retail listings, made in your brand style and saved for the brand manager to check.

you stay in control

You approve anything that matters RUPA starts by asking first. It only does more on its own when a person decides it has earned it, and some actions always wait for a person.

Always waits for a person

  • Every request, if your team chose to approve each one
  • An image asked for in a team chat, until she is trusted to go ahead alone
  • Starting a batch, with its quote on the card
  • A batch that goes past its quote, which only a person can continue
  1. 01A person decides when she gets more freedom. Images made from a team chat are logged one by one. After 30 days and 25 approvals with a strong record, Nagent suggests letting her make them without asking. A person accepts or declines. In her studio, a person sets how much she may do alone.
  2. 02Budgets are checked first. Her daily and monthly budget, the spending limit for one batch and your workspace’s own limits are all checked before anything is sent.
  3. 03Brand Lock is on by default. Your guidelines go with every request while Brand Lock is on, and the studio shows the exact text sent. If there is no logo, the image model is told not to draw one.
  4. 04Everything is on record. Every request sent to the image model is recorded in the audit log, with how it was approved. An image asked for in a team chat is also logged with how it ended.

Questions about RUPA

What is RUPA?

RUPA is Nagent's image studio lead, an AI teammate on the Content team who reports to CREA. You describe the image and pick a format if needed. RUPA makes a set of images with your brand guidelines attached, then checks your request against your brand book.

Does RUPA know our brand?

Only what your brand book says. Brand Lock, which is on by default, sends it with every request, and the studio shows the exact text sent. An image model knows nothing about your brand unless it is told every time.

Will RUPA render without asking?

Your team decides. Before she is trusted, she writes a plan and stops. If you approve each request, a person sees the cost estimate and clicks "Approve and run". If you approve in advance, she goes ahead and logs every image. Budgets are checked first either way.

How does RUPA keep image spend in check?

Before anything is sent, RUPA checks her daily and monthly budget, the spending limit for one batch and your workspace's own limits. If a request goes over a limit, she stops and tells you which one. If you approve each request, you see the estimate first. It goes up with HD quality, more images and more input images.

Does the Brand check look at the image?

No. It scans your request for banned words, and marks the rules a text check cannot judge as "Needs your eye" instead of passing them. Look at the images yourself before you use them.

Where do RUPA's images go?

To the Asset Library, which is also the Assets tab of the Knowledge Hub. Each image offers Ad set, Restyle, Relight and Cut out, and a Brand check follows each set. One request can use up to ten input images, such as a product shot or a logo that must appear.

Put RUPA on your Content team.

Your brand guidelines go with every image. Tell her what you need, see exactly what she was sent, and keep the images worth keeping.

See it on your own work.

Start free and hire your first AI team, or book a demo and we will walk you through it.