Octolens
280 posts

Octolens
@Octolens
Social listening for the agent era Trusted by Vercel, Lovable, PostHog, and 1000+ more
Katılım Şubat 2021
1.7K Takip Edilen1.1K Takipçiler

cool products i came across this week ⬇️
• @mintlify - making documentation feel like part of the product, not an afterthought.
• @flowdotclub - virtual coworking that makes deep work surprisingly social.
• Slashy AI (@GaddipatiHarsha) - an AI assistant that handles your inbox like you would.
• @Octolens - catches buying signals and brand mentions before your competitors do.
founders are shipping some ridiculously cool products.
what should i check out next?
English
Octolens retweetledi
Octolens retweetledi
Octolens retweetledi

A new era for @Octolens needs a new logo.
For over two years we'd been running with a little emoji icon we picked last minute on launch day from a free library.
It did the job. But I think we're loong overdue an original logo.
Here it is! ✨

English
Octolens retweetledi

Today we're launching a new era for @Octolens.
When we started Octolens, we set out to build a social listening dashboard. Today, our best customers barely open it.
Daily active users are down, but revenue is up 5x over the last year.
So we rebuilt Octolens as what it actually is: a data layer that plugs in wherever you work.
Today we cover the entire web + our MCP and API reads and writes.
In 2026, if an agent can't reach the data, it's not a data source.
This is social listening for the agent era.
English
Octolens retweetledi

Your best testimonials are on Reddit, X, HN, and LinkedIn. They just never reach your homepage.
So I built a workflow with our @Octolens MCP:
- pull all positive mentions
- score them against our positioning
- ship the best as a quotes.json
Once-a-year chore, now a few-mins refresh
English
Octolens retweetledi

Our entire company recently went on an offsite in Turkey. All two of us. 😉
And this time we got a huge amount done.
On this trip just some of the things we did:
– redesigned the entire @Octolens UX
– shipped our new API v2
– built our MCP v2
– rebuilt the onboarding flow
We decided something over coffee and it was live by lunch.
Then we closed the laptops and went for a hike or to the beach.
Another perk of being a small team: we decided to bring +1s. In my case, +2s. At 6 months old it felt like a lot to disappear for a whole week, so I just packed up Tobi and Vicky and brought them along. Igor brought his wife too.
Already looking forward to the next one! ☀️

English

@marshallmixing Thanks for the shoutout!
Octolens also covers X, LinkedIn, YouTube, newspaper, podcasts, newsletters, and many more sources :)
English
Octolens retweetledi

This is a very cool @attio app, built using our new workflows SDK.
You can now run automations on GTM process based on social mentions. Pretty awesome.
Octolens@Octolens
now live: Octolens app for @attio attio.com/apps/octolens
English
Octolens retweetledi

Everyone keeps telling me MCP is dead.
Meanwhile our MCP traffic just 7x’d in 5 weeks.
We shipped the Octolens API + MCP server earlier this year as a side bet.
The thesis: brand monitoring shouldn’t live in a dashboard, it should be a data layer your team (and your agents) can pull from.
Turns out a lot of people agree.
What’s unexpected for me is that API and MCP are growing together, not cannibalizing each other.
API is how devs build internal workflows and MCP is how AI agents consume data.
We’re going all-in on this.
Social data infrastructure for humans and agents → that’s the next chapter for Octolens.

English
Octolens retweetledi

octolens is one of the most underrated marketing products i've used in years
so simple and just works
not to say @LottiSchmitt somehow read my mind last year as i was thinking how shitty all of the social listening products out there were
her "want to try @Octolens again?" email couldn't have come at a better time

English
Octolens retweetledi
Octolens retweetledi
Octolens retweetledi

Redirecting complaints into a megathread can mean missed feedback and more frustrated customers.
I saw this mod post and thought: this isn't the best strategy.
From a moderation point of view, grouping complaints into one place is tidy.
But for other teams this strategy creates problems:
- important feedback gets easier to miss
- users can feel dismissed on top of being frustrated
If someone is unhappy about pricing, limits, or a product change, and the response they get is “post it somewhere else,” you may lose the original feedback point and you may now also have a user who feels ignored.
That is why product teams need their own visibility into what people are upset about, independent of how a subreddit is moderated.
Not every complaint needs a public response.
But missed feedback is expensive, and annoyed customers do not usually get quieter.

English
Octolens retweetledi





