June was the second full month of the account and the story clarified. Founder and company narratives (the enterprise-GTM turn, the on-premise origin story, the Shoptalk deal, the Beer and Brainstorm ritual) made up four of six posts and drove 73% of the month's reach. The engagement quality is strong for the base: likes ran 20 to 51 per post on a following of ~1,900. Two things held the month back. Volume was light at six posts with a two-week gap in the middle (June 10 to June 24), and follower growth slowed to +50 (+2.7%) from May's +87. The content is working; the calendar is not yet full. The one bright new signal: the account earned its first-ever save this month, on the Access Token API launch.
+50 net followers from 1,857 to 1,907. The steepest step came June 10 to 11, right after the "selling to enterprises" post, then the curve flattened during the mid-month posting gap.
A tight spread this month. All six posts landed between 790 and 1,650 impressions, with the enterprise-GTM story on top.
Each list ranks by a different signal: impressions for reach, reactions for resonance, and engagement rate for how hard a post worked relative to its reach. Saves were still near zero this month (one total), so the middle column shows reactions, with saves tracked as the account matures.
Who got seen the most.
Saves were near zero, so this shows total reactions (likes).
How hard each post worked for the reach it got.
Image dominated the calendar with four of six posts. One video (the Access Token launch) and one long-form text essay rounded it out.
Image posts averaged about 1,330 impressions, ahead of the text essay (1,054) and the video (932). The founder image stories carried the format.
We read each of the 6 posts and classified them by the job the post was doing, adapted to Hotglue's audience of technical founders, engineering leaders, and GTM teams evaluating embedded integrations. Three patterns appeared. With one to four posts per pattern the read is directional, but the ordering is clear: founder and company stories out-reach and out-engage everything else.
Founder and company BTS led reach, followed closely by the market-thesis essay and the product launch.
Engagements (likes, comments, shares, saves, sends). Founder content concentrated 72% of all interaction this month.
Three content patterns observed across 6 published posts.
| Pattern | Posts | Total imp. | Avg imp./post | Total eng. | Top performer |
|---|---|---|---|---|---|
| Founder / company BTS | 4 | 5,320 | 1,330 | 136 | Selling to enterprises (1.7K imp) |
| Industry take / thought leadership | 1 | 1,054 | 1,054 | 24 | Why customers don't build in-house (1.1K imp) |
| Product/company updates | 1 | 932 | 932 | 28 | Access Token API (932 imp, 1 save) |
Four founder-and-company posts drove 5,320 impressions (73% of the month) and 136 of 188 total engagements (72%). The winners share a pattern: a specific, named, first-person story with real stakes (the enterprise-GTM realization with Chargebee and SpotOn, the 2am on-premise QuickBooks build, the Shoptalk deal that came back to life). This is the account's most reliable pattern for both reach and interaction, and it should stay the backbone of the calendar.
"Why customers don't build integrations in-house" ran as plain text and still reached 1,054, essentially matching the image posts. It answers a real buyer objection with a clear thesis. This is exactly the kind of reference content that should be earning saves once it is structured as a named framework or numbered list rather than prose.
The Access Token API launch pulled 932 impressions, 2 shares, and the account's first-ever save. For an embedded iPaaS, concrete shipping news (a new endpoint, a new connector, a new target) is credible, technical proof of momentum and it travels with a developer audience. One product post a week would compound.
The first sentence decides reach on LinkedIn. The good news is that Hassan's hooks are consistently strong. Across the month's top performers the same five ingredients show up, and the biggest posts simply stacked more of them. We analyzed the opening lines of the highest-reach and highest-reaction posts.
"For years, we sold Hotglue only to startups", "5 years down the line", "one of maybe 2 or 3 providers", "6 weeks later", "close to 5 years". Nearly every top post drops a hard number before the argument starts, which sets scale and credibility instantly.
Chargebee, SpotOn, Shoptalk, QuickBooks Desktop, Pinterest, HubSpot, Intuit QuickBooks. Real names carry proof. The enterprise post used acquirer names as social proof and led the month on both reach and reactions.
"they weren't even our ideal buyers", "an integration I had no idea how to build", "told me Hotglue wasn't a fit... last week he texted saying he couldn't wait to work with us", "their contract has grown steadily year after year". Each hook sets up a surprise that makes the reader want the resolution.
"Here's how the deal moved", "Here's the backstory", "I think I have an answer", "Here's what happened". The openings tell the reader an explainer is coming, which earns the dwell time the algorithm rewards in the first 90 minutes.
"I once told a prospect", "many investors asked me early Hotglue", "my initial instinct was to write the opportunity off". The credibility comes from Hassan having built Hotglue and lived these decisions. The hooks make that vantage explicit, which is exactly why founder content outperforms.
The content quality stayed high, so the opportunities are about reach mechanics and structure, not writing. Two posts and one calendar pattern stand out.
This is a well-told GTM narrative (a Shoptalk prospect who said no and later came back) and it actually earned the month's best engagement rate at 3.7%, so the audience that saw it responded. The issue was reach: at 794 it landed last of the six. Two likely reasons. It was the third post in a three-day cluster (June 24 to 26), so it competed with the Brainstorm and Access Token posts for the same small audience. And the narrative leans inward (crediting the GTM lead by name) rather than opening on the reader's own problem, so it had a narrower hook than the enterprise or on-premise stories. Spacing it out and leading with the buyer's dilemma would likely lift the reach to match its engagement quality.
The culture post pulled the second-highest reach of the month but the lowest engagement rate at 1.4%. It opens well (Pinterest's ritual as a hook) but the payoff is a general "does your team do this too?" rather than a specific, high-stakes founder moment. It traveled on the network's goodwill but gave the audience less to engage with than the enterprise or on-premise stories. Culture content works best when it ties to a concrete product or decision outcome, which this post gestured at (roadmap features from the sessions) but did not make the center.
1. Cadence gaps: a full two weeks passed with no posts (June 10 to June 24), and follower growth flattened during the gap.
2. Late-month clustering: three posts shipped in three days (June 24 to 26), competing for the same small audience and holding down the reach of the last one.
3. Soft, inward-facing payoffs: posts that lead with the team rather than the reader's problem (Brainstorm, the deal story) get engagement but less reach.
4. Saves still at one: reference-grade essays are not yet structured to be bookmarked.
Four moves, each grounded in something we observed in June.
June's six posts were front and back loaded with a dead two weeks in between, and growth flattened during that gap. Off a base of ~1,900 followers, consistency is the single biggest lever on compounding. Aim for 3 to 4 posts a week on a fixed rhythm (for example Tue and Thu founder story, plus a product or thesis post) and avoid stacking three posts into three days.
Founder and BTS posts were four of six and drove 73% of reach and 72% of engagement. The pattern that works: specific, named, first-person, with real stakes. Keep mining the vein: early-customer stories, the enterprise-GTM shift, hard technical builds, deals that almost died. This is the content that pulls both reach and followers.
The Access Token API launch earned the account's first save plus 2 shares and solid engagement. For an embedded iPaaS, every new connector, endpoint, or target is credible proof of momentum for a technical audience. Ship one product post a week, and put the API reference or connector list in the first comment as was done here.
The market-thesis essay ("why customers don't build in-house") reached as well as the image posts but earned no save because it ran as prose. Give the thesis pieces a named, numbered payoff: "the 3 reasons in-house integration teams stall", "the embedded iPaaS build-vs-buy checklist". Structured, reference-grade content is what a technical audience bookmarks, and saves are the clearest sign the content is landing as a resource.