A freelancer or small agency can use free AI web design tools for concepts, wireframes, mock-ups and first drafts, then move paid client sites to plans the client owns. Free plans stop at credits, custom domains, export, transfer and commercial terms, so check those four before building anything the client will see live.
A free plan is built to let you try the tool. A client site is built to be owned, hosted on the client's domain and handed over cleanly. Those goals collide in predictable places, and the vendors' own pricing pages, read on 4 November 2026, show where: custom domains behind a paywall, code editing and export reserved for paid plans, and at least one free plan its vendor describes as ideal for non-commercial use.
The four limits that matter on a client job
Most comparisons list features. For client work, the four questions below decide whether a free plan is usable.
- Credits. How much AI can you use before the tool stops? Free allowances are small and sometimes reset daily or monthly.
- Domain and publishing. Can the site go live on the client's own domain, or only on the vendor's subdomain?
- Export and portability. Can the site, or its code, leave the platform if the client moves hosts or changes agency?
- Ownership and terms. Whose account is it in, does the free plan allow commercial use, and can the project be transferred to the client's account?
What the free plans say today
| Tool | Free allowance (vendor's page) | Agency limits to note |
|---|---|---|
| Figma (Starter) | 150 AI credits a day, up to 500 a month; unlimited drafts | A design and prototype tool on Starter; Figma Sites (beta, for publishing websites) is listed on paid Full seats. Professional is from $16 a month for a Full seat with 3,000 AI credits (check monthly against annual billing); the page did not state commercial terms for Starter |
| Framer (Free) | A free Framer domain; 1,000 pages; 10 CMS collections; 500 AI credits, available only while the workspace has no active subscription; 1 GB bandwidth; 5 MB uploads; up to three editors | Framer's FAQ calls Free ideal for non-commercial use; a custom domain needs a paid plan (Basic $10, Pro $30 a month as shown with yearly billing); the page did not address transfer or export, so ask before you build |
| Lovable (Free) | 5 build credits a day, up to 30 a month, plus small monthly grants for Cloud hosting and AI features | Free allows workspace-private projects and GitHub sync, but not code editing, code download, a custom domain or removing the "Edit with Lovable" badge; Pro starts at $25 a month |
| Webflow (Starter) | A webflow.io address; 2 static pages; limited CMS; 1 GB bandwidth; 50 form submissions | A custom domain starts with the Basic site plan ($15 a month billed yearly); code export needs a paid Workspace plan, and exported forms stop working |
| Wix | A free plan on a wixsite.com address; a free AI website builder | Wix says its sites must be hosted on its own servers, so they cannot move to another host; a site can be transferred to the client's own Wix account |
| Canva (Free) | Limited access to Standard and Premium AI; one Brand Kit with three colours only | Good for graphics, social assets and presentations; Pro is $144 a year with five Brand Kits; confirm the licence for client use |
The table is a snapshot. Credits, prices and rules move, and the point is the questions it prompts, not the exact numbers. If a figure matters to a quote, open the page again on the day.
Where each tool fits in an agency workflow
Figma: wireframes and design directions
Figma's free tier fits the early stage. Use the AI credits to generate layout directions for a home page, a services page or a pricing table, then refine by hand. The output is a design file, not a live site, so there is no domain or export problem, and the work belongs to your workspace until you share it. The limit is credits: 150 a day sounds roomy, but a few rounds of generation and edits can take it. Use it for first drafts, then work manually.
The Complete Excel Course with AI Integration
From formulas and pivot tables to Power Query, DAX, VBA and AI with Copilot, ChatGPT and Claude — hands-on from the first lesson.
By Sagnik Bhattacharya and Virginia Thorn, Primetime Emmy Award winner
Buy nowFramer: a fast live site, with a domain limit
Framer lets you publish a real site on its free domain, which is handy for a clickable prototype a client can open on their phone. The custom domain needs a paid plan. The free AI credits apply only while the workspace has no active subscription, so the moment you upgrade for a client's domain, the free allowance stops. Framer's own FAQ also describes Free as ideal for non-commercial use, which is one more reason not to run a client's business site on it. For a client site, plan on the paid plan from the start and put it in the client's name.
Lovable and similar prompt-to-app tools
These tools generate working code from a conversation. The free allowance of five build credits a day is enough for a small experiment, and not enough to build and refine a full site with a client's changes. They shine for a landing page, a booking form or a small calculator that you would otherwise brief to a developer. For a content-heavy brochure site, a page builder is usually faster and easier for the client to edit afterwards. Note what Lovable's Free plan withholds: you cannot edit or download the code or connect a custom domain there, though it does sync to GitHub, which is the route to keeping a copy the client owns.
Wix, Canva and other site-builders with AI
Builders with AI generation attract small clients because they are simple. The agency question is portability. Wix's help centre says its sites need to be hosted on Wix's servers, so a client on Wix is tied to it. That is acceptable if the client knows it and chooses it, and ownership can still move: Wix lets you transfer a free or premium site to another Wix account, so you can build in yours and hand it to the client's. Webflow sits at the other end: on a paid Workspace plan you can export the site's code and host it elsewhere, though CMS content exports collection by collection and forms stop working. Canva's strength is graphics, so it is better for brand assets and social posts than for building the site.
A worked example: a five-page site for a childcare nursery
This is an illustration with made-up numbers. A two-person agency is asked to build a five-page site for a childcare nursery: home, rooms and fees, about us, enquiry form, policies. The nursery owner has a logo, brand colours and a photo set, and wants to see something in a week. The agency's budget for tools is zero until the client commits.
- Day 1, brief and copy (no tool credits). A free chat assistant drafts page copy from the owner's answers, and the agency edits it.
- Day 2, design directions in Figma Starter. Three home-page directions, generated from a prompt that includes the colours, a sample headline and the sections. Roughly 60 credits of the daily 150, by the agency's count.
- Day 3, owner approval. The owner picks one direction and asks for warmer photos and larger text.
- Day 4 to 5, clickable prototype. The agency builds the five pages on a free Framer domain to show the flow, keeps the link private, and does not publicise it, since Framer pitches Free at non-commercial use. The enquiry form is mocked, not live.
- Day 6, the decision. The owner approves. The agency now has to choose where the live site lives: a paid plan in the nursery's name with the nursery's domain, or a handover of design files to a developer.
- Day 7, switch to paid and migrate. The site is rebuilt or transferred under a paid plan owned by the client, with the domain connected and analytics installed.
The tool cost until approval: nothing. After approval: one paid plan, billed to the client. The risk the agency avoided is the common one: building the whole live site on a free account of its own and finding, at launch, that the domain, hosting and handover terms do not suit the client. A nursery site also touches children's data in the enquiry form, so the form tool and its privacy wording need care; the safe-use points are in using AI with children's data in a nursery.
A prompt that gets a usable design direction
Generic prompts give generic sites. The prompt below gives the tool the brand, the content and the constraints, which is what makes a first direction usable. An illustration for a craft brewery supplier's trade site:
Design a home page for a trade-only craft brewery supplier.
Audience: head brewers and bar managers placing repeat orders.
Brand: deep green (#1F4D3A) and cream, a serif headline font, plain body text. No stock photos of people.
Sections in order: headline with one-line promise, three product categories as cards, a "reorder in two clicks" strip, delivery areas and times, trade account sign-up form, footer with contact details.
Tone: practical, no slogans. Body text at least 16px. Buttons with clear labels.
Return the layout with real headings and sample copy, not lorem ipsum.An illustrative result is a clean layout with a green hero, three category cards and a sign-up form. The fixes you make are the useful part of the exercise: the sample copy claims "next-day delivery everywhere", which the supplier cannot promise; the cards use three similar icons that mean nothing; the body text colour is a pale grey that fails contrast. Replace the copy with the client's own, redraw the cards with real product photos and darken the text. The tool saved the layout work, and you did the thinking.
Generic output and how to fix it
AI-built sites share a look: a large gradient hero, three feature cards, a testimonial strip, a final call to action. Clients may not mind, but their customers have seen it many times. A before and after, as an illustration, for a kitchen fitter:
- Before: headline "Transform Your Space With Innovative Design Solutions". Three cards: "Quality", "Service", "Value".
- After: headline "Fitted kitchens, measured, built and finished by the same two people". Three cards: "Survey and quote in one visit", "Fitted in 5 to 7 working days", "A snag list we finish before we leave". Each card links to a real example with photos.
The second version has facts a visitor can act on, and none of them came from the AI. They came from asking the client three questions. The rule: let the tool lay out the page, and let the client's real details fill it.
Four questions that pick the platform for each client
When a client asks "can we just use Wix, or one of those AI builders?", answer with a short test, not a preference.
- Will the client edit the site themselves? If yes, choose a builder with a visual editor they can learn in an hour, and plan a handover session.
- Might they change agency or host in the next three years? If yes, prefer a platform that lets the site move, or accept that a rebuild is the exit cost, and say so in writing. Wix, for example, says its sites must be hosted on Wix's servers, while Webflow allows code export on paid Workspace plans.
- Do they need custom behaviour? Bookings, calculators, member areas and integrations push you towards a platform that supports them without hacks, or a developer.
- What can they spend monthly? A free plan with a vendor subdomain does not suit a business that wants customers to trust the address. A first paid plan is often a modest monthly sum; confirm it on the day.
Write the answers on a one-page recommendation. It protects you if the client later says "nobody told us".
A quick sum: what a first-year tool stack can cost
An illustration with plan prices from the pages above, for a freelancer building four small client sites in a year, using Figma and Framer. The design tool free tier covers the concepts for all four. Each client takes a platform plan in their own name; on the listed Framer prices that is $10 a month for Basic or $30 a month for Pro, billed to the client, so $120 to $360 a year each depending on the plan. If the freelancer's own credits run out and they take a Figma Professional Full seat at $16 a month, that is $192 a year, which one retained client can cover. Check each price on the day, since annual billing and regional display can differ from what a page first shows.
The useful habit: decide in the proposal who pays for which plan. Writing "platform plan, billed to client, $X per month" keeps the freelancer from absorbing a recurring cost and keeps the client in control of the account.
A scoring template for any new tool
New AI design tools launch every month, and each has a different free plan. Instead of reading a list, score the tool on the four limits with a short template. Copy it into a document and fill it in for each candidate.
| Question | Where to find the answer | Example entry |
|---|---|---|
| Credits per day or month on Free | Pricing page | 150 a day, 500 a month (design tool) |
| Custom domain on Free? | Pricing page, plan table | No, paid plan only |
| Can the project move to the client's account? | Help centre search for "transfer" | Yes, via workspace transfer; or unclear, ask support |
| Can the site or code be exported? | Help centre search for "export" | Code export on paid plans only; or not possible |
| Commercial use on Free? | Terms of service | Stated for all plans; or silent |
| Where is data stored, and can uploads be used for training? | Privacy policy, settings | Opt-out found in settings |
| Date checked and by whom | Your own note | 4 November, owner of the agency |
When an answer is "unclear", email the vendor and keep the reply. A tool with unclear terms can still be used for internal drafts, but not for anything the client pays for.
Ownership and hand-over: what to settle with the client in writing
An agency's biggest exposure with free tools is not quality, it is ambiguity about who owns what. Put these in the proposal or the contract, in plain words:
- Which platform the site is built on, and why it was chosen.
- Whose account it lives in, and who pays for the plan.
- What the client receives at hand-over: logins, domain control, design files, any exported code, content in an editable form.
- What happens if the client leaves: whether the site can be exported or transferred, and at whose cost.
- That AI tools were used for drafts and images, and which parts were reviewed by a person. See whether to tell clients you use AI for wording.
A realistic mistake: a freelancer built a site on a free plan in their own account, connected the client's domain through a paid upgrade on the freelancer's card, and later fell out with the client. The client had no login and no export. Nothing in the contract said who owned the account. The fix, after weeks of friction, was a paid transfer and an apology. It is cheaper to settle ownership on day one.
The hand-off checklist
Use this on every client site, whichever tool built it. Tick each item before the final invoice.
| Item | Done when |
|---|---|
| Account ownership | The site lives in the client's account or a transfer has been completed |
| Billing | The client's card pays the plan; renewal dates are written down |
| Domain | The client controls the registrar login; DNS records are documented |
| Logins | Admin accounts for the client; yours removed or reduced to a named support role |
| Content | Copy and images are provided in editable files, with image licences noted |
| Design files | Source files shared or handed over as the contract says |
| Forms and data | Where form submissions go is documented; consent and privacy text checked |
| Analytics and search | Tracking and search-console access are in the client's name |
| Backups and export | A current export or a note of how to take one, and what cannot be exported |
| Edit guide | A one-page guide for the five changes the client will make most |
| AI disclosure | The client knows which parts used AI and which assets are generated |
| Support terms | What is covered after launch, for how long, at what rate |
An illustrative filled line: "Account ownership: transferred to the owner's Framer workspace on 12 November; Basic plan billed to the owner's card; renews 12 December." Short, dated and checkable.
Check the AI output before a client sees it
AI web design tools are fast and sloppy in particular ways. A review pass on each page catches most of it.
- Copy: replace placeholder claims. A generated "award-winning team" line is a claim the client may not be able to support.
- Images: check each image's licence or generation terms, and avoid generated people for a business that is about real staff.
- Accessibility: text contrast, heading order and alt text. Generated layouts often use pale grey on white.
- Mobile: view every page at phone width; generated sections can overflow.
- Links and forms: click every button and submit every form; a mocked form that looks live is a classic launch-day miss.
- Speed: large generated images slow pages; compress them before launch.
When the site is live, an afternoon SEO audit with AI gives the client a baseline.
When to pay, and for which tool first
A free plan has done its job when the client has chosen a direction. From then on, spend where the limit bites. For most small agencies that means: the platform plan for the live site, paid by the client; one design tool seat if the free credits run out weekly; and a chat assistant plan if long drafting sessions hit caps. Keep the sum visible: a typical agency tool stack for a handful of clients is a short list of monthly plans, and the recurring cost belongs in your quote or retainer, not in a surprise invoice. If you would like help choosing a stack and a workflow for your agency, that is what my AI implementation consultation covers.
Free web design AI: agency questions
Can I build a live client site on a free plan?
Sometimes, but rarely well. Free plans usually serve the site on the vendor's own subdomain, and a custom domain needs a paid plan, as Framer's pricing page shows. Use free tiers for mock-ups and approvals, and move the live site to a plan the client pays for and owns.
Who should own the account the site is built in?
The client, wherever the tool allows. Build in a workspace you control while you design, then transfer or recreate it under the client's account, with their billing details. If a tool cannot transfer a site, tell the client before you begin, because moving later means rebuilding.
Do free plans allow commercial use?
Terms differ by tool and by plan, and several pricing pages do not state it. Framer's FAQ, for one, describes its Free plan as ideal for non-commercial use. Read the terms of service for the exact plan, record the date, and ask the vendor in writing if it is unclear. Do not assume a free plan covers client work just because it is not forbidden.
How do I stop AI-built sites looking generic?
Start from the client's brand material and real content, not a blank prompt. Give the tool colours, type, tone and actual copy, and use it for structure and variants. Then adjust spacing, imagery and details by hand, because the default look is what makes AI sites resemble each other.
Further reads
- How to Write Your Website Copy With AI: Home, About, and Services — Write the site copy that goes into the design.
- How to Write Website Articles With AI That Still Rank on Google — Add articles that can rank after launch.
- How Much Does a Website AI Chatbot Cost, and Will It Pay Off? — Cost the chatbot clients often ask to add.
- AI Content Workflow for Agencies: From Brief to Approved Draft — Agency workflow from brief to approved draft.
- AI Rollout Plan for a Ten-Person Marketing Agency — Roll AI out across a ten-person agency.
- Figma Make for Web Designers: Client Prototypes and Where It Breaks — How a web designer can turn a brief into a clickable Figma Make prototype, which plan to check, and the places it tends to fall short on real client work.
- Web Design Client Questionnaire: Collect Content and Goals With AI Help — Twenty questions to ask a new web design client, then prompts that turn the answers into a brief, sitemap and content plan.
- Website Development by AI: What Agencies Can Ship and What Needs Review — A review checklist for AI-built client sites: what an agency can ship quickly and where a human check is mandatory.
- AI Tools and AI Development: The Complete 2026 Guide — the AI hub, including every tutorial in the AI-for-business series.
Sources: Figma, Framer, Webflow and Canva pricing pages; Lovable's credits and subscription-plans documentation; Wix's AI website builder page and help articles on hosting and site transfer. All read on 4 November 2026.