Appearance
Kendo.dev — Go-to-Market Plan
Pricing, marketing channels, launch roadmap, metrics, and strategic priorities for kendo.dev.
For positioning, SWOT, competitive landscape, and messaging: see marketing-strategy.md.
6. Pricing Strategy Recommendation
| Tier | Price | Target | Includes |
|---|---|---|---|
| Free | $0 | Solo devs, evaluation | 1 project, up to 3 seats, all core features, MCP, AI (limited) |
| Team | $8/seat/month | Small teams (3-15) | Unlimited projects, full AI, time tracking, GitHub integration, audit logs, BYOK AI keys |
Market positioning
(See research/dev-tool-pricing-landscape-2026-q2.md for the full pricing matrix.)
- Cheaper than Linear ($10) with time tracking and audit logging included — Linear gates both behind higher tiers
- Cheaper than Shortcut ($8.50) with time tracking and audit logging included — Shortcut has Korey AI but no time tracking or audit logs below Enterprise
- More feature-rich than Plane ($6) at the compliance layer — Plane gates audit logging behind Business ($13), Kendo includes hash-chained logs at $8
- Massively simpler and cheaper than Jira ($7.91 + add-ons) — Jira gates AI behind Premium ($14.54) and audit logs behind the same tier
Key pricing principles
- No per-feature add-on pricing (unlike ClickUp's $9/user AI add-on)
- MCP and AI in every tier — this is the differentiator, don't gate it
- Time tracking in every tier — competitive advantage, don't hide it
7. Marketing Channels & Strategy
(Updated 2026-04-04 based on research/dev-tool-growth-playbooks.md, research/developer-pm-sentiment-2026.md, research/eu-data-sovereignty-demand-2026.md)
Phase 1: Foundation ✅ COMPLETE
Landing page and docs are live at kendo.dev. SEO and AI discoverability (llms.txt, structured data) are shipped.
Phase 1.5: Pre-Launch (Weeks 1-8 before public launch)
Goal: Build demand, refine product with real users, establish founder brand.
Every breakout dev tool studied ran a private beta before public launch. Linear had 1,000 paying customers before going public. Resend had 20K on a waitlist. Going straight to public launch leaves signal on the table.
| Action | Channel | Priority | Notes |
|---|---|---|---|
| Waitlist / invite-only beta | kendo.dev | High | 4-8 week invite-only period. Goal: 50-200 users providing feedback before public launch. Even 200 email signups from strangers validates positioning. |
| Founder brand on Twitter/X | @jasperboerhof | High | Jasper's personal account is the primary channel, not @kendo. Build-in-public tweets 3-5x/week: screenshots, technical decisions, architecture choices. #buildinpublic. Founder brand vastly outperforms company accounts — Linear's founders generated a 10K waitlist through their Twitter following alone; Resend built a 20K waitlist purely from Zeno Rocha's personal brand. (See research/dev-tool-growth-playbooks.md §Linear, §Resend) |
| Open-source wedge | GitHub | High | Ship a useful standalone open-source tool adjacent to Kendo. Every breakout dev tool had one (Resend → React Email, Vercel → Next.js, Supabase → entire platform, PostHog → self-hosted analytics). Candidates: open-source MCP integration library, time tracking CLI, or board template format. This is the biggest gap in the current strategy. |
| GitHub README | GitHub | High | Compelling README with screenshots, feature list, link to kendo.dev. |
| Manual onboarding | Direct | High | DM first 10-50 beta users. Set up accounts personally. Watch them use the product. PostHog targeted 30-second response times — speed of support is a solo founder's unfair advantage. |
Phase 2: Public Launch (Week 8-10)
Goal: Maximum visibility from coordinated launch across channels.
| Action | Channel | Priority | Notes |
|---|---|---|---|
| Hacker News "Show HN" | news.ycombinator.com | Critical | Single highest-leverage launch action for dev tools. Post Tue-Thu, 8-10 AM PT. Write a first comment explaining who you are and why you built this. Engage every comment for 18 hours. Supabase got 1,120 upvotes and 100x growth; PostHog got 300 deployments in days. |
| Product Hunt launch | producthunt.com | High | Same week as HN. Prepare assets in advance: demo video (90s), screenshots, tagline. Riding momentum from HN into PH newsletters maximizes impact. |
| Cross-post the technical story | Reddit, dev.to, Hashnode | Medium | Same HN post adapted for r/programming, r/webdev, dev.to. Each platform has different norms — adapt the format, not the substance. |
Phase 3: Content Marketing (Month 2-4)
Goal: Organic traffic through developer-focused content. Content marketing supports growth in Month 2-6 but was never the primary 0-to-1000 driver for any studied company. Focus on authentic, honest writing.
| Content Type | Topic Ideas | Channel | Frequency |
|---|---|---|---|
| Founder blog | Honest writing about the building journey — decisions, trade-offs, mistakes. PostHog's most successful content was transparent founder writing. This naturally hits HN frontpage. | kendo.dev/blog | 2x/month |
| Technical deep-dives | "Building an MCP server with Laravel" / "Hash-chained audit logs in PHP" / "The $78K context-switching tax and how MCP fixes it" | dev.to, Hashnode | 1x/month |
| Comparison pages | "Kendo vs Linear" / "Kendo vs Jira" / "Kendo vs GitHub Projects" — honest, feature-by-feature | kendo.dev/compare | One-time, update quarterly |
| Pain-point content | "Jira fatigue: what 49,000 developers actually say" (use sentiment research data) / "Database-per-tenant: real multi-tenancy" | kendo.dev/blog | As needed |
SEO keyword targets
| Keyword cluster | Intent | Content |
|---|---|---|
| "issue tracker with MCP" / "MCP project management" | Discovery | Landing page, blog post |
| "Jira alternative for small teams" | Comparison | Comparison page |
| "project management with time tracking" | Feature | Feature page, docs |
| "AI issue tracker" / "AI project management" | Discovery | Landing page, blog |
| "GDPR project management EU" / "European Jira alternative" | Compliance | Landing page, blog. The "European alternatives" search segment is real (europealternatives.com catalogs 354+ EU companies). |
| "issue tracker terminal" / "manage issues from terminal" | Developer workflow | Landing page, blog |
Phase 4: Community & Recurring Growth (Month 2-6)
Goal: Build community, establish recurring visibility through Launch Weeks.
| Channel | Strategy | Effort |
|---|---|---|
| Twitter/X (Jasper personal) | Primary channel. Opinionated dev insights, build-in-public, MCP ecosystem commentary. Founder voice, not company voice. | Daily |
| Hacker News | Ongoing: submit technical blog posts, engage in PM/dev tool threads. Not just the launch post. | Ongoing |
| r/programming, r/webdev, r/ExperiencedDevs — publish technical posts that showcase Kendo's approach, not product mentions. "Here's how we built hash-chained audit logs" > "check out our tool." | Ongoing | |
| Discord community | Launch a Kendo Discord for users, feedback, support. Railway grew to 45K Discord members with zero marketing spend. Be there daily. | Ongoing |
| Claude Code / MCP community | Share Kendo + Claude Code workflow demos. Showcase MCP integration patterns. | Ongoing |
| Launch Weeks | Quarterly mini-launch-weeks: 3 days of feature announcements. Supabase's most repeatable growth tactic — they even open-sourced the concept at launchweek.dev. First one at Month 2-3. | Quarterly |
| Mastodon/Fediverse | Deprioritized. No studied company cited it as a growth channel. Cross-post from Twitter when relevant, but don't invest equal effort. | Low priority |
Phase 5: Partnerships & Integrations (Month 3-6)
| Partnership | Value | Approach |
|---|---|---|
| Anthropic/Claude Code | Featured in MCP ecosystem, Claude Code docs | Submit to MCP registry, write integration guide |
| Mattermost | Listed in Mattermost marketplace | Submit integration |
| Laravel community | Laravel-built tool, credibility in the ecosystem | Laravel News feature, Laracasts sponsorship |
| Vue.js ecosystem | Built with Vue, credibility | Vue.js conference sponsorship/talk |
| European alternatives directories | Listed on europealternatives.com and similar EU-SaaS directories | Submit listings — validated as a real discovery channel for EU-conscious buyers |
8. Launch Roadmap
(Updated 2026-04-04 — resequenced based on research/dev-tool-growth-playbooks.md. Key change: added pre-launch beta phase before public launch.)
| Status | Action | Owner | Phase |
|---|---|---|---|
| ✅ | Landing page shipped (kendo.dev) | Dev | Foundation |
| ✅ | Documentation shipped (kendo.dev/docs) | Dev | Foundation |
| ✅ | SEO + AI discoverability (llms.txt, structured data) | Dev | Foundation |
| Next | Start building in public on Twitter/X (Jasper personal) | Founder | Pre-launch |
| Next | Ship open-source wedge project (MCP library or time tracking CLI) | Dev | Pre-launch |
| Next | Set up waitlist / invite-only beta on kendo.dev | Dev | Pre-launch |
| Next | Onboard first 10-50 beta users manually | Founder | Pre-launch |
| Next | Prepare Product Hunt assets (demo video, screenshots, copy) | Marketing | Pre-launch |
| Launch | Hacker News "Show HN" post (Tue-Thu, 8-10 AM PT) | Founder | Public launch |
| Launch | Product Hunt launch (same week as HN) | All hands | Public launch |
| Planned | Launch Discord community | Founder | Post-launch |
| Planned | First blog posts (context switching article, MCP deep-dive) | Content | Post-launch |
| Planned | Comparison pages (vs Linear, vs Jira, vs GitHub Projects) | Content | Post-launch |
| Planned | Submit to MCP registry, Mattermost marketplace, EU directories | Dev | Post-launch |
| Planned | First mini-Launch Week (3 days of announcements) | All | Month 2-3 |
| Ongoing | 2x/month blog posts, daily Twitter, community engagement | Content | Ongoing |
9. Key Metrics to Track
Note: Month 3 targets are aspirational. PostHog took ~6 months to reach 1,000 users. Linear had 1,000 after a year of invite-only beta. Calibrate expectations — the 0-to-1000 phase depends heavily on HN/PH launch success. (See research/dev-tool-growth-playbooks.md)
| Metric | Tool | Target (Month 3) |
|---|---|---|
| Waitlist signups (pre-launch) | Internal | 200+ signups |
| Beta users (pre-launch) | Internal | 50 active users |
| Organic traffic to kendo.dev | Google Search Console | 1,000 visits/month |
| AI citations (ChatGPT, Perplexity mentions) | Manual monitoring | Appearing in "issue tracker" queries |
| Sign-ups (post-launch) | Internal analytics | 100 sign-ups |
| Product Hunt upvotes | Product Hunt | Top 5 of the day |
| Hacker News upvotes | HN | 100+ upvotes |
| GitHub stars (open-source wedge) | GitHub | 500 stars |
| Blog post views | Analytics | 500/post average |
| Discord members | Discord | 100 members |
10. Strategic Priorities
(Updated 2026-04-04 based on research/dev-tool-growth-playbooks.md, research/developer-pm-sentiment-2026.md, research/eu-data-sovereignty-demand-2026.md)
Five things that matter most
Lead with context switching, not "Jira alternative." Context switching costs developers $78K/year and 4.5 hours of focus daily. "Your board lives in your terminal — zero context switches" is a stronger and less saturated message than "Jira alternative" (at least 15 articles already compete for that phrase). (See research/developer-pm-sentiment-2026.md)
Ship an open-source wedge before public launch. Every breakout dev tool had an open-source component driving awareness (Next.js, React Email, PostHog self-hosted). This is the biggest gap in the strategy. Candidates: MCP integration library, time tracking CLI, board template format. (See research/dev-tool-growth-playbooks.md)
Run a private beta before going public. Linear had 1,000 customers before public launch. Resend had 20K on a waitlist. A 4-8 week invite-only beta builds demand, refines the product, and ensures the public launch converts. HN + Product Hunt remains the launch sequence — but after beta, not before.
MCP depth + audit trails is the moat. MCP is now table stakes (13+ PM tools have servers), but nobody is solving audit trails for AI agent actions via MCP. Kendo's hash-chained audit logs uniquely fill this gap. Position around trust and transparency: "AI manages your board — and every action is audited." (See research/developer-pm-sentiment-2026.md §6)
"Nothing extra" > "everything included." Reframe the bundle message to avoid sounding like ClickUp. "No Toggl subscription. No Tempo add-on. No enterprise tier for audit logs." is more compelling than "all-in-one." Developers who hear "everything included" think feature bloat; "nothing extra" communicates lean focus.
Related
- marketing-strategy.md — SWOT, competitive landscape, USPs, messaging framework
- product-overview.md — Full feature set powering this strategy
- brand-guide.md — Voice, tone, and visual identity for all marketing output
- mission.md — Strategic priorities that guide what we emphasize
- growth/directory-launch-plan.md — Startup directory submission strategy
- ../shared/competitors.md — Detailed competitive landscape
- ../shared/user-personas.md — Persona details for targeted messaging