How Agencies Deliver Client Websites with AI — Without Losing the Client
How agencies deliver client websites with AI: a six-stage workflow from brief to handover, quality checks, handover vs managed models, contract terms, fee structures, and a copyable handover acceptance table.
AI does not remove the hard part of agency work. It removes the slow part. To deliver client websites with AI, keep people on the decisions (positioning, claims, approvals) and let AI draft the research, copy and pages. Run the project in six stages: brief, research, generation, review rounds, launch and handover. Then sign off a handover table that proves the client owns and can run what they paid for.
Updated November 6, 2026: rewrote the guide to be tool-neutral, with a six-stage delivery workflow, quality checks, handover and managed models, contract terms and fee structures, and removed claims we couldn't support.
This guide is for agencies and freelancers building small-business and B2B marketing sites with any AI tool. It covers who does what, a stage-by-stage workflow, the checks to run before a client sees anything, how to set up the client's accounts after launch, how to price the work, and a handover acceptance table you can copy. We make PolyDraft, and we explain where it fits near the end, after the tool-neutral advice.
Key points
- AI saves the most time on first drafts: research summaries, page copy, metadata and layout. Positioning, fact-checking and client decisions still take people.
- Give every stage a deliverable and a "done when" test, so review rounds end in decisions rather than open-ended opinions.
- Check AI output before the client sees it: facts, invented testimonials, images, accessibility and on-page basics.
- Decide early whether the client will own the accounts (handover) or you'll run them (managed), and write it into the contract.
- A site is delivered when the client can run it without you. Prove that with the handover acceptance table.
Where AI saves time on a client build, and where it doesn't
AI shortens production, not judgment. On a typical marketing-site project, copy waits on the client, design waits on the copy, and SEO gets bolted on at the end because it was quoted as a line item instead of being built into the structure. AI tools can produce a full first draft (pages, copy, titles and descriptions, a keyword plan) before the first review meeting, so the client reacts to a working site instead of imagining words in a wireframe. What AI can't do is decide what the business should promise, or confirm that a claim is true.
| Task | AI drafts | Agency decides or checks | Client provides or approves |
|---|---|---|---|
| Business facts and offer | Extracts facts from the current site and materials | Confirms what's current; removes anything unverified | Corrects facts; names off-limits claims |
| Market and keyword research | Competitor summaries, keyword and question lists | Picks the target query for each page | Confirms priority services and markets |
| Site structure | Proposed page list and navigation | Merges or cuts pages so each has one job | Approves the page list |
| Page copy | Full first drafts | Edits positioning, tone and anything generic | Approves the promise, services and calls to action |
| Titles, descriptions, structured data | Drafts for every page | Spot-checks for accuracy and duplicates | Nothing, unless a claim changes |
| Images | Illustrations or placeholders | Makes sure nothing poses as the client's real product, team or premises | Supplies real photos and logos |
| Launch and accounts | Deployment steps, if the tool supports them | Runs the launch and the handover checks | Owns the domain, hosting, analytics and billing |
A six-stage delivery workflow for AI-built client sites
Run every project through the same six stages, each with one deliverable and one test for "done". The test is what stops review rounds from drifting.
| Stage | Deliverable | Done when |
|---|---|---|
| 1. Brief | A written brief: what the business sells, who buys, real differentiators, off-limits claims, markets and languages | The client has approved the brief in writing |
| 2. Research | Competitor notes, target query per page, questions buyers ask | Every planned page has one target query and no two pages share it |
| 3. Generation | A complete draft site in a preview, not a wireframe | Your internal fact and quality checks pass (next section) |
| 4. Review rounds | A preview link plus a short list of decisions you need | Each round ends with recorded decisions; the contract's round limit is respected |
| 5. Launch | The site live on the client's domain | The client has approved the exact release, and launch checks pass |
| 6. Handover | Accounts, access, documentation and a maintenance owner | Every row of the handover acceptance table has evidence |
Brief. Collect the client's existing site URL and materials, so facts come from their own sources rather than your memory of the kickoff call. If the current site already gets search traffic, capture its URLs and rankings first; our checklist for protecting rankings during a rebuild covers the baseline, and the website migration checklist covers domain or platform moves.
Research and generation. Agree the page list and the keyword assignments before the copy is written, then let the tool draft the whole site. You are the editor, not the typist: review it yourself before the client sees it.
Review rounds. Ask for decisions, not opinions. Is this the promise you want to lead with? Are these the services, in this order? Is this the action you want visitors to take? Record each answer and who gave it. A fixed number of rounds in the contract keeps a fast draft from turning into endless revisions.
Launch and handover. Launch only the version the client approved, then walk through the handover acceptance table with them before you send the final invoice.
Quality and risk checks before the client sees the site
AI drafts read well and can still be wrong, so check every draft before it reaches the client. Five checks catch most problems:
- Facts. Check every number, certification, year and client name against the client's own material. Delete anything you can't trace.
- Testimonials and reviews. Never publish invented quotes, ratings or customer names. In the US, the FTC's rule on consumer reviews and testimonials, in effect since October 21, 2024, prohibits fake reviews and testimonials, such as ones attributed to people who don't exist, and the FTC says AI-generated fake reviews are covered.
- Images. AI images must not pose as the client's real products, staff, premises or results. Use the client's photos for anything a buyer would take as real.
- Accessibility basics. Alt text on meaningful images, readable contrast, real headings in order, labelled form fields, and a site you can navigate by keyboard.
- On-page basics. The SEO fundamentals Google documents: one H1 and a unique title and description per page, structured data that matches what the page shows, correct canonicals, a sitemap that lists only live pages, and a privacy page that matches the forms and analytics actually installed.
If you're rebuilding an existing site, also note any inherited platform risks for the handover, such as an unpatched PHP runtime on the old WordPress host; our guide on how to update PHP in WordPress covers that work.
Two ways to run a client site after launch
Decide before you quote whether the client will own the accounts and pay for them directly (handover), or you'll hold them and resell the service (managed). Both work; trouble starts when nobody decided. Many hosted builders keep the site on their own platform, so the account it lives in decides who controls it. Some let you move it: Webflow, for example, documents transferring a site with a paid Site plan to a client's Workspace from Freelancer and Agency Workspace plans. AI app builders such as Lovable sync the code to GitHub on every plan, which helps a client take the code elsewhere.
| Handover: client owns the accounts | Managed: agency holds the accounts | |
|---|---|---|
| Who holds domain, hosting and analytics | The client, with the agency invited as a member | The agency |
| Who pays hosting and tools | The client, directly | The agency, rebilled with a margin |
| What the agency sells after launch | A retainer for updates, content and search work | A bundled monthly fee |
| If the relationship ends | Remove the agency's access; the site keeps running | Transfer accounts or export the site, which can be slow or limited by the platform |
| Main risk for the agency | Easier for the client to leave | You carry the outage, billing and security risk, and the client may feel held hostage |
When the relationship continues under a handover model, you keep the retainer because the work is good, not because you hold the keys.
Risks and contract terms to agree up front
Put ownership, approvals, AI use and handover in the contract before any work starts. Our SEO contract checklist walks through the clauses from both sides; for an AI-built site, make sure the agreement also says:
- Who owns what: domain, hosting account, analytics and Search Console properties, the site's code or export, and the copy and images.
- How AI is used: which tools draft the work, who reviews it, and that no fabricated testimonials, statistics or client results will be published.
- Approval before release: the client approves each version in writing before it's released.
- Review rounds and change requests: how many rounds are included, and how out-of-scope changes are quoted.
- Third-party costs: which cloud, domain and tool charges the client pays directly.
- Handover and exit: what the client receives (the table below), how the agency's access is removed, and that nothing is switched off when the contract ends.
This is general information, not legal advice. Have a lawyer in your jurisdiction review the contract.
What to charge for now
If AI shortens production, bill for the work that still takes judgment: positioning, offer strategy, content direction, conversion review, and search and content work after launch. Three structures fit AI-assisted delivery:
| Structure | How it works | Good fit | Watch out for |
|---|---|---|---|
| Fixed project fee plus retainer | One fee covers brief to handover; a monthly retainer covers updates, content and reporting | Most small-business and B2B sites | Define what the retainer includes each month |
| Strategy fee and production fee, listed separately | Discovery, positioning and the content plan are quoted apart from page production | Clients who compare you with cheap AI tools | Clients may try to buy only the strategy |
| Per page or per language | A base fee plus a unit price for each extra page or language | Multilingual or fast-growing sites | Unit prices can hide the cost of review and fact-checking |
To model what a client will spend over three years, including hosting and tools, use our website cost calculator (our own tool; its PolyDraft row counts the plan price plus small domain and miscellaneous allowances, not maintenance hours) and the website cost breakdown and budget worksheet.
Agency handover acceptance table
A client site is delivered when the client can run it without you. Before you send the final invoice, walk through this table with the client, fill in the evidence column, and keep a copy with the project records. Copy it into your own handover document and adjust the owners to match your contract.
| Check | Pass standard | Who's responsible | Evidence |
|---|---|---|---|
| Domain registrar account | Registered in the client's name, with the client's email and payment method; auto-renew on | Client owns; agency verifies | Screenshot of the registrar account showing the registrant and renewal date |
| DNS | DNS is managed in an account the client controls; every record (including email) is documented | Agency documents; client owns | Exported DNS record list |
| Hosting or cloud account | The live site runs in the client's account, billed to the client; the agency is a member, not the owner | Client owns; agency sets up | Account members page showing the client as owner |
| Agency access | Agency accounts have only the roles they need, and are removed at the end of the contract | Client grants and removes | Member list with roles, dated |
| Deploy credentials and API keys | Stored in the client's password manager or account; none sent in plain email or committed to code | Agency hands over; client stores | List of credentials by name (no values) and where each is stored |
| CMS and admin access | The client has an owner-level login and has published a test change themselves | Client tests; agency trains | Date of the client's test edit |
| Code or site export | The client has the code or export the contract promises, and knows what it does and doesn't include | Agency delivers | Archive or repository link and a note on its contents |
| Content, database and media | Current posts, form entries and images are backed up separately from the code | Agency backs up; client keeps | Backup file or snapshot and the date it was made |
| Analytics and Search Console | Properties are owned by the client's account; the agency has user access only | Client owns | Property users list showing the client as owner |
| Forms and enquiries | Every form delivers to an inbox the client monitors; spam protection uses the client's keys | Agency tests | Test submission received by the client |
| Third-party services and costs | Every paid tool, plugin and API is listed with its owner and who pays | Agency lists; client accepts | Service and cost list signed off by the client |
| Approved release | The live version is the one the client approved in writing | Client approves | Approval email or ticket with date and version |
| Redirects and old URLs | Old URLs redirect to their closest new page, with no chains or 404s | Agency | Redirect map and test results |
| Maintenance owner | A named person owns content updates, security patches and renewals after launch | Client names; agency documents | Name and contact in the handover document |
| Inherited platform risks | Known risks on any old system still running (for example, an outdated PHP version) are written down with an owner | Agency reports; client decides | Risk note in the handover document |
For the first months after launch, hand the client a post-launch SEO checklist with named owners, and use a repeatable ticket for later changes, such as our content refresh and verification workflow.
Where PolyDraft fits
We make PolyDraft. It's an AI-native website marketing system: it builds a search-ready site on your client's own Cloudflare account, uses SEO automation to plan content from SEO and GEO data, and flags pages to refresh from Search Console data. For agencies, that means the handover model above is the default rather than something you work around. As of November 6, 2026:
- Deployment to the client's account. Every paid plan deploys to a Cloudflare account the client owns, under their domain, with no platform hosting fees. Cloud and domain charges still apply and are billed to the client's own accounts, and the custom domain and DNS are set up in Cloudflare. Cancelling a subscription doesn't take a deployed site down.
- Project transfer is listed on Pro ($99 a month) and above.
- The Agency plan ($299 a month or $2,990 a year) adds full source-code export of the generated website and white-label badge control, with 10 team seats and Owner, Editor and Viewer roles for scoping client access. Check PolyDraft's Agency plan pricing for current plan details; Enterprise export and branding scope are agreed with the team.
- Search infrastructure. Titles, descriptions, Schema.org data where the page supplies it, canonicals, a sitemap, robots.txt and llms.txt come with every plan, and each page gets a keyword plan from search-demand data before the copy is written.
- After launch. Every week, PolyDraft's SEO and GEO autopilot reads the site's Search Console data, finds new keyword opportunities, writes and refreshes articles and reports what moved. It needs a deployed site with the platform's Search Console access added to the client's property.
- Recovery. Workspace snapshots let you roll back an experiment before you deploy it.

