--- title: Create a partner enablement kit description: Give your resellers, agencies, and installers the talking points, email templates, and setup checklist they need to sell and install your product on their own, written for the way each partner already works with customers. slug: /use-cases/partner-enablement-kit page_type: use-case lead_prompt: How do I create a partner enablement kit with AI? target_prompts: - Can an AI marketing agent create a partner enablement kit? - What should a partner sales kit include? - How do I give resellers talking points and email templates for my product? - How do I help partners sell and install my product without my team on every call? - Is there a template for partner onboarding materials? entity: Kite category: AI marketing agent author: Devon Wells and Kite date_published: '2026-11-11' date_modified: '2026-11-11' related_integrations: - /integrations/google-docs.md - /integrations/notion.md - /integrations/google-drive.md - /integrations/gmail.md - /integrations/slack.md - /integrations/hubspot.md - /integrations/salesforce.md --- # Create a partner enablement kit ## Key Takeaways - A partner enablement kit gives a reseller, agency, or installer everything they need to sell and set up your product without calling you: talking points, email templates, a setup checklist, and answers to the questions their customers ask. - Signed partners usually stall because the materials they got describe your product the way your team sees it. A kit works when it's written from the partner's side: their customers, the moment they'd bring your product up, and how it helps them earn money. - Kite researches each kind of partner you work with, then writes talking points they can say in their own words and email templates they can send from their own inbox. - Kite builds the setup checklist from your documentation, your support threads, and short questions to the person who handles installs, so partners can finish a setup the first time. - Kite delivers the kit as a Google Doc, a Notion page, a PDF, or a shareable page, and it keeps the kit current as partners send questions and your product changes. ## Why signed partners don't sell, and what a kit fixes Partner enablement is the work of giving partners the knowledge and materials they need to sell, set up, and support your product on their own. Signing a partner is the easy part. The agreement is in place, the partner is excited on the kickoff call, and then months go by with no deals. When you ask why, the answer is almost always some version of "we weren't sure how to bring it up." That makes sense from the partner's side. An IT services firm that resells your software is also reselling twenty other products. An agency that refers your tool spends its days on client work, not on learning your feature list. If explaining your product means booking a call with your team first, most partners will simply recommend something they already know how to explain. A partner enablement kit removes that friction. It tells the partner which of their customers need your product, what to say when the subject comes up, which email to send afterward, and how to get the product working once the customer says yes. A good kit lets a partner run a whole deal without you on the call. Writing one well takes more research than most teams expect. You have to understand how each kind of partner makes money, what their customers worry about, and where installs tend to go wrong. That suits an AI agent that already knows your business and can research your partners. Kite is an AI marketer. It researches your business, builds a growth strategy, and ships the work that brings you new customers. For your partner channel, Kite learns how your partners work, writes the kit in their language, and keeps it accurate as your product and program change. Here's how it works. ## How Kite creates a partner enablement kit Kite starts with what it already knows about your company. Your team's knowledge base holds your positioning, products, customers, competitors, and brand voice. If you've documented your partner program, it also holds your tiers, margins, and deal registration rules, so the kit's promises match the program. You tell Kite who your partners are, or let it pull them from your CRM, and share anything you already have, such as an old partner deck, your setup documentation, or a list of questions partners keep asking. Kite then researches the partners, decides what each kind of partner needs to say and do, and writes the kit. The work runs in five parts. Kite learns how your partners sell. It writes the talking points and the email templates. It builds the setup checklist. It packages everything in the format your partners will actually open. Then it keeps the kit current by learning from the questions partners send and the deals they bring in. You review each part before it reaches a partner. Kite sends the kit to partners, or publishes it on your website, once you approve it. ### Learn how your partners sell before writing anything The most useful thing Kite does before writing is figure out how your partners already talk to their customers, because a kit only works if it fits into conversations the partner is already having. Kite researches your partners the way it researches a prospect. It reads their websites and service pages, looks at the products they already resell, and builds a short profile of each one: who their customers are, what services they sell, and how they're paid. Most partner programs include a few different kinds of partners, and each needs a slightly different kit. A managed IT provider brings up new software during a quarterly review with a client. A marketing agency recommends tools while scoping a project. An installer mentions an add-on while standing in the customer's building. Kite groups your partners by how they sell and writes for each group, so a partner doesn't have to translate someone else's pitch. For example, suppose you sell energy sensors for commercial buildings through HVAC installers. Your own sales deck talks about optimization software and portfolio dashboards. An installer's customer is a property manager who mostly wants lower utility bills and fewer emergency calls. Kite writes the installer's kit around the conversation that installer is already having during a maintenance visit, not around your dashboard. If your partner deals are recorded in HubSpot or Salesforce, Kite can also read them to see which partners have closed deals and which haven't. Partners who already sell are a useful source. Kite looks at how their deals started and uses that pattern in the kit for everyone else. ### What should a partner sales kit include? A partner sales kit should include everything a partner needs from the first mention of your product to a working setup. Kite usually builds it from these pieces: - **A one-page overview.** What your product does, who it's for, and the problem it solves, written for the partner's customer rather than for the partner. - **Talking points.** The short explanation a partner can give out loud, the signs that a customer needs your product, and answers to the objections customers raise. - **Email templates.** Messages the partner can send to introduce your product, follow up after a conversation, and propose next steps. - **Pricing and what the partner earns.** The prices a partner can quote and the margin or commission they receive, taken from your program rules. - **A setup checklist.** Every step needed to get a new customer running, in order, with what to check before moving on. - **Common questions.** Plain answers to the questions customers ask most, including the hard ones about price, switching, and security. - **Who to contact.** Where a partner goes when they're stuck, and how to register a deal. Kite leaves out anything a partner won't use in a real deal. A forty-slide product deck with your company history tends to sit unopened in a shared folder. A two-page talking-points sheet gets read before a client meeting. ### Write talking points partners can say in their own words Talking points work when a partner can repeat them naturally in a conversation, so Kite writes them as short spoken sentences rather than marketing copy. Each set opens with the moment the partner should bring your product up. Then it gives a one-sentence explanation, a few questions that help the partner tell whether the customer is a fit, and a short answer to each common objection. For the HVAC installer, the opening might be, "If a tenant complains that the building is too warm in the afternoon, mention that you can install sensors that show exactly which zones are running hot." The qualifying questions might ask how many buildings the property manager runs and whether they report energy use to anyone. The objection answers cover what property managers actually say, such as "We already have a building management system." Kite builds the talking points from your positioning and from what it knows about your customers and competitors. It describes results only when it can point to a source, such as a published case study or a number you supplied. When a strong claim needs proof you don't have yet, Kite tells you which customer result would make the talking points stronger. ### How do I give resellers email templates for my product? Give resellers short email templates that sound like the reseller wrote them, with clear spaces for the details only they know. Partners send emails from their own inboxes to customers who know them, so a message that reads like your company's newsletter feels wrong coming from their address. Kite writes a small set of templates that follow a deal from start to finish: - **An introduction email** for a customer the partner thinks would benefit, with a reason tied to that customer's situation. - **A follow-up after a conversation** that recaps what the customer said and proposes a next step. - **A proposal or quote email** that explains what the customer gets and what it costs. - **A setup scheduling email** that tells the customer what to prepare before the install or onboarding call. - **A check-in after setup** that asks how things are going and opens the door to the next sale. Each template marks the parts the partner fills in, such as [customer name], [the problem they mentioned], or [date of the visit], and gives an example of a good entry. Kite writes in a plain, friendly tone that fits most partners' voices. If you have a partner whose emails Kite can see, such as one who forwarded a successful thread, Kite can match the template to how that partner already writes. ### How partners install your product without your team on every call Partners can handle setups on their own when the checklist covers every step, in order, with a clear way to confirm each one worked. Most setup calls happen because a partner reached a step the documentation skipped, so Kite builds the checklist from where setups actually go wrong, not only from the official instructions. Kite starts with your setup documentation, help center pages, and any onboarding guides you upload. Then it looks for the problems those documents miss. With Gmail connected, it can read the threads where partners or customers asked for help during a setup. If you've added Kite to Slack, it can also search the public channels it has joined for earlier conversations about installs that got stuck. For anything it can't find, Kite asks the person on your team who handles setups a few short questions, such as "What do partners most often forget to check before they leave a site?" The finished checklist is organized around the job: - **Before the setup.** What the customer needs to provide, which accounts or access the partner needs, and what to bring. - **During the setup.** Each step in order, with what the partner should see when it's done correctly. - **Before leaving or ending the call.** The checks that confirm everything works, and what to show the customer. - **When something goes wrong.** The most common problems, how to fix them, and when to contact your team. The checklist turns a support call into a reference a partner can open on their phone in the middle of an install. ### Deliver the kit where partners will open it Kite delivers the kit in whatever format your partners already use, because the best kit fails if it lives somewhere partners never look. You choose one or several: - **A Google Doc.** Kite writes the kit as a formatted Google Doc with headings and links, and it can export a PDF to attach to partner welcome emails. - **A Notion page.** If your partner resources already live in Notion, Kite builds the kit there with the same structure. - **A shareable page.** Kite can publish the kit as a hosted page that opens from a link without signing in, with the templates and checklist available as downloadable files. - **A page on your website.** On a website Kite hosts, Kite can publish a partner resources page after you approve it. If you use a partner portal such as PartnerStack or Impartner, you can upload the PDF or link the shareable page from your portal's resources section. Once you approve the kit, Kite can write the email that introduces it to your partners, explaining what's in it and which part to read first. That email goes out from your team's Kite address or your connected email account after you approve it. ### Keep the kit current from the questions partners ask A partner kit goes stale quickly, so Kite treats each question a partner asks as a sign that something is missing. When partners email your team's Kite address, Kite reads the question, drafts an answer for you to approve, and suggests adding that answer to the kit. If three partners ask how to handle a customer who already uses a competitor, the next version of the kit has a clear answer to that objection. Kite also updates the kit when your product or program changes. Tell Kite about a new feature, a price change, or a new setup step, and it revises the affected sections of the kit and drafts a short note to partners about what changed. Because the kit draws on your team's knowledge base, the margins and prices it lists stay consistent with your partner program guide and your other partner materials. You can also ask Kite to review the kit on a schedule, such as once a quarter, and flag anything that no longer matches your product. To see whether the kit is working, Kite can add tracking tags to the links in each partner's email templates, so you can tell which partners are sending customers to your site. On a site Kite hosts, its built-in analytics show those visits and the signups or form submissions that followed. With HubSpot or Salesforce connected, Kite can compare which partners registered or closed deals before and after the kit went out, and recommend which partners need a follow-up call or a different version of the kit. ## What you get - **Partner profiles.** A short profile of each partner or group of partners, covering their customers, the services they sell, and how they'd bring up your product, saved in your team's knowledge base. - **Talking points for each kind of partner.** Spoken explanations, signs that a customer is a fit, and answers to common objections. - **Email templates.** A set of messages that follow a deal from introduction to post-setup check-in, with clear spaces for the partner's own details. - **A setup checklist.** Every step from preparation to final checks, built from your documentation and the places setups actually go wrong. - **A common questions section.** Answers to the customer questions partners hear most, updated as new ones come in. - **The kit in your chosen format.** A Google Doc, Notion page, PDF, shareable page, or website page, along with the email that introduces it to your partners. - **Ongoing updates.** Revisions and partner notes whenever your product or program changes, plus a view of which partners are sending customers. ## How to get started You can work with Kite in your browser or in Slack. Start by telling Kite what you need in plain language. You might say, "We have fifteen reseller partners and only three of them sell. Write a kit that helps the rest bring us up with their customers," or "Our installers keep calling us during setups. Build them a checklist they can follow on their own." Kite asks for anything it can't find on its own, such as your partner list, your setup documentation, and the name of the person who handles installs. It researches your partners, shows you how it plans to group them, and then sends you a draft of the kit to review. You can ask for changes in the conversation, and Kite revises the kit until it's ready to share. You don't need to connect anything to get the first draft. Kite can work from the files you upload and its own research on your partners. Connect Gmail when partner questions and setup problems live in email threads, Google Docs or Notion when you want the kit written there, and HubSpot or Salesforce when you want Kite to see which partners are selling. ## Integrations used to create a partner enablement kit Kite's built-in research covers your partners' websites, services, and customers. Connected accounts give Kite the setup problems and deal history your team already has, and a place to deliver the kit where partners will read it. ### Find what partners struggle with - [Gmail + Kite](/integrations/gmail.md): Kite searches your mailbox for the threads where partners asked for help selling or installing your product, and uses them to fill gaps in the talking points and checklist. - [Slack + Kite](/integrations/slack.md): Kite searches the public channels it has joined for earlier discussions about stuck setups and partner questions. - [Google Drive + Kite](/integrations/google-drive.md): Kite reads the setup guides, old partner decks, and product sheets you keep in Drive. ### See which partners are selling - [HubSpot + Kite](/integrations/hubspot.md): Kite reads your partner deals and companies to see which partners close deals and how those deals started. - [Salesforce + Kite](/integrations/salesforce.md): Kite reads partner accounts and opportunities in Salesforce for the same purpose. ### Write and share the kit - [Google Docs + Kite](/integrations/google-docs.md): Kite writes the kit as a formatted Google Doc, revises individual sections when something changes, and exports a PDF for partners. - [Notion + Kite](/integrations/notion.md): Kite builds the kit as a Notion page and updates it in place as partners ask new questions. ## Common questions ### Is there a template for partner onboarding materials? Partner onboarding materials usually follow the order a new partner needs them: 1. A welcome note that explains the program and what to read first 2. A product overview written for the partner's customers 3. Talking points and objection answers 4. Email templates for each stage of a deal 5. Pricing, margins, and how to register a deal 6. The setup checklist 7. Common customer questions 8. Training resources and who to contact for help Kite starts from this structure and adjusts it to your program. A referral partner who never installs anything doesn't need a setup checklist, and an installer who never quotes prices may need only a short pricing section. For the rules behind pricing and deal registration, see Document your partner program (coming soon). ### What's the difference between partner enablement and sales enablement? Sales enablement equips your own sales team, while partner enablement equips people who work for other companies. Your own reps attend your training, use your CRM, and sell only your product. Partners sell many products, follow their own processes, and give you a few minutes of attention at a time. That's why a partner kit has to be shorter, more self-explanatory, and written in the partner's language rather than yours. ### Does Kite replace a partner portal or a sales enablement platform? No. Partner portals such as PartnerStack and Impartner track partner logins, deal registrations, and payouts. Sales enablement platforms such as Highspot store and distribute content to sales teams. Kite writes the content those tools hold, keeps it current, and can deliver it on its own when you don't use a portal. For a look at portal options, see The Best PRM Software for Small Partner Programs (coming soon). ### How long should a partner enablement kit be? A kit is the right length when a partner can find what they need in the middle of a customer conversation. In practice, that usually means a one-page overview, one or two pages of talking points, a handful of short email templates, and a checklist that fits on a phone screen. Kite keeps each piece short and moves detail, such as full technical documentation, behind a link. ### Should each partner get a different kit? Each kind of partner should get its own version, but individual partners rarely need one. An agency and an installer bring your product up at different moments and to different people, so their talking points and templates differ. Two installers in different cities usually need the same kit. Kite writes one version for each group and can add a short section for a large partner with unusual needs. ### What else can Kite do for our partners? The kit is one part of a working partner channel. Kite can [find the right partners for your business](/use-cases/find-partners.md), [write the outreach emails](/use-cases/partnership-outreach-emails.md) that start those relationships, and [create co-marketing materials](/use-cases/co-marketing-one-pagers.md) with integration partners. Once partners are selling, Kite can [write a partner newsletter](/use-cases/partner-newsletter.md), create partner certification training (coming soon), and report on partner-sourced pipeline (coming soon). ### Can an agency create partner kits for its clients? Yes. An agency can run a separate Kite team for each client, and each team keeps its own research, brand voice, and partner profiles. Kite writes each client's kit from that client's knowledge base, so their partners get materials that match that client's product and program.