Customer Mix and Focus Matters in Martech Selection

  • Amount. The actual number of active customers that fit into the category.
  • Percent. The percentage of its active customers that fall into the category.


The client size a vendor typically works with is telling. It guides whether the vendor likely has the features and expertise to support an organization, or if it falls outside the vendor’s norm. If a vendor primarily works only with smaller organizations, for instance, it is likely less of a fit for an enterprise.

Questions to ask:

  • Total customers. How many customers does the vendor have that are larger or smaller than your company?
  • New customers. How many customers of your size has the vendor onboarded in the last 12 months?
  • Revenue. How much revenue do customers larger or smaller than your company contribute to the vendor?


What industries, geographies, and business requirements does the vendor have expertise? If an organization is based in Europe, and the vendor has little to no European clients, this calls into question how responsive it will be during normal working hours for that team. However, be aware that there are instances where vendors are entering a new segment and won’t necessarily have a historical track record in a specific industry or geography. In these cases, it’s critical to evaluate if the vendor has successfully built out solutions in similar segments and has onboarded new resources with domain-specific expertise. If not, view this vendor with a high degree of skepticism.

Questions to ask:

  • Industry. How many of active customers does the vendor have in your industry?
  • Geography. How many active customers does the vendor have in your region/country/state?
  • Requirements. How many active customers have business requirements similar to yours?

Complexity and Sophistication.

This area focuses on the use cases a vendor can comfortably address. Some focus on the simple use cases, while others are much more complex. For example, if a vendor focuses most of its efforts on simplified use cases, though it technically may address a more sophisticated scenario, this usually means it will do so at the cost of added complexity and professional services. It may be tempting to select a vendor that can handle the most complex use cases, but this isn’t a good idea because, in some cases, complexity may come at the cost of using a purpose-built solution for baseline requirements.

Questions to ask:

  • Standard vs. Optimized. How many of the vendor’s clients have use cases more or less sophisticated the use cases you have outlined?
  • Out of the box vs. Professional services. How many use cases, and which of them, can be done out of the box without professional services? Which use cases require some or extensive professional services?


Though vendors frequently state they can integrate with any other software vendor, the actual truth is every one of them has preferred integrations. An example would be 90% of the CRM’s a vendor integrates with being of a particular type. A vendor also has integrations it can do but has actually never done, as well as integrations it has done, but only has limited experience with. Also, there is a difference between being INTEGRATED and having an integration. Some integrations are topical, passing baseline data, and affording the ability to drive baseline actions, whereas others are tightly integrated.

Questions to ask:

  • Available integrations. How many of the vendor’s active customers are integrated with the software solutions your company owns?
  • Depth of integration. Drill into the depth and breadth of each integration, asking about the number of clients actively using the integration at a level equal to or greater than your organization requires.

Product Roadmap.

A Martech vendor’s historical roadmap provides a sense of where it has invested, and the future roadmap indicates where the vendor is headed. This helps to understand if they are prioritizing the features and use cases that matter to your organization or simply paying lip service. Ask vendors about their historical and future product roadmaps through a discussion with a product lead or through an RFI/RFQ.

Questions to ask:

  • Historical roadmap. What were the primary capabilities added into the product over the last year?
  • Future roadmap. What are the primary areas the vendor is looking to build out in the product over the next year?



Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Iron Horse

Iron Horse

At Iron Horse, we specialize in creating demand for the technologies that are transforming the world.