When to choose a Pardot custom implementation

//When to choose a Pardot custom implementation

While many companies find the idea of a $4,000 Pardot QuickStart enticing, it may not necessarily be the right fit. Companies that should strongly consider a custom implementation often have the characteristics below.

Are transitioning from Hubspot, Eloqua, Silverpop or Marketo

When switching from a competitive solution, chances are that your marketing team is generally savvy with marketing automation and its concepts. You’ve probably got all the necessary skills to re-develop landing page and email templates in Pardot, but you might lack the time, patience or skills necessary to go through the technical configuration. Here we’d recommend an engagement intended to get you up and running in a matter of days and help plan the transition off the other solution, with support/training to help learn how Pardot works differently than other solutions.

Are an international business

International businesses tend to have two considerations that can impact scope: 1) tracking cookie opt-in (important in EMEA and developing elsewhere) and 2) user permissions and hierarchies, both in Pardot and Salesforce. Permissions need to be considered carefully across the organization, as they can greatly impact what users have access to (see below).

Have a complex Salesforce instance (security, roles and hierarchies)

Because Pardot is connected to Salesforce by a user account, it impacts what Pardot has access to (custom fields, prospect records, opportunities, etc). We have seen instances where Pardot users with the wrong permissioning can create waves of duplicates in Salesforce. So the more complex the Salesforce environment, the smoother the implementation will be when using a qualified Salesforce and Pardot implementation partner.

Deploying Salesforce at the same time as Pardot

Starting from a clean slate? This is a great opportunity to map both Pardot and Salesforce to your business processes at the same time. To do this, you’ll want your consultants, sales, and marketing working together during the process design, and you’ll want your Pardot consultant to be in lock-step with your Salesforce consultants, with the goal of building a system that optimizes the strengths of each solution (and avoiding building one that will require re-work in order to integrate).

Have limited web development, IT, and Salesforce resources

Sometimes we run into customers who have a great need for Pardot and all the executive support but very limited resources (i.e. IT, web development) who can help. In these cases we can optimize the interactions with these teams by bringing domain knowledge and expertise, minimizing their needed involvement during technical configuration.

Have multiple sales/marketing stakeholders and/or are seeking a turnkey deployment

Large enterprises almost always have multiple sales (and sometimes marketing) divisions and stakeholders. And while the functional steps to deploying Pardot are often the same, each division tends to have its own set of requirements that add nuances. This impacts lists, automations, reporting, user access, and permissions. Custom scoping is required in order for a successful implementation in these environments, where adequate time will be needed to gather requirements from each of these divisions and deploy the solution in accordance with those requirements.

While custom deployments come in many shapes and sizes, they can generally start as low as $5,500 and scale upwards depending on need and complexity, providing customers with an engagement much more tuned to their specific needs, corporate culture, timelines and complexities.


By | 2014-12-22T20:09:09+00:00 December 22nd, 2014|Pardot Marketing Automation|