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.
What happened
A Japanese company asks your overseas software business for a number to put into its budget request. The proposed data migration is still undefined: there may be three to five data types, and nobody has agreed the transformation rules. A polished price document could conceal those gaps instead of helping the buyer decide what to clarify.
In the fictional example below, known work is estimated at USD 3,000 and a bounded transformation stage at USD 500–1,500. The resulting planning range is USD 3,500–4,500. These are invented planning inputs, not market prices, a live customer quote or an observed range for Japanese projects.
Prepare a budget note that keeps the calculation, assumptions and route to a final proposal together. This guide addresses uncertainty in the price, while the deliverables guide helps define what you will produce. Neither a budget label nor a software status decides the legal effect of a document.
What’s going on on the Japanese side
Confirm which decision the estimate is meant to support
Ask whether the buyer needs internal budget approval, supplier comparison or a proposal it intends to order against. Confirm the purchasing entity, requested format, currency, decision date and any requested validity period. Do not assume a contact asking for a “quote” means the same stage that you mean.
| Buyer’s intended use | What to provide now | What remains to confirm |
|---|---|---|
| Reserve an internal budget | Dated range with assumptions and open questions | Whether the buyer can use a range and understands its limits |
| Compare suppliers | Range plus a comparable scope and exclusions | Whether the other figures include the same work and amount basis |
| Place an order | Explain what prevents a final proposal | Required facts, decision owners and next proposal stage |
If the buyer’s form requires a single amount, ask whether it accepts the upper planning figure with the range and assumptions attached. Do not enter a midpoint or maximum as an unconditional price merely to complete a form. If that presentation would mislead the approving person, resolve the format first.
Stripe documents product statuses including draft, open, accepted and canceled. Its open quote is finalized and awaiting customer action; acceptance can generate an invoice or subscription-related record. This supports a distinction between product workflow states, not a universal classification of informal estimates or a conclusion about contractual effect. Source
You do not need Stripe or another quoting service to prepare the note. Ask how your buyer will use and circulate it, and identify the intended status in ordinary language. Where an existing commitment or legal effect is disputed, obtain advice rather than relying on the word “estimate.”
Build the range from work and uncertainties you can actually describe
Separate known tasks from variable tasks. For each variable, identify what changes the effort and what evidence supports the lower and upper scenario. A percentage added to an undefined project does not explain the uncertainty.
In this fictional model, “data type” means a distinct source dataset with its own fields and mapping rules, not every database column. The initial inventory suggests three to five such datasets. Count alone does not determine the transformation effort: their quality, record volume and mapping complexity still need examination.
| Work element | Lower planning input, USD | Upper planning input, USD | Basis and limit |
|---|---|---|---|
| Known preparation, migration setup and agreed checks | 3,000 | 3,000 | Assumes the scope and environment listed below |
| Bounded transformation stage | 500 | 1,500 | Illustrative lower/upper effort scenarios; rules still to confirm |
| Planning total | 3,500 | 4,500 | Sum of the two rows, not a fixed offer |
For this fictional estimate, the lower transformation scenario assumes direct field mappings and format normalization across three datasets. The upper assumes up to five datasets, agreed lookup mappings and date-format rules, plus a documented exception list; reconstructing missing records is excluded. These are proposed assumptions, not findings from inspected samples, and the amounts are illustrative effort estimates to validate before relying on the range.
The lower calculation is 3,000 + 500 = 3,500; the upper is 3,000 + 1,500 = 4,500. The USD 1,000 spread comes from the transformation scenarios. It is not a contingency percentage, a confidence interval or permission to charge the upper amount.
What to do next
Put assumptions and exclusions beside the amount
- Define the boundary of the range. The fictional note assumes three to five identified datasets, one migration run, access to a suitable test environment and a buyer-provided reviewer. It assumes the transformation work remains within the described scenarios. A discovery that invalidates these assumptions requires a new assessment, not automatic use of USD 4,500.
| Assumption or exclusion | How to express it | Next confirmation |
|---|---|---|
| Data inventory | Three to five identified source datasets | Buyer supplies inventory and approximate record counts |
| Quality and transformations | Limited to the proposed lower/upper conditions; sample validation pending | Validate representative samples and rules before a final proposal |
| Environment | Buyer provides agreed test access and destination specification | Technical contact confirms availability and constraints |
| Migration and review | One migration run and the expressly described checks | Confirm what the run covers, reviewer and acceptance criteria |
| Additional work | Ongoing maintenance, further migrations and unrelated remediation outside this range | Separate scope discussion if needed |
| Taxes and other charges | Tax treatment and payment charges unresolved; not assessed in these illustrative service amounts | Determine the applicable treatment before final pricing |
Do not type zero tax because its treatment is unknown. A service-price range with an unresolved tax field is not an all-in cash budget. Ask what amount basis the buyer’s approval process requires and identify the unresolved amount separately.
- Keep omissions visible. If the buyer expects ongoing support or repeated production migrations, the current range does not cover that requirement. Add a separately described planning item only when you can support it. Do not let an exclusion below the table contradict an unqualified headline total.
Gather the minimum facts needed for a final proposal
- Request evidence that reduces the actual uncertainty. Ask for a dataset inventory, approximate volumes, representative anonymized or synthetic samples, required transformations, destination constraints and the person who will confirm the result. Record who will supply each item and what question it answers.
A sample should show the relevant structure and quality problems without exposing customer records. Use an approved secure route if confidential information is later necessary, and agree access before requesting it. Do not paste production datasets into a public worksheet or an unapproved AI service.
| Missing fact | Decision it enables | Completion evidence |
|---|---|---|
| Inventory and counts | Confirm the number and size of datasets | Dated inventory from the technical contact |
| Representative samples | Check whether assumed quality conditions hold | Sample review notes with sensitive content excluded |
| Transformation rules | Describe mappings, exceptions and unresolved cases | Buyer-confirmed rule list and questions remaining |
| Review responsibility | Agree how the migrated result will be checked | Named coordinating reviewer and proposed criteria |
A final proposal becomes possible when the scope, rules, responsibilities, price basis and delivery assumptions are sufficiently defined. It does not follow automatically from receiving a file. Use the quotation checklist once those decisions are ready to record.
Use clarification when a defensible range is not yet possible
- Choose the next step based on the uncertainty. If only a bounded quantity varies and you can support the effort scenarios, a range may help. If the purpose, data condition or transformation requirements are unknown, say which missing facts prevent a defensible figure. Do not invent a larger range to hide the absence of a basis.
For unbounded uncertainty, propose a clarification stage with its own output, such as an inventory and mapping assessment. Identify which preliminary questions you will answer without charge and which proposed investigation would be separately priced. Paid discovery needs its own scope and agreement; sending samples or continuing a conversation does not constitute approval of that fee.
Hand over a dated note with a route to the final quote
- Send the whole decision record. Include purpose, reference, preparation date, range, calculation, assumptions, exclusions, missing facts and conditions for the next proposal. Confirm any validity or recheck date with the buyer rather than inventing urgency. Preserve the note when it is revised.
For the fictional project, a note prepared on 9 November 2026 could say “internal budgeting discussion; final proposal pending data and rule review.” The date is an example, not the current date. Record the buyer’s response and the next fact owner; avoid treating silence as approval.
If a proposal has already been sent and needs changes, use the quotation revision guide. If a project has already been accepted, clarify the applicable change process rather than rewriting it as an informal budget exercise.
Template
Ask the buyer to confirm the purpose and unresolved inputs
Replace the fictional amounts and scope. The two versions communicate the same planning status without declaring the document legally nonbinding.
Subject: Budget planning range — proposed data migration
Is this figure for internal budgeting only?
Our planning range is USD 3,500–4,500: USD 3,000 of known work
plus USD 500–1,500 for the described transformation stage.
It assumes three to five datasets, one migration run and the agreed
test environment. Ongoing maintenance and additional migrations are excluded.
Tax treatment and payment charges still need confirmation.
To prepare a final proposal, we still need the dataset inventory,
representative anonymized samples, transformation rules and review owner.
Please confirm whether your budget process can use this range and
who will supply the missing information. The range needs reassessment
if the stated assumptions do not hold.
件名:データ移行案の予算検討幅
この金額は社内予算検討用でしょうか。
予算検討幅は3,500~4,500米ドルです。既知作業3,000米ドルと、
記載した変換工程500~1,500米ドルの合計です。
3~5種のデータセット、移行1回、合意するテスト環境を前提とし、
継続保守や追加移行は含みません。税の扱いと支払費用は確認が必要です。
正式提案には、データ一覧、匿名化した代表サンプル、変換ルール、
確認担当者が必要です。この幅を予算検討に使えるか、不足情報を
誰が提供するかをご確認ください。前提が成立しない場合は再評価が必要です。
When to bring in a professional
Get advice on disputed commitments or unresolved tax treatment
A technical specialist can assess data quality and migration risks. Seek qualified legal advice about disputed commitments or the effect of a document, and appropriate tax advice before completing unresolved tax fields. The planning method does not determine applicable law or authorize a change to an existing agreement.
Kit
Record the unknowns with the tools you already use
The note works in an existing document or spreadsheet. The free First-Quote Starter can organize unresolved quote inputs; it does not calculate this range or validate the assumptions. No purchase is needed. Use the overall selling workflow for the steps surrounding the eventual proposal.
This guide goes stale when
- Stripe changes the quote statuses described in its documentation.
- The input data, transformation rules or assumptions supporting the estimate change.
Sources
| Publisher | Document | Checked |
|---|---|---|
| stripe | Stripe — How quotes work | October 31, 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.
-
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.
-
Define the billable unit before multiplying the price
Agree which source words, files and embedded text a translation quote covers, then give your Japanese buyer a count record and reproducible subtotal.
Get the next guide by email
Two emails a month: new guides, and what changed on the Japanese side. Unsubscribe in one click.