The RFP process for creative services doesn't work like the one you run for landscaping. With landscaping, the deliverable is knowable. Cut the grass. With branding, the deliverable is whatever the document defines, and most branding RFPs don't define much.

A common version reads something like this: "Seeking a creative partner to develop a full brand identity for a new 264-unit Class A community delivering Q3 2027. Please submit proposal and pricing by the 15th."

An agency reading that has to guess at nearly everything. Does "full brand identity" include naming? Trademark screening? A tagline and messaging framework, or a logo and color palette? Is there an existing brand to work from? Is there a portfolio standard to match?

Every guess is risk, and risk gets priced. Which produces one of two outcomes: a padded number that protects the agency from the worst-case version of the project, or no response at all. The shops with the deepest multifamily experience will also be struggling to quote you something accurate.

Brand development breaks into five parts, and an RFP that names categories makes proposals comparable.

Research and strategy covers segmentation, location analysis, competitive analysis, and company or brand analysis. Naming covers concepts plus viability work: domain availability, social handles, search conflicts, a name search in the submarket and against competitors, and a general trademark screen. Logo covers concepts and the actual deliverable files, which is rarely one file. A complete set often runs primary, standalone iconmark, secondary, and sometimes tertiary. Visual identity covers color, typography, custom design elements, imagery direction, sample applications, and iconography. Verbal identity covers tagline, headline library, messaging, Ideal Resident Profile, positioning, brand attributes, personality, tone of voice, vocabulary, differentiators, and mission and values.

Not every project needs all five. But knowing which ones are in scope is the difference between a $6,000 engagement and a $60,000 one, and it's a question the RFP should answer (rather than the proposal).

Then there's the section almost nobody includes: quantities.

Three name concepts or nine? Two logo directions or three fully custom ones? One design element or four? Six curated images or twelve? Two sample applications or four? An iconography set of fifteen, or none at all?

Those numbers represent most of the price variance in any stack of branding proposals. An agency quoting three name concepts and one quoting nine are doing significantly different amounts of work. If the RFP didn't specify, each agency picked a number, and neither one is wrong.

Beyond scope and quantities, a few pieces of context change every figure in a proposal: asset class, whether this is a new development or an acquisition rebrand or a refresh, whether it's a single community or a portfolio-level identity, what assets already exist, and the downstream dates that depend on this work. Monument sign fabrication deadlines in particular. Branding sits upstream of a lot of other vendors.

And a budget range belongs in the document. The instinct is that naming a number guarantees you'll pay it. In creative services the more common outcome is that without a range, agencies scope to their own assumptions, and half the proposals land outside what could ever be approved. A range invites a more useful conversation: here's the version of this project that fits your number, and here's what I'd cut to get there.

One last thing worth building into the process. When proposals come back and they're finally comparable, the temptation is to sort by price and read from the bottom. Look for the questions instead. The agency that asks about the comp set, the lease-up date, or why the previous brand underperformed is doing strategic thinking in the proposal stage, unpaid, before anyone has signed anything.

That's usually a reliable preview of what the engagement will feel like.

Which raises a question worth asking about your own process: if the goal of an RFP is to get proposals you can compare, how many of the documents your team sends out are built to do that, and how many are built mostly to satisfy procurement?