Skip to main content

Sparki Monetization: Complete Documentation Index

Version: 1.0
Date: 2025-12-04
Audience: All stakeholders (engineers, marketing, leadership, community)

Quick Reference

TL;DR: Sparki’s Monetization Strategy
3 Tiers:
  • Community (Free): Unlimited local builds, 50 concurrent jobs
  • Team ($25/mo): 5 seats, 200 concurrent jobs, private projects
  • Pro ($99/mo): 20 seats, 1000 concurrent jobs, unlimited features
  • Enterprise (Custom): On-prem, compliance, white-label

Revenue Model:
  • Year 1: $1.5-2M ARR (5-8% Team tier conversion)
  • Year 3: $50-100M ARR (10-20% Pro/Enterprise)

Go-to-Market:
  • Months 1-3: Community beta + soft launch
  • Months 4-6: Paid acquisition targeting small teams
  • Months 7-12: Enterprise sales motion

Core Promise:
  • Free tier stays free forever (open-source core)
  • No vendor lock-in (always self-hostable)
  • Transparent pricing (no hidden fees)
  • Community-first values (not VC-driven)

Documentation Overview

This index provides complete context for implementing Sparki’s monetization strategy. All documents work together:
Strategic
Documents     │ SPARKI_MONETIZATION_COMPLETE_STRATEGY.md ──────┐
              │ (Business case, tier design, revenue projections) │
              │                                                   ├─→ Leadership/Board
              └─────────────────────────────────────────────────┘

Technical
Documents     │ SPARKI_POLAR_INTEGRATION_TECHNICAL.md ──────┐
              │ (API gateway, usage tracking, webhook handlers) ├─→ Backend Engineers
              │                                              │     (8-10 weeks)
              │ SPARKI_MONETIZATION_IMPLEMENTATION_GUIDE.md ┤
              │ (Step-by-step 8-week roadmap, code examples) │
              └──────────────────────────────────────────────┘

Marketing
Documents     │ SPARKI_MONETIZATION_MARKETING_STRATEGY.md ─────┐
              │ (Positioning, GTM timeline, messaging matrix)   ├─→ Marketing/Product
              │                                                 │     (12-month campaign)
              └─────────────────────────────────────────────────┘

THIS DOCUMENT: SPARKI_MONETIZATION_INDEX.md
(Navigation, FAQ, stakeholder communications, success metrics)

1. Document Descriptions & Use Cases

1.1 SPARKI_MONETIZATION_COMPLETE_STRATEGY.md (30 pages)

Purpose: High-level business case for monetization Contents:
  • Executive summary
  • Market opportunity analysis ($5.2B CI/CD market)
  • Competitive moat vs. GitHub Actions, GitLab CI
  • Three-tier monetization model with feature matrix
  • Seven hidden revenue opportunities (overages, marketplace, data licensing, etc.)
  • Conservative/realistic/ambitious revenue projections
  • Free tier strategy and community trust commitments
  • Risk assessment and mitigation strategies
  • 12-month GTM timeline
Best For:
  • Leadership presentations to board
  • Investor discussions
  • Team alignment meetings
  • New team member onboarding
Read Time: 45 minutes When to Reference: During strategy discussions, quarterly reviews, competitive analysis

1.2 SPARKI_POLAR_INTEGRATION_TECHNICAL.md (40 pages)

Purpose: Complete technical architecture for Polar integration Contents:
  • System architecture (API gateway → Polar → webhooks)
  • Data flows (signup → checkout → subscription → tier enforcement)
  • Tier enforcement system (middleware, quota checks, feature flags)
  • Usage tracking architecture (TimescaleDB hypertable, aggregation)
  • Subscription lifecycle (free tier → checkout → Polar webhook → tier sync)
  • Self-hosted deployment (free tier works offline)
  • Monitoring and observability setup
  • Implementation roadmap (5 phases over 8 weeks)
