Build pages for your partner or loyalty program

Kite settles the program's terms before it writes any copy, because a page can only be as clear as the rules behind it. It already has your products, pricing, customers, and positioning in your team's knowledge base from its research on your business. From there, it asks you the few questions that only you can answer.

For a partner program, those questions might be what partners earn, whether there are tiers, and what support you give them. For a supplier program, they might be what you buy, in what volumes, and which certifications you require. For a loyalty program, they're how customers earn rewards, what they can redeem them for, and whether rewards expire.

Kite can also read the program pages your competitors publish to see which terms are common in your market. If every comparable program offers a 20 percent referral commission and yours offers 10, Kite tells you before the page goes live, because partners will notice.

Kite saves the agreed terms in your knowledge base. Your page, your application form, and any partner emails Kite writes later all draw on the same version, so a partner never reads one commission rate on the page and another in a welcome email.

A loyalty page should explain, in a minute of reading, how a customer earns rewards, what those rewards are worth, and how to start. Customers already like you, so the page doesn't need to sell your business. It needs to remove the guesswork about how the program works.

Kite usually builds a loyalty page around these parts:

• a plain statement of what members get, such as "Earn a free coffee for every ten you buy"
• the steps to join, which are often just creating an account or signing up at checkout
• how rewards are earned and redeemed, with a worked example
• any tiers, and what it takes to reach each one
• the fine print customers actually ask about, such as expiry dates and whether rewards apply to sale items

A worked example does more than a points table. "Spend $50 and you'll have enough points for a free shipping upgrade" is easier to picture than "1 point per dollar, 50 points per reward."

Kite writes the page in your brand voice and builds it from the same sections as the rest of your site, so it looks like part of your website. The page explains the program, but the points themselves live in whatever system tracks them, such as your store or your loyalty app. Kite points the join button at that system's sign-up.

A partner or supplier page has a different job, because its readers are businesses deciding whether working with you is worth their time. The page has to show what's in it for them, make clear who you're looking for, and lead to an application.

Kite usually builds a partner or supplier page around these parts:

• who the program is for, named plainly enough that the wrong people can rule themselves out
• what partners get, such as a commission, a referral fee, wholesale pricing, co-marketing, or early access
• what you expect, such as a minimum volume, a certification, or a number of referrals a year
• how the process works from application to approval, including how long a decision takes
• the application form itself

Here's an example. A software company launching an agency referral program would get a page that says which agencies fit, what they earn per referred customer, how payouts work, and what happens after they apply. A coffee roaster looking for cafés to stock its beans would get a wholesale page with minimum orders, delivery areas, and a short application.

Being specific about who doesn't fit matters as much as describing the benefits. A page that says "for agencies that manage paid ads for ecommerce brands" brings you fewer applications than "for agencies," but far more of them are worth your time.

Kite writes the application form's questions from the criteria you'll use to approve someone. If you'd only accept a supplier with organic certification who can deliver weekly, the form asks about both. That way, each application arrives with what you need to say yes, no, or "let's talk," and you don't have to email back for basics.

Kite keeps the form short. Every question has to help you decide or help you reply. A partner application might ask for a name, an email address, the company website, the kind of clients they serve, and how they heard about the program. Kite writes the labels, the button, and the confirmation message, which tells the applicant what happens next and when they'll hear back.

On a website Kite builds and hosts, the form is part of the site's code, so there's no plugin or separate form service to set up. Each application is emailed to the addresses you give Kite, listing every answer one field at a time. When you hit reply, your answer goes straight to the applicant. You can send applications to more than one person, such as yourself and whoever manages partnerships.

If your website runs somewhere else, Kite can create the application in your connected Typeform or Google Forms account, with the same questions, for you to link to or embed. A loyalty page often needs no form at all, because customers join through your store's own sign-up.

A program page only works if the people it's for can find it, so Kite decides where it belongs on your site. It already knows your site's pages and how visitors move through them. A partner page usually belongs in the footer and on any page where agencies or resellers are likely to land. A loyalty page belongs where customers already are, such as the account page, the checkout, and the order confirmation.

Kite also gives the page a title, a description, and structured data, so search engines and AI answer engines understand what the program is. That matters because people often search for "[your company] partner program" or "[your company] wholesale" before they ever reach your site.

On a site Kite hosts, the finished page waits as an unpublished change. You open a preview, fill in the form yourself to check that the email arrives, and publish when you're happy. Kite asks for your approval before anything goes live. If your site runs on Webflow, self-hosted WordPress, Contentful, Sanity, Storyblok, or self-hosted Payload, Kite publishes through your connected account. If it's an imported GitHub site, Kite pushes the change to your repository.

Once the page is live, Kite helps you work through the applications and tells you whether the page is bringing in the right ones. On a site Kite hosts, it records each application as a conversion in the site's built-in analytics. It can report how many came in, which pages they came from, and which traffic sources sent those applicants.

When applications arrive through Typeform or Google Forms, Kite reads the responses directly. It can research each applicant's company, compare it with the criteria you set, and give you a short read on who looks like a strong fit and why. For partners and resellers, that might include what kinds of clients they serve, how big they are, and whether they already work with a competitor.

If plenty of people visit the page but few apply, Kite treats that as a problem to solve. It might rewrite the benefits, cut a question from the form, or link the page from somewhere more visible. On a site Kite hosts, it can run the change as an experiment that splits traffic between the old and new versions. It asks for your approval before the experiment starts and again before it makes the winning version permanent.