Handling 'Just One More Thing': Drawing the Line on Extra Work

Just before delivering a web project, a client calls. "Thank you for your hard work. I've reviewed the nearly finished version, but there's just one more thing I'd like to ask..." Almost no freelancer hasn't experienced this scenario.

Let's look at a specific case. Web designer A, who contracted an e-commerce site for ¥300,000 per month, received three additional requests one week before delivery: "I'd like to change the product page layout a bit," "Add five more contact form fields," and "Also, a simple blog function would be great."

Estimating the workload for these tasks: 8 hours for layout changes, 4 hours for form field additions, and at least 20 hours for blog function implementation. That's a total of 32 hours, equivalent to ¥96,000 at ¥3,000 per hour. However, the client's tone suggested they viewed these as "minor changes" that "seem easy to do."

In such situations, most freelancers face two dilemmas. First, the fear that refusing will make them appear "inflexible" and "damage the relationship." Second, the concern that providing free service creates the impression of being "someone who does everything," leading to unlimited additional requests thereafter.

In fact, according to the Freelance White Paper 2023, 73% of respondents answered they had "experience performing work outside the contract scope for free," with 42% of those performing "more than 10 hours of unpaid work per month." This is not merely an individual problem but a structural industry-wide issue.

This section analyzes the structural problems behind additional work requests and the perception gaps between clients and contractors.

Client-Side Psychological Mechanisms

At the root of "just one more thing" are three psychological patterns specific to clients.

Pattern 1: Underestimating Work Hours For non-IT clients, the labor involved in digital deliverables is invisible. A request to "change button color" actually requires CSS modification, testing, functionality verification across devices, and production deployment—multiple processes. However, clients see it as "simple work that changes with one click."

Pattern 2: "While You're At It" Expectations The psychology of "since you're already at the computer" or "while we're at it" comes into play. It's similar to asking "trim my eyebrows too" at a barber shop. However, unlike cooking or cleaning, creative work requires independent specialized processes for each task.

Pattern 3: Relationship Dependency Long-term business relationships or personal connections create recognition as "someone easy to ask," lowering the barrier for additional requests. Emotional expectations like "we've always worked together" blur business boundaries.

Structural Problems in Contracts

In many cases, the seeds of problems lie within the contracts themselves.

Ambiguous Deliverable Definitions A description like "corporate website development" leaves unclear the number of pages, functional scope, supported devices, and presence of content management systems. It's common for "what's normally included in a website" to differ significantly between parties.

Absence of Change and Revision Handling Rules Phrases like "includes minor modifications" or "reasonable changes will be accommodated" only broaden interpretation without creating practical boundaries. There are no objective standards for what constitutes "minor" or "reasonable."

Unestablished Additional Work Pricing Structure Without predefined hourly rates, minimum billing units, or quotation procedures, responses to additional requests become ad hoc.

How Contractor Response Patterns Create Vicious Cycles

Initial contractor responses determine the subsequent relationship dynamic.

Accumulation of "Just This Once" Responses When you handle the first small additional request for free, clients recognize this as "standard service." Second and third requests get justified with the logic "you did it before."

Unclear Refusal Criteria Continuing emotional judgments like "this seems reasonable" or "considering the relationship" makes even you lose track of boundaries. This creates a vicious cycle where larger additional requests become harder to refuse.

Understanding this structure sets the stage for examining specific judgment criteria and response methods in the next section.

This section provides clear criteria for deciding whether to "accept," "decline," or "conditionally accept" out-of-scope requests, supported by practical frameworks.

Three-Axis Classification Method

Systematic evaluation of additional work uses the following three axes:

Axis 1: Time/Cost Impact

• A-level (under 30 minutes): Minor fixes that can be handled immediately
• B-level (0.5-3 hours): Small-scale work completed same day to next day
• C-level (over 3 hours): Full-scale work requiring formal additional contracts

Axis 2: Impact on Existing Deliverables

• Localized impact: Changes contained to relevant sections only
• Chain impact: Requires adjustments to other pages/functions
• System-wide impact: Necessitates comprehensive system review

Axis 3: Urgency/Necessity

• Essential: Level that would impair delivery/operation
• Important: Better to have but not essential
• Desired: Client wishlist level

