01
Japan-native company data
Company names, addresses, industries, and source records stay in their original Japanese format so follow-up remains grounded in local context.
Limited paid operator beta
The English control plane for Japan GTM execution.
Governed outreach into Japanese companies, operated in English. This Japan GTM execution control plane keeps the Japanese company data, Japanese outreach copy, form conventions, and JST execution layer intact.
860,000+
Japanese company records
JST-native
Timing and observability
Operator-approved
Human control workflow
No free tier. Payment method required. Unless canceled before the trial ends, the selected plan starts automatically.
Execution Lane 01
Running
Submitting approved Japanese outreach to a Tokyo IT company
Engagement Event
Just now
A Japanese stakeholder opened a tracked proposal link
Visible in Engagement Events and Follow-up Pipeline for operator review.
Needs Review
Form condition
A complex form is flagged for operator review instead of forcing execution
SalesBreaker is designed to surface operational exceptions so teams can act responsibly.
The Japan GTM gap
Generic global sales tools miss the Japan-native layer.
Japan outreach is shaped by Japanese company records, web-form conventions, business etiquette, and JST. The English Operator Beta keeps those local constraints visible instead of hiding them behind generic automation language.
02
Japanese form conventions
Full-width characters, address fields, category selectors, and multi-step forms are part of the execution environment, not details to ignore.
03
Governed operator workflow
Operators review Japanese copy, suppression, timing, and engagement outcomes through a control plane designed to reduce operational confusion.
Control plane surfaces
What English operators can control.
The beta focuses on the human operator shell first. Deeper API and CRM integrations are being developed separately.
Company Profile & Suppression
Define sender profile assumptions, exclusions, and suppression rules before running Japan-facing outreach.
Templates & Japanese Copy
Prepare Japanese outreach copy and use Japan GTM Assistant as a drafting and etiquette helper.
Start Outreach
Queue operator-approved execution into assigned lanes while preserving JST and Japanese form behavior.
Execution History
Review submitted, not eligible, suppressed, failed, and needs-review outcomes from the execution layer.
Engagement Events
Observe clicks and high-intent signals without treating them as a substitute for operator judgment.
Engagement Pipeline
Use a lightweight follow-up workspace for post-engagement review, interested companies, and next actions.
English Operator Shell
The UI explains the workflow in English.
- - Navigation, onboarding, pricing, help, and observability use operator English.
- - Execution Lane, Suppression, Engagement Events, and Execution History stay consistent across the beta.
- - Help & Support and GPT links are designed to reduce operator confusion.
Japan-Native Execution Layer
The target market stays Japanese.
- - Japanese company records remain Japanese for source-data integrity.
- - Japanese outreach copy remains Japanese for the recipient context.
- - Form behavior, timestamps, and execution review stay aligned with Japan operations.
Operational recommendation
Use a dedicated inbox for Japan outreach operations.
For higher-volume outreach, we recommend using a dedicated inbox separate from your primary business email. Contact-form replies, thank-you emails, and direct replies can arrive at volume.
USD operator pricing
Execution Lane capacity for the limited beta.
English Operator Beta is paid-only. Starter is available monthly or annually. There is no free tier and no 6-month plan.
Self-serve beta plan
Starter
For a focused Japan GTM proof of concept.
Monthly
$200/mo
Annual
$2,000/year
$166/mo equivalent
Includes a 3-day operator trial.
- 1 Execution Lane
- Approx. up to 600 outreach attempts/hour
- Best for
- Single-market testing and workflow validation
Need more capacity?
Higher-volume Standard and Premium capacity is handled by inquiry during the limited beta so we can confirm the right execution setup before charging a larger annual amount.
- Available by inquiry
- Expanded execution lanes, reserved capacity, and dedicated support.
- Best for
- Teams that already know they need more than Starter throughput.
Throughput is approximate and varies by target websites, form conditions, page speed, validation behavior, and operational review needs. One Execution Lane is an operator-facing capacity unit that maps to roughly 6 internal processes; one internal process is estimated at up to 100 outreach attempts/hour.
USD prices are tax-exclusive. Tax collection is not enabled for the initial English Operator Beta unless otherwise required. A payment method is required. Unless canceled before the 3-day operator trial ends, the Starter plan starts automatically.
By continuing, you agree to the English beta Terms summary, Privacy summary, and Commercial disclosure summary. The Japanese legal documents remain authoritative. Open the legal overview or Security summary.
Responsible operation
Built for governed outreach, not low-quality automation.
SalesBreaker is designed to help operators manage outreach responsibly with review points, suppression, history, and engagement observability. Low-quality broad messaging and unclear targeting should be avoided.
Suppression: available
JST: visible
Operator review: expected
Self-serve FAQ
Understand the beta before starting.
These answers explain what is available now and what remains Japan-native.
Why is company data still Japanese? v
Company names, addresses, industries, tags, and source records are preserved in their original Japanese format. That keeps follow-up grounded in the same source data your Japan-facing workflow uses.
What is an Execution Lane? v
An Execution Lane is an operator-facing capacity unit for concurrent execution. In the English beta, one lane maps to roughly 6 internal processes, with each internal process estimated at up to 100 outreach attempts/hour. Actual throughput varies by target and form conditions.
Does AI execute outreach automatically? v
No. The GPTs are external helper guides for Japanese copy, etiquette, and workflow understanding. Operators still review templates, target assumptions, and execution steps in SalesBreaker.
Are API or CRM integrations available in this beta? v
The English Operator Beta focuses on the human control plane first. Programmatic execution and CRM integrations are planned and being developed separately.
What happens when a target form cannot be completed? v
The attempt can be marked as failed, not eligible, suppressed, or needs review depending on the condition. The operator should review the outcome and decide the next step.
What happens after the 3-day operator trial? v
A payment method is required. Unless canceled before the trial ends, the selected paid plan starts automatically. There is no free tier or downgrade-to-free flow for English Operator Beta.
Should I use a dedicated inbox? v
Yes. For higher-volume outreach, use a dedicated inbox separate from your primary business email. Contact-form replies and automated notifications can arrive at volume.
GPT support
Use the GPTs as operator education, not autonomous execution.
Japan GTM Assistant helps with Japanese outreach copy and etiquette. SalesBreaker English Guide explains lanes, history, suppression, JST, and operator workflow.
Ready to operate?
Start with the English operator entry.
Create an English beta account, choose execution capacity, and review the Japan-native workflow before running outreach.