Discussion starter: an agency question, posted with an answer from Niraj Raut to open the thread. If you have dealt with this on a site, reply with what you saw, especially where it differs.
- Agency
Freelancers: project fee, retainer or day rate for technical audits? Which has held up best against scope creep?
Disclosure: Niraj Raut, who posted this answer, runs the SEO consultancy linked at the end of it.
1 reply
-
adminAdmin
For the audit itself, a fixed project fee with a tightly written scope has held up best against scope creep, provided the scope defines deliverables and boundaries rather than effort. Day rates protect you on genuinely open-ended diagnostic work, and retainers suit what comes after the audit, when the client needs help getting fixes built. Most scope creep in technical audits does not come from the audit at all. It comes from implementation support, repeated checks and developer questions that nobody priced. The model that works is usually a hybrid: fixed fee for the audit, a separate price for everything after it.
Where scope creep in audits actually comes from
- The site was bigger than it looked. A second subdomain, a blog on a different platform, separate country sites or a staging area that is indexed.
- “While you’re in there”. Content, local, analytics setup or a competitor comparison, requested after the audit starts.
- Access delays. Waiting weeks for Search Console, logs or a crawl allowance, then being expected to hit the original date.
- Presentation rounds. One presentation becomes four, each for a different team.
- Developer support. Clarifying tickets, reviewing pull requests, checking staging, re-crawling after release.
Only the first two are audit scope problems. The rest are implementation work that clients experience as part of “the audit”, and they need their own line in the proposal.
How the three models compare
Model Works well when Main weakness Protection against creep Project fee The site and deliverables can be defined up front You carry the risk if the estimate is wrong Strong, if the scope names what is excluded and prices changes Day rate The problem is open-ended: traffic loss investigations, migration rescues, complex log work Clients dislike an unknown total and may cut the work short Built in, since more work means more days Retainer Ongoing support: ticket reviews, release checks, monitoring Hours drift into unrelated tasks unless the retainer is defined by outcomes or a capped allowance Moderate, depends on how the retainer is written What a creep-resistant audit proposal contains
- A defined crawl scope. Name the hostnames, the approximate URL count and the sections included. State that additional hostnames or platforms are quoted separately.
- Named deliverables. For example: a findings document, a prioritised issue list with effort and impact estimates, one recorded presentation and one live session.
- A question window. Include a set period, such as two weeks after delivery, for clarification questions. After that, questions fall under support pricing.
- Access requirements with dates. List what you need (Search Console, analytics, logs, CMS or staging access) and say that the timeline starts when access is complete.
- A snapshot clause. Findings reflect the site on the crawl date. Re-checks after releases are a separate item.
- Explicit exclusions. Content strategy, keyword research, link audits, analytics implementation, unless included.
- A change request price. Either a day rate or a fixed price per additional section, stated in the proposal so a change becomes a decision, not a favour.
- Staged payment. A deposit before work starts and the balance on delivery. It keeps the relationship healthy when timelines move for reasons on the client side.
The sentence that saves the most arguments:
“Implementation support is not included in the audit fee and is available as a block of days or a monthly retainer.” Clients rarely object when it is written down at the start. They object when it appears for the first time in week six.
Handling the unknowns before you quote
The fixed fee only works if you can scope accurately. Two approaches help when you cannot:
- A paid discovery phase. A short, fixed-price stage to crawl the site, review access and map the platform, producing a firm quote for the full audit. It filters out clients who are not serious and turns your estimate into something you can stand behind.
- Tiered scopes. Offer two or three audit sizes with clear boundaries: templates only, templates plus logs, templates plus logs plus international setup. The client chooses the risk they want to pay for.
Hypothetical example:
A freelancer quotes a fixed fee to audit an ecommerce site. During the crawl they find a separate blog on a different CMS and three country subfolders with their own templates. Because the proposal named the hostnames and sections, they send a short change request: an extra fee for the international templates, and the blog excluded unless approved. The client approves the international work and declines the blog. No argument, no free work, and the audit ships on time.
After the audit: retainer or block of days
For implementation support, I find prepaid blocks of days easier to manage than open retainers for most freelancers. The client buys a block, uses it for ticket reviews, release checks or developer calls, and tops it up. It avoids the monthly “what did we get for the retainer?” conversation. A retainer suits clients with a steady release cycle where you are effectively part of the team, and in that case it should list what is included (release checks, a monthly monitoring review, a set number of hours of support) and what is not.
Price by risk, not by hours alone
A migration audit on a large site carries more risk than a health check on a small one, even if the hours are similar, because a missed issue costs more. Pricing by the scale of consequence, not just by time, is fair and helps you stay profitable on the high-stakes work. The fixed-fee structure makes that easier to present than a day rate does.
Fixed fee for a clearly bounded audit, a paid discovery stage when the site is unclear, a day rate for diagnostic investigations, and prepaid blocks or a defined retainer for everything after delivery. Write the exclusions and the change price into the proposal, and most scope creep becomes a conversation you are paid for.
Need help with this on your own site?
Niraj Raut works with businesses in Nepal, Australia, the UK, Europe and the US on technical SEO, ecommerce SEO, local SEO and AI search.
Add a reply Cancel reply
Replies are open to approved members. Log in or apply to join.