FREE BLUEPRINTGet a free blueprint for an AI agent, a build or a program, written for your team in about a minute. ↗
HACKING
DEMAND_

← ALL PLAYS / TARGETED OUTBOUND

Identity partner outbound for a middleware vendor

Reaches partner and practice leads at identity vendors and integrators after a signal. Five touches cover connector gaps in shared rollouts.

Get this play built in your HubSpot Get your own free blueprint
TYPETARGETED OUTBOUNDMARKETB2B
INDUSTRYIDENTITY INTEGRATION MIDDLEWARE COMPANY THAT SELLS THROUGH IDENTITY PLATFORM VENDORS AND SYSTEM INTEGRATORS
OUTREACHADAPTIVE, 5 EMAILS, 3+ DAYS APARTFEEDSSIGNALS
SENDINGAUTOMATIC, LAUNCHED WITH EVERY OTHER PLAY
DRAWN BYHACKING DEMANDISSUEDOCT 30, 2026

THE PLAY / FOR AN IDENTITY INTEGRATION MIDDLEWARE COMPANY THAT SELLS THROUGH IDENTITY PLATFORM VENDORS AND SYSTEM INTEGRATORS

01

Trigger

Contacts are suggested daily from monitored companies in the identity vendor and integrator segment. A contact enrolls when a qualifying signal dated within the last 90 days is present and the record passes the relationship check.

02

Audience

Partner managers, alliances directors, solutions architects, identity practice leads and professional services directors at identity platform vendors and system integrators. These are teams that run customer rollouts where some applications have no native SCIM support.

03

Signals the agent reads

  • Strategic partnership (new alliance)
  • Executive hiring (partner or practice role)
  • Product launch
  • Tech investment (identity practice build-out)
  • Client signing
  • Growth metrics
04

Selling angle

Partners buy for coverage across many customer deployments, so the message is about connector gaps in shared rollouts rather than the daily pain of an end-user IAM team. A missing connector can stall a whole partner rollout, and custom scripts pile up while the go-live waits. Each touch brings a different point: the gap, how fast new connectors can be built, the partner program, and how a practice keeps rollouts out of the custom-build queue.

05

Outreach approach

Five touches run in one email thread with the same subject line, spaced three days apart, and the agent changes the angle on each one. Touch one names the chosen signal and the connector gap, and later touches cover build speed, the partner program and the reseller application page, and a short close. The play stops on a reply, a booked meeting, an unsubscribe, a bounce, or after 30 days.

  1. 01 / DAY 1Signal and connector gapNames the chosen buying signal in plain words, such as a new alliance or a platform launch, and ties it to the contact's identity practice. Describes the connector gap that tends to stall shared rollouts and asks about it in one question.
  2. 02 / DAY 4Build speed and catalogExplains that a pre-built connector catalog covers many applications, and that missing connectors can be built quickly so a go-live does not wait. Links the connector catalog and asks one question about current deployments.
  3. 03 / DAY 7Partner program and reseller applicationDescribes how practices bring connectors in alongside their identity platform through the partner and reseller program. Links the reseller application page and asks whether a working session would help.
  4. 04 / DAY 10Keeping rollouts out of the build queueDescribes how a practice keeps a customer rollout out of the custom-build queue by using pre-built connectors for apps without native SCIM. Makes no claims about any specific customer and asks one question.
  5. 05 / DAY 13Short closeAsks whether connector coverage is on this year's roadmap, or says that the sender will stop reaching out if the timing is wrong. Keeps it under 60 words and ends the play.
06

Advanced instructions (excerpt)

You write outreach for [Company], an identity integration middleware company. The product is a SCIM gateway with a catalog of pre-built connectors that lets identity platforms provision and deprovision users in applications that lack native SCIM support. Write to a partner or integrator practice lead, never to an end-user IAM buyer. Your job is to start a conversation about connector coverage in shared customer rollouts. Read the HubSpot record before writing. If the contact is a customer, has an open deal, or submitted a form or reseller application in the last 30 days, write nothing. If an earlier conversation went quiet, acknowledge it briefly in the first line without inventing what was said. Use only the signal names in this play. Name one chosen buying signal in plain words and tie it to the contact's identity practice. Name one proof point from the approved list only. Name one product from this play's product list and link it once. End with exactly one question. Keep the first touch between 120 and 170 words and later touches between 60 and 120 words. Use short plain paragraphs with no bullets and no bold. Use the subject line from the play. Do not state pricing, discounts, partner terms, or security attestations. Do not name any other vendor or criticize any identity platform. Never write following up or circling back. If you cannot tell which case applies, do not write.
07

