← ALL PLAYS / TARGETED OUTBOUND
ECC to S/4HANA targeted outbound for SAP consultants
Signal-sourced outbound to IT leaders at large U.S. companies still on SAP ECC. Each email leads with one migration offer matched to the company's situation.
| TYPE | TARGETED OUTBOUND | MARKET | B2B |
|---|---|---|---|
| INDUSTRY | SAP CONSULTING FIRM SERVING LARGE ENTERPRISES MOVING FROM SAP ECC TO S/4HANA | ||
| OUTREACH | ADAPTIVE, 5 EMAILS, 3+ DAYS APART | FEEDS | SIGNALS |
| SENDING | AUTOMATIC, LAUNCHED WITH EVERY OTHER PLAY | ||
| DRAWN BY | HACKING DEMAND | ISSUED | NOV 6, 2026 |
THE PLAY / FOR AN SAP CONSULTING FIRM SERVING LARGE ENTERPRISES MOVING FROM SAP ECC TO S/4HANA
Trigger
A contact enrolls when a company record in the CRM matches the segment (U.S. country, annual revenue above $500M, SAP ECC status and an S/4HANA project status) and at least one buying signal fires, such as a new IT leader or a new migration role. A connected data provider can fill gaps when CRM volume is thin.
Audience
IT Directors, SAP program or migration leads, and CIOs or VPs of Technology at U.S. companies with more than $500M in annual revenue that still run SAP ECC and are planning or running a move to S/4HANA. Finance, Procurement, government and defense contacts are excluded.
Signals the agent reads
- Executive hiring
- Job started
- Tech investment
- Mergers and acquisitions
- Growth metrics
- Leadership content
Selling angle
A new IT leader inheriting an ECC to S/4HANA program often finds that custom code and master data were never fully mapped, and that is where cutover dates start to slip. Each offer addresses one part of that risk: a custom code assessment, a clean-up of Order-to-Cash data before cutover, strategic planning that limits disruption, or a recovery team for programs that have fallen behind. Senior practitioners run the work, not junior staff.
Outreach approach
Five touches run on business days, spaced at least three days apart. Touch 1 leads with the buying signal and one offer. Touch 2 adds one concrete fact about the firm's delivery record and asks a different question. Touch 3 proposes a no-cost, short proof-of-capability sprint as the lowest-risk first step. Touch 4 invites the reader to an industry user group meeting if that date is still ahead. Touch 5 is a short close saying the sender will stop and the door stays open. Any reply, booked meeting, unsubscribe, bounce or 30 days of silence stops the outreach.
- 01 / DAY 1Signal-led first approachNames the reader's ECC to S/4HANA situation and the buying signal in plain terms, then offers one matching service. Asks for a 30-minute call on one of two named weekdays, or a reply with a time that works.
- 02 / DAY 4Concrete fact and new questionAdds one verifiable fact about the firm's delivery record, such as the number of migration projects delivered, and asks a different question about the reader's custom code or data readiness.
- 03 / DAY 7Lowest-risk first stepOffers the no-cost proof-of-capability sprint so the team can see its own custom code and risks before committing to a larger scope.
- 04 / DAY 10Industry meeting invitationInvites the reader to an upcoming SAP user group meeting where S/4HANA migration topics are covered, if that date is still ahead. Links only the descriptive words.
- 05 / DAY 13Short closeSays the sender will stop reaching out and that the door stays open. No new pitch and no new facts.
Advanced instructions (excerpt)
SUBJECT LINE: Keep subjects under six words, in sentence case, with no exclamation marks, emoji or question marks. Default subjects name a migration concern, such as custom code before the S/4HANA move, ECC to S/4HANA cutover risk, or Order-to-Cash data before cutover. On touches 2 to 5, reply in the same thread and keep the original subject line. EMAIL LENGTH: The first touch runs 120 to 180 words in short plain paragraphs, with no bullet lists and no bold. Later touches run 70 to 120 words. Use exactly one question and exactly one link per email. If you cannot fill 120 words with specifics about this company, you have not researched enough to send. WHAT EVERY EMAIL MUST CONTAIN: Name the reader's ECC to S/4HANA situation in their own terms, one offer, one concrete fact from the research, one question and one ask for a 30-minute call. CHECK THE RELATIONSHIP FIRST: If the company is a customer, has an open deal, or a recent form or meeting, write nothing. If the contact went quiet after an earlier conversation, acknowledge it in one clause and invent no details. If the record is empty, send a first approach with no invented history. If you cannot tell which case applies, do not write.
Sample first email
SUBJECT Custom code before the S/4HANA move
Hi [First name], New IT leaders on an ECC to S/4HANA program often inherit custom code nobody has fully mapped, and that is where cutover dates start to slip. Our custom code assessment work reviews and remediates that code before the migration starts. We also run a short, no-cost proof-of-capability sprint, so you can see documented, testable custom code in your own environment before you commit to a larger scope. I can walk you through the sprint in 30 minutes on Tuesday, [Date] or Wednesday, [Date]. Which day suits you better, or reply with a time that works and I will send an invite? Thanks,
Guardrails
- Never state a price, discount or contract term, and say a senior person will reply to any commercial question.
- Never claim a result beyond what the firm's published pages say, and never invent customer names, statistics or quotes.
- Never discuss a production outage, cutover incident, or a security, audit or compliance question about a client's SAP environment. Escalate those to a person.
- Any reply from a CIO or executive sponsor goes to a person.
- Never write to Finance or Procurement contacts, or to government or defense buyers.
- Stop on any reply, booked meeting, unsubscribe, bounce or after 30 days.
Setup in HubSpot
- Build an enrollment rule on the segment: U.S. country, annual revenue above $500M, SAP ECC status and an S/4HANA project status, plus at least one buying signal.
- Add exclusions for existing customers, companies with open deals, and contacts with a recent form submission or meeting, plus Finance, Procurement and government contacts.
- Turn on Send without review so approved-by-rule emails send automatically under the play's stop rules.
- Set the sender to the sales team lead, with a named fallback sender for the mailbox.
- Restrict sending to business days, 8:00 AM to 5:00 PM Central Time, and launch this play together with the other plays.
KPIs
- Meetings booked from replies, the main measure of success.
- Reply rate by touch, to see which offer and question draw responses.
- Bounce rate, kept under 3 percent.
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 ↗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.
Good questions.
Straight answers.
Why is this play Adaptive?
Every play uses Adaptive outreach, so the agent writes each email from the advanced instructions and the record. Adaptive lets the agent choose the next angle from the buying signal and the touch number, which suits a segment where the right offer depends on each company's migration stage. Every contact is still capped at five emails.
What happens if the CRM does not show the segment fields?
If the country, revenue, SAP ECC status or S/4HANA project status is missing, the contact is not sent to. The agent writes only when the record confirms the segment.
Who handles replies from senior executives?
Any reply from a CIO or executive sponsor goes to a person on the sales team, and the agent does not answer it.
Every good build
starts with a conversation.
New builds, remodels, and additions, powered by AI. Let’s plan the work.