Using the Decision Matrix

Here are decision examples combining these three axes:

Immediate Response Pattern (A-level time × localized impact × essential) Examples: Correcting typos, fixing obvious display issues Response policy: Handle immediately for free as part of quality management

Conditional Response Pattern (B-level time × chain impact × important) Examples: Main visual replacement, contact field additions Response policy: Present additional fees and coordinate schedule

Formal Contract Required Pattern (C-level time × system-wide impact × desired) Examples: New feature additions, major design changes Response policy: Create separate estimate and handle as new contract

Objective Evaluation Through Hourly Rate Conversion

To avoid emotional decisions, develop the habit of converting all additional work to hourly rates.

Setting Standard Hourly Rates For monthly contracts: Contract amount ÷ estimated hours = hourly rate Example: For a ¥300,000 monthly project with 100 estimated hours, hourly rate = ¥3,000

Setting Minimum Billing Units Establish a minimum billing rule where work under 30 minutes still counts as "0.5 hours." This prevents revenue opportunity loss from accumulated "small tasks."

Decision Templates for Declining, Accepting, and Deferring

Standardize response patterns based on decision results.

Conditions for Declining

• C-level hours or above with clear out-of-scope work
• System-wide impact that would affect other projects
• Wishlist-level requests without urgency

Conditions for Accepting

• Within A-level hours contributing to quality improvement
• Important for maintaining long-term client relationships
• High possibility of future additional orders

Conditions for Deferring/Conditional Offers

• B-level hours with feasible appropriate pricing
• Possible with schedule adjustments
• Prospect of client budget securing

Using this framework enables decisions about declining additional work based on objective criteria rather than emotions.

This section explains specific communication skills for maintaining client relationships while appropriately declining requests—the most important aspect of handling "just one more thing" situations.

Basic Structure and Phrases for Declining

Effective declining follows a four-stage structure:

Stage 1: Express Gratitude and Understanding "Thank you for consulting with us" "I've reviewed the details of the XX matter"

Stage 2: Objective Current Situation Explanation "Upon review, this work is not included in the original contract scope" "Calculating the hours, approximately X hours of work would be required"

Stage 3: Clear Reasoning "Given current schedules, impact on other projects would be unavoidable" "To maintain quality standards, securing additional time would be necessary"

Stage 4: Alternative/Next-Best Option Proposals "We could create a separate estimate" or "We could handle this in the next phase"

Specific Declining Message Patterns

Pattern-specific examples for actual situations:

Declining Due to Excessive Hours "I've reviewed your request in detail. This change would require approximately 8 hours of work time, significantly exceeding the originally contracted scope. To ensure quality response, may I propose an estimate of ¥24,000 additional fee (¥3,000/hour × 8 hours)?"

When Schedule Coordination Is Difficult "I've reviewed the content and judge it technically feasible. However, due to other ongoing projects, response within this month would be difficult. From the second week of next month onward, I could accept this as additional work. If urgent, I could consider a simplified version—how would that work?"

Clear Out-of-Scope Boundary Setting "This request moves from website development into system development territory. While we can handle it, since it's a different specialized field from the original contract, I'd like to create a separate project estimate. Shall we start with basic requirements gathering?"

Cushioning Expressions and Relationship Maintenance Techniques

Expression techniques to soften the impression when declining and maintain ongoing relationships:

Clarifying Responsibility While Avoiding Blame ×"That's not in the contract, so we can't handle it" ○"Checking the contract, this would need to be organized as additional work"

Presenting as Condition Issues Rather Than Impossibilities ×"We can't do that" ○"Response would be difficult under current conditions, but possible if XX could be adjusted"

Suggesting Future Collaborative Relationships "While difficult this time, we could incorporate it from the beginning in the next project" "Using this experience, let's conduct more detailed requirements definition going forward"

Conditional Proposal Methods That Leave Room for Negotiation

Techniques showing that acceptance is possible depending on conditions rather than complete refusal:

Staged Response Proposals "Full-feature implementation would be large-scale, but we could start with basic functions only and expand while monitoring progress"

Multiple Options by Budget

