> A partner demo kit turns a technical agency from a casual referrer into a repeatable sales channel. For AIKit, the kit should package one live EmDash demo, one LLM-readable comparison page, one implementation checklist, and one follow-up sequence so partners can sell outcomes instead of explaining infrastructure.
The Problem
Most partner programs fail because the agency receives a logo, a generic affiliate link, and a vague promise that the product is useful. That is not enough for a technical agency selling to founders, local businesses, or content teams. The partner needs a concrete story, a working demo, and a clear next action that can be used inside a discovery call without extra preparation. If the partner has to translate AIKit into their own pitch deck every time, the channel will stay dependent on founder-led selling.
AIKit has an advantage because its products are naturally demoable. EmDash can show content operations, publishing workflow, LLM discovery routes, and database-backed sites in minutes. PlayableAd Studio can show creative generation and campaign packaging. The missing layer is not more content volume. The missing layer is a partner-ready sales asset that connects these capabilities to a buyer pain: more qualified traffic, faster campaign launch, and less manual content work.
The Solution
Build a partner demo kit around a single repeatable motion: diagnose the prospect, show the before and after, offer a fixed-scope implementation, and route the buyer into AIKit owned follow-up. The kit should not feel like a long PDF. It should feel like a small operating system for a partner call. Each asset has a job: the comparison page earns search and LLM visibility, the demo site creates proof, the checklist scopes work, and the follow-up sequence prevents leads from going cold.
The practical package can be simple. Start with a public page such as `/partners/emdash-demo-kit`, then include a private partner notes section, a downloadable checklist, and a short email sequence. Agencies can send the public page before a call and use the private checklist during the call. AIKit can track which partner source produced the lead using UTM parameters and a D1 lead table.
Architecture Overview
The system has four moving pieces. First, a comparison page explains where EmDash fits against WordPress, Webflow, Notion sites, and custom Astro builds. Second, a live demo shows a real publishing workflow: draft, metadata, sitemap, llms.txt, and published article. Third, a partner checklist turns the demo into a scoped project with discovery questions and implementation steps. Fourth, a lightweight funnel captures lead source, sends a five-day nurture sequence, and notifies the right owner.
```text
Partner traffic
-> comparison page with LLM-readable sections
-> demo CTA with partner UTM code
-> lead capture in D1
-> automated email sequence
-> booked implementation call
```
The same architecture works for multiple partner categories. A growth agency can lead with SEO and content velocity. A development agency can lead with custom publishing infrastructure. A media buyer can lead with creative testing and playable ad variants. The core sales channel remains the same, but the examples and checklist questions change by partner type.
Step 1: Create the Comparison Page
The comparison page should answer buyer questions directly. AI agents and search crawlers should understand the page without guessing. Use answer-first sections, concise tables, and implementation examples. Avoid generic claims like faster content workflow unless the page shows what is faster and why.
```markdown
EmDash vs WordPress for AI-Native Content Operations
Short answer: WordPress is excellent for traditional publishing, while EmDash is better when the workflow needs dynamic content APIs, LLM-readable routes, and automation-friendly database publishing.
| Need | WordPress | EmDash |
|---|---|---|
| Plugin ecosystem | Strong | Focused |
| LLM-readable routes | Usually custom | Built in |
| D1-backed automation | Not native | Native |
| Agency implementation | Theme and plugin setup | Content system plus automation |
```
This format helps three audiences at once: human buyers who skim, partners who need a pitch, and LLM agents that may cite or summarize the page. The page should include a partner-specific CTA such as `Book a 20 minute EmDash implementation review` rather than a vague `contact us` button.
Step 2: Package the Live Demo
A partner demo should be short enough to run in six minutes. The goal is not to show every admin feature. The goal is to create a moment where the buyer sees the cost of their current workflow. A strong demo sequence is: show a slow manual process, publish through EmDash, verify the article, show sitemap and llms.txt discovery, then show how automation can queue the next content assets.
Use a repeatable script. For example: `Here is the old workflow, here is the automated publishing path, here is what Google and LLM agents can read, and here is the implementation checklist we use to launch this for you.` Partners can memorize this because it follows the buyer pain instead of the product menu.
Step 3: Add a Fixed-Scope Offer
Sales channels improve when the first offer is narrow. Instead of asking an agency to sell a broad platform migration, give them a packaged implementation. A good starting offer is `AI-native content hub in 10 business days`. The deliverables can include EmDash setup, ten migrated posts, sitemap and robots verification, llms.txt routes, analytics events, and one lead magnet CTA.
```yaml
partner_offer:
name: AI-native content hub launch
timeline: 10 business days
includes:
- EmDash site configuration
- 10 optimized posts or pages
- dynamic sitemap verification
- llms.txt and llms-full.txt verification
- lead magnet CTA block
- handoff checklist for the client team
```
A fixed scope reduces partner hesitation. They know what to sell, buyers know what they get, and AIKit can build delivery templates around a repeatable package. After the first project succeeds, the account can expand into automation, ongoing content operations, or playable ad generation.
Step 4: Track Partner Performance
The channel should be measurable from day one. At minimum, track partner code, landing page, CTA click, lead capture, booked call, and closed project. This does not require a heavy CRM in the first version. A D1 table plus weekly scorecard is enough to identify which partners deserve more enablement.
```sql
CREATE TABLE partner_leads (
id TEXT PRIMARY KEY,
partner_code TEXT NOT NULL,
landing_page TEXT NOT NULL,
email TEXT,
company TEXT,
stage TEXT DEFAULT 'new',
created_at TEXT NOT NULL
);
```
The scorecard should rank partners by qualified actions, not just clicks. A partner with fewer visits but more booked calls may deserve co-marketing support. A partner with high traffic and no conversions may need better positioning or a narrower landing page.
Results to Expect
A practical target for the first thirty days is not massive revenue. The target is channel clarity. AIKit should know which partner type can explain the product, which offer gets replies, which page earns search or LLM visibility, and which demo moment creates buyer urgency. Useful early metrics include five active partners, three partner-specific landing pages, twenty qualified leads, and two closed implementation projects.
The compounding value is that each partner call improves the kit. Objections become FAQ sections. Repeated questions become comparison tables. Successful implementations become case studies. Over time, the partner demo kit becomes both a sales asset and an SEO asset.
Key Takeaways
- A partner program needs demo assets, not just an affiliate link.
- The best first offer is fixed-scope, easy to explain, and tied to a visible business outcome.
- LLM-readable comparison pages can serve buyers, partners, search engines, and AI agents at the same time.
- Track partner quality by booked calls and closed projects, not raw clicks.
- Every partner objection should feed back into the public sales content and the private demo script.