---
title: "Latest reads"
description: "The engineering internet, summarised so you can actually read it."
---

# Latest reads
> The engineering internet, summarised so you can actually read it.

## Articles

### [Need for speed: how to address leads faster with live chat - The Intercom Blog](https://yomu.fyi/post/need-for-speed-how-to-address-leads-faster-with-live-chat-the-intercom.md)
- Company: [Intercom](https://yomu.fyi/company/intercom.md)
- Published: Oct 9, 2026
- Type: Problem & solution

A Harvard Business Review study of 1.25 million sales leads found that responding within an hour makes a deal seven times more likely to close than a two-hour response. Live chat on a website is the fastest way to achieve that speed, bypassing the delays of contact forms and email follow-ups. The first tactic is to offer live chat only to prospects matching an ideal customer profile, using tools like Clearbit to filter visitors so SDRs focus on qualified leads. The second is to combine a bot for collecting contact information with human sales development representatives for personalized conversations, avoiding over-automation that annoys prospects. The third is to set proper expectations by stating office hours, displaying average response times when unavailable, and hiding the chat outside business hours, which allows reps to be more thoughtful in their responses.


### [Make Sales & Product meetings a win-win](https://yomu.fyi/post/make-sales-amp-product-meetings-a-win-win.md)
- Company: [Intercom](https://yomu.fyi/company/intercom.md)
- Published: Oct 9, 2026
- Type: Tutorial

Fortnightly sales-product meetings at Intercom use a structured feedback loop to align product strategy with market needs. Sales teams first meet internally, using a shared Google Doc to categorize recent feedback and prioritize three to five items backed by concrete data such as the customer’s job title, revenue at risk, and competitor presence. The cross-functional sync includes representatives from each sales segment (SMB, Mid-Market, Enterprise) plus product owners, who ask context-gathering questions and share roadmap progress. This method replaces ad-hoc feature requests with evidence-based discussions, helping product understand customer impact and sales set realistic expectations with prospects. The process has resulted in popular features like automatic conversation routing to the right team and stronger cross-functional collaboration between sales and product teams.


### [Intercom on Marketing - the marketing book for startups](https://yomu.fyi/post/intercom-on-marketing-the-marketing-book-for-startups.md)
- Company: [Intercom](https://yomu.fyi/company/intercom.md)
- Published: Oct 9, 2026
- Type: Announcement

Intercom has released a new book, Intercom on Marketing, aimed at helping startups overcome marketing challenges. The book addresses the difficulty founders face in knowing where to start with marketing, especially without a background in it. It emphasizes that strong brand and go-to-market strategy can differentiate startups in a commoditized software landscape. The book collects lessons from Intercom’s own marketing team, which grew from one to over forty people. It covers 14 chapters including getting first customers, choosing tactics, aligning product and marketing, and launching products, and is available for free in PDF, Kindle, or epub formats with original illustrations.


### [Behind the design work of Building Intercom - The Intercom Blog](https://yomu.fyi/post/behind-the-design-work-of-building-intercom-the-intercom-blog.md)
- Company: [Intercom](https://yomu.fyi/company/intercom.md)
- Published: Oct 9, 2026
- Type: Explainer

For the ‘Building Intercom’ event page, the design team aimed for an ‘unapologetically nerdy’ aesthetic to appeal to engineers without resorting to tired clichés. The author discovered the Hershey fonts, originally created in the 1960s by physicist A.V. Hershey, and revived them into functional font files using FontSelf and then Glyphs for weight variations. A small Python script automated placing outlines into a .glyphs file, and Paper.js enabled interactive vector animations. Testing revealed issues such as event details being overlooked, Paperscript’s JavaScript evaluators forbidden by Intercom’s security team, and poor mobile browser support for Paper.js. The project reinforced the value of taking meaningful risks in design and development, reminding the author that overcoming fear of consequences is part of the work.


### [The pains of growing a platform - The Intercom Blog](https://yomu.fyi/post/the-pains-of-growing-a-platform-the-intercom-blog.md)
- Company: [Intercom](https://yomu.fyi/company/intercom.md)
- Published: Oct 9, 2026
- Type: Problem & solution

Many SaaS companies aspire to become platforms, but building a true platform is far more complex than offering APIs and integrations. Intercom, despite having over 250 third-party integrations and nearly 40% of customers using its APIs, acknowledges that this alone does not constitute a platform. The post identifies three common mistakes: trying to become a platform too early, expecting others to build integrations, and focusing on adoption metrics instead of developer success. Intercom emphasizes that platforms are governed ecosystems requiring extensibility and distribution, and that companies should start by building for their own customers before third parties. Building a lasting platform takes years of deliberate planning and long-term investment, as demonstrated by Salesforce’s gradual evolution from a point solution to a platform.


### [Why you should have skin in the engineering game - The Intercom Blog](https://yomu.fyi/post/why-you-should-have-skin-in-the-engineering-game-the-intercom-blog.md)
- Company: [Intercom](https://yomu.fyi/company/intercom.md)
- Published: Oct 9, 2026
- Type: Explainer

The post compares the high-stakes feedback of professional cycling to engineering, noting that engineers in growing companies often become disconnected from customers through support teams and product managers. The author, a former cyclist, advocates for engineers to maintain ‘skin in the game’ by personally connecting with customers. Intercom enforces regular customer days for all employees to give first-hand exposure, uses GitHub integration to easily dig into real customer conversations, and encourages direct outreach for complex issues. Working through a subtle bug caused by a feature update, the author iterated directly with a customer for a week, restoring their broken workflow. This personal investment in outcomes motivates engineers and ensures their work has real impact, while the post encourages others to seek similar practices.


### [The right way to respond to feature requests - The Intercom Blog](https://yomu.fyi/post/the-right-way-to-respond-to-feature-requests-the-intercom-blog.md)
- Company: [Intercom](https://yomu.fyi/company/intercom.md)
- Published: Oct 9, 2026
- Type: Tutorial

Customer support teams frequently encounter feature requests that reveal gaps between a product and user goals, and responding effectively requires a rigorous framework. The post categorizes these requests into three types: unresolved problems with existing features, improvements to existing features, and brand new feature requests. For each type, it recommends a tailored response: educate customers on workarounds for problems without promising specific fix dates, suggest alternative existing functionality for improvements, and honestly decline new requests while acknowledging the gap and offering third-party solutions like Zapier or YouCanBookMe, sharing context about limited engineering resources. Prioritization should also consider customer lifecycle, high-value users, implementation difficulty, and feedback volume to balance satisfaction with engineering resources and long-term strategy. Closing the loop by tagging conversations in Intercom and sharing monthly customer voice reports with product managers ensures feedback drives roadmap decisions and builds long-term customer success.


### [Understanding the customer success pyramid - The Intercom Blog](https://yomu.fyi/post/understanding-the-customer-success-pyramid-the-intercom-blog.md)
- Company: [Intercom](https://yomu.fyi/company/intercom.md)
- Published: Oct 9, 2026
- Type: Explainer

The post introduces the Customer Success Pyramid, a framework modeled on Maslow’s hierarchy of needs, to help businesses understand and meet customer needs. At the base is providing precise and accurate support, which builds trust and must be maintained as the product and team grow. Above that is promptness, meaning being fast when it matters, such as using real-time chat during a customer’s early days. The middle levels focus on being personal to build rapport and personalized by using customer data to tailor interactions without being intrusive. Higher levels include preemptive support, where businesses identify problematic patterns and intervene before the customer notices, and prescience, where AI and machine learning automate this proactive guidance; the post notes that operating higher on the pyramid increases the likelihood of successful outcomes.


### [Crafting feature announcements that spur action - The Intercom Blog](https://yomu.fyi/post/crafting-feature-announcements-that-spur-action-the-intercom-blog.md)
- Company: [Intercom](https://yomu.fyi/company/intercom.md)
- Published: Oct 9, 2026
- Type: Tutorial

A feature’s value depends on showing customers how it solves their problem, not on development effort. Intercom recommends targeting the right customers using message filters, such as those with access, those without (upsell), those who requested the feature, or those taking related actions, while excluding recently contacted (within 3 days) and new users (signed up less than 30 days ago). Choose the medium based on context: in-app for active users on relevant pages, email for re-engaging inactive users, and time announcements between 10am-2pm on weekdays for best open rates. The message should focus on customer benefits, be concise, include visuals, and stay personal. After announcing, track usage via events and gather feedback to inform future iterations.


### [Embracing a human tone in customer support - The Intercom Blog](https://yomu.fyi/post/embracing-a-human-tone-in-customer-support-the-intercom-blog.md)
- Company: [Intercom](https://yomu.fyi/company/intercom.md)
- Published: Oct 9, 2026
- Type: Explainer

The post argues that making customer support conversations more human, by acknowledging emotions and personal context, is key to delivering next-level service, especially on chat platforms like Intercom. It advises support reps to recognize ‘signs of life’ such as crying emojis or a simple ‘how are you?’, and to respond truthfully rather than with a robotic script. When agents inevitably make mistakes, such as sending the wrong link, they should own the error transparently and use humor or emoji to diffuse tension. Emoji and GIFs are encouraged in light moments, but the human tone should not be forced; it works best when natural and when reps look beyond conversations to gather candid product feedback. Over the long term, personal interactions make support faster by building familiarity with customers, allowing reps to recall context at a glance.


### [Learn How To Nurture New Signups Beyond The Free Trial](https://yomu.fyi/post/learn-how-to-nurture-new-signups-beyond-the-free-trial.md)
- Company: [Intercom](https://yomu.fyi/company/intercom.md)
- Published: Oct 9, 2026
- Type: Announcement

The SaaS law of averages suggests 40-60% of free trial signups use the product once and never return, often due to lack of perceived value or mismatched expectations. The Nurture Starter Kit is a guide for designing messaging campaigns to convert these signups into paying customers through improved communication. It advocates behavior-based triggered messages over timed drips, tailored to each customer’s definition of success, and includes half a dozen example messages. The kit also provides advice on measuring campaign effectiveness through actions that lead to conversions, not just macro-level rates. The goal is to make becoming a paying customer the obvious choice, avoiding radio silence followed by a last-minute expiration email.


### [What we shipped: 20 new features and counting - The Intercom Blog](https://yomu.fyi/post/what-we-shipped-20-new-features-and-counting-the-intercom-blog.md)
- Company: [Intercom](https://yomu.fyi/company/intercom.md)
- Published: Oct 9, 2026
- Type: Announcement

Intercom shipped over 20 new features in the first half of 2017, reflecting its philosophy that shipping is the beginning of iteration. Support enhancements include office hours and away mode, an Articles autoresponder that guides customers to the help center while they wait with localization in 38 languages and a link back to the website, animated GIF support, and mobile app additions for articles, images, GIFs, and saved replies. Inbox improvements let teams sort by longest waiting, group conversations, and snooze conversations for follow-up, while integrations added Microsoft Teams and a new developer dashboard that puts everything in one place. The API added Leads and Companies to the Scroll API, and outbound messaging gained engagement-based targeting, the ability to stop a message once it starts sending, and mobile delivery windows for push notifications. These smaller improvements aim to make support more personal and scalable without requiring major announcements.


### [Using Intercom to design Intercom - The Intercom Blog](https://yomu.fyi/post/using-intercom-to-design-intercom-the-intercom-blog.md)
- Company: [Intercom](https://yomu.fyi/company/intercom.md)
- Published: Oct 9, 2026
- Type: Explainer

A designer at Intercom explains how the team uses their own product to gather data-driven insights for design decisions, replacing intuition with evidence from real customer interactions. Support team members tag feature requests and confusing conversations, which the research team organizes by topic for easy access. In one example, the designer analyzed 120 conversations about multi-person messaging and found only 33% actually wanted that feature, while others needed handoff or transfer capabilities. In another, an automated message targeting users who sent one-to-one messages via the fully featured editor revealed within hours that the ability to duplicate messages was the missing feature. This approach ensures design solutions are based on real customer needs rather than surface-level requests.


### [Does your support team know more about your product than you?](https://yomu.fyi/post/does-your-support-team-know-more-about-your-product-than-you.md)
- Company: [Intercom](https://yomu.fyi/company/intercom.md)
- Published: Oct 9, 2026
- Type: Problem & solution

Customer support teams interact with customers daily and possess valuable product and customer insights that product teams often overlook. Treating support as an outsourced function or ignoring their conversations wastes unsolicited feedback that differs from survey data. Intercom tags every support conversation with team and category tags to make feedback actionable, enabling product teams to create dashboards, spot trends, and explore conversations for insights. For example, tagging ‘product confusion’ revealed an onboarding issue where customers saw nothing if they only completed one of two setup steps, leading to a pop-up that told customers exactly what they needed to do and reduced those conversations. Product teams also use tags like ‘unaware’ to improve feature discoverability, track bug reports via a GitHub integration, and compile quarterly ‘customer voice reports’ of top feature requests while closing the feedback loop with customers.


### [Opening up the power of Intercom's platform - The Intercom Blog](https://yomu.fyi/post/opening-up-the-power-of-intercom-x27-s-platform-the-intercom-blog.md)
- Company: [Intercom](https://yomu.fyi/company/intercom.md)
- Published: Oct 9, 2026
- Type: Announcement

Intercom announced the launch of its Developer Program, opening its platform for third-party integrations. The company positions Intercom as the single source of truth for customer data, with data flowing in and out to other tools. It emphasizes flexibility, acknowledging it cannot build every feature customers need, that it is naive to believe every customer uses the product the same way, and that it relies on a developer community to extend its capabilities. The program helps developers build successful integrations and helps customers discover quality tools, with approved members listed on the website alongside built-by-Intercom integrations like Slack, Facebook, and more. The first eight approved members include Aircall, AskNicely, ChargeDesk, FullStory, productboard, SatisMeter, Statbot, and Wootric, and Intercom plans further ecosystem support as the developer community grows.


### [Your product is already obsolete - The Intercom Blog](https://yomu.fyi/post/your-product-is-already-obsolete-the-intercom-blog.md)
- Company: [Intercom](https://yomu.fyi/company/intercom.md)
- Published: Oct 9, 2026
- Type: Explainer

Technology products inevitably become obsolete as industries shift, and failing to adapt can kill a business faster than most founders expect. Success breeds complacency, which breeds failure, making paranoia a necessary survival trait for everyone in tech. Historical examples like satnav manufacturers gutted by the iPhone and telcos disrupted by WhatsApp show that customers will abandon an incumbent for a simpler, faster way to achieve their goals. To avoid this fate, Intercom advocates thinking of a product as a flexible system rather than a set of screens or user flows, allowing it to integrate across new mediums. This systems approach enables the product to remain relevant through multiple technology cycles by focusing on helping customers make progress in their lives.


### [The golden mean of design and engineering - The Intercom Blog](https://yomu.fyi/post/the-golden-mean-of-design-and-engineering-the-intercom-blog.md)
- Company: [Intercom](https://yomu.fyi/company/intercom.md)
- Published: Oct 9, 2026
- Type: Explainer

The post draws on Aristotle’s golden mean to argue that great products require a balance between design and engineering, not compromise. Engineers naturally focus on functionality and performance, wanting to ship features and increase speed often without customer requests, while designers aim for optimal user flows and catch subtle interaction details. The OAuth implementation exemplifies this, with engineers building the technical side and designers crafting user flows, each pursuing their own self-interest through daily stand-ups and whiteboard sessions rather than compromising. This self-interest, guided by Adam Smith’s invisible hand, yields superior products than continual compromise, which leads to mediocrity. The post recommends embedding designers in product teams via a hub-and-spoke model, and leaders trusting their teams to find equilibrium rather than imposing rules.


### [Empathy: the key to better support content - The Intercom Blog](https://yomu.fyi/post/empathy-the-key-to-better-support-content-the-intercom-blog.md)
- Company: [Intercom](https://yomu.fyi/company/intercom.md)
- Published: Oct 9, 2026
- Type: Explainer

As businesses scale, they risk losing touch with customer problems, which becomes apparent in support content. The post argues that empathy—both cognitive and emotional—is essential for creating effective help content. Cognitive empathy involves understanding customer perspectives by surrounding oneself with customer information, as Harley Davidson does with bike trip photos, and by staying informed about product evolution through conversations with design, support, and engineering teams. Emotional empathy requires experiencing the frustrations customers face, such as imagining a world without the product’s key features or actively finding and reporting bugs to understand user pain, as encouraged by Intercom’s “if you find something broken, you now own fixing it” poster. By combining both types of empathy, support writers can produce content that resonates with users and addresses their real needs, as shown in Intercom’s Smart Campaigns and User Map documentation.


### [Build a Secure TypeScript MCP Client with Cross App Access (XAA)](https://yomu.fyi/post/build-a-secure-typescript-mcp-client-with-cross-app-access-xaa.md)
- Company: [Okta](https://yomu.fyi/company/okta.md)
- Author: Akanksha Bhasin
- Published: Oct 9, 2026
- Type: Tutorial

The post presents a tutorial for building a TypeScript Model Context Protocol (MCP) client that uses Cross App Access (XAA) to securely bridge enterprise apps across trust domains. The sample app is an employee onboarding dashboard that signs in through an identity provider, exchanges identity for an Identity Assertion JWT Authorization Grant (ID-JAG), trades it for an access token, and fetches data from a protected MCP server. The tutorial uses the MCP TypeScript SDK’s CrossAppAccessProvider to automate the four-step XAA flow, including token exchange and retry on 401 responses. Developers test against xaa.dev, a free playground that hosts the IdP, authorization server, and a todo MCP server. The post explains key concepts like ID-JAG claims, separate client credentials per trust domain, and how XAA enables AI agents and enterprise apps to act on behalf of users without OAuth consent screens.


### [Lakebase and Agentic SDLC: Branching Databases for Coding Agents](https://yomu.fyi/post/lakebase-and-agentic-sdlc-branching-databases-for-coding-agents.md)
- Company: [Databricks](https://yomu.fyi/company/databricks.md)
- Author: Thibaut Gourdel
- Published: Oct 9, 2026
- Type: Problem & solution

Coding agents working in parallel on shared databases create schema conflicts, test interference, and data exposure risks. Lakebase Postgres solves this with database branching, which creates an isolated copy of an entire database in under a second using copy-on-write. Each agent gets its own database branch via a post-checkout Git hook tied to a worktree, and each pull request gets an ephemeral branch through CI tooling. Schema changes are tracked in code with migration tools such as Drizzle or Alembic and promoted to the parent branch during deployment, not by merging database branches. Idle branches scale to zero, so running many concurrent agents incurs no compute cost for unused branches.


[Newer posts](https://yomu.fyi/posts/page/11.md) · [Older posts](https://yomu.fyi/posts/page/13.md)