Best For:
  • Backend engineers building the integration
  • DevOps engineers setting up infrastructure
  • Engineering leads planning the implementation
  • Technical reviewers validating architecture
Read Time: 60 minutes When to Reference: During sprint planning, code reviews, troubleshooting

1.3 SPARKI_MONETIZATION_IMPLEMENTATION_GUIDE.md (50 pages)

Purpose: Step-by-step, 8-week implementation roadmap Contents:
  • 5 phases over 8 weeks
  • Phase 1 (Weeks 1-2): Polar setup, database schema, tier configuration
  • Phase 2 (Weeks 3-4): API gateway middleware, tier enforcement
  • Phase 3 (Week 5): Usage tracking service, metrics instrumentation
  • Phase 4 (Weeks 6-7): Checkout flow, webhook handlers, Polar integration
  • Phase 5 (Week 8): Monitoring, Grafana dashboards, alerts
  • Code examples for each phase
  • Testing checklist (unit, integration, manual)
  • Deployment checklist and rollback plan
  • Success metrics and continuation plan
Best For:
  • Developers assigned to implementation
  • Tech leads managing the project
  • QA planning test strategy
  • DevOps planning deployment
Read Time: 90 minutes When to Reference: Daily during implementation; each team member reads their relevant section

1.4 SPARKI_MONETIZATION_MARKETING_STRATEGY.md (35 pages)

Purpose: 12-month marketing and go-to-market plan Contents:
  • Market context and Sparki’s competitive advantage
  • Positioning statement (“CI/CD for developers who prefer terminals”)
  • Messaging matrix (indie devs vs. teams vs. enterprises)
  • Product launch strategy (closed beta → open beta → GA)
  • Channel strategy (owned, paid, organic)
    • Owned: Blog, email, social media
    • Paid: Google Ads, Product Hunt, sponsorships
    • Organic: GitHub community, DevOps communities
  • Content marketing plan (blog series, tutorials, case studies)
  • Enterprise GTM strategy
  • 12-month timeline with specific milestones
  • Metrics and KPIs
  • Risk mitigation (community backlash, slow adoption, competitors)
Best For:
  • Marketing team executing campaigns
  • Product managers planning launches
  • Communications planning announcements
  • Sales team training on positioning
Read Time: 60 minutes When to Reference: Weekly during marketing sprints; monthly for leadership updates

1.5 SPARKI_MONETIZATION_INDEX.md (This Document)

Purpose: Navigation, FAQ, stakeholder communication templates Contents:
  • Document index and use cases
  • FAQ (for community, internal team, sales)
  • Communication templates
  • Decision log
  • Success metrics dashboard
  • Stakeholder responsibilities
  • Next steps and continuation planning
Best For:
  • Anyone new to the project
  • Answering community questions
  • Preparing communications
  • Tracking progress
Read Time: 30 minutes When to Reference: During onboarding; when answering questions; for status updates

2. Role-Based Reading Guide

Executive/Leadership

Goal: Understand business case and ROI Read:
  1. SPARKI_MONETIZATION_COMPLETE_STRATEGY.md (executive summary + tiers)
  2. SPARKI_MONETIZATION_MARKETING_STRATEGY.md (metrics + GTM timeline)
  3. SPARKI_MONETIZATION_INDEX.md (this doc; FAQ section)
Time: 90 minutes Key Takeaways: $1.5-2M ARR Year 1; 12-month GTM; 5-8% Team tier conversion

Backend Engineers

Goal: Implement Polar integration Read:
  1. SPARKI_MONETIZATION_COMPLETE_STRATEGY.md (understand context)
  2. SPARKI_POLAR_INTEGRATION_TECHNICAL.md (architecture)
  3. SPARKI_MONETIZATION_IMPLEMENTATION_GUIDE.md (your specific phase)
Time: 120 minutes Key Deliverables: API middleware, usage tracking, webhook handlers

Product Managers