Sample first email

SUBJECT Connector gaps in your identity rollouts

Hi [First name], Congrats on the new alliance your practice announced this month. Partner rollouts often stall on the first application with no native SCIM connector, and that is when custom scripts start piling up. A pre-built connector catalog covers that gap, and new connectors can be built in a matter of days, so a missing connector does not have to hold up a go-live. Our partner and reseller program is built for practices that want to bring these connectors into their own deployments. Would 30 minutes on Tuesday or Thursday work to compare where your team hits connector gaps on current deployments, or grab a time that works? Thanks,

08

Guardrails

  • Never state pricing, discounts, margins, or partner agreement terms.
  • Never invent customers, statistics, quotes, or links, and use only the links named in this play.
  • Never mention security attestations or any live customer incident.
  • Never name or criticize other identity vendors. Describe the product as working alongside them.
  • If a reply asks for pricing, terms, or custom connector scoping, do not answer. A person will reply.
  • Stop on reply, booked meeting, unsubscribe, bounce, or after 30 days, and respect all exclusion segments.
09

Setup in HubSpot

  1. Create an enrollment rule for the identity vendor and integrator segment that uses the daily contact suggestions and the signal list in this play.
  2. Add exclusions for current customers, contacts with open deals, contacts with closed-won deals, and anyone who submitted a form or reseller application in the last 30 days.
  3. Turn on Send without review so emails send automatically on the Adaptive cadence.
  4. Set the sender to the named account owner, with the demand generation lead as the fallback sender.
  5. Set the send window to Monday through Friday, 8:00 to 17:00 Pacific Time.
10

KPIs

  • Replies from partner and integrator practice leads, watched weekly against total sends.
  • Booked working sessions with identity experts, watched weekly as the main outcome.
  • Bounce rate, kept under 3 percent to protect the sending domain.
BUILD IT

Get this play built in your HubSpot.

The free Breeze starter pack drafts plays like this one for your company, from your website: selling context, signals, outreach instructions and guardrails, ready to paste. Want it built and tuned for you? Our team does that too.

Get this play built in your HubSpot ↗ Get your own free blueprint ↗

How we build prospecting agents ↗

This play is anonymized: company names, brands, people, domains and exact figures are removed or generalized. It is a starting point, not a guarantee of results.

Questions about this play

Good questions.
Straight answers.

Why does this play use a longer gap between emails?

Partner decisions move more slowly than an end-user IAM buyer's, so spacing touches three days apart gives the practice lead time to respond. Each touch still moves the conversation forward with a new angle.

What happens if the contact's record is empty?

The agent makes a first approach with no invented history. If the agent cannot tell which record case applies, it does not send.

Who handles pricing or custom connector questions?

The agent does not answer those questions. A person on the team replies directly.

MORE PLAYS

Keep browsing the library.

PL-023Targeted outboundIdentity rollout outbound for an IAM integration vendorReaches IAM, IT and security leaders at mid-market and enterprise firms rolling out an identity platform with apps that lack native SCIM. Triggers on funding, hiring and tech investment signals to book working sessions.MARKETB2BOUTREACHAdaptive, 5 emailsFEEDSsignalsISSUEDOct 30, 2026Open play PL-020Targeted outboundAuction house outbound for an auction software vendorFive emails to auction house leaders after a buying signal, asking for a demo. Covers the U.S., Canada, U.K. and Australia.MARKETB2BOUTREACHAdaptive, 5 emailsFEEDSsignalsISSUEDOct 27, 2026Open play PL-017Targeted outboundSignal outbound to B2B SaaS leaders from a demand agencyWrites to B2B SaaS sales, demand gen and founder leaders when a buying signal appears. Each email names one signal and one matched offer, then asks for a 30-minute strategy conversation.MARKETB2BOUTREACHAdaptive, 5 emailsFEEDSsignalsISSUEDOct 26, 2026Open play

Every good build
starts with a conversation.

New builds, remodels, and additions, powered by AI. Let’s plan the work.

Let’s build demand ↗