GREG ISENBERG engagement report
@gregisenberg - 701K followers on X
Measured over 30 original posts from a 30-day window, last computed on August 25, 2026.
Engagement
A typical post picks up 1.4K interactions against 701K followers, an engagement rate of 0.2%. Measured over 30 original posts, its engagement rate beats 81% of 3,774 tracked accounts of a similar size. Comparing inside a size band matters here: engagement rate falls as accounts grow, so a raw rate would mostly just re-measure the follower count. Posts are seen about 96K times each, and 1.44% of those impressions turn into an interaction. That is about 13.7% of the follower count, which is the gap between an audience on paper and an audience in a timeline. Posting runs at about 1.5 posts a day over the last 30 days, with activity on roughly 77% of days. Most posts go out around 12:00 UTC, and Sunday is the busiest day of the week. Of the 30 posts sampled, 43% carry an image or video, 13% are part of a thread and 33% link out. The account's strongest tracked post pulled 10K interactions, about 7.4x its own typical post.
Measured over 30 original posts from a 30-day window, last computed on August 25, 2026.
Compared with accounts its own size
GREG ISENBERG's engagement rate beats 81% of the tracked X accounts closest to it in follower count (3,774 accounts, accounts of similar size (decile 8 of 10)). A percentile is spread evenly by construction, so 50 really is the middle of that group and 90 really is its top tenth.
On engagement per impression rather than per follower it beats 62% of the same group. When those two numbers disagree, the gap is about how far its posts travel rather than how people react to them.
Where this sits in the catalog
At 0.2%, GREG ISENBERG sits above the 50th percentile of the 36,521 accounts in this comparison. That places it in the above the median band, which runs 0.08% to 0.434%.
Show the percentile table
| Percentile | Engagement rate |
|---|---|
| 10th percentile | 0.002% |
| 25th percentile | 0.012% |
| 50th percentile | 0.08% |
| 75th percentile | 0.434% |
| 90th percentile | 2.10% |
| 99th percentile | 160.7% |
This ruler is the whole measured catalog, not a size-matched group: it shows where the raw rate falls across every account we can measure, all of which are large. For a like-for-like comparison, read the size-band percentile above instead. See how the bands are built
Posting timing
This account posts most often around 12:00 UTC, and Sunday is its busiest day of the week. The bars below are the catalog-wide pattern, with this account's own busiest slot marked. They do not show how this account performs at each hour: we keep one aggregate per account, not one per hour, so that measurement does not exist in our data.
Show engagement by hour posted, utc as a table
| Hour (UTC) | Vs author median | Posts |
|---|---|---|
| 00:00 UTC | -1% | 50K |
| 01:00 UTC | -2% | 51K |
| 02:00 UTC | -3% | 50K |
| 03:00 UTC | -4% | 53K |
| 04:00 UTC | -6% | 43K |
| 05:00 UTC | -4% | 42K |
| 06:00 UTC | -4% | 48K |
| 07:00 UTC | -5% | 52K |
| 08:00 UTC | -4% | 60K |
| 09:00 UTC | -3% | 69K |
| 10:00 UTC | -2% | 72K |
| 11:00 UTC | -3% | 78K |
| 12:00 UTC | -2% | 86K |
| 13:00 UTC | -2% | 94K |
| 14:00 UTC | -4% | 97K |
| 15:00 UTC | -2% | 100K |
| 16:00 UTC | -3% | 97K |
| 17:00 UTC | -2% | 90K |
| 18:00 UTC | -1% | 84K |
| 19:00 UTC | -2% | 79K |
| 20:00 UTC | -1% | 74K |
| 21:00 UTC | -1% | 66K |
| 22:00 UTC | -2% | 57K |
| 23:00 UTC | -2% | 51K |
Show engagement by day of week as a table
| Day | Vs author median | Posts |
|---|---|---|
| Sunday | +4% | 230K |
| Monday | 0% | 286K |
| Tuesday | -2% | 276K |
| Wednesday | -1% | 251K |
| Thursday | -1% | 244K |
| Friday | -3% | 252K |
| Saturday | +3% | 227K |
Best tweets
- Jul 31, 20267.4x their median
The biggest opportunities right now: 1. build for solving loneliness (the more AI floods everything, the more people crave real human connection, IRL and small social) 2. build for agents that need to spend money (they're getting virtual cards and budgets, someone builds the spend controls, fraud protection, receipts) 3. build for people drowning in AI output (everyone generates infinite drafts now, the bottleneck moved to reviewing and choosing, build the judgment layer) 4. build for the burnout economy (everyone is expected to always be on and always optimizing, and the backlash toward rest, slowness, and enough is building) 5. build for verifying humans (deepfakes broke trust, every dating app, marketplace, and video call needs proof-of-human within 2 years) 6. build for the physical world (the trades, hardware, robots that AI is finally reaching) 7. build for the agent that answers the phone (every local business misses calls after 5pm, a voice agent that books the job is worth thousands a month) 8. build for the aging (70M+ boomers who want to stay healthy, sharp, and connected) 9. build for the LLM-search land grab (being the cited answer is the new SEO) 10. build for the newly automated (the paralegal, the analyst, the marketer whose job just changed and needs to reskill fast) 11. build for the seat-pricing collapse (software repricing from $50/seat to per-outcome, whoever nails outcome billing wins a category) 12. build for AI enablement (95% of businesses use nothing beyond ChatGPT, someone has to onboard the other 95%) 13. build for the agency everyone resents (businesses pay $1k/mo to agencies they hate, an agent that does 80% of it undercuts the model) 14. build for verticals on 2011 software (dentists, HOAs, contractors, all overdue for an AI-native rebuild) 15. build for reviving dead software (thousands of abandoned apps with real users, agents can maintain what a team couldn't, buy and revive) 16. build for markets too small to matter before (500 lobster fishermen was never worth a team, now it's a weekend and a real business) 17. build for agents hiring agents (a shadow economy is forming, it needs escrow, reputation, and dispute resolution for machines) 18. build for the anti-AI premium (as everything gets generated, human-made and analog become status symbols people pay up for) 19. build for distribution-first (anyone can build the product now, so the audience is the moat, media company first, product second) 20. build for the reinvention of college (what does an MBA even mean anymore) 21. build for a world with more free time than it knows what to do with (if AI takes the busywork, the question becomes what people do with the hours, and that's a civilization sized market) note: more trends/ideas @ideabrowser (free to sign up) 22. build for the return to the physical (screens fill with slop, people crave the real world, the hands-on, the local, the analog) 23. build for the caregiving wave. The population is aging fast, tens of millions are caring for parents, and the whole burden is landing on families with no support. 24. build for the longevity shift (people want to live to 100 healthy, and a whole industry is forming around actively managing your own biology) 25. build for the housing and rootlessness problem (people can't afford to settle down, and the whole idea of a stable home base is up for grabs) 26. build for spiritual hunger (as institutions hollow out, the need for meaning, ritual, and belonging is exploding into new forms) KEEP BUILDING
- Jul 29, 20266.2x their median
Stripe had around 50 users after its first 2 years. Imagine quitting because of that.
- Oct 13, 20244.9x their median
my entire content strategy is this give you free startup ideas + growth playbooks that work i won't hold back and every time you build something from my tweets/pod I'm sippin' a martini & cheering you on your success is my ultimate flex now go ship something & make me proud https://t.co/4mXJR800Hx
- Aug 13, 20263.2x their median
i agree https://t.co/NJHpA9zjce
- Aug 2, 20262.9x their median
Every startup should have a daily markdown file called "what_the_market_is_telling_us.md" It updates every morning from the places where customer truth already lives: 1. Stripe for who pays, upgrades, downgrades, and churns 2. PostHog for what people actually do in the product 3. Intercom or Plain for support tickets/complaints 4. Granola or Gmeet transcriptions for sales calls/ customer interviews 5. HubSpot or Salesforce for CRM notes/lost deal reasons 6. Linear, Jira, or GitHub Issues for bugs and feature requests etc 7. Ideabrowser MCP for outside market signal: startup ideas, trend reports, social/search demand, AI research reports, and builder prompts that show what people are starting to want before it shows up in your own customer data. Basically, the file should notice what changed in the business this week and not just be this summary of here’s what happened (which I think a lot of people have their agents do). Why this is valuable: 1. Maybe new buyers are using different words than they were a month ago. 2. Maybe trial users are getting stuck in the same place. 3. Maybe upgraded customers all touched one feature right before they paid. 4. Maybe churned customers keep mentioning setup confusion. 5. Maybe sales calls are suddenly losing to a competitor you used to beat. 6. Maybe support tickets are revealing a workflow your product accidentally became responsible for. You get the point. The fastest way to PMF is understanding customers better than anyone else, and the highest signal customer insight is usually a change in behavior. So I’d have the agent update the file every morning with the pattern it found, the receipts behind it, and the product or GTM decision it might affect. For example: “3 customers who churned this week all mentioned setup confusion, and 2 of them never invited a teammate. This looks more like an activation problem than a pricing problem, so I’d look at team invite and onboarding before building another analytics feature.” A little helpful tip for all those out there looking to get more from their LLMs.
- Aug 21, 20262.5x their median
Grok Bot might be the first tool that lets one non-technical person run an entire business with a team of AI agents. My friend Billy runs his whole newsletter business on Grok Bot agents, and I think we're about to see 100,000+ businesses like his. BEST PRACTICES: 1. The agents run on a shared cloud computer, so running your newsletter, your X, and your receipts all in one place creates context bloat and burns tokens fast. One mission per setup. 2. Start with a Chief of Staff. Give it access to your existing docs (Notion, Slack, Gmail), have it audit the business, then tell you the top three agents to build first to drive revenue. 3. Perfect a task with the Chief of Staff before spinning up a new agent. Have it do the outbound sales once, review it, and only then say "now build a bot that does exactly that." You earn each new hire by proving the task works first. 4. Constraints are the feature. You get a limited number of agents, one thread per bot, like DMs with a teammate. It forces you to stay mission-oriented instead of spinning up a bot for every random idea. 5. You make the decisions, not the agent. Billy's team spent three weeks unable to pick where content should live. At some point you say "we're doing Notion, no more tinkering" and move on. 6. Run week one with no new agents. Build the team, learn to fly the plane, just execute. Week three is when you find the real gaps and expand, someone to man the inbox, someone for the Shopify shop. 7. Then add routines so it works while you sleep. Ask your Chief of Staff what recurring jobs would move the business forward overnight, and it builds the automations that run without you. Thanks to @billyjhowell for sharing the sauce on @startupideaspod (follow for more). Grokbot is really cool. Watch below: https://t.co/9jTXeOiu9x
- Jul 23, 20262.1x their median
16 things that will be normal in 3 years and sound insane today 1. Somebody's entire job is making sure your agents don't do dumb things. 2. Kids grow up assuming any adult who types is old, the way we assume anyone who prints emails is old. 3. You get an itemized bill for what your agents bought last month and it reads like an expense report from a small company. 4. Someone you've never met sells you a business that runs itself, and you never learn what the code does. 5. Your doctor's first opinion comes from a model, and the human's job is deciding whether to trust it. 6. Job posts will say "must be able to manage agents" the same way they used to say "proficient in Excel." 7. The best-paid person at a company will be whoever's best at explaining the business to machines. 8. Your company has more agents than employees, and HR manages both. 9. Companies start hiding how few employees they have, because a lean team reads as fragile to enterprise buyers. 10. Your calendar fills with meetings you didn't schedule, because your agent and their agent worked it out. 11. The CV dies and gets replaced by a body of work an agent can verify in 4 seconds. 12. You interview an agent before you hire it. Give it a fake task, watch how it handles the weird cases, then decide. 13. Losing your job means losing your agents too, and it's kinda scary losing your best agents. 14. "Made by a person" becomes a label on products, and there's a certification body for it. 15. You'll have a folder of agents the way you have a folder of apps 16. Getting a human on the phone becomes a paid tier, and people gladly pay it.
- Jul 28, 20261.7x their median
EVERYTHING you NEED to know about Jack Dorsey's AI agent "Slack killer" Buzz (set up, use-cases etc in 38 mins) What we get into: 1. What Buzz actually is and should founders switch from Slack? 2. How to swap the model under any agent and keep all your context? 3. How to talk to your agents live with audio huddles? 4. How to get agents to build and deploy real apps for you, like a full CRM from one ask? 5. How to set up the context loop that feeds your live app data back to your agents? 6. How to share compute so a few people split one machine running a local model? 7. Who it's actually for right now, and what's still rough? Full breakdown on the pod @startupideaspod. Thanks to @hot_town for jumping on and clearly explaining @jack and team's latest product. My TLDR take is Buzz is a glimpse into the future of work. Some of you will roll your eyes at that, and I get it, it's alpha software and it's slow in places. But the core idea, that your context is the foundation and agents build out from there, is right, and that's worth seeing early. Watch https://t.co/RVU6TuEJ7k Curious what you think
- Aug 9, 2026
23 ways I'd use AI agents to grow my startup to $1M ARR or PMF (my running list): 1. An agent read your Stripe refunds/cancellation reasons, then trigger a different CustomerIO sequence for each, so the person who left over price gets a discount and the person who left over a bug gets a "we fixed it" email. 2. Wire an agent to your PostHog feature flags and have it race two onboarding flows on live signups, auto killing whichever activates fewer people each week. An A/B test that prunes itself!! 3. Watch your competitor's status page, and the hour they go down, spin up Google Ads targeting "[competitor] alternative" while their users are actively searching. (kind of ruthless, kind of brilliant) 4. Feed an agent your closed-lost deals, have it draft a personalized reopen email for each, and drop them in your outbox for 1 click send. 5. Turn your best customer's onboarding into a playbook.md, then run every new signup down that exact path so your best outcome becomes the default. 6. Point an agent at your inbox for positive-sentiment messages and auto-send a Senja review request while the customer is still glowing. And then your G2 page fills itself. 7. Watch for the moment you solve someone's support problem and fire the referral ask right then, while they're relieved and grateful. Timing is everything on referrals. 8. An agent watch your Stripe data for annual customers who never log in, and reach out to re-onboard them, because realistically silent renewers are one bad quarter from canceling so get ahead of it. 9. Catch pricing page bouncers via a PostHog webhook, enrich them with Apollo, and send the objection-handler for their specific industry before they forget you exist. 10. Build an agent that continuously scans for new "best X" and "X vs Y" articles ranking in your category, and auto-drafts a personalized pitch to each writer asking to be added as an option. 11. Use Apify to scrape everyone who liked your competitor's launch post, waterfall their emails through Apollo, and draft a warm cold email to each. 12. Build an agent that runs your buyers' top 50 questions through ChatGPT, Claude, and Perplexity every week, logs which competitors get named and which sources get cited, and Slacks you the moment a competitor starts showing up in an answer where you don't. 13. Turn your single best-performing post into a landing page, a Meta ad, and a cold email in your voice using a saved style.md, because you already found the message that lands and you're only using it once. 14. Load your founder context into the Ideabrowser MCP once, and every skill your agent runs after that already knows your niche, your customer, and your offer, so nothing starts from scratch. 15. Wire the ideabrowser MCP into your growth agent so every winning headline and pricing test stores back into your project, and each experiment makes the next one smarter. 16. Firecrawl your competitor's docs weekly and have an agent flag every feature they quietly shipped, so you never get blindsided. 17. Watch the changelogs of the platforms you integrate with, so the day Stripe or Shopify ships a new API, you're the first tool built on it and you own that search traffic for months. 18. When a deal stalls for 14 days, have an agent auto-draft the "should I close your file?" breakup email, because that one closes more dead deals than any "just following up" email lol. 19. Have an agent turn every shipped Linear ticket into the public changelog entry automatically, so your changelog stays current without anyone remembering to update it. 20. Build a Clay enrichment waterfall that scores every inbound lead 1-10 before it hits your inbox, so you only ever open the 8s, 9s, and 10s. 21. Wire an agent to your Resend or Loops data to find the subscribers who open every email but never click, then quietly move them into a harder-CTA sequence, because engaged non-buyers need a different nudge than cold ones. 22. Have an agent read your Stripe metadata to find the customers who upgraded fastest after signup, then trace what all of them did in their first hour, because that's your activation "aha" and you can redesign onboarding to force it. 23. Have an agent watch for the moment a customer's usage doubles month over month, and route them to a human for a "you're growing, let's talk enterprise" call. These are just a few ideas. Ill keep sharing more here and @startupideaspod if people are into it. Really into marketing agents right now. These are just some ideas to get your creative juices flowing. You take a growth task a human used to do, wire an agent into the data and tools that task needs, and let it run on a loop. Do that across your business and the agents start making your product better, finding you customers, and pulling you toward PMF or scaling your company if you already have PMF. Now, go point some agents at your business. I'm rooting for you.
- Aug 23, 2026
AX is the new UX. Software was built for humans clicking, now it gets rebuilt for agents. Stripe just paid $8B for OpenRouter betting the main user of the internet is an agent. Rebuilding all that software is 1000+ new companies. The most obvious opportunity in a long time!
Ranked by total interactions across everything we have tracked for this account, which is a longer history than the 30-day window the rates above use. The multiple compares each post to this account's own median.
Buy or sell X accounts - escrow-protected
PlayerSells is an escrow marketplace for X accounts. Every deal is protected, with no middleman risk.
Reading these numbers
A typical post picks up 1.4K interactions against 701K followers, an engagement rate of 0.2%. Measured over 30 original posts, its engagement rate beats 81% of 3,774 tracked accounts of a similar size. Comparing inside a size band matters here: engagement rate falls as accounts grow, so a raw rate would mostly just re-measure the follower count. Posts are seen about 96K times each, and 1.44% of those impressions turn into an interaction. That is about 13.7% of the follower count, which is the gap between an audience on paper and an audience in a timeline. Posting runs at about 1.5 posts a day over the last 30 days, with activity on roughly 77% of days. Most posts go out around 12:00 UTC, and Sunday is the busiest day of the week. Of the 30 posts sampled, 43% carry an image or video, 13% are part of a thread and 33% link out. The account's strongest tracked post pulled 10K interactions, about 7.4x its own typical post.
- What is GREG ISENBERG's engagement rate on X?
- GREG ISENBERG (@gregisenberg) has an engagement rate of 0.2%, based on the median interactions across 30 original posts from the last 30 days against 701,145 followers. Replies, reposts and quote-posts of other people are excluded from that sample.
- Is that a good engagement rate?
- At 0.2%, GREG ISENBERG sits above the 50th percentile of the 36,521 accounts in this comparison. Those comparison accounts are all large ones, because our scanning cadence is weighted towards big accounts, so this is a ranking among peers of similar scale rather than a ranking across X.
- Does @gregisenberg have real engagement?
- Its engagement rate beats 81% of the tracked X accounts closest to it in follower count (3,774 accounts), which puts it in the top quarter for its size group. Ranking inside a size band matters because engagement rate falls as accounts grow, so a raw rate would mostly re-measure the follower count. It is a starting point for a look at follower quality, not a verdict on it.
- When does @gregisenberg post?
- Most posts go out around 12:00 UTC, and Sunday is its busiest day, at roughly 1.47 posts per day across the measured window.