Goal: Plan launches and manage product changes Read:
  1. SPARKI_MONETIZATION_COMPLETE_STRATEGY.md (full strategy)
  2. SPARKI_MONETIZATION_MARKETING_STRATEGY.md (launch planning)
  3. SPARKI_MONETIZATION_IMPLEMENTATION_GUIDE.md (technical constraints)
Time: 90 minutes Key Deliverables: Feature prioritization, launch checklist, tier definitions

Marketing/Communications

Goal: Execute GTM campaign and community communication Read:
  1. SPARKI_MONETIZATION_MARKETING_STRATEGY.md (full strategy)
  2. SPARKI_MONETIZATION_COMPLETE_STRATEGY.md (business context)
  3. SPARKI_MONETIZATION_INDEX.md (FAQ + communication templates)
Time: 75 minutes Key Deliverables: Blog series, email campaigns, pricing page copy

DevOps/Infrastructure

Goal: Set up and monitor billing infrastructure Read:
  1. SPARKI_POLAR_INTEGRATION_TECHNICAL.md (monitoring section)
  2. SPARKI_MONETIZATION_IMPLEMENTATION_GUIDE.md (phase 5: monitoring)
  3. SPARKI_MONETIZATION_COMPLETE_STRATEGY.md (high-level understanding)
Time: 60 minutes Key Deliverables: Prometheus metrics, Grafana dashboards, alerts

Community / New Contributors

Goal: Understand why and how Sparki is monetizing Read:
  1. SPARKI_MONETIZATION_COMPLETE_STRATEGY.md (executive summary)
  2. SPARKI_MONETIZATION_MARKETING_STRATEGY.md (section 8: community building)
  3. SPARKI_MONETIZATION_INDEX.md (FAQ for community)
Time: 45 minutes Key Takeaways: Free tier stays free; no vendor lock-in; transparent about business model

3. Frequently Asked Questions

Q1: Will the free tier stay free forever?

A: Yes. The Community tier is permanently free and open-source. This is a core promise we’re making to the community. Free tier includes:
  • Unlimited local builds (self-hosted)
  • 50 concurrent jobs
  • Basic CLI + TUI
  • Framework autodetection
  • No credit card required
We’re monetizing through Team tiers (collaboration features, cloud hosting), not by paywalling core functionality. Reference: SPARKI_MONETIZATION_COMPLETE_STRATEGY.md § 4.2; SPARKI_MONETIZATION_MARKETING_STRATEGY.md § 5.1

Q2: Why are you charging for Team collaboration if you’re open-source?

A: Open-source core ≠ open-source cloud. We’re charging for:
  • Team tier: Collaboration features (shared projects, team seats)
  • Pro/Enterprise: Scale operations (1000+ concurrent jobs), compliance (SSO, audit logs), support
The open-source core remains free and self-hostable. If you want to run Sparki locally, you pay 0.Ifyouwantcloudcollaboration,youpay0. If you want cloud collaboration, you pay 25-99/month. Reference: SPARKI_MONETIZATION_COMPLETE_STRATEGY.md § 3; SPARKI_MONETIZATION_MARKETING_STRATEGY.md § 2.3

Q3: Can I self-host Pro/Enterprise features?

A: Yes. Pro tier supports:
  • Self-hosted deployments (on-prem)
  • Private Kubernetes clusters
  • Managed updates + dedicated support
  • Enterprise pricing (annual commitment discount)
We’re betting on the hybrid model: free locally + cheap cloud for teams + enterprise for self-hosted. Reference: SPARKI_POLAR_INTEGRATION_TECHNICAL.md § 5; SPARKI_MONETIZATION_COMPLETE_STRATEGY.md § 7

Q4: What happens if I hit my quota?

A:
  • Community tier: Excess jobs get queued (you can still use Sparki)
  • Team tier: You can upgrade to Pro immediately (no waiting)
  • Pro tier: You get unlimited (or very high limits)
