---
title: Publish your metrics to build in public
description: Kite helps you choose which numbers to share, pulls them from Stripe, PostHog, or Google Analytics, builds a public metrics page with a clear definition for every figure, and keeps it current on the schedule you set.
slug: /use-cases/public-metrics-page
page_type: use-case
lead_prompt: How do I build a public metrics page for building in public with AI?
target_prompts:
  - Can an AI marketing agent build a public page that shows my company's metrics?
  - How do I create an open startup page with our revenue and growth numbers?
  - What metrics should I share when building in public?
  - Can AI build a page that shows our live business numbers?
  - Is publishing our metrics publicly good marketing?
entity: Kite
category: AI marketing agent
author: Devon Wells and Kite
date_published: '2026-10-25'
date_modified: '2026-10-25'
related_integrations:
  - /integrations/stripe.md
  - /integrations/posthog.md
  - /integrations/google-analytics.md
---

# Publish your metrics to build in public

## Key Takeaways

- A public metrics page, sometimes called an open startup page, shows your company's real numbers, such as revenue, paying customers, and growth, so people can follow your progress. It earns trust because it keeps updating month after month, in the slow months as well as the good ones.
- The numbers worth sharing are the few that tell your story honestly: usually revenue or monthly recurring revenue, paying customers, growth rate, and one measure of usage or traffic. Each one needs a plain definition and a date.
- Kite proposes which numbers to share, reads them from your connected Stripe, PostHog, or Google Analytics account or from its own site analytics, and builds the page on a website it hosts, through your content system, or as a public page that opens from a shared link.
- Kite refreshes the page on the schedule you choose. The numbers are as current as the last refresh, and every figure shows the date it covers.
- Each refresh can also become an update post for your audience, and Kite tracks how many people visit the page and what they do next.

## What is a public metrics page, and is it worth building?

A public metrics page is a page on your website that shows how your business is actually doing. A typical one shows monthly recurring revenue, the number of paying customers, how fast both are growing, and maybe signups or website visitors. Founders who build in public use it as the anchor for everything else they share. Their posts and updates point back to it, and the page proves the story is real.

For the right company, it's good marketing. Real numbers are rare, so they get attention. Other founders link to them, write about them, and come back to see what changed. Buyers who are deciding whether to trust a small company see that it's growing and that it isn't hiding anything. It works best when your buyers are founders, developers, or small teams who care how a product is built and who's building it.

The page itself is easy to make once. The hard part is everything around it:

- **Choosing the numbers.** Share too few and the page says nothing. Share too many and nobody can tell what matters.
- **Defining them clearly.** "Revenue" can mean a dozen things. Readers trust a number they understand, and they lose trust fast when a figure quietly changes meaning between updates.
- **Pulling them from the right place.** Revenue lives in your billing system, usage lives in your product analytics, and traffic lives somewhere else again.
- **Keeping it current.** A metrics page that stopped updating six months ago tells readers something too, and it isn't what you meant to say.
- **Telling people about it.** The numbers only earn attention when someone shares what changed and why.

Most founders build the page in a weekend and then let it go stale, because the monthly update always loses to more urgent work. That's exactly the kind of work an AI agent handles well. It can read the same accounts on the same day every month, apply the same definitions every time, and write the update while you're busy with customers.

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 builds a public metrics page and keeps it going.

## How Kite builds and maintains your public metrics page

Kite starts with what it already knows about your business. During onboarding, it researched your positioning, your customers, and how you sell, and saved that in your team's knowledge base. That tells it what story your numbers should tell and which ones your audience will care about.

From there, Kite proposes the numbers to share and how to define each one. Once you agree, it reads them from the accounts where they live, builds the page, and asks you to approve it before it goes live. Then it repeats the refresh on a schedule, writes the update that goes with each one, and watches how the page performs.

### Choose the metrics worth sharing

The metrics worth sharing are the few that show whether your company is growing and whether customers stick around. For most subscription businesses, that means four to six numbers:

