AI saves an agency the most time in the middle of a project: turning an approved brief into a first draft, producing two or three design directions for the client to react to, and building every page at desktop, tablet and phone widths. It does not replace discovery, positioning, final copy or quality checks. Agencies that hand those to a machine ship faster and worse. Agencies that keep them human ship faster and better.
Where AI actually saves time
On a five-to-ten page marketing site, many hours go to layout labor rather than creative decisions: a third version of the services grid, a pricing table restacked for phones, type sizes adjusted at tablet width. That is the work an AI builder absorbs well.
First drafts from an approved direction
Once you and the client agree on a sitemap and a look, a builder can produce the full first draft in one sitting. With FNJ's AI website builder for agencies, you describe the business and attach up to three references: screenshots, the link of a public site the client likes, or the client's own brand folder. The builder plans a design system first (pages, palette, typefaces, reusable styles), then builds each page section by section on a live canvas while you watch.
Direction variants for the first client meeting
Clients react better to options than to a single proposal. Build two or three directions from different reference sets: one quiet and editorial, one bold and high-contrast, one close to what the client has today. On FNJ, a new site's first prompt costs 2 credits because it also builds the Home page, so three homepage directions cost about 6 credits. Exploration that used to be too slow to bill for becomes routine.
Responsive layouts
Every FNJ page is designed at three widths at once: 1440px desktop, 810px tablet and 390px phone, each with its own type sizes and layout, built with real flex and grid layouts rather than absolutely positioned boxes. That removes one of the least billable parts of a build: reworking every section for smaller screens.
Small revision rounds
"Swap the testimonials and the stats section." "Make the hero darker." "Add an FAQ to the pricing page." Plain-language edits like these take one prompt each, and you can also select any element on the canvas and change its text, spacing, colors, layout or image directly. Each prompt can be undone from the chat while the editor is open, so trying a change during a client call costs very little.
Where people have to stay in charge
Strategy and structure
An AI builds what you ask for. It will not tell you that the client's real buyers are facility managers rather than homeowners, or that "Services" should be split into three pages because each service is searched for separately. Discovery, the sitemap, and the one action each page should drive are agency decisions. Write them down before anyone opens a builder.
Copy
The builder writes copy for the client's business, but it can only work with what you give it. Ask for "a plumbing company" and you get generic plumbing-company copy. Ask for "24-hour emergency plumbing in Leeds, Gas Safe registered engineers, fixed call-out price shown before we arrive" and you get lines a customer can act on. A person still edits every line after that: claims, prices, guarantees, and the phrases the client's customers actually use.
Google's guidance on generative AI content holds AI-written pages to the same standards as any other page, warns that generating many pages without adding value can break its spam policies, and tells site owners to fact-check AI output, including titles and image alt text. For editing patterns that remove the machine tone, see how to write website copy with AI that doesn't sound like AI.
Photography
FNJ has no stock-photo library. It leaves styled spaces for photos, and you upload the client's own images anywhere on the page. Budget for a shoot, or at least a session to choose the best existing photos. A polished layout filled with blurry phone pictures still looks cheap.
Quality assurance
Someone accountable checks the site before it goes live. A QA list for AI-built client sites:
- Every page at desktop, tablet and phone width with the client's real content, including the longest service name and the longest headline.
- Every claim, price, phone number and address checked against what the client signed off.
- Every button points to a real destination: the booking tool, the quote form, a
tel:link. - Each page has its own search title and description, and the site address is set so sitemap.xml and robots.txt are generated.
- An Open Graph image and canonical link are set for pages that will be shared.
- Text contrast, heading order, keyboard focus and image alt text are checked.
- After deploy, a speed test on a phone and a click through every link.
A 10-step workflow for an AI-assisted client site
- Discovery. Goals, audience, competitors, and the primary action per page. The output is a sitemap and a one-page brief.
- Collect references. Ask the client for two or three sites they like, and what they like about each. If they have a brand, ask for the files: design tokens, stylesheets, a Tailwind config, a brand guide, logo files.
- Order the references on purpose. When references disagree, the builder follows the first one. Put the brand folder first and the layout inspiration second. With a brand folder, the builder follows the brand exactly and places the real logo when the folder includes logo files.
- Write the build prompt. Business, audience, location, pages, tone and primary action. An example follows this list.
- Generate directions internally. Two or three Home pages from different reference sets. Pick the strongest, or show all of them.
- Client review. Screen-share the canvas, or push the draft to a branch of a GitHub repository connected to a host that builds preview URLs for branches, and send the client that link.
- Revisions. Plain-language prompts and canvas edits. Developers on your team can also connect ChatGPT, Cursor or Codex to FNJ's MCP server, which lets those assistants edit FNJ sites on the AI subscription you already pay for, without using credits.
- Copy and photo pass. Replace every line the client has not approved and upload final photos.
- SEO and QA. Titles, descriptions, social image, site address, then the QA list above.
- Export and launch. Export, deploy on the client's hosting account, and hand over accounts and documentation.
A build prompt for step 4 might read:
A website for a family-run heating and cooling company serving Columbus, Ohio. Audience: homeowners whose furnace or AC has just failed, usually searching on a phone. Pages: Home, Services, Service Areas, About, Contact. Tone: calm, plain English, no jargon. Primary action: call now. Secondary action: request a quote, linking to their existing quote form. Follow the brand folder for colors, type and logo, and the screenshot for layout and spacing.
It works because every sentence narrows a decision the AI would otherwise guess at: who is reading, in what state of mind, on what device, and what they should do next.
Pricing AI-assisted work
If the build stage shrinks from days to hours, hourly billing punishes you for getting faster. Price the scope and the outcome instead.
- A fixed project fee by scope. Number of pages, number of design directions, revision rounds, and who writes the copy.
- Separate line items for the human work. Discovery, copywriting, photo direction, QA and launch are where your judgment lives, so make them visible.
- A care plan after launch. Monthly edits, seasonal updates, new pages, link and speed checks.
- Tool cost as overhead. FNJ charges in credits: one prompt is 1 credit and each page it builds is 1 more. A complete 5-page site refined over 10 prompts is about 15 credits, and the Agency plan includes 250 credits a month, roughly 16 sites. Current prices are in the builder pricing section.
Be open with clients about using AI. You are not selling hours of mouse work. You are selling decisions, accountability and a site that does its job.
Own the code, then hand it over
The worst client relationship is one the client cannot leave. With FNJ you can download a Next.js App Router project or static HTML, or push to a branch of a GitHub repository, where the default branch stays untouched until you merge. There is no FNJ runtime, script or badge in the code, and the site keeps working if you or the client stop using FNJ. Read what the code export contains, and for the accounts side, follow this guide on how to hand off a website to a client.
One hosting detail that catches agencies out: Vercel's free Hobby plan is for personal, non-commercial use, so a client's business site there needs Pro ($20 per seat). Cloudflare Pages' free plan has no published bandwidth cap for static assets and includes custom domains.
When this workflow is the wrong fit
FNJ builds marketing websites, not web apps. It does not build forms, store checkouts, log-ins, databases or a blog engine. If a project's core is a members' area or an online shop, an AI marketing-site builder covers the front pages at most, and the rest needs separate scoping or a different stack. For lighter needs, link a form, booking or store tool from a button and keep the site itself simple.
Using FNJ for client work
FNJ fits the middle of the agency process: drafts, directions, responsive layouts and revisions, with exportable code the client can own. Your team still owns the brief, the words and the sign-off. If that split matches how you work, see how FNJ's AI website builder works for agencies, including the Agency plan and MCP access.
Frequently asked questions
Should an agency tell clients it uses AI to build websites?
Yes. Clients are paying for strategy, copy, quality checks and accountability, and AI does not change that. Being upfront also makes it easier to explain why you price by scope rather than by hours.
How much faster is a client site built with AI?
The build stage gets much shorter because first drafts, variants and responsive layouts come from prompts. The overall calendar shrinks less, since discovery, content collection and client approvals still move at the client's pace.
Does an FNJ-built client site carry FNJ branding?
No. The exported Next.js or HTML code contains no FNJ runtime, script or badge, and the site keeps working on the client's hosting if you stop using FNJ.
Can the client's developer work on the site after export?
Yes. The Next.js export uses the App Router with one route per page and plain CSS per breakpoint, with no Tailwind or component library, and the HTML export is one file per page plus one stylesheet. Any web developer can read and edit either.