Quotas are enforced at the API gateway, not by kicking you off. We want to give people a chance to upgrade, not surprise them with outages. Reference: SPARKI_POLAR_INTEGRATION_TECHNICAL.md § 2.3

Q5: What if Sparki shuts down?

A:
  • Open-source core remains available (MIT/Apache license)
  • Self-hosted deployments continue working (no cloud dependency)
  • Community can fork and continue development
  • Your data is portable (standard PostgreSQL, exportable)
We’re betting our future on not becoming the next acquihire. If we do fail, the community is protected. Reference: SPARKI_MONETIZATION_COMPLETE_STRATEGY.md § 6; Marketing Strategy § 2.3

Q6: How much will Pro/Enterprise cost exactly?

A:
  • Pro: $99/month (20 team seats, unlimited builds)
  • Enterprise: Custom (typically $5k-50k+ annually depending on scale)
Pricing is transparent on the pricing page. No hidden fees. Annual commitments get 20% discount. Reference: SPARKI_MONETIZATION_COMPLETE_STRATEGY.md § 3; Pricing page: sparki.tools/pricing

Q7: When will monetization go live?

A:
  • Month 1-2: Closed/Open beta (feedback loop)
  • Month 3: General availability (full monetization enabled)
  • Months 4-12: Scale (paid ads, enterprise sales)
Tiers are tested with beta users first. No surprise price changes for early adopters. Reference: SPARKI_MONETIZATION_IMPLEMENTATION_GUIDE.md § Testing Checklist; SPARKI_MONETIZATION_MARKETING_STRATEGY.md § 3

Q8: Will Team tier features make my GitHub Actions workflow portable?

A: Yes. Sparki is designed to be CI/CD-agnostic:
  • Export pipelines as YAML (if you want to migrate)
  • API is standard REST (not Sparki-specific)
  • Self-hosted = no cloud dependency
  • Integrations (GitHub, GitLab, custom) are open
You can migrate from Sparki to GitHub Actions in 1 day (see migration guide on blog). Reference: SPARKI_MONETIZATION_MARKETING_STRATEGY.md § 8 (blog post: “Migrating from GitHub Actions to Sparki”)

Q9: Is there a free trial for Pro tier?

A: Yes. New users on Team tier get 7-day free trial of Pro features. We want you to experience unlimited before deciding to upgrade. Reference: SPARKI_MONETIZATION_IMPLEMENTATION_GUIDE.md § 4.1 (checkout flow)

Q10: What if I’m unhappy with Pro tier?

A:
  • 30-day money-back guarantee
  • Downgrade to Team anytime
  • Community support always free
  • Contact enterprise@sparki.tools for custom arrangements
We’re betting on product-market fit, not locking people in. Reference: SPARKI_MONETIZATION_MARKETING_STRATEGY.md § 2.2

4. Communication Templates

4.1 Announcement Blog Post (Template)

# Introducing Sparki 1.0: Free Core + Affordable Paid Tiers

Dear Sparki Community,

Today we're announcing Sparki 1.0 and a sustainable business model
that lets us continue building the best open-source CI/CD platform.

## The Problem We Solved

Building open-source infrastructure is expensive. Without revenue,
we can't afford the engineers, servers, and support infrastructure
that make Sparki reliable.

## Our Solution: Three Tiers

**Community (Free)**

-   For solo developers and small projects
-   Unlimited local builds, 50 concurrent jobs
-   Full open-source core (Apache 2.0)
-   No credit card required

**Team ($25/month)**

-   For small teams (5-50 people)
-   Collaboration features, private projects
-   Cloud-hosted pipelines
-   Team seats and Slack notifications

**Pro ($99/month)**

-   For growing teams and enterprises
-   Unlimited resources, SSO, DLP
-   Self-hosted option
-   Priority support

## Why Free Stays Free

The Community tier is a permanent promise. The open-source core
will always be free because:

