Little purchases, easy to lose
A designer buys a stock image for a poster, a font family for a brand identity, a plugin to speed up a layout. Each purchase is modest and each is paid by card in a minute. By the month’s end, the statement lists half a dozen small charges with unfamiliar merchant names, and nobody remembers which project each was for.
Those charges are not overhead. They were bought for particular jobs, and the jobs should carry them.
Tag at the moment of payment
The habit that fixes this is simple: when a purchase is made, add the project name to the transaction straight away. If the same asset might be used for several jobs later, note that too. A line such as “licence for brand typeface, Project A, may reuse for Project B” captures the intent.
Doing it later, from memory, means guessing. Doing it at once means the project’s cost is accurate by the time the final invoice is sent.
Know what the licence allows
Licences differ. Some allow use in a single project, others across many, some only for personal work, some include extended rights for print runs or resale. The fine print decides whether an asset bought for one client can safely be used for another. Read it, and save a copy of the terms with the purchase.
The details vary by seller and by licence, so the seller’s own terms are the authority. A saved copy turns later questions into a quick check.
Pass the cost on, or absorb it deliberately
Decide how asset costs are handled in quotes. Some designers include them in the fee. Others list them as a separate line. Either approach works if it is stated up front. The mistake is leaving them out of the price and then paying out of the margin without noticing.
| Approach | Advantage | Watch for |
|---|---|---|
| --- | --- | --- |
| Included in fee | Simple for the client | Margin shrinks if assets are costly |
| Itemised line | Transparent | May invite haggling |
| Client buys directly | No upfront cost to the designer | Client may pick restrictive licences |
Build a reusable library carefully
Assets that will be used again and again, such as a core typeface or a plugin used on every job, are better treated as business tools than project costs. Record them under software or tools, and spread the cost over expected use. Reserve project tagging for items bought for one job only.
Review once a quarter
Scan the quarter’s small asset purchases. Which were used? Which were never needed? Which could have been replaced by free options with suitable licences? A few honest reviews reduce the habit of buying just in case.
In SpendixAI, a category for project assets with project tags lets a report show how much each job spent on resources. That figure, set beside the project fee, is one of the more useful signals of whether quotes cover real costs.
When the client supplies the assets
Some clients send their own images, fonts or plugins, or insist on buying through their own account. Record nothing in the business books for these, but save a note of whose licence covers the work and who holds the files. If the project is handed over, the licence details should go with it.
Confusion arises when an asset purchased by the designer is delivered inside a finished file without the client having a licence of their own. Spell out in the handover who holds the licence and what happens if the work is later reused or adapted by someone else.
Linking asset costs to the quote
At the quoting stage, list the assets that the job may need and their likely cost. After delivery, compare the quote with actual spending. If assets regularly cost more than planned, update the standard allowance. If they cost less, the surplus is a pleasant addition to the margin. Either way, the comparison turns small, scattered purchases into a clear input for better pricing.
Useful ideas start with a clearer picture of your own spending.
Explore your reports


