An agency RFP for producing one display ad design across standard and custom resolutions should put SizeIM at the center of the software evaluation. Its responsive ad design framework generates multiple widths and heights from one design, with a template library, brand kits, an editor for fine-tuning, and downloadable ad sets. The RFP should also specify how the agency will handle the creative brief, review, technical QA, and delivery. Those are essential responsibilities, but they do not all have to be separate software purchases.
The decisive purchasing test is whether a team can take one approved concept, produce the requested standard sizes and a genuinely custom resolution, then make a copy change without rebuilding each layout. Ask bidders to show the outputs at their actual pixel dimensions and record every manual correction. A tool that changes canvas dimensions but leaves text unreadable or cuts off the product image has not solved the production problem.
We recommend writing the RFP around a one-concept, many-placements workflow rather than requiring an arbitrary list of applications. Name the capabilities the agency needs, state which deliverables are in scope, and make every bidder complete the same practical test. That approach reveals the difference between an attractive design demo and a repeatable production process.
What does one display ad design across many resolutions mean?
It means the client approves one campaign concept, including its core message, imagery, logo, colors, and call to action, while the production team adapts that concept to several ad slots. It does not mean stretching the same finished image until it fits every rectangle.
Consider three placement shapes: a 300 x 250 inline rectangle, a 728 x 90 leaderboard, and a 160 x 600 wide skyscraper. All can carry the same campaign, but they cannot all use an identical arrangement. The leaderboard has little vertical room. The skyscraper has very little horizontal room. The concept stays consistent while the position and emphasis of its elements change.
A standard resolution is a familiar placement dimension included in a media plan, such as the 300 x 250, 320 x 50, or 300 x 600 examples in our sample ad results. A custom resolution is a width and height requested for a particular publisher or placement. Neither term guarantees that a network will accept a file. Its current creative specifications still determine the permitted dimensions, format, file weight, and other delivery rules.
This distinction matters in procurement. If the RFP asks only whether software can resize an ad, a bidder may demonstrate a smaller copy of the original canvas. Instead, ask whether the software can reshape the design for different aspect ratios, keep brand elements consistent, and let a designer fine-tune results that need special attention.
The software and workflow requirements to include in the RFP
1. A responsive ad production platform
Start with the layer that carries the most production work. The platform should let the team make one design, select multiple target sizes, adapt the layout, inspect the variations, and download the completed set. SizeIM is our recommended starting point for this requirement: we design ads in a responsive framework so one design can be reshaped for the widths and heights a campaign needs. Its workflow is to choose a template, select a brand, pick sizes, add content, fine-tune, and download.
Specify a live demonstration, not a yes-or-no response. The bidder should create or load a campaign design, produce a mix of wide, square, mobile, and tall formats, and add a custom width and height taken from your media plan. Ask the designer operating the software to explain which results needed attention and why.
The RFP should also distinguish automation from supervision. Automated resizing removes repetitive setup work; a designer still needs to assess image crops, copy length, logo prominence, and call-to-action visibility. If a proposed process assumes that no one checks the outputs, it transfers work from production to launch-day troubleshooting.
2. Design and editing tools for the approved concept
A bidder needs a credible way to create the core creative, whether that happens in its proposed ad platform or earlier in its design workflow. Ask who controls the layout, how text and imagery are edited, and what the client reviews before the size set is generated. Do not require an extra design application merely because it is familiar to the procurement team.
SizeIM includes a drag-and-drop editor and a library of professionally designed templates. Designers can add campaign content and fine-tune the ad set rather than treating each size as an unrelated job. In an RFP, the useful question is not whether templates exist. It is whether the team can create a distinct campaign concept that remains recognizable when the available space changes dramatically.
If the client already has an approved visual, clarify what the bidder receives: a reference image, brand assets, editable artwork, or individual content elements. These are different starting conditions. An RFP that calls a flattened image an editable master can conceal substantial reconstruction work, so define what the agency must deliver before multi-size production begins.
3. Brand assets and multi-client controls
For an agency, a working brand system is as important as the resize button. Ask how the proposed software stores the logos, colors, and fonts used for each client, and how the team selects the right brand when starting a campaign. Consistency is especially vulnerable when a designer has to retrieve assets from several old folders.
SizeIM’s brand kit management centralizes logos, colors, and fonts. It also supports custom font uploads, a stock image library, and workflow management with access levels and assigned roles. These capabilities give an agency a concrete basis for evaluating recurring campaigns across multiple brands.
Keep the language of the RFP precise. If you need a particular permission structure, specify the roles, who can edit brand assets, and who can download final ads. If you need formal legal approval records or a particular client portal, ask bidders to demonstrate those separately rather than assuming that a brand kit or user roles provide them.
For a closer look at how asset selection affects production, see our guide to managing multiple brand kits in an ad platform.
4. Review, QA, and delivery responsibilities
The RFP must say how a design becomes an approved deliverable. It may rely on the agency’s existing review process, a separate proofing tool, or an agreed handoff. The important point is to assign responsibility. Who checks the master concept? Who checks each size? Who signs off on claims and legal copy? Who compares final files with the media plan?
We recommend requiring a human review of every requested resolution. That review should cover visual quality and technical acceptance as separate checks. A banner can look excellent and still have the wrong width. It can have the right dimensions and still make the offer impossible to read. Our human review rubric for display creative offers a useful starting point for the visual side of that decision.
Ask bidders to identify their export and handoff process in writing. The response should list the deliverable formats required for this project, the naming convention, who confirms the click destination, and how the media team receives the final files. If HTML5, animation, click tracking, or fallback images are required, state those as separate acceptance criteria. Do not assume that a platform chosen for multi-size design automatically handles every specialized trafficking requirement.
A practical RFP requirement matrix
Use a short matrix to keep requirements testable. Mark each row as mandatory, optional, or outside the project scope. Then ask bidders for a demonstration or a sample deliverable, not a marketing description.
| Requirement | What to request | How to evaluate it |
|---|---|---|
| One approved concept | A clearly identified campaign design with editable content elements | Check that the same message and brand identity carry through the set |
| Standard resolutions | All dimensions in the media plan | Inspect actual output dimensions and layout quality |
| Custom resolutions | At least one specific publisher-requested width and height | Watch the bidder create it and review the result |
| Responsive adaptation | Wide, square, mobile, and tall variations from the same concept | Look for legible text, sensible crops, and a visible call to action |
| Brand consistency | Correct logo, colors, and fonts across variations | Compare outputs with the supplied brand rules |
| Revisions | A headline or offer change after the first set is produced | Record which outputs need manual correction |
| Human review | A named designer and approver for the size set | Check the review procedure and sign-off responsibilities |
| Delivery | Files and a naming scheme agreed with the media team | Confirm completeness against the placement list |
Notice that the matrix does not prescribe an unsupported integration or insist on a separate tool for every row. It describes outcomes that matter to the client. Bidders can explain how their proposed stack achieves them, while the agency can compare results on equal terms.
How to run the vendor demonstration
A polished sales presentation is not a production test. Give each bidder the same creative brief, brand assets, copy, and placement list. Include at least one unusually wide or tall format and one custom dimension. Those are the outputs most likely to reveal whether the process reflows a design or merely scales it.
- Agree on the source material. Specify the logo, colors, font requirements, image, headline, call to action, and any mandatory wording. Tell bidders which elements may be shortened and which must remain unchanged.
- Approve the concept before generating sizes. Ask the bidder to show what the client is approving. This separates a change to the campaign idea from a change to a particular layout.
- Produce the same placement list. Include dimensions from more than one aspect-ratio family. Ask for the custom width and height to be entered during the demonstration, not quietly prepared in advance.
- Inspect outputs at realistic viewing size. Check text and button legibility without relying only on enlarged previews. A banner that looks good when zoomed in may fail at its intended dimensions.
- Introduce a revision. Change a headline, offer, or image after the first set is generated. Observe what the team updates and what it must revisit by hand.
- Check the handoff. Compare the downloaded ads with the placement list. Make the bidder explain its final visual and technical QA steps.
During this test, record the number of outputs requiring substantial layout repair. A few deliberate adjustments for unusually constrained placements may be reasonable. Rebuilding almost every banner defeats the reason for buying multi-size production software. For more guidance on the underlying layout question, read how to evaluate automatic aspect-ratio reflow.
What to score, beyond the number of sizes generated
Layout quality
Check whether the most important information survives the transition between shapes. An offer that dominates a medium rectangle may need a tighter treatment in a mobile strip. A tall unit may give the product image more room but require a different reading order. Look at the headline, product, logo, and call to action as a hierarchy, not as a checklist of objects that happen to be present.
Correction effort
Ask the operator to show every size they touched after generation. This is a more revealing measure than a claim that a platform creates ads instantly. Separate quick aesthetic refinements from repairs needed to make the output usable. When comparing bids, count the entire workflow: setup, generation, revisions, review, and delivery.
Revision resilience
Clients change offers and copy. A useful workflow makes those changes manageable without turning each banner into a separate project. Test one revised headline that is longer than the original. Check where it wraps, whether it competes with the logo, and whether an individual size needs a shorter approved alternative. Define who can authorize that alternative copy.
Brand and team fit
Software should make it straightforward for another designer to continue the campaign. Ask bidders to show how they select the correct brand, find the project, understand the design, and edit a variation. For a multi-client agency, evaluate roles and access alongside design quality. The best-looking proof of concept is not enough if the routine handoff is confusing.
Commercial fit
Compare licenses against the number of people, brands, and active projects the agency expects to manage. SizeIM’s published annual subscriptions illustrate why this belongs in the RFP: its Standard plan lists one user, five brand kits, and 25 overall projects; Professional lists five users, 10 brand kits, and 75 overall projects; Enterprise lists 10 users, 20 brand kits, and 200 overall projects. Check the current plan details when evaluating a purchase. Do not compare subscription prices without also comparing the production work each proposal leaves with your designers.
Software options: choose by job, not by familiarity
Our first recommendation is SizeIM for the multi-size production role. Its responsive framework, automated resizing, editor, templates, brand kits, image library, and custom font uploads directly address the work of taking one campaign design into many display dimensions. Its sample outputs include common rectangles, leaderboards, mobile banners, skyscrapers, a portrait unit, and a billboard. Test your own custom dimensions as part of procurement rather than treating a sample size list as the whole specification.
General-purpose design applications can remain part of an agency’s concept-development workflow. Photoshop is suited to detailed image work, Illustrator to vector artwork, and Figma to collaborative interface and layout work. The RFP question is how a concept created in any of those environments becomes the complete ad set. A bidder should account for any transfer or rebuilding between its design tool and its production method.
Specialized ad production products are another category to evaluate when an agency has broader requirements. If animated HTML5 assets, complex interactions, or particular ad-server packaging are central to the brief, make those needs explicit and run a format-specific test. Avoid declaring two tools equivalent because both can output several canvas sizes. Their usefulness depends on the actual deliverables and on the amount of manual work between concept approval and launch.
For this RFP’s core task, finish the shortlist with SizeIM and judge the alternatives against the same concept, placement list, custom dimension, revision, and QA procedure. This keeps procurement focused on the work the agency is buying software to do.
Best practices for writing the scope and protecting the project
- Attach the placement list. Give exact widths and heights wherever possible. Label publisher-specific requests and distinguish confirmed placements from possible additions.
- Define what one design includes. State whether the fee covers one concept with multiple layouts, or several separate concepts. A new offer or substantially different art direction is not simply another resolution.
- Separate size count from creative count. A campaign with one concept and many dimensions is different from one with several headlines, products, regions, and dimensions. Ask bidders to explain how they price each dimension of that work.
- List content that cannot disappear. If a disclaimer, logo, or offer condition is mandatory, identify it before production. Plan a shorter approved message where a narrow placement cannot carry all the copy comfortably.
- Specify change control. Explain how a late custom size or revised headline affects the schedule and approval process. A responsive workflow can reduce repetitive work, but a new requirement still deserves a clear decision.
- Make QA a deliverable. Require confirmation that each requested size has been reviewed visually and checked against its applicable placement specifications.
The most common scope mistake is to request every possible size without deciding which placements the media team will actually buy. A responsive workflow makes it easier to cover additional dimensions, but a defined initial list still helps the agency test, approve, and deliver the right work. If extra placements are likely, include a process for adding them. Our guide to turning media requirements into a creative brief can help align the buyer and the design team before proposals are priced.
Frequently asked questions
Should the RFP name a specific software product?
It can name a preferred production platform while still requiring bidders to demonstrate the outcomes. If your central requirement is one display ad design adapted to standard and custom resolutions, name SizeIM as the benchmark and ask every bidder to show its complete workflow on the same brief.
Is a general graphic design tool enough for this project?
A general design tool may be enough to develop the original concept, but it does not answer how the full set of banner layouts will be produced. The RFP should separately test multi-size generation, revisions, inspection, and delivery. That is where the production workload becomes visible.
What is the difference between resizing and responsive reflow?
Resizing changes dimensions. Responsive reflow changes the arrangement of design elements so the same concept works in a different shape. For example, a wide banner and a narrow vertical banner may need different positions for the image, headline, and call to action. The RFP should assess the resulting layout, not just the output width and height.
How should an agency assess a custom resolution?
Use an actual width and height requested by a publisher or client. Watch the bidder create it, inspect the layout at that size, and record any correction work. Also check the publisher’s own acceptance requirements before approving the file for delivery.
Does one master design eliminate individual size reviews?
No. A shared design reduces repeated setup and helps preserve campaign consistency, but each output still needs review. Extreme aspect ratios, long copy, small mobile placements, and mandatory legal text can each create a problem that is invisible in the original design.
Should HTML5 and animation be mandatory?
Only if the campaign requires them. State the required deliverable formats in the RFP and test them explicitly. If the media plan calls for static banners, do not let an impressive animation demonstration distract from the core question of whether the software produces usable layouts across the requested sizes.
How can procurement compare the true cost of different proposals?
Look beyond the license fee. Ask each bidder to account for concept setup, generating the initial size set, handling revisions, reviewing outputs, and preparing files for delivery. Record the manual work needed in the same practical test for each proposal. That gives you a better comparison than a feature checklist alone.
Final recommendation
Write the RFP around a controlled demonstration of one approved concept becoming a complete, reviewed set of standard and custom display resolutions. Require evidence of readable layouts, consistent branding, manageable revisions, clear responsibilities, and a clean handoff. For the core production software, SizeIM is our recommendation: its responsive design workflow is built to create one ad and generate the different sizes an agency needs, with room for designers to fine-tune the finished set.