Summarize with AI
AI generated images on your website cost more than they save. Visitors spot them fast, and they read them as a company that never decided what it looks like. Swap the generated hero, the feature art and the team headshots for cropped screenshots of your product and plain photos of your people, because a real screenshot does more for how serious you look than the best generated illustration.
This matters most when a stranger arrives cold. He decides what kind of company you are in about four seconds, from the surface, before he reads a line. You know what your product does and how long it took to build. A generated image shows him none of that, since it could sit on any homepage in your category, and he has probably seen it on one already.
A glowing brain above a produce invoice
Picture an AI tool for restaurant groups. This is an example, not a client. It reads every supplier invoice as it arrives, matches each line to the price the group agreed with that supplier, and flags any line that crept up. A purchasing director who runs buying for fourteen locations used to find a jump in the price of romaine at month end, weeks too late. Now he sees it the morning the invoice lands.
Now open the site. The hero is a generated image of a glowing blue brain floating above rows of server racks, with light trails running into it. The headline reads Intelligent procurement for modern restaurants. Below it sit three feature cards, each with its own generated picture. Upload shows a chef holding a tablet in both hands. Match shows a paper invoice under a magnifying glass, and the letters on the invoice almost form words. Save shows a heap of vegetables with a gold coin on top.
The team page has five headshots in a row. Each face is lit softly from the left, each has the same blurred office plants behind it, and each wears the same half smile. Not one image on the site shows an invoice, a flag or a price. Look again at the chef on the Upload card. His left hand has six fingers.
The six-fingered chef in the ops group chat
Here is how that plays out, told as an illustration. A purchasing director at a twelve location group gets a cold email and clicks through. He scrolls past the brain, stops on the Upload card, takes a screenshot of the hand and drops it into the group chat he shares with his kitchen managers. Two of them reply with laughing faces. Nobody books the demo, and the founder never learns why, because analytics only records one more short visit.
The founder sees the effects in other places. On a call, a prospect asks how big the team is before he asks a single question about the product. Another asks, half joking, whether the people on the team page exist. The founder swaps the headshots for phone photos that same week and leaves the brain where it was. He now sends the deck instead of the link, because the deck has a screenshot of a flagged invoice in it and the website does not.
A perfect generated image would still fail
Most advice on this topic is about quality. Check the hands, clean up the text, keep one consistent style, maybe add a disclosure. That advice assumes the trouble is the mistakes. It is not. Fix every finger and the brain over the server room still fails, because it is the answer to a prompt, and a prompt is not a decision about your company.
Here is the claim, plainly. A generated image tells a visitor that nobody chose what this company looks like. Someone typed a description of what an AI company ought to look like, and the model returned the middle of every AI company it had seen. That is why these images feel familiar before they feel wrong. The visitor has met that brain in other decks and on other blog covers, so he puts you in the same pile.
A plain screenshot works the other way round. Crop the invoice table down to one row: Romaine hearts, case of 24, contract price 38.50, this invoice 46.20, with a red tag that says Above contract. It is less pretty than the brain. It could also only belong to this company. It proves the product exists, that it handles the buyer's real paperwork, and that the team knows what a case of romaine should cost. That is where stature comes from on a website: from detail only you could show.
We saw the same rule on the site we built for Mi-VAD, a company making a heart pump the size of a coin. Its whole case is that the device is small, so the page shows the pump beside a US quarter dollar, about the same size, along with renders of its actual parts: the metal body, the sleeve and the anchoring frame. No glowing picture of a heart could carry that argument, because the argument is the object itself.
What the buyer concludes, and what it costs you
A restaurant group that adopts this tool hands over its supplier contracts and every invoice it receives. The purchasing director is deciding whether you are a real vendor or a risk he has to manage. Generated faces on the team page push him toward the second answer, and they do it before the demo starts.
The cost is priced rather than counted. It shows up in who takes your first call, in how hard procurement pushes back, and in the size of the first contract. It also shows up in a raise. Investors are paying up for AI right now, with seed rounds priced roughly 42 percent above non-AI peers, so every partner's inbox is full of AI links. When yours opens on the third glowing brain he has seen that week, he files it with the other two. The founder reached for generated images to look bigger and more finished. To the people he most needs, they make the company look like a weekend project.
Stock, generated or the product: what each one says
Every image slot on your site has three options, and each sends a different message before anyone reads a word.
- A stock photo says we needed a picture here. The people in it are at least real, but a buyer knows the handshake and the laptop on the café table, and he learns nothing about you from them.
- A generated image says we described what a company like ours should look like. It carries the same emptiness as stock, plus the tells a visitor hunts for: extra fingers, signs and labels that almost spell something, the same light on every face, skin with no pores, objects that melt into each other at the edges.
- Your product says this is what we built. It is the only one of the three a competitor cannot copy, and it is the one most AI startups leave off the first screen.
So the order for any image that claims to show something real is simple. Your product first, real photos of your people second, stock third, and generated images never. If the site already reads as assembled from defaults in other ways, why your AI startup looks like every other AI startup covers the gradients and copy that travel with these images.
When a generated image is fine
Generated images are not banned everywhere. They are fine wherever the picture is decoration and does not pretend to be evidence. A soft texture behind a pricing table, a pattern on a blog cover, a placeholder in a mockup that never ships. If your product is itself an image generator, its outputs are the product, so show them with the prompt printed underneath.
The rule that sorts every case is one question: does this image claim that something is real? A person, a place, a document, a customer, a result. If it does, it has to be real. That rules out generated images on the team page, beside testimonials, in case studies and in the hero, which is the one image every visitor sees. Everywhere else, use them sparingly and keep them away from the first screen.
Replace each image slot, one afternoon at a time
You can do all of this without hiring anyone. Work through the site slot by slot.
- Hero. Replace the brain with one cropped panel of the product at the moment it does its job. For the invoice tool, that is the flagged romaine line. Use a demo account with realistic data, never a customer's numbers without permission. Product screenshots on SaaS websites covers cropping and labels.
- Feature cards. One crop per card, taken from the same product, in the same frame and at the same scale. If a feature has no screen, draw a plain diagram of your real data flow and label it with the real names, such as the supplier portal and the point of sale system.
- Team page. Take phone photos against the same wall, by a window, on one afternoon. Plain and consistent beats polished and fake. Anyone who does not want a photo gets a name and a role.
- The buyer's world. If a page needs a photo of the customer's day, take it yourself or borrow one from a design partner, with permission. For the restaurant tool, a clipboard of invoices in a real walk-in cooler beats any generated kitchen.
- Blog covers and link previews. Set the title in your own type on a flat color from your palette, and use one template for every post.
- The test. Put your homepage next to two competitors, cover the logos and ask someone outside the company which images belong to which company. If he cannot tell, the slot is not done.
Who decides what the company looks like
Every generated image on a homepage is a decision someone handed to a model. Take those decisions back, one slot at a time, and the site starts to show the thing a stranger cannot see from outside: what the product actually does, and who built it.
If the brain over the server room sounds familiar, Studio Maydit designs websites for AI founders that look like the company they have actually built. We build in Framer, Webflow and custom code, usually as a fixed scope of three to four weeks, and our website design service explains what that covers. If your homepage still opens on an image nobody chose, book a call with Studio Maydit.
