AI wireframes: map out your website before you commission it
What a wireframe is and why to make one before you pay for design
If you’ve ever commissioned a website, you know the scene. The agency presents its first design mockup, with colors, photos and fonts, and in the meeting everyone weighs in on the shade of blue on the button, while nobody notices that the pricing page is missing or that the quote request form is buried at the bottom of the homepage. By the time someone spots it, the design is done, and moving things around takes hours that someone is going to bill for.
A wireframe is a black-and-white outline of each page: gray boxes where the images will go, lines where the text will go, rectangles where the buttons will go. It shows which pages the site has, which sections each one contains and in what order, and it leaves out everything visual. Think of it as the floor plan of a house before you pick the tiles. A mockup, on the other hand, already has colors and photos, and a prototype can be clicked through as if it were the finished site. The wireframe comes before both.
There’s a practical reason to have one before you pay for design: it’s the stage where changing something costs almost nothing. Moving a section in a gray outline means dragging a rectangle; moving that same section in a finished design, or worse, on a site that’s already been built, means redoing work. It also gets the people inside your company, the manager, the salesperson and whoever runs the store, to agree with each other before a vendor comes on board, not halfway through the project.
Until recently, making a wireframe meant knowing how to use a design tool, or paying someone who did. AI has changed that, and someone who knows their business inside out and has never opened Figma can have a first outline of their website in an afternoon.
How AI wireframes work: text, screenshot or sketch
The tool doesn’t guess anything. It works with what you tell it, and there are three ways to tell it.
The most common is to describe the site in words. You write what your company does, who it sells to and which pages you want, and the AI comes back with a set of screens with their sections in order. The more specific the text, the better the result. “Website for a dental clinic” gives you a generic outline that could belong to anyone, whereas “website for a neighborhood dental clinic that wants people to book appointments on WhatsApp and see the price of a cleaning before they call” forces the tool to put the WhatsApp button at the top and a price table on the homepage.
The second route is to start from a site that already exists. Some tools take a screenshot and turn it into an editable outline, which is useful for rebuilding your own site while keeping what works, or for using the structure of a site you like in your industry as a reference. Be careful with the second option: copying a competitor’s structure is fine as a starting point and a bad idea as the end result.
The third is a hand sketch. You draw the homepage boxes on paper, take a photo, and the tool cleans it up. It’s the most natural route for people who think with a pen in hand. In all three cases what you get is a draft, and you work on it by correcting it with more instructions, the same way you’d edit a piece of writing.