- **Monthly recurring revenue**, the predictable revenue you earn each month from subscriptions
- **Paying customers**, counted the same way every month
- **Growth rate**, month over month, so readers can see the trend without doing math
- **Churn**, the share of customers or revenue you lost that month
- **One measure of reach or usage**, such as monthly website visitors, signups, or weekly active users

A business that doesn't run on subscriptions would swap in its own versions, such as monthly sales and repeat customers.

Kite proposes a set like this based on your business model and your audience, then writes a plain definition for each one. For example, it might define paying customers as "accounts with an active paid subscription on the last day of the month, not counting free trials." That definition goes on the page beside the number, so a reader never has to guess what it means.

You decide where the line sits. Some founders share everything, including cash in the bank. Others share growth rates and customer counts but keep exact revenue private. Kite can show a growth percentage or a rounded figure in place of an exact one. Whatever you choose, the page shows company totals, never anything about an individual customer.

### Pull the numbers from where they live

Kite reads each number from the system that already records it, so the page matches your own books.

- **Revenue and customers come from Stripe.** Connect your Stripe account, and Kite reads your subscriptions, charges, invoices, and customers. It works out monthly recurring revenue, new and lost customers, and churn from those records, applying the definitions you agreed on.
- **Product usage comes from PostHog.** If you track your product in PostHog, Kite can query signups, active users, or any event you record, such as projects created.
- **Website traffic comes from Google Analytics or Kite's own analytics.** For a site Kite hosts, it already tracks visitors, page views, and where visitors came from. For a site measured elsewhere, it reads the same numbers from your connected Google Analytics property.

Before it uses a number, Kite checks it against the previous month. If paying customers jumped from 212 to 640 overnight, that usually means something changed in how the data was recorded, such as a batch of test accounts or a new free plan counted as paid. Kite tells you what it found and asks how to treat it, rather than publishing a figure it can't explain.

### Build the page

Kite builds a page that leads with the numbers and explains each one. The top of the page shows the headline figures, such as monthly recurring revenue, paying customers, and growth rate, each with its label and the month it covers. Below that, Kite adds a chart of the trend over time, a short note on what changed this month, and the definitions. A page like this is more convincing with a few sentences from the founder about what's working and what isn't, so Kite drafts those for you to edit.

Where the page lives depends on your website:

- **On a website Kite hosts**, Kite adds the page to your site, links it from your navigation or footer if you want, and returns the live URL. Your team can also change the text directly in the site's content editor.
- **On a website that runs elsewhere**, Kite publishes through your connected content system, such as Webflow, Contentful, Sanity, or Storyblok, or through your GitHub repository.
- **As a standalone page**, Kite can publish the metrics as a public report that opens from a shared link without signing in. That works well when you'd rather not touch your main site yet, and you can link to it from anywhere.

Kite shows you the finished page before anything goes live. Approve it with the Publish button or a reply in the conversation, and Kite publishes it.

### Keep the numbers current

Kite keeps the page fresh by refreshing it on a schedule you choose, usually monthly for revenue and customers. When the schedule runs, Kite reads the latest numbers, applies the same definitions, adds the new month to the chart, and updates the note on what changed.

The page shows the numbers as of the last refresh, and every figure carries the date it covers. That's the honest version of "live." A page that says "October 2026" beside each number is more trustworthy than one that claims to be real-time and leaves readers wondering.

By default, Kite shows you each refresh and asks before publishing it. Once you've seen a few updates and trust the process, you can let Kite publish refreshes on its own and just tell you what changed.

Kite also keeps the slow months on the page. A flat month followed by an honest note about why is what makes readers believe the good months. If you want to stop sharing a number, Kite removes it and can add a short line saying when and why, so returning readers aren't confused.

### Share each update and see what it earns

A metrics page earns attention when someone tells people what changed. After each refresh, Kite can write the update: a post for X, a draft for your LinkedIn, or a short email to your newsletter list. The update leads with the most interesting change, explains what drove it, and links back to the page.

Kite publishes to your connected X account or sends the email through your connected email product once you approve it. LinkedIn drafts wait for you to post them from your own profile.