1. We believe in sustainable open-source
2. We want users to have choices (not locked in)
3. Free tier validates our product-market fit

We're monetizing through team collaboration and enterprise features,
not by taking away what made Sparki special.

## When Does This Launch?

-   Week of [DATE]: Soft launch (closed beta for 50 users)
-   Week of [DATE]: Open beta (pricing available, feedback welcome)
-   Week of [DATE]: General availability (full launch)

Early adopters get 20% off first year of Team tier.

## FAQ

**Q: Will my current pipelines continue to work?**
A: Yes. Existing users get 90 days free access to understand their tier.

**Q: Can I run Sparki locally for free?**
A: Yes. Community tier runs fully locally without Polar or any cloud dependency.

**Q: What if I can't afford Team tier?**
A: Community tier has everything you need to build CI/CD pipelines locally.

## Next Steps

1. Read the [monetization strategy](/sparki/link) for full details
2. Join our Discord for early access
3. Provide feedback during beta

We're excited to build a sustainable Sparki with you.

— The Sparki Team

4.2 Internal Kickoff Email (Template)

Subject: Sparki Monetization Launches [DATE]. Here's your role.

Team,

In 8 weeks, Sparki moves to a freemium model. Here's what's happening:

ENGINEERING (Backend team):
- Start Phase 1 (Polar setup, database schema)
- Read: SPARKI_POLAR_INTEGRATION_TECHNICAL.md § 2
- Sync every Monday 10am (standup format)

PRODUCT (Product + Engineering leads):
- Finalize tier definitions (quota levels, feature matrix)
- Read: SPARKI_MONETIZATION_COMPLETE_STRATEGY.md § 3
- Review during Phase 1, refine during Phase 2-3

MARKETING (Marketing + Communications):
- Start blog series on "CI/CD without YAML"
- Read: SPARKI_MONETIZATION_MARKETING_STRATEGY.md § 8
- First blog post due [DATE]

DEVOPS (Infrastructure):
- Set up Polar sandbox account
- Prepare monitoring infrastructure
- Read: SPARKI_POLAR_INTEGRATION_TECHNICAL.md § 6

COMMUNITY (Growth + Support):
- Prepare community communications
- Draft FAQ for GitHub Discussions
- Start gathering early adopter feedback
- Read: SPARKI_MONETIZATION_INDEX.md § 3

All-hands meeting: [DATE] at [TIME] to discuss strategy.

Questions? Slack #monetization.

— [CEO]

4.3 Community FAQ Post (Template)

# Community Q&A: Sparki's Monetization Model

We're excited to announce Sparki's sustainable business model.
Here are answers to the most common questions:

## Free Tier Questions

**Q: Will the free tier stay free?**
A: Yes. Community tier is a permanent promise.

**Q: What can I do with Community tier?**
A: Everything needed for local CI/CD: unlimited builds, 50
concurrent jobs, full CLI/TUI, framework autodetection.

## Paid Tier Questions

**Q: When do I need to upgrade to Team tier?**
A: When you hit limits (>5 team members, >20 private projects,
need Slack notifications). Most solo devs never need to upgrade.

**Q: Is there a free trial of Team tier?**
A: Yes. 7-day free trial for new users.

## Migration Questions

**Q: Can I migrate my GitHub Actions workflows?**
A: Yes. Our migration guide shows how to convert in 1 day.

**Q: Can I use Sparki with multiple git providers?**
A: Yes. Sparki integrates with GitHub, GitLab, Gitea, and webhooks.

## Business Questions

**Q: Who decided to monetize?**
A: Team consensus. We realized we couldn't afford to hire
more engineers on volunteer time.

**Q: Will this affect the open-source core?**
A: No. The core remains MIT/Apache licensed and community-driven.

**Q: Are you taking VC funding?**
A: No plans currently. We want to stay independent.

...

Full FAQ: [link]

5. Stakeholder Responsibilities

