Des Traynor on Intercom, Product Strategy and the Real Cost of Growth

Des Traynor says Intercom grew out of a consultancy and a need to communicate with users inside an earlier product. The team saw customers respond strongly to in-product messaging and considered how it fit trends in messaging and software. When outside users embraced it, the founders closed the consultancy and committed to the new company.

When investing, he considers both founder quality and idea quality, but would choose the founder if forced to choose one. An idea can become widely known as soon as it is described, he argues; a more capable or committed competitor can execute it better. This is his angel-investing view, not a rule for every company.

Being first alone rarely sustains an advantage, Traynor says. Large incumbents also cannot prioritize every possible market, leaving openings for startups. A company needs more than being the original provider of a feature that competitors can copy.

He says defensibility on day one is rare, but unusually difficult engineering or craft can create a long road to the starting line for a competitor. He cites Figma as an example and suggests that a rival catching up also has to contend with the original product continuing to improve.

For a startup building something with a long technical runway, he recommends testing the differentiator first. In a new email client, for example, demonstrate the novel experience before spending years on expected functionality and discovering too late that the distinctive idea does not work.

Traynor does not generally use elaborate market-sizing models for his own seed checks. He asks what problem the product solves, how many people have it and how often and intensely they experience it. His rough threshold depends on his check size and desired outcome, and is not a universal market-size requirement.

He says early customer-acquisition cost and lifetime-value calculations can distract founders from making a great product. At scale the metrics matter, but early on he is more interested in whether a company has a distinctive route to customers. He contrasts a concrete target list with a vague plan to compete for attention.

Angel investing has made him notice how much less tolerant he is of explanations for missed targets at other companies than at Intercom. It also exposes him to how other businesses make decisions and where a tool like Intercom ranks among their priorities. He has an obvious professional interest in that perspective.

He prefers relatively little scheduled time and more asynchronous communication with founders. Investing gives him access to the internal workings of companies, including teams at earlier stages from which he can still learn. He says some companies he backed grew to valuations above Intercom’s, without presenting this as realized returns.

Traynor cites Miro and its founder as an example of focused execution on collaborative whiteboarding rather than prematurely chasing every adjacent category. He is an investor in Miro, so his praise comes with a financial interest. He views the team’s ability to resist a distracting expansion narrative as instructive.

When considering a second product, he first asks whether the company can hire enough engineers, designers and product managers without starving its existing product. He also asks whether improving the first product would create more value, and whether two products together have a meaningful advantage over separate companies.

Shared customer records, workflows or interfaces can make a combined offering more valuable. The company should be confident in the first product’s trajectory, be able to staff the second and believe the two reinforce each other. Traynor frames this as a set of questions rather than a rigid timetable.

He advocates proving the new product’s differentiator with a lean test, then funding a credible release if the idea works. The standard changes with the company: he says Intercom’s survey product needed to meet established customer expectations, while a young startup may be able to launch incrementally.

Intercom has confused products with features, he says. A distinction is whether there is a different buyer, an existing separate solution and a credible cross-sell path. Instead of starting with accounting or technical architecture, he suggests asking how target customers currently solve the problem and what they expect in a connected workflow.

For a product that is not working, he looks for trajectory and momentum: does it retain users or does it require repeated promotion merely to get another brief trial? A company can investigate and rebuild, but if it decides to retire the product it should give existing users notice and a migration path.

Good product marketing starts with the needs of users and buyers, who are not always the same. Traynor warns against assuming a screenshot and a slogan explain every product. Consumer hardware with the same buyer and user has a different marketing problem from business software bought by a committee.

Using Intercom as an example, he says a support leader buying software may care about cost, revenue and proof of value, while frontline users care about doing their jobs well and enjoying the tool. He is speaking as Intercom’s co-founder and strategy leader, with a direct commercial interest.

Whether a particular message should lead with the user or the buyer depends on the adoption path and audience. A user-focused campaign can build bottom-up demand, but the buyer will still need evidence and enterprise case studies. He argues that companies ultimately have to address both.

For a horizontal product, he suggests mapping industries against workflows and choosing specific combinations to explain. A tool can serve many purposes, but in a given marketing moment it still needs to say clearly who it helps and what problem it solves. His examples include Notion and Trello.

The right time to move upmarket depends on growth among existing customers and the needs of the best ones. If the company can keep growing with the same simple product, he says, it may not need to move. Otherwise it should compare the return on new vertical features with the work needed to serve larger customers.