Which AI tool to use for wireframes
The question that comes up most is which AI wireframe generator is best, and the answer depends less on the tool than on what you’re going to do with the wireframe afterward. There are two families: dedicated tools, built just for this, and general-purpose assistants like ChatGPT or Claude, which weren’t made for wireframing but still handle it pretty well.
Three questions help you choose between them. Who’s going to work on the wireframe afterward, you or a designer? Do you want it to think through the structure or to show to vendors? Are you already paying for one of these services? Adding another subscription for a job you’ll do once may not be worth it, which is why, for a small business that already uses ChatGPT or Claude, we usually recommend starting there. Free plan terms change often, so check them on each tool’s website on the day you plan to use it.
Dedicated generators: Uizard, Visily, Relume and Banani
Uizard, Visily and Banani work in a similar way. They generate screens from a text description and then let you edit them by dragging sections around with the mouse. Relume starts from a sitemap: first it proposes the list of pages and their hierarchy, and from there it builds a wireframe for each one. For a business website that order makes sense, because it forces you to decide which pages exist before arguing about what goes on each one.
The advantage of this family is that the result looks like a real wireframe, one any designer will recognize, and several of these tools export to Figma, where a lot of designers work. The downside is that they tend to suggest startup-style websites, with a huge hero section, three columns of benefits and a testimonial carousel, because that’s what they’ve seen most. For a repair shop or an accounting firm, you’ll need to correct that.
They’re the right choice if you’re going to show the wireframe to several vendors and want it to make sense without any explanation.
ChatGPT or Claude: from page map to HTML wireframe
With a general-purpose assistant, the work happens in two stages. First comes the conversation about structure. You explain your business, ask for the page map and the sections on each page, and discuss it back and forth. This is where these models really shine, because they ask questions, suggest alternatives and take corrections, much like a patient consultant would.
Then you ask it to turn that structure into an HTML wireframe, in grayscale and without styling. You get back a file that opens in any browser and looks a lot like an outline made with a dedicated tool. Nothing gets dragged here: every change is requested in writing and the assistant regenerates the file.
It’s a good fit if you already use one of these assistants at work, or if you care more about structure and content than about how the wireframe looks. The result does, however, look less polished in front of a vendor than a wireframe from Relume or Visily.
How to create wireframes with AI, step by step
Most wireframes that turn out badly go wrong before the tool is even opened, because someone asked the AI for a website without deciding what it’s for. That’s why the order of the steps matters more than the tool you pick.
- Write one paragraph on what the website needs to achieve. Phone calls, quote requests, purchases, newsletter sign-ups. One or two actions, ranked by importance. Everything else in the wireframe is decided based on this paragraph.
- Make the list of pages. Ask the AI for it based on the previous paragraph, then trim it. The temptation is to accept everything it suggests, and a small services website rarely needs a blog, resources, case studies and a team page from day one.
- Define the sections on each page. On the homepage, for example: what people see when they land, where the services are, where the proof that you do good work goes (reviews, photos of past jobs) and where the form goes. Write it in the order you want the customer to read it.
- Generate the wireframe. Paste that structure into the tool you’ve chosen along with the context of your business. If you’re using ChatGPT or Claude, explicitly ask for grayscale HTML with no colors or images.
- Correct it with instructions. “Move the form up,” “remove the team section,” “put the prices before the reviews.” Several small corrections work better than rewriting the whole request.
- Show it to whoever deals with customers. Your salesperson, or whoever answers the phone, knows what people ask before they buy, and those questions often call for a section nobody had planned.
Use step 3 to note down what happens to each form when someone fills it out: who receives it, whether it goes to a spreadsheet or the CRM, whether it triggers an automatic reply email. The wireframe doesn’t show this, but it’s the cheap moment to decide it, and it’s exactly the part that later gets automated with tools like n8n or Zapier.
The page list is usually what takes the most time, and it’s the last thing you should leave up to the tool. When we look at a wireframe made with AI, the first thing we check is the pages the generator suggested and nobody dared to remove.
The wireframe as a brief for an agency or freelancer
Ask several vendors to quote “a corporate website” and you’ll get numbers that are impossible to compare. One pictured a short template-based site, another a custom build with an online store, and the third added a blog nobody asked for. Each one quoted the website they imagined, and the wireframe makes sure they all imagine the same one.
Comparable quotes for the same pages and sections
Send the same wireframe to everyone, with the page list and a short note on every section that does something, for example that the form sends to a given email address or that the product listing updates from the catalog. That way everyone quotes on the same thing and the price difference reflects how each one works.
Ask for the quote to be broken down by page or by section. If anyone adds pages or features that weren’t in the wireframe, have them list those separately, and you decide whether you want them. The breakdown also shows you who actually read the brief, because the vendor who asks about a specific section of the wireframe is the one who looked at it.
If you made it with a dedicated generator, just share the link or export it to PDF. If it came from ChatGPT or Claude, you can send the HTML file as is, or screenshots of each page if you’re worried someone won’t know how to open it.

What to leave open for the designer
The opposite risk exists too. A wireframe that’s too locked down turns the designer into someone who just cleans up your decisions, and you’re paying them because they can do more than that.
Pin down which pages there are, which sections each one has and what action you want on each page. Leave open the fine ordering within each section, the size of elements, the number of columns and anything to do with appearance, which the AI tends to fill in out of habit. If the generator added three columns of benefits, tell the vendor “the benefits go here,” not “three columns.” One sentence in your email makes it clear: the structure is what we want, and the layout is a suggestion.
When you don’t need a wireframe
A website with a home page, services, about us and contact, built on a template, already comes with its structure decided. What you need there is to write the copy and choose good photos, and a wireframe would only duplicate what the template already shows.
Something similar happens with an online store on a standard Shopify or WooCommerce theme. Product page, category, cart and checkout work in much the same way on almost all of them, and shoppers expect to find them that way. Drawing those screens with AI is reinventing something that already works. At most, it’s worth wireframing the homepage and any custom page, like a seasonal landing page or a wholesale order page.
A wireframe starts to pay off when the site needs to do something the template doesn’t include, when several people in the company are going to weigh in on it, or when you’re going to get quotes from more than one vendor. If none of those three apply, our advice is to skip the wireframe and spend that time on the copy, which is where you win or lose the customer.
If your wireframe ended up with a form and you’re not sure what should happen when someone fills it out, AI can help with that too. Tell us about it and we’ll look at it with you.