• Option A: Complete response (¥80,000, 2 weeks)
• Option B: Basic functions only (¥30,000, 1 week)
• Option C: Incorporate into next project (separate estimate, from next month)

Solutions Through Delivery Adjustments "If you could extend the original delivery by one week, we could respond without additional charges"

Using these techniques transforms "declining" into positively "exploring better solutions."

This section details specific preventive measures and boundary setting methods that should be established at the contract stage to fundamentally prevent additional work problems.

Techniques for Specifying Deliverable Definitions

Ambiguous contracts are the biggest cause of additional requests. Define the following elements specifically:

Clear Enumeration of Page Count and Functions ×"Corporate website development" ○"Total of 4 pages: top page, company overview, business introduction, contact. Includes contact form function. Does not include blog function or member registration function"

Device and Browser Limitations "Display optimization for PC (Windows Chrome, Edge) and smartphone (iOS Safari, Android Chrome). Tablet display and Internet Explorer operation guarantee are out of scope"

Pre-set Revision Count and Scope "Includes up to 2 revisions per page. 3rd revision onward: ¥5,000 additional fee per revision. Revisions refer to adjustments of existing elements and do not include addition of new elements"

Standardizing Additional Work Pricing Structure

Clearly document pricing calculation rules for when additional requests occur.

Hourly Rates and Minimum Billing Units "Additional work hourly rate: ¥3,000 (excluding tax) Minimum billing unit: 0.5 hours Work under 30 minutes calculated as 0.5 hours"

Fixed Pricing by Work Category

• Minor modifications (color changes, text corrections, etc.): ¥5,000
• Page additions: ¥20,000/page
• Function additions: Separate estimate (minimum ¥30,000~)

Quotation Process "When receiving additional work requests, we will provide hour estimates and pricing within 48 hours. Work begins after approval"

Clearly Stating "What's Not Included"

Negative lists are as important as positive lists.

Technical Constraint Clarification "Third-party system integration, custom system API connections, SSL certificate acquisition and setup are not included"

Operation and Maintenance Scope "Post-delivery content updates, server maintenance, domain management require separate contracts"

Design Change Limitations "Major layout structure changes and complete color theme changes are treated as new design work"

Creating Client Education Systems

Build educational processes to deepen client understanding at contract time.

Pre-explaining Production Flow "At each stage of planning → design → coding → testing → delivery, major returns to previous stages incur additional fees"

Showing Cost Differences by Change Timing

• Planning stage changes: Free
• Design stage changes: 30% premium
• Coding stage: 50% premium
• Testing stage onward: 100% premium

Regular Progress Reports and Checkpoints "Please confirm at each stage completion. Changes after confirmation completion are treated as additional work"

Ensuring Flexibility for Long-term Relationships

Overly rigid contracts can harm relationships. Appropriate flexibility is also necessary.

Defining "Reasonable Range" "Minor adjustments within 1 hour monthly handled free to maintain long-term cooperative relationships. However, advance notice is mandatory"

Comprehensive Agreements in Annual Contracts "Annual contracts include up to 5 hours monthly additional work. Excess can carry over to following month (maximum 3 months)"

Special Rules for Emergency Response "After-hours and holiday emergency response: 50% premium fee. However, emergency contact methods and conditions confirmed in advance"

These preventive measures reduce additional requests themselves and create systems for smooth handling when they do occur.

This section lists typical failure patterns contractors fall into when handling additional work and specific countermeasures to avoid them.

Failure Pattern 1: Continuous "Just This Once"

Typical Scenario Handled first small additional request for free "just this once, considering the relationship," then received an even larger request two weeks later. Logic of "you did it before" made refusal difficult, resulting in 20 hours monthly unpaid labor.

Root Causes of Failure

• "Just this once" becomes self-justification
• Free response becomes learned as "standard service" for clients
• Boundary criteria are emotional and inconsistent

Specific Countermeasures Create an "additional work log" recording all extra tasks, calculating total hours and value monthly. Before deciding "just this once," check cumulative unpaid hours for the past 3 months.

When cumulative unpaid time exceeds 5 hours monthly, clearly communicate to client: "We've been providing service responses so far, but please understand we'll transition to appropriate fee structure going forward."

