--- title: Add customer proof to your homepage description: Gather the testimonials, customer logos, reviews, and results your company has already earned, pick the proof that matters most to your buyers, and rebuild your homepage hero and proof section around it. slug: /use-cases/homepage-social-proof page_type: use-case lead_prompt: How do I add social proof to my homepage with AI? target_prompts: - Can an AI marketing agent pull together our customer proof and rebuild our homepage around it? - How do I add social proof to my website? - What should go in the proof section of a homepage? - How do I find all the testimonials, logos, and results we already have? - How do I rewrite my hero section around customer results? entity: Kite category: AI marketing agent author: Devon Wells and Kite date_published: '2026-11-09' date_modified: '2026-11-09' related_integrations: - /integrations/fathom.md - /integrations/google-docs.md - /integrations/google-drive.md - /integrations/webflow.md --- # Add customer proof to your homepage ## Key Takeaways - Most companies already have more customer proof than their homepage shows. It sits in review sites, sales decks, call recordings, Slack threads, and thank-you emails, and nobody has gathered it in one place. - The strongest proof is specific. A result with a number, a quote that describes what happened, and logos from companies that look like your buyers all persuade more than a quote that says the product is great. - Kite builds a list of every piece of proof it can find, from your website, public reviews, your documents, and your call transcripts, and notes where each one came from. - Kite then picks the angle your proof supports best, rewrites your hero section around it, and builds a proof section with the right quotes, logos, results, and ratings in the right places. - Once you approve the changes, Kite publishes them to a site it hosts or through Webflow and other supported content systems, then measures whether more visitors click your main button or fill in your form. ## Why customer proof belongs on your homepage Social proof is evidence that other people already use your product and got something out of it. On a website, it usually takes the form of customer testimonials, logos of companies you work with, ratings from review sites, results with numbers attached, and links to case studies. A visitor who lands on your homepage is asking two questions: "Does this solve my problem?" and "Can I believe it?" Your copy answers the first. Proof answers the second. The odd thing is that most small teams have plenty of proof and show almost none of it. A customer told your sales rep on a call that they cut their reporting time in half. Three people praised the same feature in G2 reviews last quarter. Someone posted a screenshot of their results in your community Slack. A slide in your sales deck lists twelve recognizable customers. Meanwhile, the homepage carries one generic quote from two years ago and a headline that describes the product in your words instead of your customers'. Fixing that takes three kinds of work: - **Finding the proof.** Someone has to search the reviews, the decks, the inboxes, and the call recordings and write down everything worth using. - **Choosing what to show.** Not every quote earns a place. The best proof is specific, comes from customers who look like the buyers you want, and supports the main promise on the page. - **Rebuilding the page.** The hero section and the proof section need to be rewritten around what you found, then published and measured. This is work an AI agent does well, because the hard part is reading a lot of scattered material carefully and making good judgment calls about it. Kite is an AI marketer. It researches your business, builds a growth strategy, and ships the work that brings you new customers. Here's how it handles your homepage proof. ## How Kite adds customer proof to your homepage Kite starts by collecting proof. It reads your current homepage, searches the public web for reviews and mentions of your company, and goes through the documents, call transcripts, and messages you give it access to. Everything it finds goes into a proof inventory: a list of each quote, result, logo, rating, and signal, with the source beside it. Next, Kite looks across the inventory for a pattern. If customers keep praising the same benefit, and your homepage doesn't mention it, that benefit is often a better headline than the one you have. Kite chooses the angle your proof supports best and tells you why. Then Kite rewrites the hero section around that angle and builds a proof section that backs it up. You review the new copy and layout before anything goes live. After the change is published, Kite watches how visitors respond and reports what changed. ### How do I find all the testimonials, logos, and results we already have? Kite finds your proof by searching every place it tends to collect, then writing it all into one list with the source of each item. Some of that searching needs no setup at all. Kite reads your website, including case study and customer pages that the homepage never links to. It also searches the public web for reviews on sites such as G2 and Google, articles that mention you, and public posts on X and Hacker News. For a developer product, it notes community signals such as GitHub stars and contributors. Your private proof needs a connection or a quick hand-off. Connect Google Drive or Google Docs, and Kite searches your sales decks, customer interview notes, and old case study drafts for quotes and numbers. Connect Fathom, and Kite reads the transcripts of calls with people outside your company, looking for moments where a customer describes a result in their own words. You can also upload PDFs and screenshots in the Kite web app, or forward a customer's thank-you email to your team's Kite address. The inventory Kite produces groups proof by type, so you can see at a glance what you have: - **Results with numbers**, such as "cut onboarding from three weeks to four days." - **Testimonials**, with the customer's name, role, and company when the source gives them. - **Customer logos**, which Kite can fetch for the companies you name. - **Ratings and review counts** from the review sites your buyers read. - **Usage and community signals**, such as customer counts, downloads, or GitHub stars. Each item keeps a link to where Kite found it, so you can check any line before it goes on your website. ### What should go in the proof section of a homepage? A strong proof section shows specific results from customers who look like your buyers, placed next to the decisions visitors are making. Kite judges each item in the inventory against three questions. The first question is whether the proof is specific. Kite prefers a quote that describes a moment, such as what the customer expected, what happened, and what they did next, over one that grades the service. "We booked eleven demos in the first week, and two of them closed" gives a reader something to test against their own situation. "Great product, highly recommend" doesn't. The second question is whether the customer resembles the buyer you want. Kite uses what it knows about your ideal customer to decide which logos and quotes lead. If you sell to dental clinics, a quote from a clinic manager does more work than a logo from a large company in an unrelated industry. The third question is where the proof belongs on the page. Visitors hesitate at specific points: just below the hero, beside the signup or demo button, and near pricing. Kite places the proof that answers each hesitation at that point. A rating and review count can sit right under your main button, while a short results strip and two or three named testimonials fill the proof section below the hero. When you can't name a customer, Kite writes an anonymized proof statement that keeps the specific result, such as "A 40-person logistics company cut its quote turnaround from two days to two hours." When you have logos but no results, Kite points that out and drafts testimonial requests to the customers most likely to say yes. For real examples of how small teams lay out their proof, see Social proof examples: how small teams show real customer proof on their homepage (coming soon). ### How do I rewrite my hero section around customer results? Kite rewrites your hero section by leading with the benefit your customers praise most, then backing it up with the strongest proof right beside the headline. The inventory usually makes that benefit obvious. When five reviews and two call transcripts all mention how fast setup was, "Live in an afternoon" is a better headline than "The all-in-one platform for growing teams." Take a scheduling app for dental clinics. Its homepage headline talks about "modern practice management." Kite's inventory shows that customers keep mentioning the same thing: fewer patients missing appointments. One clinic manager said on a call that no-shows fell from 18 a week to 5 after switching. Kite proposes a new hero that leads with fewer no-shows, puts that clinic manager's result directly under the headline once the clinic approves it, and adds the app's 4.8-star rating from 300 reviews beside the "Book a demo" button. Kite writes the proof section to match. It keeps every customer quote exactly as the customer said it, attributes it with a name and role, and pairs it with the result it supports. It can lay out the section as a testimonial grid, a carousel, a strip of logos, or a row of statistics, depending on what you have and what suits your site's design. If the customer's words came from a call or an email rather than a published review, Kite drafts a short request asking the customer to approve the exact wording before it goes on the page. For the headline and button copy on its own, see [Write a stronger homepage headline and call to action](/use-cases/homepage-headline.md). For turning your best results into full stories, see [Turn customer wins into case studies](/use-cases/case-studies.md). ### Publish the new homepage and measure what changed Kite publishes the new hero and proof section once you approve them, then checks whether the change helped visitors take the next step. On a website Kite built and hosts, it adds the new sections directly. Each change waits as an unpublished change you can preview, and when you publish, Kite checks that the page displays correctly. Your team can also edit the testimonials later in the site's content editor, without asking Kite. If your site runs on Webflow, Kite updates it through your connected account and tells you whether each change is staged or live. Kite can also update content in Contentful, Sanity, Storyblok, and self-hosted Payload, and it can work on a site you import from GitHub. After the change goes live, Kite compares how visitors behave before and after. On a Kite-hosted site, its built-in analytics show clicks on your main button, form submissions, and how far visitors get through your signup path. Kite can also run the old hero against the new one as an A/B test, splitting traffic between them and asking for your approval before it makes the winner permanent. For a site measured elsewhere, Kite reads the same before-and-after comparison from your connected analytics product. For broader work on getting more visitors to sign up, see [Improve website conversion](/use-cases/improve-website-conversion.md). ## What you get - **A proof inventory.** Every testimonial, result, logo, rating, and community signal Kite found, grouped by type, with a link to the source of each one. - **A recommended angle.** The benefit your proof supports most strongly, with the evidence behind it and a note on how it differs from your current headline. - **A new hero section.** A headline, supporting line, and button copy built around that angle, with the strongest proof placed beside it. - **A new proof section.** Named testimonials, results, logos, and ratings, laid out in the format that fits your site and placed where visitors hesitate. - **Testimonial requests.** Drafts asking specific customers to approve a quote or share a result, for the gaps in your inventory. - **A before-and-after report.** How button clicks, form submissions, and signups changed after the new homepage went live. ## How to get started Start by asking Kite to gather your proof. You might say, "Find all the customer proof we have and rebuild our homepage hero around it," or "Our homepage has one old testimonial. What else do we have?" You can work with Kite in your browser or in Slack. Kite begins with the public sources it can reach on its own, then asks you to connect Google Drive, Google Docs, or Fathom if your best proof lives there. It sends you the inventory and its recommended angle first, so you can remove anything you'd rather not use or point out proof it missed. Once you agree on the angle, Kite writes the new hero and proof section and shows you a preview. Approve it with the Approve or Publish button, or with a reply, and Kite publishes it. If your website runs outside Kite, connect Webflow or your content system before that step. ## Integrations used for adding customer proof to your homepage Kite finds public reviews, mentions, and logos with its own built-in research tools, so the first inventory needs nothing connected. Connections help in two places: finding the private proof your team has collected, and publishing the new homepage to a site Kite doesn't host. ### Find the proof in your calls and documents - [Fathom + Kite](/integrations/fathom.md): Kite reads the transcripts of your customer and sales calls and pulls out the moments where customers describe their results in their own words. - [Google Drive + Kite](/integrations/google-drive.md): Kite searches your sales decks, customer interview notes, and case study folders for quotes, numbers, and customer lists. - [Google Docs + Kite](/integrations/google-docs.md): Kite reads the case study drafts and customer notes your team keeps in Docs, and it can deliver the proof inventory as a Google Doc your team can comment on. ### Publish the new homepage - [Webflow + Kite](/integrations/webflow.md): Kite updates the hero copy and the testimonials, logos, and results in your Webflow site, and tells you whether each change is staged or live. ## Common questions ### What is social proof on a website? Social proof on a website is anything that shows visitors other people already trust your product. Common forms include customer testimonials, logos of companies you work with, star ratings and review counts, specific results such as time or money saved, case studies, and usage numbers such as the count of active customers. It works because buyers look for evidence from people like them before they commit. ### How can I add testimonials to my website? You add testimonials by collecting real customer quotes with permission, then placing them where they support a decision on the page. On a website Kite hosts, Kite can add a testimonials section, a carousel, or a testimonials collection your team edits in the content editor. On Webflow, Kite adds them through your connected account. In both cases, Kite keeps each quote word for word and puts the customer's name and role beside it. ### What if we don't have many testimonials yet? You probably have more than you think, but if the inventory is thin, Kite fills the gaps. It drafts testimonial requests to the customers most likely to give a specific quote, such as the ones who praised you on a recent call. It can draft a customer story from public evidence, such as a customer's own post about using your product, along with an email asking that customer to approve it. It also writes anonymized proof statements that keep the result even when you can't share the name. ### Where does the proof Kite writes come from? Every quote, number, and logo Kite uses comes from a source in the inventory, and each one links back to it. Kite keeps customer quotes exactly as written. When Kite reviews an existing homepage, it also flags testimonials and case studies that name no customer or give no specific result, and recommends replacing them with real proof. ### Do I need permission to put a customer's logo or quote on my homepage? Ask first. Many customer contracts say whether you can show a customer's logo, and a quote from a sales call or a private email should be approved by the customer before it goes on your site. Kite drafts those requests for you, quoting the exact wording it wants to use, and you send them from your own account or from your team's Kite address once you approve them.