Turn a vague client brief into quoteable deliverables
Define quantities, client inputs, review rounds and exclusions before quoting a Japanese client. Includes a worked brochure scope and bilingual confirmation.
What happened
You work outside Japan and a Japanese company asks you to “prepare an English version of our sales brochure.” Nobody has said whether you are translating, rewriting or laying out supplied English copy.
Consider a fictional Singapore-based designer quoting to a Japanese manufacturer. The proposed output is a twelve-page English brochure, delivered as a PDF and an editable design file; translation would come from the client. The buyer is also considering four extra pages, but has not selected them.
This example’s quantities and arrangements are invented, not market rates or a Japanese standard. Prepare a scope block showing your outputs, the buyer’s inputs and what prevents a firm proposal.
What’s going on on the Japanese side
Name the deliverable instead of quoting an undefined service
JETRO provides English business correspondence for exporters from Japan, including a covering email that describes a quotation’s pricing, terms and specifications. That is a document example, not a rule for an overseas provider selling into Japan. Source
Takeda asks suppliers to report purchase-order discrepancies in price, quantity, delivery time and unit of measure to their contact. Those are Takeda’s instructions, not a shared Japanese purchasing policy. Source
In this worked example, define a page as one finished PDF page, including the front and back covers. Twelve source pages do not necessarily become twelve English pages; confirm the finished count against the proposed layout before treating it as fixed.
| Scope field | Proposed brochure definition | What the buyer must confirm |
|---|---|---|
| Purpose and audience | English product overview for prospective distributors | Intended readers and content priorities |
| Finished quantity | Twelve PDF pages, including both covers | Approved page map and content that fits it |
| Designer’s work | Layout of supplied English copy and approved images | Whether new diagrams or image editing are also needed |
| Outputs | PDF plus editable design file | Page dimensions, PDF use, design application and version |
| Content baseline | Named English copy version and asset list | Which files are final enough to price against |
Do not leave “editable file” as the entire handover specification. Identify the application/version, included linked assets and any items the recipient must license separately. File delivery and permission to use third-party materials are different questions; do not promise ownership of everything inside the file.
Separate client inputs from work you will supply
The phrase “English version” describes an output language, not who translates the text. Ask whether the client will supply final English copy or wants translation priced separately. If the answer is unknown, label it as unresolved rather than quietly excluding translation in a footnote.
This responsibility map proposes arrangements, not legal duties.
| Input or task | Proposed owner | Evidence needed before fixing the scope |
|---|---|---|
| English text and technical terminology | Client | Approved copy file, version and content reviewer |
| Translation from Japanese | Client’s chosen translator | Confirmation that translation is outside the designer’s base work |
| Logo, images and permission to supply them | Client | Asset list and any restrictions relevant to delivery |
| Layout and PDF production | Designer | Confirmed page map and output specification |
| Copy rewriting and new illustrations | Not included in base proposal | Separate description and price if requested |
Keep confidential files in the agreed private location. Record references and responsibility here; a filename alone does not establish approval.
What to do next
Define one review round through a visible input and response
- Propose a review unit before adding an allowance. For this example, propose two rounds, each consisting of one consolidated annotated PDF from the buyer’s nominated coordinator and a revised PDF responding to that list. Ask the buyer to confirm the unit, who consolidates conflicting comments and what marks completion of a round.
Separate corrections against the agreed input from changed preferences and new content. State how errors and later comments will be handled; do not describe every email as a new round or treat your own production error as an automatic paid addition. Two rounds are a negotiable term in this example, not a default entitlement.
- Make the completion check observable. Propose checking page count, presence of approved copy and images, PDF readability, editable-file opening requirements and resolution of the agreed review list. Ask who will check each item and how they will report the result. A stated goal such as “more persuasive” needs concrete content or layout criteria before it can serve as a completion test.
For feedback on accepted work, use the separate guide to included revisions and new requests rather than rewriting the accepted allowance retrospectively.
Put exclusions and optional work beside the base scope
- Show what is being priced and what is not selected. Keep the proposed twelve-page base separate from the possible four-page addition. If the addition is agreed, the finished count becomes sixteen pages; that arithmetic does not determine the extra design effort or establish an agreed per-page rate.
| Item | Scope status | Treatment in the proposal |
|---|---|---|
| Twelve-page layout, PDF and specified editable file | Proposed base | Price after confirming inputs and output specification |
| Four additional pages | Optional, not selected | Separate scope and price; exclude from the base total |
| English translation and copy rewriting | Outside proposed base | Ask whether the buyer wants a separate quotation |
| Print procurement and physical delivery | Outside proposed base | Do not imply that a PDF delivery includes printed brochures |
| Rights or licences beyond those specified | Unresolved where relevant | Clarify before promising the affected handover or use |
Check whether the PDF is for screen use or print production. If the buyer needs a printer-ready file, obtain that printer’s requirements before committing to it. Do not treat printing as an included task because the project happens to be called a brochure.
Choose a fixed scope, an explicit assumption or a clarification step
- Choose the next step according to the unanswered question.
| Current evidence | Practical next step | What remains unconfirmed |
|---|---|---|
| Finished quantity, input versions and output requirements are confirmed | Prepare the defined scope for pricing | Commercial terms and authorization to proceed |
| Purpose is clear but finished page count is provisional | State the provisional count and how it will be confirmed before a firm offer | Final quantity and any resulting price or schedule change |
| Translation or rewriting responsibility is unknown | Ask the buyer to choose who supplies that work | Whether the base proposal can exclude it |
| Audience, content or success criteria are not settled | Propose a bounded clarification stage, if useful | Its own deliverable, price and approval, separate from production |
A clarification stage might produce an agreed page map and missing-input list. Obtain agreement before starting a paid stage; a quote request is not an instruction to perform extra work. Do not present the finished brochure as a fixed-price commitment while its essential scope remains unresolved.
Send a scope block the project owner can confirm
- Return a brief decision request with the proposed scope attached. Identify the proposal version, the fields ready for confirmation and the specific unanswered question. Ask the existing contact who can confirm content and who handles purchasing; a helpful reply from one person does not establish every approval needed to start.
Before sending, check that the scope shows:
- The finished deliverable, unit and quantity, with covers and optional pages treated consistently.
- The exact input responsibility, file version and output format.
- The proposed review unit, coordinator and completion checks.
- Exclusions, unselected options and unresolved rights or licence questions.
- The next decision, its owner and any schedule dependency.
Use the full quotation checklist for price, currency, payment terms and document references after the scope is clear. If an earlier unaccepted quotation needs changing, preserve its version and use the quotation revision record.
Template
Confirm the translation responsibility before pricing the base scope
Adapt this single bilingual request to the actual proposal. Both versions ask for clarification, not authorization to start work.
Subject: Scope confirmation before the brochure quotation
The proposed base scope is a twelve-page English brochure, including
both covers, delivered as a PDF and the specified editable design file.
It assumes your team supplies final English copy and approved assets.
Translation, copy rewriting and print ordering are outside this base.
The possible four extra pages are optional and not yet selected.
Will your team supply the final English copy, or should translation
be quoted separately? Please also identify who can confirm the page
map, output requirements and proposed consolidated review process.
I will use those answers to prepare the quotation; this message does
not request authorization to start production.
件名:パンフレットの見積作成前の業務範囲確認
基本案は、表紙・裏表紙を含む全12ページの英語パンフレットを、
PDFと仕様を確認した編集可能なデザインデータで納品する内容です。
確定した英文原稿と使用可能な素材を貴社からご支給いただく前提で、
翻訳、英文の書き直し、印刷発注は基本案に含みません。
追加4ページはオプションで、まだ選択されていません。
確定英文原稿は貴社でご用意いただけますか。それとも翻訳を別途
見積もる必要がありますか。ページ構成、納品仕様、ご意見を取り
まとめる確認手順について、回答いただける担当者もお知らせください。
回答をもとに見積書を作成します。本メールは制作開始の承認を
お願いするものではありません。
When to bring in a professional
Escalate rights and disputed obligations rather than guessing from file formats
You can describe outputs, inputs and open questions with the project contact. Ask a qualified legal adviser about disputed scope, intellectual-property ownership, licence restrictions or contract terms. A translator or subject specialist can check whether supplied English copy conveys the intended technical content; the designer’s layout review does not establish that accuracy.
Kit
Put one unresolved scope question into your next quotation
Use the tables in your existing document, or open the free First-Quote Starter as a starting point. No paid kit is needed for this exercise. Transfer one unresolved input or output question, obtain the buyer’s answer, and then update the scope; the overall selling workflow places that step before ordering, delivery and invoicing.
This guide goes stale when
- JETRO changes its quotation correspondence or document examples.
- Takeda changes its published purchase-order review instructions.
- The proposed deliverables, input responsibilities or review arrangements change.
Sources
| Publisher | Document | Checked |
|---|---|---|
| jetro | JETRO overseas business support | October 30, 2026 |
| other | Takeda Third-Party Tools and Resources — Purchase Order Review | October 30, 2026 |
Was this useful?
More on Selling B2B
-
Japanese Client Requests Extra Work After Accepting Your Quote: Agree on the Change
Preserve accepted scope, price a requested addition, and ask your Japanese client to approve the work, delivery conditions and purchasing record.
-
Give a budget estimate without presenting it as a final quote
Build a defensible budget range from named uncertainties, show assumptions and exclusions, and identify what is needed for a final proposal.
-
Three buyer contacts give different instructions: map who owns each approval
Record conflicting project, procurement and onboarding instructions, ask the buyer to name a coordinating owner, and preserve one traceable answer.
Get the next guide by email
Two emails a month: new guides, and what changed on the Japanese side. Unsubscribe in one click.