Why licensing structure matters
Most data subscriptions are built for the vendor's revenue predictability, not your actual usage pattern. A team that needs data once a quarter shouldn't pay for a monthly platform, and a team that needs continuous access shouldn't be stuck re-purchasing project by project. Licensing at Data Mappers is structured around how you actually use the data, not a default annual contract.
This matters more than it sounds. A rigid licensing model quietly shapes behavior, teams either over-buy access they don't need to avoid running out mid-project, or under-buy and hit friction right when a campaign is picking up momentum. Matching the license to the actual usage pattern removes that guesswork from the budgeting conversation entirely.
What's included in every license
Regardless of which model you choose, a Data Mappers license includes clearly defined usage rights, so there's no ambiguity about how the data can be used internally. It includes our standard accuracy guarantee and replacement policy, and it includes support from a team member who understands your project, not a ticket queue. The difference between the four models is duration and scope, not the quality or terms underneath them.
Four licensing models
| Model | Best for |
|---|---|
| One-time project licensing | A single targeted campaign or short-term initiative |
| Annual licensing | Organizations that need ongoing access throughout the year |
| Enterprise licensing | Multiple departments or enterprise-wide business intelligence needs |
| Custom licensing | Requirements that don't fit a standard model |
Where licensing applies
These models apply across the full range of Data Mappers' data products, our data cards (education, professional contacts, and others), custom-built databases, and appending or enrichment projects. You're not locked into a single licensing structure per product, the model follows your usage pattern, not the specific data you're licensing.
Who uses each model
A marketing team running a single campaign this quarter typically wants one-time project licensing, no ongoing commitment once the campaign wraps.
A sales organization that's constantly prospecting typically wants annual licensing, so data access doesn't require a new purchase every time.
A large enterprise with multiple teams pulling from the same data typically wants enterprise licensing, consolidated under one agreement instead of several overlapping ones.
A team with unusual requirements, a specific data retention policy, an unusual usage pattern, or a need to combine models across product lines, is exactly who custom licensing exists for. If none of the three standard models fit cleanly, that's a conversation worth having rather than forcing the requirement into the wrong box.
Before you commit
- Commitment concerns: one-time project licensing exists specifically for teams that don't want a long-term contract.
- Cost concerns: pricing scales with the model and volume you choose, not a flat platform fee.
- Flexibility concerns: custom licensing exists for requirements that don't fit the standard four models.
- Compliance concerns: all licensed data is 100% verified and permission-passed.
Frequently asked questions
What licensing models are available?
One-time project licensing, annual licensing, enterprise licensing, and custom licensing agreements.
Do I need a long-term contract?
No. One-time project licensing is available for a single campaign with no ongoing commitment. Annual and enterprise options exist for teams that want continuous access.
Can licensing cover multiple departments?
Yes. Enterprise licensing is built specifically to support multiple departments or business units on one agreement.
Does licensing apply to all your data products?
Yes. Licensing models apply across our data cards, custom databases, and enrichment or appending projects.
How is licensing priced?
Pricing depends on data volume, licensing model, and usage scope. Contact our team for a quote specific to your requirements.