Agency Project Feasibility: How to Decide If You Can Deliver a Scope Profitably

A project feasibility assessment is a structured check of whether a proposed piece of work is practical and worth doing before you commit resources to it. For a marketing or creative agency, that check takes an afternoon, not a quarter, and it answers one question: can we deliver this scope, with the people we actually have, at a margin we are willing to accept? The output is not a report. It is a decision — accept as written, accept with changes, or decline — and a proposal that reflects it.

What does a feasibility assessment mean when you run an agency?

A scope has landed. The client wants a number by Friday. Someone on your team has already said "yeah, we can do that," because of course you can do it — you have done harder things. That is the trap. "Is this possible" is almost never the question. The question is whether it is possible with the people who are not already booked, at the fee this client has in their head, and within a timeline that depends on a client approval chain you have not met yet.

Everything a generic project management article tells you about feasibility was written for someone deciding whether to build a factory. Technical, economic, legal, operational and scheduling feasibility — the TELOS model — assumes the hard part is whether the thing can be engineered. In agency work, the technology question is usually trivial. The constraints that kill agency scopes are capacity, margin and the client's own ability to supply inputs on time.

Feasibility study vs feasibility assessment vs scoping

These three get used interchangeably and they are not the same thing.

In an agency, you are nearly always doing the second and the third at once. You scope well enough to estimate, then you assess whether the estimate works. The scope of work and the eventual statement of work are the documents that carry the verdict into something the client signs.

Why the standard five-pillar model does not fit services work

The textbook pillars assume a one-off build with a capital budget. Agency scopes are different in three ways. First, your scarcest resource is a specific senior person's unbooked hours, not money. Second, a large share of your capacity is already committed to recurring retainers that consume the same people every month. Third, your delivery timeline is partly controlled by the client — their approvals, their asset handover, their legal team.

So the five pillars below are not TELOS. They are the five questions an agency owner can actually answer before the proposal goes out.

What are the five questions that decide whether an agency scope is feasible?

Five questions, asked in this order, because each one can kill the scope on its own and you want the cheap kills first. Capacity takes ten minutes to check. A full cost-of-delivery model takes an hour. There is no point building the model for a scope you cannot staff.

1. Capacity. Can we staff it in the window the client wants?
2. Margin. Does the money work at our real cost of delivery?
3. Dependencies. Can the client actually supply what we need from them?
4. Unbounded scope. What in this brief has no ceiling?
5. Downside. What does it cost us if it overruns?

A "no" on any single question does not mean decline. In most cases it means one specific change to the proposal — phase it, cap it, reprice it. The last section of this page maps each failure to its rewrite.

Question 1: capacity — can we staff it in the window?

Capacity is not a feeling, it is arithmetic. List the roles the scope needs, the hours each role needs, and the hours those named people genuinely have free inside the delivery window after existing commitments. Three columns. If you cannot fill the third column, you do not have a capacity plan, you have a hope.

The specific trap: agencies check whether a person is available — meaning not on holiday — rather than whether a person has unbooked hours. Retainers are the hidden consumer. Recurring monthly work eats the same senior people every month, quietly, and it never shows up as a line item in a new project estimate because nobody re-adds it. Your senior designer is "free" in the sense that no project has their name on them in week four, and fully consumed in the sense that four retainers need twenty of their hours that week.

Then there is billable utilisation. A designer booked to 100% has no slack for revisions, and revisions are the single thing every agency scope underestimates. You should plan capacity against a utilisation target you set yourself. The trade-off is straightforward and you have to choose where you sit on it: higher utilisation means higher margin per head and no absorption capacity when something overruns; lower utilisation costs margin and buys you the ability to swallow a bad week without it reaching the client. This page does not publish a recommended percentage, because the right number depends on your mix of retainer and project work, your seniority spread and how much rework your clients typically generate. Pick yours deliberately and plan against it.

Freelancers look like the answer and partly are. Subcontracting makes a scope staffable — but it changes the cost of delivery, often significantly, and it introduces a quality and availability risk you do not control. Subcontracting does not solve a capacity failure. It converts it into a margin question, which is Question 2.

Deliverable from this question: a one-line verdict. "We are short 40 senior design hours in weeks 3–6." That sentence is either empty, in which case move on, or it is the thing you have to solve before the proposal goes out.

Question 2: margin — does the money work at your real cost of delivery?

This is the question most agencies answer with instinct and then regret. Do it properly in four steps.

