Our agents
Every role.
Every handoff.
Meet the seven agents behind a production request: what each one needs, what it produces and how the work moves forward.
From your direction to your deliverables
01
Intake
02
Production
03
QA
04
Delivery
The request goes to the production agent it needs. QA returns any corrections to that agent before the checked work reaches your project channel.
01
Communication & classification
Intake
Available
A clear brief before production.
Intake receives requests from your designers, identifies what needs to be produced and routes the work to the right production agent. If information is missing, it asks for clarification.
Starts with
Key artwork, design direction and delivery requirements.
Produces
A classified request, ready for the right agent.
A typical request
“Use this approved key design for the listed campaign formats and versions.”
Intake identifies the production task, checks for missing information and routes the request. When clarification is needed, it communicates through the agreed channel.
Next: the relevant production agent.
02
Digital Production
Adaptation
Available
Layout, scale and format.
Adaptation takes your approved key artwork into the sizes, layouts and versions your campaign needs, then exports the deliverables to the agreed specifications.
Starts with
Approved key artwork and a list of formats and versions.
Produces
Adapted layouts, campaign versions and exports.
A typical request
“Create the vertical, square and landscape versions using this key design.”
The design direction carries through the different proportions. The deliverables include the layouts, versions and exports specified in the request.
Next: QA checks the requested formats and specifications.
03
Digital Production
Content
Available
One direction. Consistent versions.
Content applies copy changes, prices, legal text and language versions across your assets, following the direction your designers provide.
Starts with
Design files, content instructions and version requirements.
Produces
Consistent content updates across the requested assets.
A typical request
“Apply copy A, B and C across this campaign, using the supplied language direction.”
Copy, price, legal and language changes follow the designer’s instructions. The original direction stays with the request as it moves through the versions.
Next: QA checks content against the request.
04
Digital Production
Motion
Available
Movement built from the design.
Motion turns approved static designs into animated assets, following your direction for movement, timing and delivery formats.
Starts with
An approved static design and animation direction.
Produces
Motion assets in the formats your project needs.
A typical request
“Animate this approved static design using the supplied movement and timing direction.”
Motion works from the key artwork, then develops the requested animation and delivery formats. The designer supplies the direction for how it should move.
Next: QA checks the result against the motion brief.
05
Digital Production
Available
Artwork prepared for production.
Print takes the designer’s approved key artwork and prepares the production document for print, following the designer’s layout and production requirements.
Starts with
Approved key artwork and print production requirements.
Produces
A prepared production document and print-ready output.
A typical request
“Prepare this approved key artwork for the specified print format.”
Print carries the designer’s layout into the production document and prepares the requested print-ready output using the supplied production requirements.
Next: QA checks the production requirements.
06
Quality & review
QA
Available
A correction belongs with its source.
QA checks the outputs against the request and agreed specifications. When something needs correcting, it sends the task back to the responsible production agent.
Starts with
Produced assets and the original requirements.
Produces
Checked files, with corrections routed when needed.
A typical request
“Check the outputs against the original brief and delivery specifications.”
QA reviews the produced files. If a correction is needed, it routes that work to the responsible production agent; checked files can continue to Delivery.
Next: correction with the responsible agent, or Delivery.
07
Communication & delivery
Delivery
Available
The work returns to your channel.
Delivery shares the checked deliverables and version information through your agreed project channel, keeping designers and PMs informed when the work is ready. It also communicates delivery status and any issues.
Starts with
Checked deliverables and delivery information.
Produces
Files and a clear completion message in your project channel.
A typical request
“Share the checked files and their version information in the project channel.”
Delivery communicates completion and makes the deliverables available through the agreed channel. It also communicates delivery status and any issues.
Next: the designer and PM receive the delivery update.
In development
Where production
goes next.
These workflows are at different stages of development.
Pilot
Websites
From a key design or design system to a website. Testing in defined workflows.
Pilot
Email Campaigns
From a key design to an email campaign. Testing in defined workflows.
Research
Web Apps
Exploring how a key design connects with application behavior and requirements.
People and agents, working together
Designers
Provide the key artwork, design direction and production requirements. They are the agents’ point of contact for the design.
Project managers
Coordinate priorities and deadlines, with visibility into delivery status through the agreed channels.
Brother Hills
Builds and trains the agents for each client, manages system security and continues developing the production system.
Let’s talk
Let’s shape your
production workflow.
Bring us the work your team needs to produce. We’ll discuss the agents and requirements that fit it.