A source export isn't the whole handover. PolyDraft's own integrations page says live database content and media aren't promised as part of the export, which is why the table above backs them up separately.

PolyDraft is the wrong choice if the client needs a store, pixel-level canvas design, or a direct import of an existing Webflow, Framer or WordPress site (it can read a public site's URL to inform a rebuild, but nothing else moves across), and it has no built-in redirect manager, so redirects are set up in Cloudflare. See what a PolyDraft site connects to and the agency plans and delivery workflow for details. After launch, the SEO and GEO autopilot runs the client site's content work every week.
We build a website product, and we also offer AI FDE (AI forward-deployed engineering), a done-for-you AI SEO and GEO service run on it: a PolyDraft engineer runs PolyDraft for you, building your new site from your current one. Contact us to ask about scope.
FAQ
Who should own the client's hosting account?
The client, in most cases. Put the domain, hosting, analytics and Search Console in accounts registered to the client and invite the agency as a member with limited roles. If you run a managed service instead, say so in the contract and agree how the accounts transfer if the client leaves.
Should an agency resell hosting?
Only if you're prepared to carry the outage, billing and security risk and you've written down how the client gets the site back. Otherwise, a retainer for updates and search work keeps the relationship simpler than a hosting margin.
What should a website handover include?
Ownership of the domain, DNS, hosting, analytics and Search Console; credentials stored in the client's systems; owner-level CMS access the client has tested; the code or export the contract promises; backups of content and media; a list of paid services; the approved release record; and a named maintenance owner. The handover acceptance table gives a pass standard and evidence for each.
How do you price AI-assisted websites?
Charge for outcomes and judgment rather than hours of page assembly: a fixed project fee plus a retainer, or a strategy fee quoted separately from production. Include review and fact-checking time, since AI drafts still need both.
Can a client leave and keep the site?
Yes, if the site runs in the client's own accounts and the handover table is complete. Remove the agency's access, hand over credentials and backups, and the site keeps running. If the site lives in your account on a hosted platform, check that platform's transfer or export rules before you promise this.
Continue with the next task
Make recurring work and handoff responsibilities explicit in the project estimate. Read the website cost breakdown and budget worksheet.
Choose the tool before you choose the workflow. Read how to evaluate an AI website builder.
Include equivalent pages and translated metadata when a client serves several markets. Read the multilingual delivery checklist.
If you sell AI-search work as a retainer, read what GEO services should include.
About this article. Drafted by an AI agent following PolyDraft's blog workflow, checked by an automated QA script, fact-checked by a separate AI agent, and approved by Vincent Chen. The workflow, checks and handover table are general practice, not results from measured client projects. Third-party details come from the vendors' and the FTC's own pages; where our tools couldn't open a page, we relied on search excerpts from that site and paraphrased them. PolyDraft details come from our own public pages as of November 6, 2026. Screenshots of PolyDraft's public pricing and integrations pages were captured on November 6, 2026, unedited apart from resizing; we didn't sign in or build test sites.
Sources
All sources checked November 6, 2026.
- Federal Trade Commission: Final rule banning fake reviews and testimonials, Consumer Reviews and Testimonials Rule: Questions and Answers
- Webflow Help Center: Can I transfer a site with a paid Site plan to my client?
- Lovable Docs: GitHub integration
- Cloudflare Docs: Manage account members
- Google Search Central: SEO Starter Guide, Introduction to structured data markup
- PolyDraft: Pricing, Integrations, For agencies
Revision history: November 6, 2026: corrected the publication date to August 12, 2026, when it first went live.