Step 1: work out an internal hourly cost per role. Take the role's salary, add employer costs, add a share of overhead, and divide by the hours that person is genuinely billable in a year — not contracted hours, billable ones. For illustration only: a $60,000 salary, plus employer on-costs, plus an overhead share, divided by the billable hours you actually expect from that role. Employer on-costs vary enormously by country, employment type and contract, so Wieldy does not publish a percentage for you to borrow. Get yours from your own payroll figures or your accountant. The same applies to overhead allocation — rent, software, non-billable staff — which is specific to your P&L.

Step 2: cost the delivery. Multiply estimated hours per role by that internal hourly cost. Sum it. That is your cost of delivery, and it is almost always higher than the number in people's heads, because the number in people's heads is a billing rate for one person rather than a loaded cost across a team.

Step 3: subtract from the proposed fee, including pass-through costs. Media spend, licences, stock imagery, print, third-party tools — if your agency fronts the money, it belongs in this calculation even though it is not your revenue. Pass-through costs that sit on your balance sheet are a cash risk as well as a margin risk.

Step 4: compare the gross margin to your floor. The floor is your decision, not an industry number. It depends on your overhead, your growth plans and how full your new business pipeline is. An agency with three other scopes in play can hold a higher floor than one with none. Write your floor down before you look at the deal, because deciding the floor after you see the fee is not deciding anything.

Two costs agencies routinely leave out of step 2:

• Sales commission on the won deal. If a rep earns commission on this contract, that money leaves with the revenue. A tiered structure means the rate can differ depending on where this deal lands in the rep's period — worth checking before you commit to a margin. (Tiered sales commissions, explained.)
• Account-management time. It is never in the estimate and it is always in the calendar. Status calls, client emails, chasing assets, internal co-ordination. Put a real hours figure on it per week for the life of the project.

The agency profit calculator and the retainer pricing calculator do this arithmetic for you. Both are free, with no sign-up and no email gate, and each shows the formula with a worked example so you can check the logic rather than trust it. If the scope is recurring rather than one-off, how to price your agency retainers covers the structural differences.

The honest conclusion from this section: a scope can be perfectly deliverable and still infeasible. Feasible means feasible at a price you will accept. A project you can absolutely do, at a margin below your floor, is a no — or a renegotiation.

Question 3: client-side dependencies — can they supply what you need?

Client delay is the most common cause of agency overruns and almost no feasibility article mentions it. The asymmetry is brutal: when the client is slow, your clock keeps running. Your team is booked, your overhead is burning, and the window you reserved is being consumed by waiting.

List the dependencies concretely before you price:

• Brand assets, fonts, logo files, image libraries
• Ad account, pixel, analytics and CMS access
• Product data, feeds, pricing, inventory
• Legal, medical or compliance sign-off
• A named decision-maker with authority to approve
• Content and copy approvals
• Access to their customers or internal stakeholders for research

Then ask these questions in the scoping call, out loud, and write down the answers:

1. Who signs off, by name?
2. How many people are in the approval chain between the draft and "yes"?
3. What is the longest an approval has taken you before?
4. What happens to the timeline if an approval slips by two weeks — do we extend, or do we compress our own time?

An unnamed approver is not an admin detail. It is a margin risk with a number attached. If the answer to question 3 is "three weeks sometimes," that is now an input to your schedule, not an anecdote.

Write the dependencies into the proposal as named obligations with dates: "Client supplies final product imagery by [date]. Each week of delay moves the delivery date by one week." Dependencies that live in a proposal are enforceable. Dependencies that live in a kickoff call are a disagreement waiting to happen. And approval trails are far easier to defend when they sit in one place with timestamps — a client portal with approvals, a shared project record — rather than scattered across email threads and WhatsApp.

Question 4: unbounded scope — what in this brief has no ceiling?

Scan the brief for language with no quantity attached. These five phrases do more damage to agency margin than anything else in a document:

The hourly rate for extra work is your own number. This page does not publish a recommended one, because it depends on your market, the seniority of the people doing the work and what you have already agreed elsewhere with this client. What matters is that the rate is named in the proposal, before signature. An out-of-scope rate you invent after the overrun has started is a negotiation; one that is in the signed document is an invoice.

Media buying is the biggest unbounded item for agencies that run paid. Spend moves between platforms mid-flight. The client raises the budget on a Tuesday and tells you on a Friday. Someone has to reconcile what was planned, what was spent, what was invoiced and what was actually recovered — and that reconciliation work is almost never scoped, never estimated and never billed. If paid media is in this scope, read tracking media-buying money flow before you price it, and decide explicitly whether spend passes through your accounts or the client's.

The rule to apply: if you cannot state the maximum quantity of a deliverable, you cannot price it fixed-fee. Either bound it or move it to a rate card.

