Choosing Between Quasi-Mandate and Contract Work

This section clarifies the specific risks and losses that occur when the choice between quasi-mandate contracts and lump-sum contracts is made incorrectly.

"When I accepted a website creation project under a lump-sum contract, the client made endless revision requests, and I ended up earning 300 yen per hour." "When I made a marketing consulting project a quasi-mandate contract, the relationship deteriorated due to accountability for lack of results, and the contract was terminated." Such troubles arise from mismatches between project characteristics and contract types.

Looking at actual data, the Freelancers Association survey shows that about 40% of contract troubles stem from "misunderstandings about responsibility scope." This is not simply due to insufficient agreement, but because contract types are chosen without understanding the fundamental differences between quasi-mandate contracts and lump-sum contracts.

Common failure patterns on the contractor side are as follows. Choosing a lump-sum contract for system development projects based solely on the reason that "deliverables are clear," only to end up bearing the cost of additional development work arising from ambiguous requirements definition. Also, being attracted to high hourly rates in consulting work and choosing quasi-mandate contracts, but being unable to prove the legitimacy of contract continuation due to lack of clear deliverables, leading to early termination.

Typical mistakes on the client side are also serious. Choosing lump-sum contracts for projects where quasi-mandate would be appropriate for the reason of "wanting to reduce costs," leading to decreased contractor motivation and quality deterioration. Conversely, choosing quasi-mandate contracts despite wanting clear deliverables, failing to get expected results and incurring additional costs.

Taking a monthly 500,000 yen marketing support project as an example, with a quasi-mandate contract, the budget of 3 million yen over 6 months is fixed, but with a lump-sum contract setting "20% sales improvement" as the deliverable, if this cannot be achieved, the contractor is obligated to continue without compensation. On the other hand, even if achieved, if there's no agreement on additional compensation, the contractor's profit remains unchanged.

Such judgment mistakes lead to losses of hundreds of thousands of yen for single projects and millions of yen for ongoing projects. The important recognition is that contract type selection is not merely a difference on paper, but a strategic decision that determines the risk allocation and revenue structure of the entire project.

This section systematically organizes the differences in legal nature and practical responsibility scope between quasi-mandate contracts and lump-sum contracts.

The essence of quasi-mandate contracts lies in "processing entrusted affairs with the care of a prudent manager." While Article 656 of the Civil Code applies the provisions of contracts by analogy, the important difference is that "processing affairs" rather than "completion of work" constitutes the content of the obligation. In other words, contractors have the obligation to execute appropriate processes, but do not have the obligation to guarantee specific results.

For example, when undertaking SEO consulting work under a quasi-mandate contract, the contractor has the obligation to properly implement industry-standard SEO measures, but does not bear the responsibility for results such as "definitely improving search rankings." Compensation is also paid based on working time or duration, and there is the right to receive consideration regardless of results.

The core of lump-sum contracts lies in the obligation to "complete work" stipulated in Article 632 of the Civil Code. The contractor bears the obligation to complete the agreed work and deliver the results to the client. The important point is bearing responsibility for results, not processes.

When undertaking website creation under a lump-sum contract, the contractor has the obligation to complete a site with agreed specifications, and basically has no right to claim compensation until completion. Also, if defects are discovered after completion, they bear warranty liability for defects (current non-conformity liability) under Article 636 of the Civil Code.

Benefits of quasi-mandate contracts from the contractor's perspective include, first, high revenue predictability. Through monthly fixed fees or hourly rate compensation settings, they can reliably receive consideration corresponding to the amount of work. Second, pressure from result responsibility is reduced. As long as appropriate processes are executed, they are unlikely to be held responsible even if expected results are not achieved.

The benefit of quasi-mandate contracts for clients is being able to continuously utilize expert knowledge. In consulting and advisory work, the value of providing know-how is often higher than specific deliverables.

Risks of contract work are mainly concentrated on the contractor side. Due to completion obligations, even if man-hours exceeding initial estimates occur, there is an obligation to continue work without additional compensation. Also, due to warranty liability for defects, they bear the cost of handling defects after delivery.

In system development contract projects, cases where additional development occurs due to ambiguous requirements definition are common. Since contractors have "completion obligations," they basically need to respond to specification changes that grasp the client's true intentions. As a result, it's not uncommon for initial estimates of 1 million yen to ultimately require 3 million yen worth of man-hours.

Risks of lump-sum contracts on the client side mainly appear in quality aspects. Incentives for contractors to cut corners to secure profits work easily, and while minimum specifications are met, quality exceeding expectations is difficult to obtain.

Judging how to choose freelance contract types without understanding these structural differences leads to serious misalignment after project commencement.

This section presents practical judgment flows for analyzing project characteristics and selecting appropriate contract types.

