Show your product on your homepage

Kite chooses the one view of your product that proves your main claim, because a homepage visual works best when it makes a single point. If your homepage says your tool finds the deals most likely to close, the visual should be a pipeline table with those deals ranked at the top. If it says you save finance teams hours on month-end reporting, the visual should be the finished report.

To make that choice, Kite draws on the research it did when you started working together. It knows your positioning, the customers you serve, the outcome they care about, and the headline your homepage leads with. It also reads your public website, help docs, and product pages, and it can look at screenshots or screen recordings you upload to show what the real product looks like.

The answer usually falls into one of four kinds of view:

• A dashboard with three or four key numbers and a chart, for products whose value is insight, such as analytics or monitoring tools.
• A table or list of the records your product works with, such as leads, candidates, invoices, or support tickets, for products that organize work.
• A chart on its own, when one trend tells the whole story, such as costs falling after a customer switched to your tool.
• A workflow, shown as connected steps from a trigger to a result, for automation and integration products.

Kite explains its choice before it builds anything, so you can steer it toward a different view if you'd rather show something else.

Kite writes believable sample content for every slot in the mock-up, because empty or obviously fake data is what makes a product visual look like a template. A recruiting tool's candidate table gets real-looking names, roles such as "Senior Product Manager," and statuses such as "Phone screen scheduled." An analytics dashboard gets labeled metrics with units and time ranges, such as "1,247 signups, last 30 days," along with a change from the previous period.

Kite also adds the small details that make software feel like software. Tables carry enough rows to look like a working account, with column headers, a sort arrow, and a count such as "Showing 12 of 47." Each view includes a search box, a filter, or a date range picker. Text inside the product lines up on the left the way it does in real applications, and numbers line up on the right so the digits are easy to compare.

The content stays true to what your product actually does. Kite builds the visual around features and outcomes your product delivers today, and the sample data reflects the kinds of customers you serve, so a visitor who signs up finds what the homepage promised.

Kite builds the mock-up as part of the page itself, using HTML and CSS, rather than generating an image of a dashboard. That choice is what keeps the visual crisp, light to load, and easy to change. Kite uses image generation for photographs and illustrations, but it builds software screens in code because generated images of interfaces tend to come out blurry and garbled.

The visual takes its colors from your brand, so it blends into the rest of the page. Inside the product frame, Kite uses the clean, compact type and tight corners of a real application, which keeps the mock-up looking like your product rather than like another marketing banner. It sets the visual on a background that fits the section, whether that's a plain page, a soft tint, or a full gradient behind the hero.

If you want the preview to be interactive, Kite can add simple interactions. Visitors might click tabs to switch between a dashboard and a report, or hover over a chart to see the exact numbers. Each interactive piece is built separately from the rest of the page, so the homepage still loads quickly.

If your team keeps product designs in Figma, Kite can work from those instead of starting fresh. It reads the frames, components, colors, and text styles in the file and builds the coded version from your designer's layout.

Kite checks the finished visual on desktop, tablet, and phone widths before it shows it to you, because a homepage visual that breaks on a phone hurts more than it helps. The mock-up is designed at full desktop size and then scales down as a single unit, so a visitor on a phone sees the same composition, only smaller, instead of a jumbled stack of cards.

Kite also reviews the visual for the problems that give generated designs away. It looks for gray placeholder bars where text should be, cards floating in empty space, and labels that run off the edge. It fixes what it finds before the preview reaches you.

Kite's finished change waits on your site as an unpublished change, and you can open a preview of the homepage before anything goes live. When you're happy with it, approve it with the Publish button in the conversation or by replying, and Kite publishes it and checks that the site displays correctly.

If you change your mind later, you can undo that single change without losing anything you've published since. You can also ask Kite to adjust the visual after it's live, such as showing a different metric, swapping the sample company names, or adding a second view further down the page.

Once the new homepage is live, Kite measures how visitors respond with the built-in analytics on sites it hosts. It compares the period after the change with the period before, looking at how long visitors stay, how many click your main call to action, and how many sign up or book a demo.

For a clearer answer, Kite can run an A/B test on a site it hosts, showing the homepage with the product visual to half your visitors and the previous version to the rest. It asks for your approval before the test starts, watches the results, and asks again before making the winner permanent. For more on testing and improving your pages, see Improve website conversion.

The mock-up also keeps up with your product. When you ship a new feature or rename part of the interface, tell Kite, and it updates the labels, numbers, or layout in the code. That takes minutes, compared with retaking, cropping, and blurring a new set of screenshots.