Understanding Cadence Blueprints

Understanding Cadence Blueprints

Summary
A cadence blueprint is a reusable template for a cadence. Instead of building the same outreach strategy from scratch each time, users can start from a blueprint and use a prebuilt structure. Blueprints also support roll-up reporting, so teams can review performance across multiple cadences created from the same blueprint.

Note: This article covers Cadences 2.0, the newer outreach experience. Read Cadences vs. Cadences 2.0: What’s the Difference? or go to the original Cadences 1.0 help articles.

Watch the video to learn more about cadence blueprints and how they work.  When you’re ready to create a blueprint, visit this article to learn how with a great video.

When to use a blueprint

Use a blueprint when your team wants a repeatable outreach strategy that more than one person may reuse. Blueprints are especially helpful when you want a shared starting point, a more consistent setup, and reporting across related cadences.

What you can do with a blueprint

From the Cadence Blueprints area, you can review available blueprints, open a blueprint to understand its structure, and select Use for New Cadence to create a live cadence from it.

When you create a new cadence from a blueprint, much of the setup is already filled in, such as the success metric, step order, templates, waiting periods, and conditional logic. This saves time and gives users a strong starting point that can still be tailored as needed.

What to know

Blueprints can support different types of work, including cadences, prospect plans, and bulk messages.  A prospect plan is not the same thing as a blueprint. Instead, it is one type of blueprint a team may choose to create.

Reporting

The blueprint details page shows how many cadences were created from a blueprint, which cadences are linked to it, and how those cadences are performing together. This roll-up view helps teams understand whether a reusable strategy is working across multiple uses.

Best practices

  • Use clear names so users can understand the blueprint’s purpose at a glance.

  • Make sure any cadences that use the blueprint are tied to it (and remove cadences from the blueprint if they veer too far away from the original blueprint)

  • Tag blueprints consistently so they are easier to find later.

  • Build blueprints around repeatable strategies rather than one-time outreach.

 

Was this article helpful?

Content aside

  • yesterdayLast active
  • 18Views
  • 1 Following