WillItSurvive

Geekbot makes an async standup bot that runs inside Slack and Teams.

Little protection left
Assessed 22 July 2026 · Evidence as of 22 July 2026
Not much stands between this business and its pressures.
On the recordSince 22 July 2026 · Checkable from next 6-12 months · Every call on the record Checkpoint: Watch for Slack Workflow Builder or Teams Copilot to ship a native AI standup feature
The call

Geekbot survives on old habit inside Slack while the platforms it lives on build the same feature for free.

Geekbot is a small, self-funded company that makes a tool for work teams to run automated daily check-ins: it collects what people are working on, summarizes the responses, highlights problems, and tracks team mood. The problem is that Slack and Microsoft Teams are now building the same features directly into their platforms, and general AI language tools can do what Geekbot does without anyone needing a separate app. Geekbot's only real advantages are that teams already use it and that it's starting to connect to AI agents through a new technical layer, but those are thin shields. The one thing that could save Geekbot is if AI agents driven by tools like it become how teams actually work instead of just a novelty, but there is no sign of that yet.

Why
01
AI pressure: Slack AI and Microsoft Copilot in Teams. Native platform AI can already collect, summarize, and flag blockers, the exact job Geekbot charges for. Could AI do the core job? Yes, likely.
02
Bigger players: Slack (Salesforce) and Microsoft Teams. Both platforms are shipping workflow builders and AI summaries that make a standalone standup bot optional. Could a giant copy it? Yes, easily.
03
What protects it. Ten years of workflow habit and integration setup inside thousands of Slack workspaces that customers have not bothered to rip out.
What would change this call
Slack Workflow Builder or Teams Copilot ships a native AI standup/status feature. Platform absorption of Geekbot's core function, removing its reason to exist as paid add-on.
Geekbot headcount falls below 14 employees in future filings or profiles. Further contraction signaling shrinking revenue or runway pressure.
Geekbot is acquired by a productivity suite (Slack, Microsoft, Atlassian, etc.). Soft-landing exit at feature-level pricing rather than standalone growth.
Key numbers
  • 14 employees, down 17.6% year over year (2026-07)
  • Website visits ~83K/month, up 30.6% quarter over quarter (2026-07)
  • Headcount fell from 22 (2022) to 14 (2026) (2026-07)
Named risks
  • Slack and Microsoft Teams shipping native AI standup/workflow features could make Geekbot redundant as a paid add-on. Severity: high
  • Bootstrapped, unfunded status limits resources to compete against well-capitalized platform incumbents. Severity: medium
  • Category-wide price discounting of 15 to 30 percent (Vendr, n.d.) signals margin pressure among standup-bot vendors. Severity: medium
  • Most user, customer, and traction figures are vendor-claimed with no independent verification of revenue or retention. Severity: medium
Rivals, as read in July 2026
RivalDirectionEvidence
Slack (Salesforce)losing toSlack's native Workflow Builder and AI summarization threaten to absorb Geekbot's core standup use case, ongoing 2026
Microsoft Teamslosing toTeams Copilot AI features could natively replicate standup collection and summarization, ongoing 2026
RangecontestingRange markets itself as broader team-coordination alternative claiming higher engagement (vendor-claimed, 2025-12-27)
Polly, Standuply, TrooprcontestingVendr reports list-price discounting of 15 to 30 percent amid competitive negotiation dynamics (n.d.)
DailyBot, Status HerocontestingNamed as direct standup-bot peers in third-party comparison content, September 2023
Questions people ask
Is Geekbot profitable in 2026?
No revenue or profitability figures are publicly disclosed. Geekbot is a private, bootstrapped company; Pitchbook's company profile lists no funding rounds or investors, suggesting it has operated independently on its own revenue since founding in 2015.
Could AI replace Geekbot?
Geekbot's core function, collecting text updates, summarizing them, and flagging blockers, is exactly what Slack Workflow Builder and Microsoft Teams Copilot are natively adding. Geekbot itself launched Geekbot AI and Ask Geekbot features around February 2026 as a defensive response to this threat.
Who owns Geekbot?
Geekbot Ltd was founded in 2015 by CEO Nick Papanotas and remains privately held. No funding rounds, investors, or acquisition are recorded in Pitchbook's profile, indicating it is likely still founder-owned and bootstrapped as of 2026.
Who is Geekbot's biggest competitor?
Geekbot competes directly with Standuply, Polly, DailyBot, Status Hero, Troopr, and Range in the standup-bot niche (named as of September 2023), but its bigger structural threat is Slack (Salesforce) and Microsoft Teams shipping native AI workflow and summarization features.
Does Geekbot have AI features?
Yes. Geekbot enabled AI features including conversational 'Ask Geekbot' standup/poll creation and AI-driven sentiment and blocker categorization (Dependencies, Technical, Health, Personal, Time, Fatigue) in help documentation dated February 2026.
Is Geekbot venture-backed?
No. Pitchbook's company profile for Geekbot lists no funding, valuation, or investor data, consistent with the company's decade-long history as a bootstrapped, independently operated SaaS business founded in 2015.
Timeline
  • 2026-03-09Geekbot publishes updated tiered pricing (Starter/Standard/Enterprise) with usage-based billing
  • 2026-02-17Geekbot Insights help article details AI sentiment and blocker categorization features
  • 2026-02-09Geekbot publishes help article on enabling Geekbot AI features
  • 2025-12-02Geekbot security page cites ISO/IEC 27001:2022 certification and GDPR/CCPA/PCI compliance
  • 2025-11-11Geekbot's design process featured at Thessaloniki UX Meetup marking its 10th anniversary
  • 2024-01-11Geekbot blog claims 200,000+ users and marquee customers including GitHub, Shopify, Netflix
  • 2015Geekbot founded by Nick Papanotas
Revision history
22 July 2026
First assessed. Little protection left. The text above is fixed as of this date and is not edited afterwards.
In the same band
Sources