Failure Pattern 2: Scope Expansion After Work Begins

Typical Scenario Accepted "text correction within page" request and began work, then received sequential additional demands: "Also adjust layout a bit while you're at it" and "Replace this image too." Before realizing, workload had tripled from original.

Root Causes of Failure

• Insufficient scope confirmation before starting work
• Unprepared for declining "while you're at it" requests
• No rules set for mid-work scope changes

Specific Countermeasures Always send "work scope confirmation email" before starting. "Today I will perform the following work:

1. Change top page heading text from 'XX' to 'YY'
2. Replace representative photo on company overview page Is this correct? For additional requests, I will provide separate estimates."

When additional requests come during work, always pause current work and respond: "I'll send an estimate for additional items after completing current work."

Failure Pattern 3: Judgment Weakness Due to Urgency

Typical Scenario Accepted work normally declined for free due to "urgent, need by tomorrow for presentation" request. Later confirmed actual presentation was one week away.

Root Causes of Failure

• Taking client "urgent" statements at face value
• Unprepared emergency response conditions and pricing
• Psychological hurdle for declining too high

Specific Countermeasures When receiving emergency requests, always confirm: "Understood regarding emergency response. Please confirm:

1. Specifically when is this needed?
2. What would be the impact if this work is delayed?
3. This would be emergency response pricing (50% premium over normal rates)—is this acceptable?"

Even when urgency is genuine, always charge appropriate compensation. Free emergency response creates misunderstanding of "always available for free response."

Failure Pattern 4: Problem Postponement Through Ambiguous Responses

Typical Scenario Responded ambiguously to additional requests with "I'll consider it" or "let me check," avoiding clear answers. Client perceived this as "accepted," leading to troubles.

Root Causes of Failure

• Psychological resistance to declining
• Unclear judgment criteria
• No response deadline set

Specific Countermeasures Always set response deadlines when receiving additional requests. "Understood. I'll check hours and pricing and respond by tomorrow morning."

When uncertain about decisions, apply the aforementioned framework mechanically. To avoid emotional decisions, document judgment reasoning.

Failure Pattern 5: Excessive Consideration for Long-term Clients

Typical Scenario 3-year continuous monthly contract client said "we've worked together long, please do this as service," leading to accepting major additional work for free. However, next month's contract renewal reduced monthly payment 20% citing budget cuts.

Root Causes of Failure

• Excessive expectations and dependence on long-term relationships
• Confusing "obligation" with "business"
• Insufficient objective profit analysis

Specific Countermeasures Long-term clients especially require maintaining healthy commercial relationships. Review business conditions annually, confirming numerically:

• Annual unpaid response hours and value
• Condition comparisons with other clients
• Revenue stability from continued contracts vs. opportunity loss from new business development

Clarify position: "To maintain long-term cooperative relationships, I believe receiving appropriate compensation is healthy for both parties."

By recognizing these failure patterns in advance and preparing countermeasures, you can significantly reduce additional work problems.

Here are specific action guidelines for freelancers and creatives to solve the "just one more thing" problem and build sustainable business relationships.

First, immediately conduct an inventory of additional work situations with all current clients. Calculate unpaid response hours for the past 6 months and convert to hourly rates to quantify "invisible losses." This provides objective understanding of problem severity.

Next, review existing contracts. List ambiguous sections regarding deliverable definitions, revision scope, and additional work handling as improvement points for next renewal. For new contracts, apply clear boundaries using frameworks introduced in this article.

Most importantly, document judgment criteria for additional work and create systems for objective indicator-based decisions rather than emotional ones. Make the three-axis evaluation of hours, impact, and urgency habitual, and secure consultation partners (professional communities, etc.) for uncertain decisions.

In client communication, master techniques for converting "declining" into "proposing better solutions." Create templates for declining methods usable from today and practice in actual situations.

Long-term, aim to build revenue structures not dependent on additional work. By setting appropriate basic fees, create conditions where "business operations aren't affected whether you accept additional requests or not"—this leads to true problem resolution.

Healthy business relationships enable equal-standing value exchange between contractors and clients. This requires balancing appropriate compensation demands for expertise with long-term partnerships. Please implement this article's content gradually to build sustainable freelance business foundations.