Clarity of deliverables becomes the first judgment criterion. Projects where the completed form can be specifically imagined and defined in detail through specifications or wireframes are suitable for lump-sum contracts. Conversely, process-focused projects with fluid results are appropriate for quasi-mandate contracts.

Taking website creation as an example, for corporate site renewal projects where design mockups and site maps are finalized, lump-sum contracts function well. However, for abstract requests like "website creation to improve brand image," completion criteria are ambiguous, making quasi-mandate contracts safer.

The number of uncertain factors is also an important judgment factor. Projects where policy changes are expected during execution, such as new business marketing support or technical research, are suitable for quasi-mandate contracts. Conversely, existing system feature additions or routine work can control risks with lump-sum contracts.

Classification by duration characteristics is also effective. Short-term intensive projects (1-3 months) with clear deadlines match lump-sum contracts, while medium to long-term continuous projects (6+ months) requiring phased results match quasi-mandate contracts.

The specific judgment flow is shown below:

1. Can deliverables be defined at the specification level?

   • YES → Contract work candidate
   • NO → Quasi-mandate candidate

2. What is the frequency of specification changes during the project period?

   • Low → Maintain lump-sum contract
   • High → Change to quasi-mandate contract

3. What is the client's level of involvement?

   • Low (want to delegate) → Lump-sum contract
   • High (want to proceed together) → Quasi-mandate contract

4. What is the risk tolerance?

   • Contractor can take risks → Lump-sum contract
   • Client takes risks → Quasi-mandate contract

Industry trends are also helpful references. In the system development industry, lump-sum contracts are mainstream, but separated contracts with quasi-mandate for requirements definition phases and lump-sum for manufacturing phases are increasing. In the design industry, branding uses quasi-mandate while logo creation uses lump-sum is common differentiation.

In the consulting industry, quasi-mandate contracts are basic, but there are cases adopting performance-based lump-sum contracts when there are clear goals like "achieving 20% cost reduction through business improvement."

The experience level of contractors and clients also becomes judgment material. When both parties are well-versed in the project content, lump-sum contracts are less likely to cause problems, but when either party is in their first transaction or new field, it's wiser to hedge risks with quasi-mandate contracts.

Consider a monthly 300,000 yen SNS marketing support project. If the goal is "achieving 10,000 followers," quasi-mandate contracts are appropriate due to the large influence of external factors like algorithm changes. On the other hand, "post management and report creation" as work-based tasks can succeed with lump-sum contracts.

The important recognition is that contract type selection can be reviewed not only before project start but also during project progress. Even projects that start with quasi-mandate can be changed to lump-sum if deliverables become clear during the process, requiring this flexibility.

This section shows the misunderstandings that frequently occur when concluding quasi-mandate contracts and lump-sum contracts, and specific checkpoint items to prevent them.

The most dangerous pitfall is misunderstandings about "hybrid contracts." Cases where the contract is legally quasi-mandate but verbal promises set expectations like "please definitely produce results" are occurring frequently. Legally it's quasi-mandate, but misalignment arises where clients seek result responsibility while contractors consider only work responsibility.

In an actual case, a monthly 200,000 yen SEO consulting project concluded a quasi-mandate contract, but the client took "reaching TOP 10 in search rankings within 3 months" for granted. The contractor executed appropriate measures but didn't achieve expected results, leading to contract termination in the 4th month. In this case, legally the contractor bears no fault, but relationship and business opportunity losses are unavoidable.

Frequent troubles in quasi-mandate contracts include ambiguous deliverable definitions. When concluding quasi-mandate contracts under the name of "consulting work," but clients expect specific reports and proposals while contractors consider only advice.

To prevent this problem, it's necessary to document specific work content and deliverables even in quasi-mandate contracts. Record specific obligations like "conduct 4 monthly meetings," "create monthly reports," and "provide 3+ improvement proposals" in the contract. The important point is clearly stating that it's a "best effort obligation" and clarifying that it's not a result guarantee.

Typical failures in lump-sum contracts are ambiguous completion criteria. When setting abstract completion criteria like "user-friendly site" for website creation, there's a possibility of being judged "incomplete" based on the client's subjectivity.

In lump-sum contracts, it's essential to quantify and specify completion criteria. Set objective standards like "responsive design support," "page load speed within 3 seconds," and "W3C compliance." Also, clearly define inspection periods (typically 7-14 days) and warranty periods after inspection (3-6 months).

Payment condition setting mistakes also cause serious problems. Setting performance-linked payment conditions in quasi-mandate contracts creates contradictions with legal nature. Since quasi-mandate involves consideration for work, payment should basically be monthly fixed fees or hourly rates.

In lump-sum contracts, lump-sum payment upon completion is basic, but cash flow problems arise for long-term projects. In this case, set installment payments like "30% advance payment, 30% interim payment, 40% upon completion" or partial payments upon milestone achievement. The important point is clarifying inspection criteria for each payment timing.