Question 5: downside — what does it cost you if it overruns?

Stop asking whether the project will overrun. It might. Ask instead: if it overruns by 30%, does this lose money, or does it just make less? Sizing the loss is a different and more useful exercise than estimating the probability.

Run three cases on the same scope. The numbers below are illustrative only — they are not Wieldy data and not a benchmark — and exist to show the shape of the arithmetic.

Two things fall out of a table like that. First, a scope with a healthy headline margin can be one bad month from breakeven, and you want to know that before you sign rather than in month three. Second, the shape tells you how much protection the proposal needs: a scope that still clears your floor at 50% over can be priced loosely; one that goes underwater at 20% over needs caps, a phased structure, or a higher fee.

Once the work is live, the mid-flight version of this question is budget at completion (BAC) — the forecast of what the project will have cost by the time it finishes, based on what has been consumed so far. It is the same arithmetic, run with actuals instead of estimates, and it is the earned value concept most worth stealing for agency work. The budget at completion calculator does the maths; it is free with no sign-up. The discipline is checking it weekly rather than at the end.

Two risks that belong in the downside question but rarely get counted:

Opportunity cost. A thin-margin project that consumes your senior team also blocks the next project. If this scope takes your lead strategist for six weeks, the real cost includes whatever you cannot pitch or deliver in those six weeks. A 15% margin project is not merely a 15% margin project; it is a 15% margin project instead of something else.

Client concentration risk. A scope that would take one client to a large share of your revenue is a different conversation from a scope that would not. You should set your own exposure limit — the share of revenue you are willing to have riding on a single relationship — and check new work against it. There is no universal number; it depends on your contract lengths, notice periods and cash position.

What do you do when the answer is "not as written"? Four proposal rewrites

Most scopes do not fail cleanly. They fail on one question, which means they are signable after one specific change. Here are the four, each matched to the failure it fixes.

Phase it — fixes a capacity or dependency failure

Split the work into a discovery or phase-one deliverable with its own fee, and a decision point before phase two. This solves two problems at once: you only have to staff the next eight weeks, not the next six months, and you learn how this client actually behaves on approvals before you commit to the big number. A discovery phase is also the honest answer when you genuinely cannot estimate the main build until you have seen their data or their stack. It protects both sides — the client is not committing a six-figure budget to an agency they have not worked with.

Cap it — fixes unbounded scope

The fixed fee covers a stated quantity: three concepts, two revision rounds, six assets. Everything beyond that quantity is billed at your standard hourly rate, named in the proposal. This is not a hostile clause; it is the clause that stops the relationship souring in month four, because the client knows the price of a fifth revision before they ask for it.

Reprice or restructure — fixes a margin failure

Four options, in roughly the order clients find them acceptable:

• Reduce the deliverable set to fit the budget they have. Often the easiest yes.
• Raise the fee, with the cost of delivery arithmetic ready to explain why.
• Move from fixed fee to retainer if the work is genuinely ongoing, which converts an estimating risk into a monthly capacity commitment. Fixed-fee pricing is a bet on your estimate; a retainer is a bet on your capacity. Choose the one you are better at.
• Move pass-through media spend out of the fee entirely, so the client funds the platforms directly and you are not carrying their ad budget on your balance sheet. This can change a marginal deal into a comfortable one without the fee moving at all.

Decline — when it fails more than one question, or fails the downside test badly

Say it early, say it plainly, and give a reason that is about fit rather than about them. Something like: "Having costed this properly, we can't deliver the scope to this timeline at a price that works for both of us. Here is what we could do instead at this budget — and if the budget is fixed, I'd rather tell you now than halfway through." Offer the smaller version if one exists. A well-reasoned no is a credibility builder with exactly the kind of client worth having, and the clients who respect it come back with a better-funded brief.

Whichever rewrite you choose, the feasibility verdict should be visible in the document the client signs. Assumptions, named dependencies with dates, revision caps and the out-of-scope hourly rate all belong in the proposal and then in the statement of work — not in an internal file that nobody reads again. The free agency proposal template has sections for exactly these; it is free, editable in the browser, and downloadable as Word or PDF with no sign-up.

What should an agency feasibility checklist include?

Run this in the scoping meeting. It is designed to be worked through in under an hour.

1. Capacity

• [ ] Roles the scope needs, listed
• [ ] Hours per role, estimated
• [ ] Unbooked hours per named person in the delivery window, after retainers
• [ ] Revision capacity built in, against your own utilisation target
• [ ] Freelance cover identified, and its cost added to Question 2
• [ ] One-line verdict written: short X hours in weeks Y–Z, or clear

