Skip to content

feat: added comparison #1

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
vinamrasareen wants to merge 1 commit into
base: docs/ghl-cli
Choose a base branch
from
Open

feat: added comparison #1

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
18 changes: 18 additions & 0 deletions docs/ghl-cli-PRD.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -55,6 +55,24 @@ All three wrap the same API. They are layers for different users, not competitor

> Net: SDK = build apps. MCP = easiest agent plug-in. CLI = leanest execution for scripts, CI, and agent-via-skill workflows. The CLI is a **good-to-have** that closes a real gap the other two don't — provided demand clears the Phase 0 gate.

## 3B. Competitors already ship a CLI (and it gets real usage)

Every major CRM/dev platform GHL competes with offers an official CLI, and the download numbers show it's used at scale — this is table stakes for a developer-friendly platform, not a novelty.

| Platform | Official CLI (npm package) | Downloads/month | Downloads/year |
| ------------------------------- | -------------------------- | --------------- | -------------- |
| **Salesforce** | `@salesforce/cli` | ~1.38M | ~14.0M |
| **HubSpot** | `@hubspot/cli` | ~96.7K | ~841K |
| **GHL (community, unofficial)** | `gohighlevel-cli` | ~62 | — |

**What this tells us:**

- **It's an expected developer surface.** Salesforce and HubSpot both invest in and maintain official CLIs; GHL is the outlier with only an unofficial one.
- **The usage gap is the opportunity, not proof of no demand.** HubSpot's ~97K/month vs. the community GHL repo's ~62/month reflects _official support + distribution_, not lack of interest — the community tool has no marketing, no releases, and one maintainer.
- **Competitive parity + agent timing.** Shipping an official, SDK-backed CLI closes a visible gap with Salesforce/HubSpot and lands exactly as agent-driven (CLI + skill) workflows take off — a window the incumbents' older CLIs weren't designed for.

> Caveat: HubSpot/Salesforce CLIs are heavily used for _CMS/code deployment_ workflows, which inflates their numbers vs. a pure CRM-ops CLI. Treat these as ceiling/benchmark signals, not a direct forecast — the Phase 0 demand gate still applies.

## 4. Monetary benefit (to customers and to GHL)

**To the customer community**
Expand Down