TL;DR
- A contract type can describe its business purpose, pricing model, or legal classification. These are different dimensions of the same agreement.
- Common business agreements include sales, supplier, services, SaaS, confidentiality, employment, and partnership contracts.
- One agreement can belong to several categories and use more than one pricing model.
- Start with the transaction's purpose, then review scope, payment, risk allocation, approvals, and responsibilities after signing.
A sales agreement, a fixed-price contract, and a bilateral contract can all describe the same transaction. They answer different questions: what the agreement covers, how payment works, and how the parties make their commitments.
Understanding those distinctions helps legal, procurement, sales, and finance teams choose the right starting document and review the risks that matter. This guide explains common types of contracts in business, the pricing models used within them, and legal classifications you may encounter.
What is a contract?
A contract is an agreement that creates obligations enforceable under applicable law. It can set out what each party will deliver, how payment works, who bears particular risks, and what happens if the arrangement changes or ends.
Business teams often work with written contracts because they provide a record of agreed terms. A signature alone does not resolve every question about validity or enforceability. Applicable law, the parties' authority, the circumstances of formation, and the agreement's terms all matter. Cornell's Legal Information Institute provides an overview of contract formation and enforceability.
For a wider introduction to managing agreements from request through renewal, see the basics of contract management.
Three ways to describe a contract
Before choosing a template, separate these three dimensions:
- Business purpose: What relationship does the agreement govern? Examples include sales, procurement, services, employment, confidentiality, and partnerships.
- Pricing model: How will the parties calculate payment? Examples include fixed price, time and materials, cost reimbursement, and unit pricing.
- Legal classification: How are commitments made or terms expressed? Examples include bilateral and unilateral contracts, or express and implied agreements.
These dimensions overlap. A supplier's managed services agreement might be a bilateral, written contract with a fixed monthly fee and separately priced project work. Calling it a services contract does not tell you its payment terms or how liability is allocated.
For most business requests, start with the purpose of the relationship. Then choose the pricing structure and review the legal terms with the appropriate stakeholders.
Common types of contracts in business
1. Sales agreements and bills of sale
Sales agreements govern transactions in which a business supplies goods or services to a customer. The same agreement is a sell-side contract for the seller and a buy-side contract for the purchaser.
A sales agreement typically addresses the description of goods or services, price, payment dates, delivery, acceptance, warranties, and remedies. For physical goods, the parties may also need to specify when ownership and risk transfer.
A bill of sale records a transfer of property. Depending on the transaction, it may sit alongside a broader sales agreement rather than replace the terms governing delivery, warranties, or continuing obligations.
Example: A manufacturer sells production equipment to a customer. The agreement identifies the equipment, delivery date, installation responsibilities, acceptance tests, and warranty process.
Review focus: Make sure the commercial quote, purchase order, and contract describe the same transaction. Resolve conflicting terms before relying on the documents to manage delivery or payment.
2. Supplier, vendor, and procurement agreements
Supplier agreements establish the terms under which an organization buys goods or services. A framework or vendor-of-record arrangement can define ongoing terms, with individual orders specifying quantities, dates, and prices. Whether there is a minimum purchase commitment depends on the agreement.
Useful terms include specifications, ordering procedures, pricing changes, delivery standards, quality requirements, subcontracting, and continuity arrangements. Where the supplier accesses systems or data, security and data-processing obligations may also need review.
Example: A company appoints a supplier for packaging materials. The framework sets quality standards and pricing rules; purchase orders specify each shipment.
Review focus: Define who measures supplier performance, what happens when standards are missed, and how the business can transition to another supplier. Termination rights and remedies should be expressly agreed, rather than assumed from the document's title.
3. Professional services agreements, MSAs, and statements of work
Professional services agreements cover work performed by consultants, engineers, accountants, agencies, and other service providers.
A master service agreement, or MSA, commonly establishes terms for an ongoing relationship. A statement of work, or SOW, describes a particular project, including deliverables, responsibilities, acceptance criteria, timing, and fees. The documents should specify their order of precedence if their terms conflict.
Example: A consultancy and a customer agree an MSA. A separate SOW defines a systems implementation, named milestones, required customer inputs, and acceptance tests.
Review focus: Be clear about what is included, what is excluded, who owns deliverables, and how scope changes are approved. The pricing model is a separate choice: services can be delivered for a fixed price, on time and materials, or through another agreed structure.
4. SaaS and software license agreements
A SaaS agreement governs access to a hosted software service. A software license governs permitted use of software or related intellectual property. Licenses may be perpetual or time-limited, depending on the terms; support and maintenance can be covered separately.
These agreements often address authorized users, usage limits, subscription fees, renewal, intellectual property, support, and termination. Hosted services may also require clear commitments for availability, security, data processing, and data export at the end of the relationship.
Example: A company subscribes to an application for a defined number of users. The order form specifies the subscription, while incorporated terms describe permitted use, support, and renewal.
Review focus: Check every incorporated document, including online terms, service-level commitments, and data-processing terms. Identify how terms can change and what the customer can do if the service no longer meets its needs.
5. Managed services agreements and service-level agreements
Managed services agreements cover recurring operational work, such as maintaining infrastructure or providing ongoing technical support.
A service-level agreement, or SLA, can define measurable standards such as availability, response times, or resolution targets. It may be a schedule to the main agreement. Service credits, escalation procedures, and other remedies depend on the negotiated terms.
Example: A provider manages a company's cloud environment. The agreement defines coverage hours, incident responsibilities, reporting, and service levels.
Review focus: Specify how performance is measured, any exclusions, how incidents are reported, and which remedies apply. Also plan for transition assistance, access revocation, and return of data when the service ends.
6. Non-disclosure and intellectual property agreements
A non-disclosure agreement, or NDA, governs the use and disclosure of confidential information. It may apply to one party's disclosures or to information exchanged by both parties.
An NDA should define protected information, permitted purposes, exceptions, authorized recipients, and the duration of obligations. Confidentiality provisions do not necessarily transfer ownership of intellectual property. Licensing, assignment, and ownership of newly developed work need their own terms.
Example: Two companies exchange technical information while evaluating a collaboration. An NDA limits how the information can be used and shared; a later development agreement addresses ownership of the resulting work.
Review focus: Align confidentiality obligations with the actual information flow and the people who need access. For more detail, read the guide to non-disclosure agreements.
7. Employment and independent contractor agreements
Work-related agreements can cover duties, compensation, confidentiality, intellectual property, and the end of a working relationship. Depending on the arrangement, an organization may also use offer letters, policy acknowledgments, or separation agreements.
An employee and an independent contractor are different relationships. A document's label alone should not be used to determine the worker's status. Employment requirements and the treatment of restrictions vary by jurisdiction.
Example: A company engages a freelance designer for a project. The agreement specifies deliverables, payment, access to confidential material, and rights in the completed designs.
Review focus: Coordinate with HR and qualified legal reviewers on worker classification, mandatory terms, and any post-engagement restrictions. Avoid treating one global template as suitable for every location.
8. Partnership, joint venture, and collaboration agreements
These agreements define how organizations work together on a project, product, market opportunity, or continuing relationship. The chosen structure affects governance, contributions, and responsibilities.
Terms may include decision-making, contributions of money or resources, intellectual property, revenue or cost allocation, exclusivity, dispute handling, and exit arrangements.
Example: Two companies jointly develop and market a product. Their agreement identifies each party's contribution, who can approve changes, how the product's intellectual property is handled, and what happens if one party leaves.
Review focus: Define authority and operational responsibilities early. A shared commercial objective does not remove the need to agree how decisions and disagreements will be handled.
Pricing models used in contracts
The contract's purpose tells you what the parties are doing. Its pricing model tells you how payment is calculated and helps explain who bears cost uncertainty.
Fixed-price and lump-sum contracts
The parties agree a price for a defined scope. This can make budgeting easier, but changes to scope, assumptions, or agreed adjustment mechanisms can still affect what is paid.
Example: An agency agrees to deliver a specified website for a set fee, with additional work handled through approved changes.
Review scope, acceptance criteria, dependencies, and change control. For U.S. federal procurement, FAR Part 16 distinguishes firm-fixed-price arrangements from other fixed-price variants. Those rules are specific to federal acquisition, rather than a universal template for commercial agreements.
Time-and-materials contracts
Payment is based on agreed labor rates and chargeable materials or expenses. This structure can suit work whose extent is uncertain, but it requires budget oversight.
Example: A technical team investigates and repairs a legacy system using agreed hourly rates and approved expenses.
Specify rates, billable activities, records, expense rules, and approval requirements. Where appropriate, agree a ceiling or a process for authorizing additional spend. U.S. federal procurement has specific requirements for time-and-materials contracts, including a ceiling price.
Cost-reimbursement and cost-plus contracts
A cost-reimbursement arrangement pays eligible costs under agreed rules. A cost-plus arrangement includes an agreed fee structure. Do not assume the fee is always a percentage of actual costs or that every cost will be reimbursed.
Example: A research project reimburses defined eligible costs and pays a negotiated fixed fee.
Review cost eligibility, records, oversight, funding limits, and fee calculation. In U.S. federal acquisition, a cost-plus-fixed-fee contract uses a negotiated fee that does not vary with actual cost, although changes in the work can affect it. FAR Part 16 prohibits cost-plus-a-percentage-of-cost contracting in that setting.
Unit-price contracts
Payment is calculated using an agreed price per unit and the quantity accepted under the contract.
Example: A supplier charges an agreed amount for each inspected and accepted component.
Specify the unit, measurement process, quality criteria, and any volume limits or minimum commitments. Predictable unit pricing does not necessarily make the total spend predictable if quantities change.
Retainers and recurring fees
A recurring fee may cover availability, a defined service package, or a set allocation of work. The agreement should explain which of these the customer is buying.
Example: A consultant provides an agreed monthly advisory service, with additional projects priced separately.
Define included work, service periods, unused allocations, overages, and renewal or cancellation terms. Do not assume every retainer includes unlimited access or the same payment treatment.
Incentive arrangements and milestone payments
Incentives tie part of compensation to agreed performance measures. Milestone payments link payment dates to defined events or deliverables. Either can be used within a broader pricing structure.
Example: A project includes payments on acceptance of specified deliverables and a separately agreed incentive for meeting a performance target.
Define objective measures, evidence, approval authority, and how disputes are handled. Paying at milestones does not, by itself, change a fixed-price agreement into a cost-reimbursement contract.
Legal classifications are a different dimension
Legal classifications describe how an agreement is formed or structured. They should not be treated as alternatives to choosing a sales, services, or supplier agreement.
Bilateral and unilateral contracts
In a bilateral contract, both parties exchange promises. A buyer promises to pay and a seller promises to deliver goods.
A unilateral contract involves an offer accepted through specified performance, such as a reward for returning lost property. Detailed formation rules depend on applicable law.
Express and implied agreements
An express agreement states terms in words, which may be written or spoken. An agreement implied in fact is inferred from conduct and circumstances. Cornell distinguishes these from obligations sometimes called implied-in-law or quasi contracts, which concern restitution rather than an agreed exchange.
For business operations, written terms help teams identify and administer commitments. Do not assume that the absence of a signed document means there can be no obligation.
Adhesion and unconscionability
An adhesion contract is generally a standardized agreement offered with little opportunity to negotiate. That description does not automatically make it invalid.
Unconscionability concerns potentially oppressive or unfair terms and the circumstances of an agreement. It is not a contract type a business should select as a template. For example, UCC § 2-302 describes several responses a court may take when a contract or clause is unconscionable. The applicable jurisdiction and facts matter.
Similarly, calling a document a “simple contract” is not a substitute for reviewing its terms, required formalities, and enforceability. Short agreements can still create significant obligations.
How to choose and manage the right agreement
Choosing a document is the beginning of the process. A useful review answers these questions:
- What is the transaction? Identify the goods, services, relationship, and entities involved. Choose an approved starting template for that purpose.
- Which documents form the agreement? Reconcile the MSA, SOW, order form, schedules, purchase orders, and incorporated online terms. Specify precedence.
- How does payment work? Confirm the pricing model, invoices, expenses, acceptance triggers, and any spending limits.
- Where are the material risks? Review liability, warranties, confidentiality, intellectual property, data obligations, and relevant regulatory requirements.
- Who needs to approve? Route deviations to legal, procurement, finance, HR, security, or other accountable reviewers according to the transaction.
- What happens after signature? Assign owners for delivery, service levels, payments, renewal notice windows, and other obligations. Document amendment and termination procedures.
Consider a hosted software purchase with implementation services. It might require a SaaS order form, service terms, a data-processing agreement, and an implementation SOW. Different pricing structures can apply to the subscription and project work. The teams need to reconcile the documents and assign owners, rather than choose just one label for the entire relationship.
Store the executed agreement and linked documents together in a contract repository. Capture the terms your team actually needs to act on, including owners, deadlines, renewal windows, and approved deviations.
Supporting different contract types with Leah Contracting
Different agreement types need different information, review rules, and approval paths. A standard NDA should not automatically follow the same process as a complex supplier agreement.
Leah Contracting supports work across intake, drafting, review, approvals, and obligation tracking. Its agents operate within configured workflows and playbooks, with people handling decisions that require their judgment. The purpose is to connect the work around an agreement, while keeping the relevant terms and decisions available to the teams responsible for it.
Start with the contract types your organization uses most often. Define approved templates, required information, escalation rules, and post-signature responsibilities for each. Then assess whether the workflow supports those needs. Request a demo to explore Leah Contracting for your team's agreements.
Frequently asked questions
What are the most common types of business contracts?
Common examples include sales, supplier, professional services, SaaS, managed services, confidentiality, employment, and partnership agreements. The right set depends on what the organization buys, sells, and does.
How many types of contracts are there?
There is no single count that covers every business purpose, pricing model, and legal classification. Lists of three, seven, or ten contract types often group different dimensions. Choose a classification that answers the question you are trying to resolve.
What is the difference between a buy-side and a sell-side contract?
They describe the parties' perspectives. A business buying a service treats the agreement as buy-side; the provider treats the same transaction as sell-side. The underlying terms still need to be reviewed by both parties.
Is a fixed-price contract the same as a services agreement?
No. A services agreement describes the relationship or work. Fixed price describes how payment is calculated. A services agreement can instead use time and materials, a retainer, or a combination of pricing structures.
Can one agreement belong to several contract types?
Yes. A written professional services agreement may be bilateral, use a fixed price for one deliverable, and use time and materials for another. Record the purpose and pricing terms separately so the teams managing it can find what they need.
