Buying a template for a client project: what to know first
When buying a template for a client, check whether the license covers work delivered to a third party, decide upfront whether the client or you holds the purchase and account, and be transparent with the client that the site started from a template. All three prevent problems that surface later, usually at the worst time.
Using a template for client work is a completely normal, sensible way to deliver a professional site faster than building from scratch. But buying one for a client is a slightly different transaction than buying one for yourself, and three questions are worth settling before you hand over an invoice: does the license actually allow this, who owns the purchase, and how do you talk about it with the client.
Check the license covers client delivery
Not every template license is written the same way, and the difference matters here specifically. Some licenses are scoped to a single end product used by the purchaser — meaning the account that buys it is meant to be the one using the finished site. Others are explicitly written to allow a designer or agency to build and deliver a site to a separate client. Using a personal-use license to build paid client work, when the license doesn't cover that, is the single most common licensing mistake in this scenario — not because anyone's being dishonest, but because the distinction is easy to miss when you're moving fast.
The fix is simple: read the licensing terms for the specific marketplace before you buy, specifically looking for language about commercial use, client work, or delivering the finished product to a third party. Template Market's own licensing terms are laid out at /licensing — if you're buying elsewhere, look for the equivalent page rather than assuming all marketplaces license the same way.
| Question | Why it matters |
|---|---|
| Does the license cover work delivered to a third party? | Determines whether this purchase is even valid for the use case |
| Does the client need their own license, or does yours cover them? | Some licenses transfer with the delivered site, some don't |
| Is there a limit on the number of end products per license? | Relevant if you plan to reuse the same template across multiple clients |
| Who legally owns the purchase — you or the client? | Affects who can access support, updates, and future licensing questions |
Decide who holds the purchase and account
There are two common models, and neither is wrong — but pick one deliberately rather than defaulting into whichever is easiest in the moment. In the first, you (the freelancer or agency) purchase under your own account, and the license terms determine whether that covers delivering the finished site to your client. In the second, the client purchases directly, under their own account, and you do the customization work as a separate service.
The second model has a real advantage worth considering: if the client owns the purchase, they retain direct access to any future updates, support and licensing questions without going through you. That matters if the relationship is a one-off project rather than an ongoing retainer — you don't want to be the permanent bottleneck for a client's access to their own site's template updates two years after the project ended.
- 1Decide the ownership model before quoting the projectClient-owns-the-purchase or you-own-the-purchase — pick one and say so.
- 2Confirm the license fits that modelRead the terms for third-party delivery or account-transfer language.
- 3Document the decision in the project agreementA line or two is enough — it prevents a confused conversation later.
- 4Hand over account credentials if the client owns itDo this at project handoff, not as an afterthought months later.
Being honest with the client about the template
Some freelancers worry that telling a client "this is built from a template" undersells the work. In practice, the opposite is usually true. Clients generally care about the outcome — a professional site, delivered on time, at a fair price — far more than whether it started from a blank file or a well-built starting point. Framing a template-based build honestly, as a deliberate choice that gets them a better result faster and often cheaper than a fully custom build, tends to land better than either hiding it or over-apologizing for it.
The one thing worth avoiding is presenting a lightly customized template as if it were built entirely from scratch when a client specifically asks or when pricing implies custom development. That's less a legal issue and more a trust issue — and trust is the actual product in a freelance or agency relationship, not the code.
What this looks like across relationship types
A one-off project for a client you may not work with again leans toward client-owned purchase — it's cleaner for both sides once the engagement ends. An ongoing retainer relationship, where you're likely to be the one making future updates anyway, can reasonably use either model, since you'll be the one interacting with the template's updates regardless of whose name is on the account. An agency standardizing on a small set of templates across many clients needs to read licensing terms most carefully of all, since volume increases the odds of hitting a per-license limit you didn't notice on your first read.
- ✓Confirm the license explicitly covers delivering the finished site to a third-party client.
- ✓Decide deliberately whether you or the client owns the purchase and account — don't default by accident.
- ✓Client-owned accounts give them independent access to future support and updates.
- ✓Be transparent that the site started from a template — clients generally care about outcome, not origin.
- ✓Agencies reusing one template across many clients should check for per-license or per-project limits.