Summary
A small business should build a rough version of its website with AI before it pays a developer anything. The rough version answers most of the questions a developer would otherwise ask in paid meetings, and it turns a vague request into a document that can be priced. It also shows the owner, before any money changes hands, which parts of the site they can maintain themselves and which parts need a professional.
Developer Rates and Paid Discovery
The Bureau of Labor Statistics put the median annual pay of web developers at $90,930 in May 2024, and freelancers and agencies bill above the equivalent hourly rate to cover their own overheads. The first phase of most projects is discovery, in which the developer asks what pages the business needs and what visitors should be able to do on each.
The output of discovery is a specification, a document listing each page with its content and functions. A prototype built by the owner covers most of the same ground, and reviewing one takes less of a developer’s time than writing a specification from interviews.
An owner who arrives without answers pays for the developer to help find them. An owner who arrives with a working draft pays for the build.
Scope and Structure Decisions
A prototype requires decisions that are easy to postpone in conversation. The owner has to choose the pages, write or approve the text on each, and decide which features the site needs, such as online booking, a shop, a members’ area or a simple contact form. Each feature changes the price of the build, and each one is easier to judge when it is on a screen.
Integrations belong on the same list. A booking system or an email platform each comes with its own account and settings, and the developer needs to know which ones the business already uses before quoting. The logo in its original file format and any licensed fonts should be collected in the same folder.
A menu with nine items looks crowded on a phone, and the prototype shows that before anyone is paid to build the navigation.
A Working Model of the Site
The quickest way to produce that brief is to build a website with AI and treat the result as a working model, one that shows the developer every page, every form and the order in which visitors move through them. Current tools can generate a multi-page draft with real copy from a few paragraphs of description, and the owner can revise it without any coding.
The model does not have to be finished. It needs the real text and prices, with labeled placeholders where photographs are still missing, since a developer quoting from placeholder copy is quoting on guesses. The draft should also be checked on a phone before anyone else sees it, because a crowded layout shows its problems there first.
Testing the Prototype With Customers
The prototype can be tested before any developer is involved. Jakob Nielsen’s research at the Nielsen Norman Group found that teams only need to test with 5 users to uncover about 85% of the usability problems in a design, and he recommends several small rounds over one large study. Five customers asked to book an appointment or find a price on the draft site will show where the structure fails. Each session needs a task and someone taking notes on where the customer hesitated, and a model can summarize the notes from all five sessions afterward.
Each problem found at this stage is a change to a draft. The same problem found after the developer’s build is a change request, billed at the developer’s rate.
Scope Creep Before the Quote
The Project Management Institute’s 2018 survey found that 52% of projects completed in the previous year had experienced scope creep, up from 43% five years earlier. A prototype reviewed and signed off by the owner fixes the scope in a form both sides can point to, and any later addition is a separate, priced item. Common mid-project additions include extra pages and a second language, and each is cheaper to price at the start.
Limits of Generated Code
When the site handles payments or customer accounts, the prototype should stay a brief, and the production version should come from a developer. In Veracode’s 2025 tests of more than 100 models on 80 coding tasks, the code was insecure in 45% of cases, and larger models did no better than smaller ones. The report found that security results had not improved even as the models’ coding accuracy had, so the review is needed with newer tools as well.
The most common failure in those tests was cross-site scripting, which lets an attacker run their own code in a visitor’s browser through a vulnerable page. The models failed to defend against it in 86% of relevant samples. Any feature that accepts input from visitors belongs with a developer who checks the code line by line. Static pages with no forms have less of this risk, since there is no input for an attacker to abuse.
The Handoff Package
The developer should receive a short package made up of a link to the prototype, a document with the final copy for every page, the feature list with priorities, and access details for any accounts the site depends on. The prototype shows intent. The copy document is the version the developer builds from, and it should use the same page names as the prototype’s menu so both files describe one structure.
Accounts need care in the handoff. The domain should be registered in the business owner’s name, and ICANN’s statement of registrants’ benefits and responsibilities makes the registrant solely responsible for the domain and for keeping its contact details current. A developer can be given access to the registrar and the site without being made the owner of the domain or the site itself. Passwords should be shared through a temporary access account or a password manager’s sharing feature, and changed when the project ends.
Contract Terms With the Developer
The contract should state who owns the finished code and design, what counts as acceptance, and how changes are priced. A fixed price works when the prototype has settled the scope. An hourly rate is appropriate for work where the scope is still open, and the prototype narrows that uncertainty even there. Payment is usually split into stages, with a deposit at the start and the balance on acceptance, which ties the final payment to the agreed criteria.
A Clickable Brief
An AI-built prototype is a brief that can be clicked. It records the owner’s decisions about pages and features in a form a developer can price and a customer can test, and its job ends on the day the developer’s version goes live.