Setting liability limitation clauses also differs by contract type. In quasi-mandate contracts, liability limitations excluding intentional/gross negligence are common, but in lump-sum contracts, it's necessary to specifically define the limitation scope of warranty liability for defects.

In system development lump-sum projects, set clauses like "covering only direct damages, excluding indirect damages and lost profits" and "liability limit within contract amount range." Clauses exempting third-party software and API-related defects are also important.

Setting mid-term cancellation clauses also differs greatly by contract type. Quasi-mandate contracts allow cancellation by either party at any time under Civil Code Article 651, but lump-sum contracts only allow cancellation before completion at the client's convenience (Civil Code Article 641).

In practice, even quasi-mandate contracts set clauses like "1-month advance notice" and "settlement of performed portions" to prevent confusion. In lump-sum contracts, predetermine the scope of damages for client-convenience cancellation.

Practical checklist for contract review:

1. Do the contract type and actual work content match?
2. Are deliverables and completion criteria specifically defined?
3. Does the responsibility scope align with the contract type?
4. Do payment conditions contradict legal nature?
5. Are mid-term cancellation and change procedures clarified?

Neglecting these checks leads to "this wasn't supposed to happen" situations with high probability after contract conclusion.

This section shows specific strategies and negotiation techniques that contractors and clients should adopt when selecting contract types.

Strategic thinking for contractors requires first clarifying the balance between risk tolerance and revenue goals. For high profits, maximize added value with lump-sum contracts; for stable income, minimize risks with quasi-mandate contracts.

Contractors choosing quasi-mandate contracts should make continuity-focused proposals effective. Present long-term perspectives like "annual contract of 300,000 yen monthly × 12 months, aiming for gradual performance improvement," appealing that comprehensive value is higher than single lump-sum projects. Also emphasize unique benefits of quasi-mandate contracts like "optimizing measures through monthly reviews" and "flexible response to market changes."

Contractors choosing lump-sum contracts should front-load clear value provision. Promise specific results like "improving website conversion rates to double current levels" or "improving system processing speed by 50%," and demand appropriate compensation as consideration. It's important to show the legitimacy of setting high profit margins in exchange for taking risks.

Negotiation techniques for contractors include effectively proposing contract type change options. Stage-wise approaches like "proceed with quasi-mandate contract for the first 3 months, then shift to lump-sum contract when results become clear" can find optimal contract types while reducing client anxiety.

Also, hybrid compensation designs are worth considering. Structures that add performance-linked bonuses to basic quasi-mandate contract compensation secure both stable income and incentives. For example, designs like "monthly basic compensation 200,000 yen + goal achievement bonus 100,000 yen."

Strategic thinking for clients requires objectively viewing their own project management capabilities and expectations for results. When internal resources are limited and wanting to delegate to experts, quasi-mandate contracts are suitable; when there are clear requirement specifications and quality can be managed, lump-sum contracts are appropriate.

Clients choosing quasi-mandate contracts should focus on partnership-oriented relationship building. Treat contractors not as external resources but as team members, establishing information sharing and collaborative systems. Set continuous communication opportunities like monthly review meetings and quarterly strategy reviews.

Clients choosing lump-sum contracts find thorough specification management as the key to success. Rather than making vague requests and later demanding additions, conduct sufficient requirements definition before contracting. Also, objectify inspection criteria and create mechanisms that eliminate emotional judgments.

Key negotiation points for clients include clarifying responsibility scope as most important. In quasi-mandate contracts, specifically define "how far does the scope of good management duty extend," and in lump-sum contracts, detail criteria for "what constitutes completion."

From a budget management perspective, consider setting upper limits in quasi-mandate contracts. Conditions like "300,000 yen monthly, 3.5 million yen annual cap" prevent unlimited spending. In lump-sum contracts, predetermine conditions for additional cost occurrence, setting clear standards like "100,000 yen additional cost per specification change."

Important consensus-building processes for both parties involve securing sufficient discussion time before contract conclusion. Rather than deciding in 1-2 meetings, secure at least one week of consideration time to identify questions and concerns.

In actual success cases, a web production company and manufacturing company's annual contract uses differentiation where "basic website updates are quasi-mandate contracts (50,000 yen monthly), new feature development is individual lump-sum contracts." This maintains continuous relationships while applying optimal contract types according to project characteristics.

As a final judgment criterion, it's important for both parties to evaluate from a long-term perspective of "can we continue with this contract type for one year?" Rather than short-term profits or burden reduction, the perspective of building sustainable business relationships leads to appropriate contract type selection.

Contractors should judge which of quasi-mandate contracts or lump-sum contracts will bring long-term success based on next project acquisition possibilities, while clients should judge based on expected result realization possibilities, and proceed with contract negotiations in that direction.