RolePhase 1 (Weeks 1-2)Phase 2 (Weeks 3-4)Phase 3 (Weeks 5-8)Phase 4-5 (Months 2-3)
CEO/LeadershipApprove strategyWeekly standupsBoard updatesGTM launch
Backend EngineersPolar setup, databaseAPI middlewareUsage trackingTesting/deployment
ProductFinalize tiersQuota enforcementMonitoring planBeta feedback
MarketingBlog strategyContent creationCampaign prepPublic launch
DevOpsInfrastructure setupMonitoring prepDashboardsProduction deploy
Community MgrFAQ draftingCommunity commsDiscord setupBeta user recruitment

6. Decision Log

DECISION 1: Polar.sh for payment processing
Status: ✅ APPROVED
Date: [DATE]
Rationale: API-first, webhook support, good documentation, pricing
transparency aligns with Sparki values
Alternatives considered: Stripe (more features but more complex),
Lemonsqueezy (good but less flexible)

DECISION 2: Three tiers (Community, Team, Pro) not four
Status: ✅ APPROVED
Date: [DATE]
Rationale: Simpler GTM, easier to market, most users fit three
clear segments
Alternatives: Four tiers (added "Startup" tier) but felt too complex

DECISION 3: Team tier pricing at $25/month
Status: ✅ APPROVED
Date: [DATE]
Rationale: Affordable for small teams, competitive with GitHub Actions
per-user ($30), targets 5-8% conversion
Alternatives: $15/mo (less revenue) or $50/mo (too expensive for SMB)

DECISION 4: Free tier includes framework autodetection
Status: ✅ APPROVED
Date: [DATE]
Rationale: Core product feature, not a "premium" feature, needed to
show value of Sparki
Alternatives: Put in Team tier (rejected—hurts adoption)

DECISION 5: Launch with closed beta (not direct public launch)
Status: ✅ APPROVED
Date: [DATE]
Rationale: Get feedback before public launch, build early adopter
community, validate pricing
Alternatives: Direct public launch (riskier, faster)

7. Success Metrics Dashboard

Month 1-2: Beta Phase

Target Metrics:
  ✓ 50 beta testers signed up
  ✓ 1,000+ email list subscribers
  ✓ NPS >50 from beta users
  ✓ 0 major bugs in beta
  ✓ 2 blog posts published

Success Criteria:
  ✓ 50%+ of beta users complete first build
  ✓ 0 critical issues reported
  ✓ Pricing feedback positive (no "too expensive" consensus)

Month 3: Launch Phase

Target Metrics:
  ✓ 5,000+ signups on launch week
  ✓ 50+ Team tier customers
  ✓ $5,000 MRR by end of month
  ✓ Product Hunt top 50 ranking
  ✓ 10,000+ blog visitors

Success Criteria:
  ✓ 2-3% signup-to-Team tier conversion
  ✓ <5% paid tier churn
  ✓ NPS >40 from all users

Month 6: Scale Phase

Target Metrics:
  ✓ 50,000+ total signups
  ✓ 500+ Team tier customers
  ✓ 100+ Pro tier customers
  ✓ $50,000 MRR
  ✓ 50,000+ blog visitors monthly
  ✓ 5,000+ Twitter followers

Success Criteria:
  ✓ CAC <$20 per Team customer
  ✓ LTV >$1,200 per customer
  ✓ 90%+ paid tier retention
  ✓ NPS >45

Month 12: Year 1 Review

Target Metrics:
  ✓ 100,000+ total signups
  ✓ 1,000+ Team tier customers
  ✓ 50+ Pro tier customers
  ✓ 10+ Enterprise tier customers
  ✓ $125,000+ MRR
  ✓ $1.5M+ ARR
  ✓ 30,000+ Twitter followers
  ✓ 500+ GitHub stars growth

Success Criteria:
  ✓ 2-5% overall paying rate
  ✓ 85%+ paid tier retention
  ✓ NPS >50
  ✓ Team can hire 2-3 full-time engineers
  ✓ Organic referral >40% of signups