2. Margin

• [ ] Internal hourly cost per role calculated (salary + employer costs + overhead share ÷ billable hours)
• [ ] Cost of delivery = hours × internal cost, summed
• [ ] Pass-through costs identified and allocated (media, licences, print, stock)
• [ ] Sales commission on the deal included
• [ ] Account-management hours included
• [ ] Gross margin compared to your written floor

3. Client dependencies

• [ ] Every input the client must supply, listed
• [ ] Named approver identified, with the full approval chain
• [ ] Their historical approval speed asked about and recorded
• [ ] Timeline consequence of delay agreed and written into the proposal

4. Unbounded scope

• [ ] Brief scanned for "as required", "ongoing", "until approved", "unlimited", "related"
• [ ] Every deliverable has a maximum quantity
• [ ] Revision rounds numbered, and a "round" defined
• [ ] Out-of-scope hourly rate named in the proposal
• [ ] Media spend reconciliation work scoped and costed, if paid media is involved

5. Downside

• [ ] Margin modelled at estimate, 20% over and 50% over
• [ ] Opportunity cost of the senior hours considered
• [ ] Client concentration checked against your exposure limit
• [ ] Verdict recorded: accept / accept with changes / decline — and which rewrite

Once the verdict is in, the next two artefacts are the proposal and, eventually, the invoice. Both the free agency proposal template and the invoice generator are free with no sign-up, alongside the rest of the free agency calculators. If you want the ongoing version of this discipline rather than the per-scope one, the five numbers every agency owner should watch covers what to track monthly.

Frequently asked questions

What does feasibility mean in simple terms?

Feasibility means whether something can realistically be done with the resources, time and money available — and whether it is worth doing. For an agency, "can be done" is rarely the hard part. The real test is whether you can do it with the people who are not already booked, at a fee that leaves a margin you are willing to accept.

What is the difference between a feasibility study and a feasibility assessment?

A feasibility study is a formal, often months-long evaluation of a major investment, producing a written report for a board or lender. A feasibility assessment is the fast, internal go/no-go check you run on a specific piece of proposed work before committing resources. Agencies need the second. The output is a decision and a revised proposal, not a document.

How long should an agency spend assessing a scope?

Under an hour for most scopes, and the order matters: check capacity first because it takes ten minutes and can kill the deal outright, then cost the delivery, then interrogate the client dependencies. Spend longer only on scopes that are large relative to your revenue or that would make one client a significant share of your income.

What are the five areas a feasibility assessment covers?

Generic project management lists technical, economic, legal, operational and scheduling feasibility. For agency scopes, the five that actually decide the answer are capacity (can we staff it), margin (does it work at our real cost of delivery), client dependencies (can they supply what we need), unbounded scope (what has no ceiling) and downside (what it costs us if it overruns).

Who should run the feasibility check — the account lead or the delivery lead?

Both, in the same room, and the delivery lead has the veto on hours. Account leads are optimistic about timelines because they are closest to the client's enthusiasm; delivery leads know who is actually booked. The owner or finance lead signs off on the margin floor, since that is a business decision rather than a project one.

Can a project be feasible and still not worth taking?

Yes, and this is the most common honest answer. A scope can be entirely deliverable and still fail on margin, on opportunity cost — because it consumes the senior team that a better project needs — or on concentration risk, if it would leave too much of your revenue dependent on one relationship. Deliverable and worth doing are separate tests.

Keeping the feasibility answer in one place

The reason feasibility checks get skipped is not laziness. It is that the inputs live in four different places: capacity in a spreadsheet someone updates on Mondays, hourly rates in the founder's head, what the last similar project actually cost buried in old invoices, and the commission on the deal in a separate file the salesperson maintains. Pulling those together takes long enough that, under deadline, people guess instead.

Wieldy is agency management software built to keep them together. Proposals, clients and retainers, projects and tasks, invoicing and expenses, and tiered sales commissions sit in one workspace — so the cost of delivery, the people who are genuinely free, and the commission that will come off this deal are all visible while the scope is still a proposal rather than a problem. Wieldy is priced flat per workspace, not per user and not per client, which matters here: assessing one more prospective project should never add to your software bill. You can open the live demo workspace with sample agency data from wieldyapp.com without creating an account, or start the free trial.

About the author. Ed Kamel is the founder of Zerak and Wieldy. Wieldy began as the internal system of the marketing agency he runs, which is why retainers, sales commissions and media-buying money flow are core features rather than add-ons — he built them to answer these questions about his own scopes. Published September 2026. Reviewed by the Wieldy team.