The First Marketer in Japan: A 90-Day Playbook (Solo, In-House)

You're the only marketer, eight time zones from your budget

Before the plan, name the situation honestly, because it changes what "good" looks like.

You have three audiences, not one. The obvious one is the Japanese buyer. The second is your own headquarters, who controls your budget and cannot read a word of what you publish — so they judge your work by metrics they half-understand and a gut feeling about whether you seem in control. The third is you: deciding, alone, with no senior marketer to sanity-check you, what to do first when everything looks urgent.

That isolation is the real tax of the role. Not the workload — the absence of a second opinion. Every prioritization call, every "is this Japanese copy actually good?" question, every "how do I explain a three-month SEO timeline to an HQ that wants leads next week?" lands on one desk. So the playbook below is built to reduce decisions, not add them. It tells you what to ignore in the first 30 days, not just what to do.

And one constraint up front: trust compounds slowly in Japan, and the playbook respects that. A Japanese B2B buyer rewards depth, evidence, and patience over speed and urgency. Tactics that feel fast in other markets — aggressive CTAs, scarcity, "book a demo now" — quietly erode credibility here. We will come back to this, because it determines the order of everything.

Days 1–30: audit what HQ already shipped (and why it isn't landing)

Resist the urge to make something new in month one. Your first deliverable is not content — it is a clear-eyed inventory of what already exists and an honest verdict on each piece. You cannot build a function on top of assets you have not examined.

Pull together everything HQ has shipped into the Japanese market: the localized website, any translated case studies, the Japanese ad copy, the email templates, the sales decks the local team is already using. Then read them the way a Japanese buyer would, and sort each asset into one of three buckets:

• Built for Japan — written or genuinely adapted for the local buyer. Keep and amplify.
• Translated, and it shows — accurate Japanese, but obviously a foreign page wearing a Japanese costume. Re-write, in priority order.
• Actively damaging — keigo errors, command-tone CTAs, machine-translation artifacts that signal carelessness. Fix or pull immediately, because in Japan one visible language failure makes the whole product look amateur regardless of its quality.

Most of your inventory will land in the middle bucket. That is normal, and it is the opportunity. Here is what the gap usually looks like in practice.

What "translated, not built" looks like — an illustrative before → after

The following is an anonymized, illustrative composite — not any real client's copy — of the kind of hero section a SaaS company commonly ships into Japan after a competent literal translation. It is the most frequent pattern in a month-one audit.

You do not need to re-do the whole site in month one. You need to produce this audit — a short, honest document, ideally bilingual — so that you and HQ are looking at the same reality before any money gets spent.

Days 31–60: build the first compounding asset (SEO + one case study)

With the audit done, you have a budget question to answer: of everything that needs fixing, what do you build first? The temptation is to spread thin — patch the site, run a little paid, start a newsletter, post on LinkedIn. Don't. As a team of one, your only durable advantage is compounding — assets that keep working after you stop touching them. Two of them matter most in Japan, and they reinforce each other.

First, plant SEO that targets how Japanese decision-makers actually search. This is where "translated ≠ built" bites hardest. The English keyword your HQ ranks for, translated word-for-word, is frequently not the term a Japanese buyer types. Worse, the same concept may be searched in kanji, katakana, or a mix, and the SERPs for each can be completely different markets. Pick a small number of genuinely decision-stage Japanese queries — the ones a buyer uses when they are close to choosing a vendor — and build a few deep, useful pages around them. Depth beats volume here; Japanese buyers read.

Second, produce one real Japanese case study (導入事例). Of all trust content, the customer story does the most work in Japan, because a conservative buyer weighs "who else like us already chose this" more heavily than any feature claim. One credible, locally interviewed reference is worth more than ten translated logos. The catch is that this is the asset HQ most often gets wrong: an English customer story, translated, reads as marketing in Japan and persuades no one. A case study built for Japan starts from a fresh interview in Japanese, leads with the customer's situation and considered decision rather than emotional praise, and is comfortable being honest about the challenge. If a customer is reluctant to be named — common and reasonable here — an anonymized, problem-based story (industry, company size, the problem, the measured outcome) still carries real weight.

Sixty days in, you want exactly two things live: a handful of SEO pages built for real Japanese search behavior, and one credible 導入事例. That is a foundation that keeps paying. A dozen half-finished tactics is not.

Days 61–90: a reporting rhythm your HQ trusts

Now address the audience that quietly determines whether you get a second quarter: your own headquarters. Budget renewal is rarely lost on results — it is lost on an HQ that cannot see the results in a language and shape they trust.

Build a reporting rhythm before you need it. The instinct under pressure is to wait until you have a big number, then send a triumphant update. The opposite works better in Japan, where the work is slow to pay off: report consistently, in plain English, on a predictable cadence, framing leading indicators (search visibility climbing, the case study published, qualified inbound starting) as the early signal of a slow-compounding investment — so that when a slow month comes, it reads as expected, not as failure.

Two specifics matter. First, explain quality, don't just translate metrics. When HQ asks "is the Japanese copy actually good?", the answer is not a back-translation — back-translation makes good Japanese look strange and bad Japanese look fine. The answer is an annotated explanation in English: here is the before, here is the after, here is why the change matters to a Japanese buyer. Second, make the budget conversation a non-event. An HQ that has watched the leading indicators move every month, in English, on schedule, does not need to be sold on renewal. The reporting is the selling.

What to do yourself, what to hand to a partner

You cannot do all of this alone in 90 days, and you should not try. The honest split is the difference between burning out and building a function.

Keep for yourself the things that require being inside the company: strategy and prioritization, the relationship with HQ, the reporting, customer and sales-team access, and final judgment on what is on-brand. These are not outsourceable; they are the job.

Hand to a partner the specialist execution that eats a generalist's week: native Japanese SEO research and writing, conducting and writing the case-study interviews, and editorial QA on anything translated or AI-assisted. This is exactly the work where "translated ≠ built" decides whether the output lands, and it is the slowest for a solo marketer to do well alone.

You have roughly three ways to buy that execution, and they price very differently. A full agency typically means a high retainer and a multi-week scoping process before anything ships — strong for large programs, heavy for a team of one. A freelancer is cheaper but leaves the integration, briefing, and QA on your desk. An embedded or fractional partner sits in between: someone who works as an extension of you, reports in English so you can pass it straight to HQ, and is accountable for outcomes rather than billing by the word. For a solo in-house marketer, the question is rarely "agency or not" — it is "what do I keep, and who do I trust with the rest." If you want to think that split through against your own budget, the fractional vs. agency comparison for Japan content and the cost of Japanese content lay out the real numbers.

For reference, productized monthly support runs $1,400/mo for a focused Sprint, $2,900/mo for ongoing Growth, and $4,800+/mo for an Embedded partner — month-to-month, no long minimums. Knowing those numbers turns "what should I outsource" from a vague worry into a line you can defend in a budget.

The order matters: trust before speed in Japan

If you take one thing from this playbook, take the sequence. The reason the plan goes audit → one compounding asset → reporting, rather than "launch a campaign," is that Japan rewards trust before speed, and trust cannot be rushed.

A Japanese B2B buyer is, structurally, more risk-averse and more evidence-driven than buyers your HQ is used to. They read more before they act. They weigh who already chose you. They are repelled, not energized, by urgency. So the early wins that look impressive in a US playbook — fast paid acquisition, aggressive CTAs, volume of touches — are the ones most likely to quietly undermine you here. The slow assets — search presence built around real questions, an honest case study, a clean and correctly-registered site — are the ones that compound.

This is also why "translated ≠ built" is not a copywriting nicety but a strategic constraint. Every translated-but-not-built asset is a small withdrawal from a trust account you are trying to grow. The 90-day plan is, underneath, a plan for making deposits in the right order.

Your 90-day deliverables checklist

By the end of your first 90 days, you should be able to hand HQ this list and have every box checked:

• Days 1–30 — Audit: A bilingual inventory of every Japan-facing asset HQ has shipped, each sorted into built-for-Japan / translated-but-not / actively-damaging, with at least one before→after example showing what "translated, not built" looks like.
• Days 1–30 — Triage: Any actively-damaging assets (keigo errors, command-tone CTAs, MT artifacts) fixed or pulled.
• Days 31–60 — SEO foundation: A small set of deep pages targeting genuine decision-stage Japanese queries (chosen by real search behavior, not translated keywords).
• Days 31–60 — First case study: One credible Japanese 導入事例 built from a fresh interview — anonymized if needed, problem-led, honest about the challenge.
• Days 61–90 — Reporting rhythm: A predictable, plain-English HQ report that frames leading indicators and explains quality with annotated before/after, not back-translation.
• Throughout — The split: A clear, written decision on what you keep in-house and what you hand to a partner, with the budget to back it.

That is a function — not a pile of tactics. It is defensible to HQ, it compounds without you, and it is built for the market you are actually in.

Where to go next

• How to Report Japan Marketing Results to English-Speaking HQ — design the report that makes budget renewal a non-event.
• Fractional vs. Agency vs. Freelance for Japan Content — the real cost and trade-offs of each way to buy execution.
• What Japanese Content Actually Costs — transparent monthly numbers you can defend in a budget.

See it in practice: The audit in Days 1–30 is exactly the work we publish openly. See real before → after teardowns of Japanese B2B copy — anonymized, illustrative, and annotated with why each line passes or fails for a Japanese buyer.