How to Calculate the Monthly Cost of a Design Subscription per Completed Request

A design subscription might cost $2,000 a month, but that number does not tell you what your team paid for each finished landing page, ad set, or sales deck. To make a useful comparison, calculate the design subscription cost per design request using completed work—not the provider’s advertised capacity or the number of tasks your team submitted.

The calculation is simple. The judgment lies in defining “cost,” deciding what counts as one completed request, and choosing a period that reflects how your team actually works. Get those details wrong and a precise-looking number can still lead to a poor decision.

The basic cost-per-request formula

Start with this formula:

Cost per completed request = total subscription-related cost for the period ÷ requests completed in that period

For a straightforward view, use the amount your business paid the provider during the month. For a fuller operating-cost view, add directly related expenses and the value of your team’s time spent managing the work. Keep the two versions separate: the invoice-based figure answers “What did the service cost us?” while the fuller figure answers “What resources did this workflow use?”

For example, say a team pays $2,400 for a monthly plan and $180 for a separately billed stock-image or rush fee. If the provider completes eight requests that month, the invoice-based cost is $2,580 divided by eight, or $322.50 per completed request.

That is a useful starting point, not a verdict on value. Eight small image crops are not equivalent to eight substantial campaign concepts. The number becomes more meaningful when you make the denominator consistent and look at the work behind it.

Decide what belongs in the monthly cost

Include costs tied to using the service

Use the charges that your team needs to incur to get the work delivered. Depending on the plan, that may include:

• The recurring subscription fee.
• Additional seats or a second active request slot.
• Rush fees, paid add-ons, or one-off charges from the provider.
• Required third-party assets or licensing costs paid by your business.
• An onboarding or setup fee, if you want to account for the first year’s true cost.

If setup costs are a one-time expense, do not quietly bury the full amount in one ordinary month and then omit it later. Either show it separately or spread it across a stated period. For example, a $600 setup charge spread across a 12-month evaluation adds $50 per month to that view. That is an accounting choice for comparison, not a claim about how the provider bills.

Do not count an expense twice. If the plan fee already includes a stock-asset allowance, do not add an estimate for those same assets as a separate cost. Record what was actually paid, and note any assumptions where costs are shared across projects.

Track internal time as a separate layer

Someone on your team may spend time writing briefs, finding examples, answering questions, reviewing drafts, and routing approvals. That effort can be material, especially when requests arrive incomplete or several stakeholders give conflicting feedback.

For an expanded cost view, estimate those hours and multiply them by an appropriate hourly cost. Suppose the team spent 10 hours coordinating work in the example month, and you use an illustrative internal cost of $45 per hour. That adds $450. The expanded total is $3,030, or $378.75 per completed request.

Be clear about what your hourly figure represents. Salary divided by working hours is not always the same as the full cost of employing someone. The U.S. Bureau of Labor Statistics’ Employer Costs for Employee Compensation data reports wages and benefits as separate components of employer compensation. Use a consistent loaded rate if you want to include benefits and employer costs, or label your calculation as salary-only. If the employee’s time is fixed and would be paid regardless, show internal hours as a workload measure too; do not imply that every hour is an additional cash expense.

Define a completed request before counting

A request should have a clear scope and a clear finish line. A practical definition might be: “One agreed deliverable or closely related set of deliverables, completed to the approved brief, with the included revision rounds finished and files handed over.” Your definition can differ, but keep it stable from month to month.

Consider a request for a three-panel social campaign. If the provider treats the panels as one brief, and the team receives all three approved files together, count it as one request—not three—unless you have deliberately defined each panel as a separate unit. Likewise, a landing page design with desktop and mobile layouts is often one scoped deliverable, not two unrelated requests.

Do not count a request as complete just because a first draft arrived. If substantial revisions are still underway, it is still in progress. Conversely, if the provider delivered the agreed files and the team later changes its mind about the brief, record that as a new request or a change in scope according to your rules. This makes rework visible rather than hiding it in the original item.

Written request and revision boundaries matter here. The OpenStax explanation of job-order costing illustrates why assigning costs to defined jobs depends on knowing what work belongs to each job. You do not need formal accounting software to use the principle: define the unit, then track its costs consistently.

Use a real example, not the advertised capacity

Imagine a small marketing team with a $2,400 monthly plan. During one month it has the following outcome:

