What it means
A consultancy agreement sets out work an external specialist will perform for a business. It should identify the parties, scope, deliverables, fees, timing and the process for accepting completed work, and it may also address confidentiality, data, intellectual property, liability and how the relationship ends.
The document is a working reference, not merely a signature collected before the first invoice. Define the problem before drafting a task list: is the consultant providing advice, producing a report, implementing a system or managing staff?
Each shape needs different acceptance criteria and decision rights, and a vague instruction to "improve operations" makes it hard to tell whether a useful result was delivered or whether additional work is outside the price. The scope should name deliverables, assumptions and exclusions, and if the consultant relies on timely access to company data or employees, say who will provide it and when, so an owner can distinguish a delay caused by the consultant from one caused by unavailable inputs and can set milestones that allow review before the whole project is complete.
Fees can be fixed, time-based, milestone-based or mixed; a day rate of $3,000 for 25 days gives a base amount of $75,000, before tax, expenses or additional approved days. State whether a day has a standard number of hours and whether travel counts, and if the amount is capped, explain what happens when the cap is reached rather than assuming that a quoted estimate is a hard maximum.
Change control protects both sides: if the client asks for more locations, data sources or revised outputs, record the new scope, fee and date before work begins, because otherwise a consultant may deliver extra work expecting payment while the client thinks it was included, and approval authority should stay clear so a friendly request from one employee does not silently expand the budget. A contract can say the consultant is independent, but the label alone does not determine employment or tax status, because the actual pattern of control, personal service, integration and economic risk can matter under local law.
UK government guidance, for example, urges engagers to assess the real working relationship rather than rely on a written description. Other jurisdictions use their own tests, so get advice where misclassification would be material.
Ownership of work needs precision, since in many systems a commissioner does not automatically own copyright in independently created work merely because it paid for the work, and UK copyright guidance explains this for commissioned material. Specify what is assigned, when rights transfer and which pre-existing templates, tools or third-party materials remain with their original owner, and ensure the client has the licence it needs to use the final output.
A consultant may deliver a report using licensed data or software, so check whether the client may copy, modify, share or reuse those materials after the engagement, remembering that a full assignment of rights the consultant does not own cannot solve third-party licence limits and that for software the agreement should include source code, configuration and documentation requirements when needed to avoid dependence on one individual. Acceptance criteria can be objective without promising an impossible result: specify a review period, how defects are notified and the time to correct them, and note that a client should not withhold approval indefinitely for reasons outside the agreed scope.
Liability provisions need to fit the risk and fee, so review any cap, excluded losses, insurance requirement and carve-outs for confidentiality or intellectual-property claims, because a tiny engagement should not casually expose either party to unlimited loss, but a low cap can leave a client unprotected on a high-risk system change, and professional indemnity cover should be checked to see whether it applies to the services provided. The client should appoint an internal owner who can answer questions and review deliverables, and the consultant should give regular progress reports and flag blocked work early.
In practice
Real-world examples.
Example
A business hires a marketing consultant for six months to rebuild its lead-generation process. The agreement lists a monthly report, a final playbook and a handover session as deliverables. Anything beyond those items needs a written change.
Example
The agreement says all work belongs to the client, except the consultant's pre-existing templates, which the client may use but not resell. The client therefore owns the final report but not the consultant's underlying tools. Both parties sign off the carve-out before the first day of work.
Example
Fees are paid monthly against agreed deliverables rather than on elapsed time alone. If a deliverable is rejected, the client states the reason within the review period and the consultant corrects it. Payment for that item follows acceptance.
Formula
Calculation
Project cost = Day rate x Days
Worked example. A $3,000 day rate for 25 days.
- Project cost: $3,000 x 25 = $75,000.
- If the agreement caps fees at $80,000, headroom is $80,000 - $75,000 = $5,000, which buys about 1.7 further days at $3,000.
- If the same work were instead a fixed fee of $75,000 and the consultant needed 30 days, the effective day rate would fall to $75,000 / 30 = $2,500, which is why the pricing basis should be agreed before work starts.
This excludes tax and expenses, which should be stated separately in the agreement.Case study
Seen in the real world.
This illustrative and entirely fictional case follows Horizon Travel, an invented agency hiring a consultant to redesign a booking workflow. Its first brief says only "improve customer service," so the parties define a process map, training guide and acceptance dates before work begins. A new request for a payment integration is priced as a written change. They specify ownership and licence terms for the final materials. No guaranteed operational improvement is assumed.
The base engagement is agreed at $2,400 a day for 10 days, or $24,000, paid in two instalments of $12,000 on acceptance of the process map and the training guide. The payment integration is estimated at 4 further days, a written change of $9,600 ($2,400 x 4) that the agency approves before the work starts. When the consultant's draft training guide uses a licensed stock image set, the agreement's licence clause prompts a check that Horizon may keep using it after the project ends. The question is settled in writing rather than discovered months later.
Watch out
Common mistakes.
- Using a vague brief without deliverables or acceptance criteria.
- Assuming payment automatically transfers every right in commissioned work.
- Relying on an independence label while the working relationship suggests otherwise.
Questions
People also ask.
What is a consultancy agreement?
A contract for specified external professional services, with work and payment terms.
What should it cover?
Scope, deliverables, fee, changes, confidentiality, work rights, liability and exit, tailored to the project.
Why state independence?
It records intent, but status depends on actual facts and local law, not wording alone.
From the founder's library
Take it further with the book.
Build your financial confidence beyond this definition. Shihan's full-length guide, Accounting Fundamentals, takes the same plain-English approach and turns it into a complete, practical playbook for non-finance managers, business owners and students - with chapter-end quiz answers and presentation slides included.
25% off with code MMHQ25, applied at checkout. Priced in USD - checkout may show the equivalent in your local currency.
View the book and save 25%