# Market Intelligence Pricing Models

> Market intelligence is priced by scope, seats, modules or usage, and the model matters more than the headline figure because it sets what growth costs.

Source: https://moojing-global.com/wiki/market-intelligence-pricing-models

Last updated: 30 September 2026

Market intelligence is sold under a small number of pricing structures, usually combined. The headline figure gets the attention during evaluation; the **structure** is what determines the cost of the relationship over its life.

## The four structures

| Model | Charges by | Expands expensively when |
|---|---|---|
| **Scope** | Categories, platforms, markets, history depth | You enter a new market or category |
| **Seat** | Number of users | The capability spreads across teams |
| **Module** | Capabilities licensed separately | You need a second kind of analysis |
| **Usage** | Queries, exports, API calls | You automate or integrate |

Most contracts blend two or more — commonly scope plus seats, with modules for distinct capabilities.

Each structure is defensible. Each also has an axis along which growth is disproportionately expensive, and that axis is what a buyer should be looking at, because **the first year is quoted and the following years are structural.**

## Price the future requirement, not the current one

The exercise worth doing before signature: describe how you expect to use the data in two years, and price *that*.

- Under scope-based pricing, will you have added markets or categories?
- Under seat-based, will other teams want access once the first team demonstrates value?
- Under usage-based, will you automate anything that currently runs by hand?
- Under module-based, will the second kind of analysis become necessary?

Vendors will quote the two-year scenario readily. Buyers rarely ask. The gap between the two quotes is where renewal surprises come from, and it is entirely avoidable.

The related failure: succeeding with the data, wanting to expand it, and finding the expansion is priced as a new negotiation from a position where you are now dependent.

## What headline quotes commonly exclude

Each of these is legitimate to charge for. Each is worth surfacing during evaluation rather than at renewal:

- **Custom category definitions.** Your commercial view of your market usually does not match any platform's taxonomy, so someone has to assemble it. This is the most frequently underestimated line, and it is not optional — see [Data Coverage and Completeness](https://moojing-global.com/wiki/data-coverage-and-completeness) on why classification decides whether the numbers describe your market or an adjacent one.
- **Historical backfill** beyond a default window.
- **Export or API access** at usable granularity — decisive for the hybrid approach in [Build vs Buy Market Intelligence](https://moojing-global.com/wiki/build-vs-buy-market-intelligence).
- **Additional seats** past a threshold.
- **Analyst support** beyond documentation.
- **Redistribution rights**, if figures will be shown to clients or published.
- **A faster refresh cadence**, where a vendor offers one at extra cost; it is worth paying for only when a decision cannot wait for the standard cycle, and [Data Refresh Frequency](https://moojing-global.com/wiki/data-refresh-frequency) sets out how to match the cadence to the decision.

A quote only becomes comparable across vendors once you know what each one includes.

## Comparing quotes properly

Comparing headline figures across differently structured contracts measures the structures rather than the value. Normalise instead:

1. **Write the requirement down** — categories, markets, history depth, users, export method, use rights.
2. **Ask every vendor to price that same specification**, itemising anything charged separately.
3. **Compare total cost for the stated requirement.**
4. **Separately, price two named expansions** you consider likely, and compare those too.

Step four is the one that changes decisions. Two contracts that look similar at signature frequently diverge sharply on the expansion you actually make.

## Where price should sit in the decision

Price is one dimension among ten in [Market Intelligence Platform Comparison Criteria](https://moojing-global.com/wiki/market-intelligence-platform-comparison-criteria), and it is rarely the one that should decide. The reason is switching cost: the visible cost of changing provider is the contract, but the hidden cost is retraining analysts, rebuilding dashboards and re-benchmarking the historical baseline. That asymmetry means a marginal price advantage rarely justifies a switch, and it also means the initial choice carries more weight than its price difference suggests.

The practical consequence: spend the evaluation effort on whether the dataset answers your questions, and treat price as a constraint to satisfy rather than a variable to optimise. A cheaper dataset that does not answer the question is not cheaper.

## Negotiating points that are usually available

- **Multi-year terms** in exchange for a capped escalation
- **A paid pilot** on your real workflow before full commitment
- **Scope staging** — starting narrow with agreed pricing for defined expansions, which converts the renewal risk above into a known number
- **Named use rights**, settled in writing rather than assumed

The third is the most useful and least often requested.

## Where to look next

For the alternative to licensing entirely, see [Build vs Buy Market Intelligence](https://moojing-global.com/wiki/build-vs-buy-market-intelligence). For what to ask and require in procurement, see [Market Intelligence RFP Checklist](https://moojing-global.com/wiki/market-intelligence-rfp-checklist). For the full evaluation process, see [How to Evaluate Market Intelligence Providers](https://moojing-global.com/wiki/how-to-evaluate-market-intelligence-providers) and [Market Intelligence Platform Comparison Criteria](https://moojing-global.com/wiki/market-intelligence-platform-comparison-criteria).

## How Moojing approaches this

Moojing scopes commercial terms per engagement, against the categories, platforms, markets and access method a buyer actually needs, so the structure is set during evaluation rather than inherited from a standard tier. Pricing is not published; the contact route is on this site and scoping questions are answered before a proposal. For what a scope can include, see [market intelligence](https://moojing-global.com/market-intelligence).

## Common questions

### How is market intelligence usually priced?

Four structures dominate, usually in combination. Scope-based pricing charges by what the dataset covers — categories, platforms, markets, history depth. Seat-based pricing charges per user. Module-based pricing separates capabilities so each is licensed individually. Usage-based pricing charges by query, export or API call. The structure matters more than the headline figure, because it determines what happens when you succeed: the model decides whether adding a category, a market or a team costs a little or triggers a renegotiation, and that is where the real cost of a contract is usually decided.

### Why does the pricing model matter more than the price?

Because the first year is quoted and the following years are structural. A contract that looks competitive at signature can become expensive on the axis you happen to grow along — adding markets under scope-based pricing, adding analysts under seat-based, or increasing automation under usage-based. The useful exercise before signing is to describe how you expect to use the data in two years and price that, not just the initial requirement. Vendors will quote the second scenario readily; buyers rarely ask, and the gap between the two is where renewal surprises come from.

### What is usually excluded from a headline quote?

More than buyers expect. Common exclusions: custom category definitions where your commercial view of the market does not match a standard taxonomy, which is most of the time; historical backfill beyond a default window; export or API access at usable granularity; additional seats past a threshold; analyst support beyond documentation; and redistribution rights if figures will be shown to clients. Each is legitimate to charge for, and each is worth surfacing during evaluation rather than at renewal — a quote is only comparable across vendors once you know what each one includes.

### How should a buyer compare quotes from different vendors?

By normalising to a defined requirement rather than comparing headline figures. Write down what you actually need — the categories, markets, history depth, number of users, export method and use rights — and ask every vendor to price that same specification, including anything they would charge separately for. Then compare on total cost for the stated requirement and, separately, on the cost of two named expansions you consider likely. Comparing headline numbers across differently structured contracts measures the structures, not the value.