What Segment's change of direction teaches about customer discovery

A prospect can tell you exactly why they will not buy, and still be showing you a promising business. The difficulty is hearing the second part while you are busy defending the first.

That tension runs through Segment's early story. In Peter Reinhardt's retrospective, the team spent a long period building education and analytics ideas that were poorly validated. A small library created to send events to multiple analytics services eventually became the more promising direction.

The library was already open source when the team tested its business direction with a landing page and a Hacker News post. Reinhardt describes explaining the data-routing problem, then expanding the scope into more integrations and support for server-side and mobile data. Interest in that test was a useful signal, rather than proof of a business from the first positive response.

Our reading of the story is that a useful problem can sit beside the product you intended to build. The conversations and tests should leave room for that discovery.

When the objection points somewhere useful#

If a prospect says they already have a tool, your instinct may be to explain why your tool is better. Sometimes that is the right conversation. Sometimes it misses the part of the work they actually dislike.

A team can be satisfied with its reporting software and frustrated with preparing data for it. A company can like its CRM and dislike the manual handoff between departments. A manager can trust an existing supplier and still need help covering a particular location. The category you want to sell into may be broader than the problem the customer wants solved.

The useful question is what happens around the current solution. What must the person prepare before it works? Where does a task wait for another team? Which recurring exception sends people back to a spreadsheet? You are looking for something the person can describe from experience, rather than asking them to predict whether they would love a future product.

Meet people close enough to show you the work#

A conversation with a senior title is not automatically a conversation with the right person. For a workflow problem, the person who sees the failure may sit several steps away from the person who approves a purchase.

Your first objective can make room for both. Start by understanding who performs the work, who owns its result and who can authorise a change. If those are different people, the Introduction criteria should reflect the conversation you are trying to have. Research participants and commercial buyers are not interchangeable.

A good research conversation leaves you with a concrete example of the current process. A commercial conversation adds whether there is a reason and a practical route to evaluate your offer. Neither should be described as a sale until a sale occurs.

Keep disagreement in the evidence#

Founders can accidentally train themselves to collect agreement. They revisit friendly contacts, describe the idea more enthusiastically and discount the people who are unconvinced. The resulting notes look positive while the business remains uncertain.

A more useful record keeps the uncomfortable answers. Write down what a person already uses, which part they would keep, what they would change and why they might do nothing. Separate observations from your interpretation. If several people describe the same inconvenience, investigate whether they mean the same underlying problem. Similar words can hide different workflows.

Then choose a test that can change your mind. A public launch can reveal interest, but a work-related evaluation may be needed to understand ownership, implementation and payment. Select the smallest test that answers the question you actually face.

The next Introduction should test a question#

The story becomes useful when it changes whom you want to meet. A broad request for potential customers becomes a more precise request for people responsible for a particular workflow, with a reason to discuss improving it.

Kite can help you pursue that objective and get introduced to relevant people. Bring the business context you already have, including what remains uncertain. You do not need to arrive with a finished ICP. You do need a useful reason for the conversation and a clear standard for what makes the Introduction worthwhile.

The right-people guide helps translate that question into roles, locations and exclusions. The next discussion may confirm your direction or expose a better one. Both deserve to be heard.