Choose a site you can finish
A local service business needing five informational pages is a more manageable first client than a marketplace, medical portal, or custom subscription platform. List the essential customer actions before choosing software: call, request a quote, view services, find the location, or make an appointment.
Wix describes an AI-assisted site-generation workflow and business features such as commerce and booking. That establishes available building blocks, not a guarantee that every generated site meets a client's operational or accessibility requirements. Other builders may fit better when the client already has a platform and staff know how to maintain it.
Ask these questions before proposing a build:
- Who controls the current domain, hosting, and business email?
- Which existing URLs attract customers or need to remain reachable?
- Who will supply and approve text, photos, and policies?
- Where should inquiries go, and who responds?
- Which tools or payments must the site connect to?
- Who will update it after launch?
Account ownership should be clear from the beginning. Do not put a client's only domain or payment account under an address they cannot access.
Write a scope based on pages and behavior
Define the pages, forms, integrations, migration work, revision rounds, and content responsibilities. A “five-page website” can conceal a large job if it also includes writing, photography, appointment setup, and moving years of old content.
Use a simple acceptance table:
| Area | What you deliver | How you verify it |
|---|---|---|
| Services | Approved descriptions and service area | Owner checks factual details |
| Contact | Working inquiry route | Send and receive a test inquiry |
| Mobile layout | Usable navigation and forms | Check narrow screens and zoom |
| Existing pages | Agreed redirects or preserved URLs | Open each mapped address |
| Ownership | Client access and renewal information | Client signs in successfully |
| Handoff | Editing guide and support boundaries | Client completes a basic update |
Do not promise search rankings. You can promise concrete work such as descriptive titles, useful headings, sensible internal links, and readable page content.
Use AI where errors are easy to inspect
AI can help draft a page outline, generate alternative copy from verified facts, or suggest CSS. Review everything it invents. Never publish fictional staff members, testimonials, customer numbers, credentials, or project photos represented as real work.
Build one representative page first. Agree on typography, spacing, buttons, and content hierarchy before duplicating the pattern across the site. This avoids finishing ten pages only to discover the client dislikes the basic direction.
For forms, test required fields, successful submission, error messages, spam controls, and the actual destination inbox. Verify that the person responsible for leads knows a form exists. A beautiful form that sends inquiries to an unattended account is a failed deliverable.
For accessibility, start with semantic headings, descriptive link text, visible keyboard focus, labeled fields, readable contrast, and meaningful image alternatives. Do not claim formal compliance based only on an automated checker. More complex requirements may need a specialist audit.
Price setup and ongoing work separately
Suppose a hypothetical project is $1,200. You spend 18 hours on discovery, content, design, build, testing, and handoff, plus $60 in direct costs. Your pre-tax contribution is $1,140, or about $63.33 per hour. If revisions expand the project to 30 hours, it drops to $38.
Record the recurring costs separately: domain, hosting or builder plan, email, paid apps, maintenance, and transaction charges where relevant. State who pays each supplier and what happens if the client cancels your maintenance service.
A maintenance plan might include a monthly backup check, software updates where applicable, limited content changes, and a defined response window. It should not promise unlimited redesigns or round-the-clock support unless you can provide them.
For a first client, offer a fixed small scope with staged approvals. Our first-client guide explains how to make the proposal specific.
Plan launch and handoff before launch day
Use a checklist covering page approval, domain configuration, working HTTPS, forms, links, image loading, contact details, analytics consent where relevant, and old-to-new URL mapping. Keep a recovery plan for the previous site until the new one is verified.
Deliver an inventory of accounts, subscriptions, renewal dates, files, and licenses. Use secure account-sharing methods; do not put passwords into a public handoff document. Explain how to edit text without breaking the layout.
Obtain permission for portfolio use. A client may approve the site for publication but not approve sharing private project data or internal screenshots.
Use one complete customer journey as the pilot
For a fictional mobile dog groomer, the first page should help a visitor understand the service area, see the service options and request an appointment. The supplied facts might include three towns, Tuesday-to-Saturday hours and appointments confirmed after review.
The generated site must not turn a request form into a confirmed booking. A useful confirmation says the inquiry was received and explains the approved next step. Test it by submitting a fictional request, confirming receipt in the business inbox and checking that the message contains the information staff need.
An outreach example could say: “I build small service-business sites around the actions customers need to take. A first project could cover your services, service area and a tested inquiry path, with the domain and accounts under your control.”
Before acceptance, have the owner edit the hours, open the site on a phone and process a test inquiry. Deliver the page inventory, account ownership record, approved content and a short editing guide.
Use AI content services when the real gap is source-based copy, and service pricing to separate content creation from design and technical setup.
FAQs
Do I need to know how to code?
A builder can reduce coding needs, but you still need to understand and test the site's behavior. Decline integrations you cannot support reliably.
Can I use the same design for several clients?
You can reuse your own patterns within applicable licensing terms. Adapt the content and structure to each business and do not copy another client's proprietary assets.
Who should own the domain?
The agreement should make the client's control clear. Keep renewal notices and recovery access available to the actual owner.
Can this become recurring income?
Maintenance can recur when there is real ongoing work. Price it around defined responsibilities, not an unexplained monthly charge. See AI automation services for related process work.
What if the client has no content ready?
Make content creation a separate, explicit part of the scope. Use verified business facts and staged approval; do not fill the site with invented claims to meet a launch date.
Sources and research notes
Source pages checked October 30, 2026. Worked examples are hypothetical; they are not observed earnings or guarantees.