One warning sign is successful customers growing beyond the product’s capabilities. Traynor suggests examining whether missing permissions, integrations or similar requirements are causing valuable customers to leave. He weighs that against the extra complexity to product and brand.

Feature creep cannot be eliminated completely, he argues, but teams can fight it by counting the full cost of each addition. A feature must be marketed, sold, supported and maintained, not just built. He prefers work with high leverage and says apparent simplicity can hide major downstream obligations.

He gives the hypothetical example of adding reports that turn Intercom into an analytics company. That would affect positioning, storage, engineering and sales skills as well as the product. As an Intercom executive, he describes why the company has resisted that particular expansion.

On pricing, he rejects a blanket instruction to raise prices and instead argues for aligning price with customer value. At the same time, a broad product must earn enough to support maintenance and reinvestment. He sees a tension between fair value for customers and the cost of sustaining the service.

Traynor lists four needs when selling to larger organizations: adoptability, scalability, justifiability and interoperability. Buyers may require security reviews and procurement, sufficient capacity, evidence of value and integration with existing systems. Requirements vary by customer; his list is a framework, not a universal compliance checklist.

He notes that many enterprise requirements are behind the scenes and hard to show in an attractive product screenshot. Stebbings discloses investments in infrastructure serving enterprise adoption, including WorkOS and Secureframe. The discussion reflects both hosts’ investment interests.

Traynor is interested in bringing software to industries that use less of it, while recognizing long sales cycles and slower adoption. He mentions a construction-software investment and says it takes patience to see the value of products in such markets. His positive assessment is that of an investor.

He is skeptical of pitches to put all consumer data in one place or turn a simple document template into standalone software without clear additional value. He asks who benefits from imposed structure and how hard a competitor would find it to copy. These are preferences in his investment process, not universal judgments.

On giving direct feedback, Traynor says he tries to explain his investment principles and why a particular proposal does not fit them. He is comfortable if a founder rejects his reasoning or accepts it; what matters to him is that the disagreement becomes explicit rather than vague.

Asked about misses, he says his greater tendency may be writing too many checks. He recalls opportunities delayed by paperwork or missed because of commitments to competing products, and an opportunity to invest in SpaceX that he could not afford at the time. His expectations for named startups are opinions, not established future outcomes.

He describes a normal angel check around $25,000, with larger checks for a small number of especially compelling opportunities. He avoids forcing his way into allocations. He also says he relies on a lead investor to perform diligence and conditions his participation on that work; this is his own practice, not a substitute for independent due diligence.

Parenting and leadership both require care for outcomes that emerge over years, he says. A leader cannot micromanage people every moment, so they must communicate principles and intentions and support others as they act independently. He presents an analogy, not an assertion that employees are children.

He favors being both demanding and supportive: ask talented colleagues to attempt hard work, then help them if they hit barriers. Where performance is in doubt, he recommends agreeing explicitly on the task, timing and quality bar and asking people to raise concerns early if the plan changes.

A major hiring mistake early in his career was being impressed by a famous company logo. Someone may have worked at a successful business without causing its success. He recommends probing individual contribution rather than assuming a prestigious title will reproduce the same result elsewhere.

Traynor questions simplistic advice to hire only supposedly perfect performers. People join to learn, teams need a mix of experience and ambition, and a candidate’s trajectory matters. The right hire depends on what the function and company need at that stage, not an abstract global ranking.

He says a team may need to correct for the shortcomings of a previous leader: a very harsh manager may leave a need for a different approach, while another team may need more structure. He treats hiring as a fit for a period of company development rather than a decision for an entire lifetime.

His favorite book is Clayton Christensen’s How Will You Measure Your Life?, which applies business strategy ideas to personal choices. At Intercom, he says prioritization is the hardest part of his role, and focus is advice he gives more consistently than he follows himself.

He wishes he had known how Intercom’s early uncertainty would unfold and had understood more clearly how product choices connect to hiring, brand and long-term economics. He also wants more technology journalism that is both interested in technology and open to optimistic possibilities.

Looking toward 2027, Traynor imagines remaining in Dublin with his family and possibly taking a different role at Intercom. He would like less of his attention consumed by worries about employees and industry risks. The five-year picture is his aspiration in 2022, not a report of what later happened.

His greatest concern is that the Intercom journey should work out meaningfully for the people who took it together. He describes a tendency to imagine worst-case scenarios and says getting physically stronger helped his own confidence. This is personal experience, not a general medical claim.