8. Next Steps & Continuation Planning

Immediate (This Week)

  • All stakeholders read relevant docs (by role)
  • Team kickoff meeting (align on strategy)
  • Create Polar sandbox account
  • Assign phase leads for each section

Week 1

  • Phase 1 starts (Polar setup, database schema)
  • First blog post published
  • Discord server created
  • Beta user recruitment begins

Month 1

  • Phase 1-2 complete
  • API gateway middleware + tier enforcement working
  • 50 beta users recruited
  • 3 blog posts published

Month 2

  • Phase 3-4 complete
  • Polar integration tested in sandbox
  • Closed beta feedback incorporated
  • Open beta launch

Month 3

  • Phase 5 complete
  • Monitoring + Grafana working
  • Public launch (GA)
  • Full marketing campaign live

Month 6+

  • Analyze retention + churn
  • Optimize tier boundaries based on data
  • Enterprise sales machine
  • Roadmap for Year 2 features

9. Escalation & Support

Who to Ask Questions

Strategy Questions → [CEO/Head of Product]
Engineering Questions → [Tech Lead, Backend]
Marketing Questions → [Head of Marketing]
Community Questions → [Community Manager]
DevOps Questions → [DevOps Lead]
Polar Integration Help → [Backend Engineers]

Slack Channels

#monetization → General announcements
#monetization-strategy → Strategic discussions
#monetization-engineering → Implementation details
#monetization-marketing → Campaign planning
#monetization-community → Community communications

Meeting Schedule

Weekly Standup: Mondays 10am (30 min, all hands)
Strategy Sync: Wednesdays 2pm (60 min, leads only)
Marketing Sync: Thursdays 3pm (45 min, marketing only)
1:1 Check-ins: Bi-weekly with each lead

Internal Documents

  • SPARKI_MONETIZATION_COMPLETE_STRATEGY.md (strategy)
  • SPARKI_POLAR_INTEGRATION_TECHNICAL.md (architecture)
  • SPARKI_MONETIZATION_IMPLEMENTATION_GUIDE.md (roadmap)
  • SPARKI_MONETIZATION_MARKETING_STRATEGY.md (GTM)

External Resources

Reference Spreadsheets

  • Tier Feature Matrix: [GSheets link]
  • Revenue Projections: [GSheets link]
  • Marketing Calendar: [GSheets link]
  • KPI Dashboard: [GSheets link]

11. Appendix: Glossary

ARR (Annual Recurring Revenue): MRR × 12
CAC (Customer Acquisition Cost): Marketing spend / New customers
Churn Rate: % of customers who cancel monthly
Community Tier: Free tier (local-only, no cloud)
Hypertable: TimescaleDB optimized time-series table
LTV (Lifetime Value): Average revenue per customer lifetime
MRR (Monthly Recurring Revenue): Recurring revenue per month
NPS (Net Promoter Score): Customer satisfaction metric (0-100)
OAT (Organization Access Token): Polar API authentication
Polar: Payment platform for subscriptions
Tier: Pricing tier (Community, Team, Pro, Enterprise)
Usage Meter: Tracking API calls, builds, storage, etc.
Webhook: HTTP callback for event notifications

Conclusion & Accountability

This document is the single source of truth for Sparki’s monetization strategy. Every team member should:
  1. ✅ Read the role-based section
  2. ✅ Understand how their work contributes to revenue targets
  3. ✅ Align with the 12-month GTM timeline
  4. ✅ Hold each other accountable to success metrics
The goal is not to maximize revenue at the expense of our community. The goal is to be sustainable, transparent, and true to open-source values. We’re betting that a profitable, independent Sparki will build better products and serve our users better than a venture-funded fast-growth play. Let’s make it happen.
Questions? Start an issue in #monetization-strategy or ask in the next standup. Last Updated: [DATE] Next Review: [DATE + 30 days]