When we reviewed our Japan marketing automation programs last year, the picture wasn’t pretty. Our automated emails were generating about 12 qualified leads per month against a goal of 160.
That’s a huge gap.
We could have done the obvious and by hiring a local marketing automation specialist in Japan. Instead, we rebuilt Japan’s entire email automation program in two months, with zero additional headcount, using a model any marketing team can replicate. Here’s what we learned.
Table of Contents
The Problem Most Teams Don’t Name
HubSpot is a US-headquartered company. And like most US-headquartered companies, our marketing automation investment has historically been concentrated in a handful of core markets: English, French, Spanish, German, Portuguese. Those programs get built, refined, optimized, and rebuilt again. Markets outside that core group tend to get less dedicated attention, not because anyone decided to deprioritize them, but because the automation resources weren’t scoped to cover them.
For Japan, that meant automation programs that were years old, partially built, or never meaningfully localized. The content existed, and the infrastructure was there. But it wasn’t performing because it wasn’t designed for the Japanese market.
This is a pattern that shows up across companies operating in multiple regions. Wherever there’s a primary market and a secondary one, the secondary market tends to lag. That’s because the people with automation expertise are almost always scoped to the markets that generate the most volume.
Marketing automation in markets outside the core group tends to fall into one of two failure modes: it was never built, or it was built years ago and never meaningfully updated.
Japan was the second case. And the typical response, “we need to hire a local automation expert,” wasn’t realistic. What we needed was a different model.
The Insight Behind the New Model
We were asking the wrong question. Instead of “Who can own this end to end?”, we should have asked, “Should one person own this?”
Marketing automation has two fundamentally different jobs. One is technical: building journey logic, setting up workflows, defining enrollment criteria, creating segmentation, and configuring tracking. None of that requires speaking Japanese. The other job is cultural: making sure the message feels right, the tone lands, the pain points are real, the call-to-action makes sense. That absolutely requires someone who knows the market.
The mistake teams make is assuming both jobs need to live with one person. They don’t. When you separate them cleanly, you don’t need a local automation specialist. You need an automation marketer who understands the technical side, and a local marketing or sales partner who owns the cultural validation. Together, they cover everything.
What We Actually Built
With that model in place, here’s what two months of focused work produced for Japan:
What it took:
- ~12 days of automation marketer time total (~1.5 days/week over 2 months)
- 5 days of regional marketer time for QA
- 0 additional headcount
What it produced:
- 71 emails and 38 workflows built from scratch
- 2 core programs (one targeting prospects who hadn’t engaged with sales yet, one targeting leads already showing interest)
Within the first reporting period, automation-sourced qualified leads jumped roughly 9x (from 12 to over 115 per month), making a significant contribution to Japan’s monthly qualified lead goal. We estimate that translates to about 44 incremental deals per month.
We deliberately focused on high-intent automation programs rather than trying to rebuild everything at once. Here’s why that paid off.
The Benefit of Targeting High-Intent Prospects
Treating all email programs the same kills most rebuilds before they start.
There are two types of automation programs: high-intent and low-intent. High-intent programs go to people who are already showing early buying signals: they’ve visited pricing pages, browsed product features, or taken actions that suggest they’re actively evaluating. Low-intent programs reach colder audiences through broad nurture flows.
The difference shapes a rebuild.
High-intent programs have fewer emails, more focused messaging, and clear calls-to-action. They’re easier to localize, faster to build, and they convert. Low-intent programs have large email volumes, varied content, and much longer paths to conversion. They require significantly more localization work for a smaller payoff.
In Japan, our decision to start with high-intent trigger-based emails is the reason we saw 9x growth in qualified leads in two months instead of incremental improvement over a year.
The Two-Person Operating Model in Practice
Once we had one person owning the technical side and one person owning the cultural side, here’s how things played out day-to-day.
The automation marketer owned the following:
- Journey design
- Workflow setup
- Segmentation logic
- Enrollment criteria
- Email structure and timing
- Technical QA, and reporting
None of this required Japanese fluency.
The regional marketing partner owned the following:
- Validating that messaging felt right for Japanese audiences
- Checking that pain points were relevant
- Confirming that the tone was appropriate (Japan has specific norms around formality in business communication)
- Signing off on the final customer experience
The regional partner didn’t write the emails from scratch. We used AI to produce first drafts, which they then refined and validated. Their job was cultural expertise rather than copywriting, which kept their time commitment to five days across the whole project.
We held firm on one principle: the regional partner must understand the local customer journey, not just the language. Translation alone isn’t enough. A native speaker who doesn’t know how Japanese SMBs evaluate software is not the right person for this role.
How to Know If This Model Will Work For You
Before applying this approach to any market, we ran a simple go/no-go check. The model works when all of the following are true:
- Automation is non-existent, outdated, or underperforming. If automation is already mature and driving results, this rebuild effort won’t move the needle as much as focusing on optimization.
- A large enough high-intent audience exists. You need enough people actively showing purchase signals to see real lift. For us, the threshold was roughly 2,000 contacts per month entering the programs.
- A qualified local partner is available. Not just a translator but someone who understands the audience, their pain points, and the local buying journey.
- The local partner can commit minimal time. In our case, five days total. This isn’t a full-time engagement.
If your automation is already strong, don’t use this model. The incremental gain won’t justify the effort to rebuild. If you don’t have a local partner who genuinely understands the market, wait until you do. Language fluency alone will produce technically correct emails that don’t convert.
The Playbook, Briefly
For teams that want to try this, here’s the process we’d use again:
Step 1: Assess the gap.
Check how many active workflows exist for this region, whether email delivery volume has been declining year-over-year, and whether automation-sourced qualified leads are significantly below goal. Those signals tell you whether you’re doing a full build, a rebuild, or an expansion.
Step 2: Size the opportunity.
Multiply your high-intent audience size by your email-to-lead conversion rate. If the estimate is fewer than 20 incremental qualified leads per month, the project probably doesn’t justify the investment.
Step 3: Find the right local partner.
Ask two questions: Do they understand how customers in this market make buying decisions, beyond just the language? Can they commit roughly one day per program for QA and messaging review? A contractor counts. A translator alone does not.
Step 4: Build a shared messaging guide.
Answer six questions with your local partner before writing a single email: Who is the primary audience? What are their three most urgent pain points? Which global messages resonate here, and which don’t? What tone is right? What proof points are most credible? What should you avoid? Both parties sign off before anything gets built.
Step 5: Audit what to reuse vs. rebuild.
The automation marketer reviews everything language-independent: journey structure, workflow logic, segmentation, performance data. The local partner reviews everything copy-dependent: subject lines, body copy, tone. Assign a verdict for each element: reuse, adapt, or rebuild.
Step 6: Start with high-intent programs only.
Quick test: would this email make sense to send to someone who visited your pricing page today? If yes, build it first. Low-intent programs need more content and localization work for a smaller payoff. Layer them in once the foundation is live.
Step 7: Run two-track QA.
The automation marketer checks tokens, workflow logic, test send, suppression lists, and tracking. The local partner checks for natural language, appropriate tone, relevant pain points, and a clear CTA. Both sign off before launch.
Step 8: Measure at 30, 60, and 90 days.
Day 30: early signals only. Don’t optimize yet. Day 60: compare against baseline and adjust if needed. Day 90: full picture. Qualified lead volume, deals, contribution to goal, and a decision on whether to expand.
What This Means For Your Team
The Japan pilot proved something we now believe applies broadly: you don’t need a local automation specialist in every market. You need a clear split of responsibilities between someone who owns the technical infrastructure and someone who owns the cultural context.
That’s a much more achievable team structure than hiring specialized roles in every region. It’s also faster because both people can work simultaneously rather than sequentially.
The biggest risk is rushing past the cultural alignment step or treating QA as a translation proofread. Give your local partner real authority to validate the customer experience, and the results will follow.
We went from 12 qualified leads to 115 in two months, and we didn’t add headcount.