How to Read Estimates: A Buyer's Guide to Market Rates and Validity

When you receive an estimate from an agency or freelancer, the five required elements to check are these. An estimate missing any of them becomes a source of later cost creep and misunderstanding.

Element 1: Line Items

A single-line "Website build: ¥X" is a red flag. At minimum, you should see this level of granularity:

• Requirements definition and planning
• Design (top page, subpages, shared components)
• Coding (HTML/CSS/JS)
• CMS implementation (e.g., WordPress)
• Testing and delivery
• Direction fees

When line items are bundled, you risk "that wasn't included" disputes down the line.

Element 2: Unit Rates

Unit rates for each line item should be visible. The basis matters — per-day rates, per-page rates, or flat rates all imply different billing logic for change orders.

Knowing typical per-day rates lets you reverse-engineer how many person-days an estimate's total implies. The rough bands below reflect what we observe in client projects rather than a public statistical average, but most engagements fall within them:

Note: These are editorial observations and vary substantially by agency involvement, region, experience, and project scale. For current market data, see public surveys from CrowdWorks, Lancers, or the Freelance Association, or see Freelance Pricing Strategies.

Element 3: Effort

"How many days is this expected to take?" must be visible. A line like "Design set: ¥300,000" gives no indication whether that's 3 days or 10 days of work. When effort is explicit, scope changes and schedule shifts can be quantified and discussed on the same basis.

Element 4: Assumptions

The conditions under which the estimate holds must be stated. Typical assumptions:

• "This assumes the client provides materials (photos, copy, logos)."
• "Up to two rounds of revisions per phase."
• "Acceptance period is five business days after delivery."
• "Development and production server environments are provided by the client."

An estimate without stated assumptions leaves room for later "the assumptions turned out to be different, so there's a surcharge."

Element 5: Exclusions

What is not included should be explicit:

• "Attendance at client internal meetings is not included."
• "Multilingual support is not included in this estimate."
• "Post-launch maintenance is not included."
• "Photo and video shoots are quoted separately."

If exclusions are listed, the client understands in advance that these items will cost extra if needed. Vendors that omit exclusions tend to bill for these items mid-project as surprises.

If one vendor comes in dramatically below the others, you must check these three points.

Pitfall 1: Long Exclusion List

The total is low because "X is excluded," "Y is separate," and so on — once you add all the missing items, the real cost matches or exceeds the other bids. Clients who decide based on the initial "cheap" total face a stream of change orders and end up over budget.

Pitfall 2: One-Round Revisions

"One revision per phase" is hidden in the assumptions to keep the total low. No design, code, or copy lands perfectly on the first try. One revision yields only a "direction check," and the next round triggers additional fees.

In most production workflows, two to three revision rounds per phase is the common norm, although the appropriate count varies with industry, scale, and timeline. Agree on the number of rounds in writing before the contract starts.

Pitfall 3: Zero Direction Fee

"We include direction fees as a service." Direction work — requirements definition, progress management, client communication — is actually happening, but it's either buried in other line items or skipped outright. When it's skipped, schedules slip and misunderstandings accumulate.

Refer to Agency Margin and Hidden Value for more on why direction costs exist. Direction fees are invisible but essential to project success.

When one vendor is dramatically higher, you need to distinguish "unjustifiably expensive" from "expensive for a reason."

Reason 1: Heavier Direction and Strategy Effort

An estimate with generous strategy-phase effort looks high up front. But this pattern reduces post-launch rework costs, so total cost often ends up lower.

Reason 2: Specialist Domain Expertise

Agencies with deep knowledge in specific domains (medical, legal, finance) cost more per day — but the communication cost during requirements definition drops dramatically, and legal risk is mitigated.

Reason 3: Broader Warranty

"X months of free bug fixes after launch," "accessibility guarantees," "security audit included" — these warranty scopes increase the headline number but bundle in risk mitigation.

Signs of Unjustified Markup

• Total is large but no itemization
• Assumptions and exclusions are vague
• Same effort as other vendors, but higher unit rates
• Sales contacts cannot answer specific questions

These are signs the vendor is targeting clients who don't know the market.

The iron rule when requesting multiple quotes: align the assumptions. Gathering quotes under different assumptions produces a pile of non-comparable numbers.

How to Request Under Identical Assumptions

1. Write a Request for Proposal (RFP) — at minimum, cover the following nine items in one or two A4 pages:
   • Project purpose and background
   • Target users / personas
   • Scope (in and out)
   • Page list or functional requirements
   • Quality requirements (browser support, accessibility, etc.)
   • Timeline and major milestones
   • Budget range (e.g., "under ¥X million")
   • Evaluation criteria (how you will decide)
   • Contact and deadline for questions
2. Send the same RFP to all vendors — not "please quote your proposal" but "please quote based on this RFP"
3. Specify response deadline and format — uniform format makes comparison easy
4. Offer Q&A opportunities simultaneously — don't give extra information to one vendor only

Comparison Dimensions

Don't compare by unit rate alone. Evaluate on five dimensions:

Don't pick the cheapest total immediately. A mid-priced vendor with clear assumptions and honest Q&A usually produces a more successful project.

Step 1: Five-Element Check

Don't decide right away. Run the five-element check. If anything is missing, ask for supplemental documentation or explanation.

Step 2: Ask Unclear Points in Writing

"What specifically does this line item cover?" "Is 'two revisions' two per phase or two total?" — always clarify ambiguity in writing. Verbal clarifications are the source of later "he said, she said" disputes.

Step 3: Cross-Check Against Market Rates

Cross-check the unit rates you received against references like /estimation/understanding-fair-pricing and /estimation/why-competitive-bidding-fails.

Step 4: Formalize Final Agreement

Confirming the selected estimate by email alone is insufficient. Sign a service agreement, and attach the estimate as an exhibit. Include a clause in the main body along the lines of "the scope and compensation under this agreement are governed by the attached estimate dated YYYY-MM-DD," so that the assumptions and exclusions carry legal weight as part of the contract. See also 10 Clauses Every Client Needs for the main contract items.

If you are about to commission work, start by writing a one-page RFP that captures your goals, page count, features, timeline, and budget range. That single page improves both your own clarity and the quality of the estimates you receive.

If you have already received estimates, run the five-element check immediately. If anything is missing, request supplemental information in writing. That one round trip significantly raises project success rates.

References

Guidelines for Creating a Safe Working Environment for Freelancers (2021)

Act on Ensuring Appropriateness of Transactions Involving Specified Commissioned Businesses (Freelance Protection Act) (2024)

Act against Delay in Payment of Subcontract Proceeds (2024)