Glean Actions vs Rowboat

“Glean already owns the search index in enterprises where it's deployed, so Actions isn't a cold-start problem — it's an upsell on top of data access they already have. The direct competitors are ServiceNow's AI layer, Microsoft Copilot for M365, and frankly just Slack + a well-configured Workato flow. Where this breaks: any company whose HR and IT data isn't cleanly indexed in Glean already, which is most companies in year one of a Glean deployment. My 12-month prediction: this either becomes table stakes for Glean's renewal motion or it gets cannibalized when Microsoft ships the same workflow triggers natively in Copilot Studio — Glean's bet is that enterprise search context beats platform incumbency, and that's a real but narrow window.”

“The 'knowledge graph from email' promise is where these tools historically fall apart — noisy inboxes produce noisy graphs. And 'local-first' often means 'labor-intensive setup.' The abstraction is right but execution on messy real-world data is hard. Watch the 1-month reviews.”

“The buyer is the CIO or CHRO who already wrote a Glean check — this is pure expansion revenue with essentially zero new sales motion required, which is a beautiful thing. The moat is the existing index: once Glean has crawled your Workday, ServiceNow, and Confluence, the switching cost to rip it out and replace it with Copilot is genuinely painful. The risk is that this is an enterprise feature expansion masquerading as a product launch — if it's gated behind an additional SKU with a separate SOW negotiation, adoption will be slow enough that competitors close the gap before Glean gets the case studies.”

“The primitive here is: natural language → workflow action dispatch, using Glean's existing knowledge graph as the intent resolver. That's a defensible idea. But the entire blog post is marketing copy with a screenshot at the bottom — there's no API surface documented, no SDK, no mention of how custom actions are defined or what the action schema looks like. If I'm an IT engineer at a 5,000-person company who wants to add a custom action for our in-house provisioning tool, I have no idea how to do that from anything published. The DX bet is entirely opaque, and a tool that lives inside enterprise deals with no developer-facing documentation is a platform I have to adopt wholesale on someone else's timeline — exactly what I'm tired of.”

“Plain-text persistence + MCP + local model support is the right architecture. It'll survive AI winters and API deprecations. The Obsidian compatibility alone is a killer feature for the PKM crowd that already lives in that ecosystem.”

“The job-to-be-done is clear and singular: let an employee resolve an HR or IT need without opening a new tab or filing a ticket manually. That's a real, high-frequency frustration in any company over 500 people, and Glean is solving it at the right layer — the search interface where employees already go to find answers. The completeness question is the real test: this only works if your company's Glean deployment is mature, your HR and IT data is actually indexed and current, and your IT team has configured the action integrations. For a new Glean customer, this is a 6-month-away feature, not a day-one capability — which means it's a retention play, not an acquisition hook. Still a ship because the job is real and the placement is right.”

“Personal knowledge infrastructure that you own is becoming the moat in AI-augmented work. Rowboat's transparent, portable approach builds durable value. In two years the question won't be which AI assistant you use, but which knowledge graph underlies it.”

“Drafting meeting briefs and decks from accumulated context is the workflow I've wanted for years. The Obsidian integration means my notes and my AI context stay in sync naturally — no separate import/export dance.”