• Six requests are completed and approved.
• Two requests remain in progress at month-end.
• One request is paused because the team has not supplied copy.
• The team pays $180 in additional fees.

For that month, the invoice-based cost per completed request is $2,580 divided by six, or $430. The two in-progress items and the paused item do not belong in the completed-request denominator. They should remain visible in your tracking, though: they may explain why monthly output is low.

Do not divide the fee by the number of requests the plan says it can handle. Capacity is not the same as completed output. A provider might permit several requests in a queue while working on them sequentially, or a team may not have enough ready-to-work briefs to use the service. To check whether the plan has enough practical throughput, assess the active-work rules and expected turnaround separately. Our guide to estimating design subscription capacity covers that question.

Make mixed workloads easier to compare

A single average can conceal a lot. If a month includes five minor banner updates and one complex product-page design, $430 per request does not mean each item consumed the same effort or delivered the same value.

Use two views side by side:

• Average cost per completed request: monthly cost divided by completed requests. This is quick and useful for monitoring a stable workload.
• Cost by request type: group work into a few useful categories, such as small updates, standard assets, and larger design projects.

A lightweight log might record the request name, category, date submitted, date completed, provider fees, internal coordination hours, and whether it required a new brief after approval. Avoid creating so many categories that nobody keeps the log current.

If you want to compare months with different mixes, you can create weighted units. For example, your team might agree that a small update equals one unit, a standard asset equals two, and a larger project equals four. Divide the monthly cost by the weighted units completed. Those weights are your planning assumptions, not objective measures of design quality. Revisit them when experience shows that the categories do not reflect the work.

Choose an accounting period that fits the workflow

One month is easy to understand, but it can be misleading when requests span month-end. A large job submitted in March and completed in April makes March look expensive and April unusually productive if you use only cash paid and completed count for each calendar month.

For a quick operational check, calculate monthly results and label in-progress work. For a decision about renewing a plan, also review a longer period—such as a quarter—so one quiet month or a delayed approval does not drive the conclusion. Use the same time window for costs and completed requests, and explain any fees paid in advance or setup costs that you have spread across the period.

For a formal estimate or budget, write down the assumptions, what is included, and how the denominator is defined. The U.S. Government Accountability Office’s Cost Estimating and Assessment Guide emphasizes documenting the basis and assumptions behind estimates. That discipline is useful even for a small team: it lets someone else understand or update your calculation later.

Use the number to make a decision—not to rank every option

Compare the result with alternatives only when the scope is reasonably similar. A freelancer may charge by project, an agency may bundle strategy and account management, and a full-time hire includes ongoing responsibilities beyond producing a set number of assets. Put the same types of work, review effort, and licensing costs into each comparison where possible.

Also ask whether the completed work was usable. A low average can be poor value if deliverables repeatedly miss the brief, require extensive internal repair, or arrive after the campaign deadline. A higher figure may make sense if it replaces a bottleneck, gives the team predictable access to production support, or includes work that would otherwise be delayed. If the workload is irregular, consider whether a subscription is a good fit at all; our guide to subscriptions versus freelancers for uneven workloads outlines the trade-offs.

Before acting on your calculation, check three things: the completed-request count follows a written rule, the costs include the fees you actually paid, and the period is long enough to reflect your normal workflow. If those are true, the figure is a practical signal—not a universal price for design.

FAQ

Should I count revisions as separate requests?

Usually not when they are revisions within the agreed scope. Count the request once when the agreed deliverable is complete. If a later change substantially alters the brief, record it as a new request or scope change under a rule you apply consistently.

What if a request is still in progress at month-end?

Do not include it in that month’s completed-request denominator. Track it as in progress, along with its submission date and any costs that apply. Review longer periods as well, particularly when work often crosses month boundaries.

Should I include my team’s review time?

For a fuller view of the resources used, yes: record the hours and state the hourly-cost assumption. Keep that figure separate from the provider invoice total so readers can tell cash spending from internal effort.

Is cost per request useful if requests vary in size?

It is useful as a broad trend, but it can hide differences in scope. Add a small number of request categories, or use clearly labeled weighted units, to compare months with different work mixes.

How many months should I review before renewing?

There is no universal minimum. Review enough months to include a representative workload, and consider a quarterly view if approvals or project sizes vary substantially month to month. Note unusual delays or one-off fees rather than treating them as typical.