Competitive analysis
What Hootsuite offers, what we already cover, and what we are deliberately not building.
docs/COMPETITIVE.md
What Hootsuite offers, what we already have planned, and what is genuinely missing.
The bar for adding something is not "Hootsuite has it". It is: does a Verjson marketing lead or a hired agency contractor need it to do their job? We are building an internal tool for one organization, not a product for sale — so several of Hootsuite's headline features exist to serve a customer we do not have.
Already covered
Most of the overlap was already in scope, because brightbean-studio was itself a
Hootsuite-shaped platform and PORTING.md carried its design across.
| Hootsuite | Ours | Status |
|---|---|---|
| Publishing & scheduling | F-030 composer · F-036 scheduling · F-037 publisher | 🔲 planned |
| Unified social inbox | F-046 | 🔲 planned |
| Analytics & reporting | F-060 · F-061 · F-062 · F-063 | 🔲 planned |
| Approval workflows | F-035 · F-074 | ✅ done — and stricter: agents pass the same gate |
| AI caption generation | F-031 | 🔲 planned |
| Media library / templates | F-033 | 🔲 planned |
| Link management + UTM | F-038 | 🔲 planned |
| Industry benchmarks (ads) | F-052 | 🔲 planned |
| Integrations (Slack, CRM…) | F-012 notifications · F-092 Apollo | 🔲 planned |
Worth adding
Ranked by what it would actually change for us.
| # | Feature | Why it earns a place | Effort |
|---|---|---|---|
| F-101 | Best time to post | Derived from our own engagement data — no vendor, no recurring cost, and it directly improves every scheduled post. The cheapest real win on this list. | Small |
| F-102 | Bulk scheduling | A quarter's calendar arrives as a spreadsheet, not as forty individual forms. Without it the composer is unusable for the planning work the brief actually describes. | Small |
| F-103 | Saved replies & templates | The inbox is unusable at volume without them. Pairs with F-046. | Small |
| F-104 | Social listening | Brand mentions, sentiment and emerging trends. The highest-value item here and the most expensive — it is a data-vendor problem, not a build problem. Scope it to our own brand and a named competitor set rather than "millions of conversations". | Large |
| F-105 | Competitor tracking | Their posting frequency, engagement and follower growth. Answers "are we behind?", which no amount of our own analytics can. Partly served by OpenSEO for search; social needs its own source. | Medium |
| F-106 | Employee advocacy | Verjson has staff and hired agency people. Letting them reshare approved content multiplies reach at zero media cost — and it fits our approval gate exactly, since the content is already approved. | Medium |
| F-107 | Sentiment reporting | Sentiment already lands per message via the inbox; aggregating it over time turns "people are annoyed" into something with a trend line. Cheap once F-046 exists. | Small |
| F-108 | Scheduled report delivery | A report nobody opens is not a report. Email it weekly or it does not get read. Part of F-063 rather than separate work. | Small |
| F-109 | Review management | Google Business, Trustpilot, app stores. Genuinely useful, but only if Verjson has review surfaces worth watching — a real question, not an assumption. | Medium |
Deliberately not building
Saying no is most of the value of an exercise like this.
| Hootsuite feature | Why not |
|---|---|
| Chatbots / automated DMs | Automating replies to real people, in an org this size, trades a small time saving for the risk of an automated message that reads badly in public. If inbox volume ever justifies it, revisit — it does not today. |
| Skill-based inbox routing | A routing engine needs a team large enough to have skills to route between. A shared inbox and an assignee field cover it until then. |
| 30+ networks, 300+ review sites | Breadth is a selling point for a product with thousands of customers. We need the handful of channels Verjson actually uses; every extra adapter is maintenance against an API that changes without warning. |
| White-label / agency multi-client | We are the client. Already dropped in PORTING.md. |
| Canva / Adobe Express embeds | A partnership integration that earns Hootsuite a distribution deal. We can upload a file. |
| Employee advocacy leaderboards, gamification | The mechanism (F-106) is useful. The scoreboard is a product feature for selling advocacy to enterprises, not something an internal team needs. |
What we have that Hootsuite does not
Worth recording, because it is the reason we are building rather than buying.
| Paid and organic in one place | Hootsuite bolts on ads management; the budget, the spend and the organic calendar are not one model. Ours are — a project has a marketing mix, and paid search sits next to organic social under one budget roll-up. |
| An approval gate that covers AI | Theirs approves human posts. Ours has no path from running to applied for an agent either — the same gate, tested as a negative property (D-022). |
| Agency contractors as a first-class role | Project membership is the scope (D-009). Hootsuite's equivalent is team permissions inside one account. |
| SEO and AEO alongside social | F-093 · F-094. Hootsuite is social-only; a marketing lead's job is not. |
| Self-hosted, no per-seat cost | The reason the "should we just buy Hootsuite?" question has an answer. |
The honest summary
Hootsuite is a good product for a social team at a company that sells to consumers at scale. Most of what makes it expensive — breadth of networks, listening at internet scale, enterprise advocacy — is priced for a customer we are not.
The nine features above are worth having. Four of them (F-101, F-102, F-103, F-107) are small, use data we already hold, and should be built alongside the features they attach to rather than as a separate push. F-104 listening is the only genuinely large one, and it should be scoped to our brand and a named competitor set before anyone starts.