A minimum project fee can stop an agency from spending weeks on work that barely covers its delivery costs. But a number announced without context can also push away a good client whose first need is modest, even if there is room for a valuable relationship later.
The answer is not to avoid a minimum. It is to set one based on the economics of your agency, explain what it buys, and distinguish a small project from a small opportunity. A well-designed minimum protects your team without requiring every client to buy the same package.
Here is a practical way to calculate your floor, decide when to make exceptions, and respond when a prospect’s budget falls below it.
What a minimum project fee is—and what it is not
A minimum project fee is the lowest price at which your agency will take on a defined kind of engagement. It is a commercial boundary, not necessarily a public rate or a promise that every project costs exactly that amount.
It is also different from a target project value. Your minimum should make a project viable; your target is the value you would generally like to sell. For example, a design agency might set a $4,000 minimum for a standalone identity project while aiming for $8,000 to $12,000 when strategy, guidelines, and rollout support are included.
Set separate minimums when the work has materially different delivery patterns. A fixed-scope website build, a brand strategy sprint, and a monthly content engagement create different demands. One figure applied across all three can disguise unprofitable work or make a simple, profitable service unnecessarily hard to buy.
How to set a minimum project fee
1. Define the kind of work the minimum covers
Start with a service and scope, not a number. Write down the smallest engagement you can deliver responsibly: its objective, key activities, deliverables, client inputs, revision limits, and likely timeline.
For instance, “website project” is too broad. A minimum might cover a planning workshop, a five-page marketing site using an agreed content structure, one design direction, two review rounds, and launch support. It would exclude custom application development, extensive copywriting, and unplanned integrations.
This definition matters because a low fee may be workable for a tightly bounded engagement but not for an open-ended request. If the scope is unclear, you cannot make a meaningful fee decision yet.
2. Estimate the delivery effort by role
Estimate the time each role needs, including work clients rarely see: discovery, project management, research, internal review, quality assurance, and handoff. A simple planning table can expose hidden effort:
| Role or activity | Estimated hours |
|---|---|
| Strategy and discovery | 8 |
| Design or production | 24 |
| Project management and client reviews | 10 |
| Quality assurance and handoff | 6 |
| Total estimated delivery time | 48 |
Use estimates from comparable completed work where possible, then adjust for uncertainty. If you have not delivered that exact service before, identify the assumptions and add a sensible contingency rather than presenting a precise guess as fact.
3. Use a loaded internal cost, not just salary
Multiply estimated hours by an internal cost rate that accounts for compensation and the costs of employing or supporting the people doing the work. Depending on your setup, that may include payroll taxes, benefits, contractor costs, software, rent, insurance, and other overhead. Do not confuse this internal cost with your client-facing hourly rate.
Suppose those 48 hours cost the agency an average of $55 per delivery hour after allocated employment and overhead costs. Direct delivery cost is $2,640. That is not yet the minimum fee: it does not necessarily cover sales time, non-billable work, risk, or the profit your business needs to reinvest and remain resilient.
The U.S. Small Business Administration’s break-even guidance is a useful reminder to distinguish fixed costs from variable costs when assessing whether revenue covers the business’s expenses. For an agency, the calculation is more involved than a single project, but the same discipline helps prevent pricing from ignoring overhead.
4. Check the fee against your business economics
There is no universal markup that works for every agency. Review your delivery estimate alongside your overhead, expected non-billable time, desired operating margin, and the amount of capacity the work will occupy. Then compare the proposed fee with the contribution you need from projects of this type.
For a simplified illustration, an agency estimates $2,640 in delivery cost for the smallest viable project. It adds $600 for sales and administration effort, then decides that this kind of engagement needs to contribute another $1,260 toward profit and business resilience. That suggests a minimum near $4,500. The exact figure is a management decision, not a universal formula; the point is to make the assumptions visible.
Also test the fee against capacity. A project that consumes two weeks of a specialist’s time may block other work or create a scheduling gap. If the agency has limited capacity, the relevant question is not only “Does this cover the hours?” but “Is this a good use of the capacity we have?”
5. Validate the number with completed projects
Compare the proposed minimum with actual projects from the last six to twelve months, if you have reliable records. Which engagements ran over estimate? Which generated extra rounds or senior involvement? Which were smooth and repeatable? Use that evidence to adjust both the fee and the scope definition.
If you do not track hours precisely, use a lightweight project review: estimated versus actual effort, major scope changes, write-offs, and the final gross margin if you can calculate it. The purpose is not perfect timesheets. It is to find patterns before setting a rule that repeats a bad estimate.
Set a boundary without making it a rejection
Clients usually care less about your internal cost logic than about what they can accomplish within their budget. State the minimum plainly, then connect it to the work required to produce a useful result.
“Our full website projects start at $9,000 because they include planning, design, build, testing, and launch support. Based on what you described, we could also scope a paid planning sprint first, then decide whether a full build makes sense.”
This response protects the project standard while opening a smaller, bounded option. It is more useful than offering an arbitrary discount that leaves the same scope and expectations in place.
Offer a smaller path only when it has its own value
A smaller engagement should solve a meaningful problem on its own. Options may include a paid audit, a strategy workshop, a single landing page, a pilot campaign, or a clearly defined first phase. Specify the deliverable, fee, duration, and what is not included.
A discovery phase can be a poor workaround if it is really unpaid sales work disguised as a project, or if the client expects the entire solution for the smaller fee. Make clear whether the phase is standalone, whether its output informs a later proposal, and whether any fee is credited toward subsequent work.
Do not automatically promise that a small first project will lead to a larger one. Treat it as a worthwhile engagement in its own right and assess the next opportunity if it arises.
Use exceptions deliberately
There may be sound reasons to accept work below your usual minimum: a strategically important case study, a genuinely repeatable productized service, a low-risk test of a new offering, or a client with a credible path to ongoing work. But name the reason and limit the exception.
Set conditions such as a fixed scope, limited review rounds, a specific start date, or a cap on internal hours. Record the exception so it does not quietly become your new normal. If a project repeatedly requires exceptions to sell, revisit the offer or the minimum rather than blaming every prospect’s budget.
Qualify budget before writing a proposal
A minimum fee is most useful when prospects learn about it before you and your team spend hours preparing a detailed proposal. You can show a “starting at” range on your website, mention it in an initial response, or ask about budget during a fit conversation. Which approach works best depends on how custom your work is and how much context buyers need.
Ask what the client has budgeted, what outcome matters most, and whether there is a deadline or approval process. If the figure is below your floor, find out whether the client needs a smaller outcome or expects the full scope at a lower price. Those are different problems. A structured list of discovery questions for fit and budget can help make that conversation more consistent.
Be equally clear about your own decision criteria. If the work cannot be delivered well at the proposed budget, say so and offer a narrower option only if one genuinely fits. If the prospect is a strong fit but needs time to decide, use a follow-up process rather than repeatedly renegotiating the fee. A defined sales pipeline with clear stages can help separate a pending decision from a project that is not viable.
Review your minimum as the agency changes
Revisit minimums when your delivery costs, service mix, team structure, or demand changes—not simply because another agency announced a higher rate. A minimum that worked for a founder handling delivery may not work once the agency adds project management, specialist roles, or more formal quality checks.
Review the scope and economics together. If your minimum has risen but the deliverable has not changed, make sure the client can understand why. If you keep selling below the minimum, check whether the rule is too high for the market you serve, the scope is too broad, or your qualification process is letting unsuitable leads through.
The goal is not to reject every small engagement. It is to avoid taking on work that cannot support a good outcome and a healthy business. A clear fee floor, a bounded smaller option, and an honest conversation about fit give the right clients a way forward without asking your team to subsidize the project.
FAQ
Should an agency publish its minimum project fee?
It can be useful when prospects often arrive with budgets far below your viable range. A “projects start at” figure or range can save time, while a fully custom service may need a short explanation of what affects the price. Test whether publishing it improves the quality of inquiries without discouraging good-fit prospects who need context.
How often should I review my minimum fee?
Review it when costs, capacity, scope, or delivery methods change, and periodically compare it with actual project outcomes. There is no required calendar interval. A small agency might review after a run of similar projects or when it changes team structure or service packaging.
What if a client wants the full scope for less than my minimum?
Do not keep the scope unchanged and quietly cut your fee unless there is a deliberate, time-limited reason. Explain the minimum, then offer to reduce deliverables, phases, or support to match the budget. If no viable scope fits, decline respectfully.
Should I charge a minimum for hourly or retainer work?
Often, yes, but define the commitment differently. A retainer might have a monthly minimum tied to reserved capacity, a minimum term, or a set of recurring deliverables. Explain how unused time, response times, and additional requests are handled so the client knows what the commitment buys.
Is a minimum fee the same as a deposit?
No. A minimum fee sets the lowest price for an engagement; a deposit is an upfront payment toward the agreed fee. Payment timing, milestones, and cancellation terms should be stated separately in the proposal or contract.