Which one are you?

A brand owner. An agency. A DAM, MAP, or CMS vendor. Each one buys IQIN for a different reason. Underneath all three: the same IQ Score, the same API.

Primary market
Enterprise brand owners
Buys directly, runs their own campaigns
Secondary market
Agencies
Runs many client brands through one account
Channel partnership
DAM, MAP, and CMS vendors
Embeds the score as a native product feature
Same IQ Score, same API, whichever door a customer comes through
Primary market

Enterprise brand owners

A retailer, a financial services brand, a consumer tech company, a CPG, any company with an internal marketing org, an agency roster, a brand book, and real regulatory exposure. The fit comes from organizational shape: a brand function, a creative team, and typically a legal or compliance function.

Who buys

Usually a Brand or Creative Director first. Legal Counsel joins once the compliance registry starts paying for itself.

What matters most

Intent and Identity first, the compliance registry close behind as regulatory exposure becomes the forcing function.

Why it fits

Every persona the platform scopes for already exists inside this kind of org: brand, creative, legal, and the agency partners they work with.

Secondary market

Agencies

Does not own a brand, manages many. Needs the same IQ Score to work consistently across every client brand, fast, with reporting a client can read without translation.

Who buys

An agency director who needs one tool to behave identically no matter which account is using it.

What matters most

Consistency across client brands, and an answer already on file the next time a client asks how a deliverable was vetted.

Why it fits

The product's own data model already treats multiple brands as first class, so running many clients through one account is the intended shape.

Channel partnership

DAM, MAP, and CMS vendors

The platform the end customer already has open every day, so the sale runs through a partnership rather than a direct pitch: the IQ Score becomes a native, filterable field inside a system your customers already use.

Who buys

A Product or Partnerships lead deciding whether to build this in-house or license it.

What matters most

A documented API and schema that turns into a real, filterable field inside your product, not an integration your customers have to wire up themselves.

Why it fits

Your customers already ask which assets they can use, every time they search the library. This answers that question inside the tool they're already in.

Tell us which one you are

A brand's own campaigns, an agency's client roster, or a DAM/MAP/CMS integration: we'll walk the actual screen for that.

Get early access