Kite then measures what the page and the updates bring in. On a site it hosts, it reads how many people visited the page, where they came from, and whether they clicked through to sign up. For a site measured elsewhere, it reads the same through Google Analytics or PostHog. Over a few months, that shows whether building in public is bringing you customers or mostly bringing you other founders, and Kite adjusts what it emphasizes in the next update.

## What you get

- **A short list of metrics with definitions.** The four to six numbers that tell your company's story, each with a plain definition you agreed on.
- **A public metrics page.** Headline numbers, a trend chart, the definitions, and a note on what changed, on your site or at a shareable link.
- **Scheduled refreshes.** The same numbers read from Stripe, PostHog, Google Analytics, or Kite's analytics on the same schedule, with each figure dated.
- **An update to share.** A post or email for each refresh, written around the most interesting change and linking back to the page.
- **A read on what the page earns.** Visits, referrers, and signups from the page and its updates, used to shape the next one.

## How to get started

Tell Kite what you want in plain language. You might say, "Build us an open startup page with our revenue and customer numbers," or "We want to start building in public. What should we share?"

Kite proposes the metrics to share, how to define each one, and where the page should live. You change the list, decide which numbers stay private or rounded, and approve it. Then connect the accounts Kite needs: Stripe for revenue and customers, and PostHog or Google Analytics if you want usage or traffic numbers on the page. If Kite hosts your website, it already has your traffic numbers.

Kite builds the first version of the page and shows it to you before publishing. Once it's live, agree on how often to refresh it and whether you want an update post each time. Kite asks before it publishes each refresh until you decide to let it run on its own.

Most AIs wait for instructions. Kite finds what needs doing and does it. Once the page is running, Kite can point out when a month is worth sharing more widely, such as passing a milestone you've been working toward.

## Integrations used to publish your metrics

Kite reads your numbers from the accounts that already record them. Connect the ones that hold the metrics you've chosen to share.

### Revenue and customers

- [Stripe + Kite](/integrations/stripe.md): Kite reads your subscriptions, charges, invoices, and customers to work out monthly recurring revenue, paying customers, new and lost customers, and churn.

### Product usage

- [PostHog + Kite](/integrations/posthog.md): Kite queries the events your product records, such as signups or weekly active users, so the page can show how much people use what you've built.

### Website traffic

- [Google Analytics + Kite](/integrations/google-analytics.md): For a site Kite doesn't host, Kite reads visitors, sessions, and traffic sources from your Google Analytics property. It also uses those reports to see how many people visit the metrics page and where they come from.

## Common questions

### Should I share my revenue publicly?

Share it if your audience cares how the business is built and the number helps your story. Founders, developers, and small teams tend to respond well to real revenue numbers. If exact revenue feels too exposing, share the growth rate, a rounded figure, or the number of paying customers instead. Those still show momentum. Kite can show any of these, and you can change your mind later.

### Can the page show live numbers that update by themselves?

The page shows your numbers as of the last refresh, and Kite runs that refresh on whatever schedule you set. Monthly suits revenue and customers, because those are the numbers people compare month to month. Weekly suits faster-moving numbers like signups. Each figure carries the date it covers, so readers always know how current it is.

### Do I need a separate subscription analytics tool?

No. Kite reads your subscription records from Stripe directly and works out monthly recurring revenue, customers, and churn using the definitions you agreed on. If you already use a subscription analytics tool and prefer its numbers, Kite can match its definitions so the page agrees with the figures your team already watches.

### What happens if we have a bad month?

Kite keeps it on the page and writes a short, honest note about what happened, such as a large customer leaving or a pricing change. You review the note before it goes out. Readers follow a public metrics page for the real story, and a bad month told plainly does more for your credibility than a gap in the chart.

### Where should a public metrics page live on my site?

Most companies put it at a short, memorable address like /open or /metrics and link it from the footer, the About page, or the founder's social profiles. If Kite hosts your site, it adds the page and the links for you. If you'd rather keep it off your main site for now, Kite can publish it as a standalone public page that you link from your posts.
