Go-to-Market Strategy for Specialized Customers
The company was founded in October 2003 by a team of five co-founders, and its first product was built for the intelligence community.
Selling to Customers Who Cannot Explain Their Work
Most software is sold to customers who can describe their problems openly. A hospital can explain its scheduling trouble, and a retailer can explain its inventory trouble. The customer names the problem, the vendor proposes a fix, and the two sides work toward an agreement. This story is different. It concerns a company whose first customer community did its work in secret and could not explain its needs to outsiders.
When and How the Company Began
The company was founded in October 2003. Five people founded it together. The source treats their names as part of the company's historical record rather than something a learner must memorize, so this article focuses on what the founding involved rather than on who the individuals were.
What matters for understanding the founding is the combination of two things: a technology idea and a market that was difficult to reach. The founders had a technical bet they believed in, and they had no simple path to the customers who could use it. The company's first product was built for the intelligence community, so that community was both the intended user and the hardest group to approach.
A technical bet is a belief that a specific technology idea will solve a real problem, held before anyone has confirmed that customers will buy or use it. In this founding story, the founders' bet was that a single software platform could help analysts, but the bet had no direct route to the people who would use it.
The Original Product Idea
The original product was a software platform for the intelligence community. Its design was partly a response to failures of information sharing that had been blamed for the 9/11 attacks. The core pitch was straightforward: if intelligence analysts had one tool that could integrate fragmented data from many sources, and could expose the relationships within that data through a clean visual interface, they could spot threats that existing pipelines were missing.
The product had two jobs, and the founders' bet depended on doing both. The first job was integration: pulling together data that lived in separate places. The second job was exposure: making the connections between those pieces of data visible to a person. A system that gathered data but showed nothing useful would not help an analyst. A clean display of data that was never integrated would show only part of the picture. Each job alone was incomplete, which is why the design combined them.
The Standard Enterprise Playbook
Enterprise software companies of the period commonly followed a fairly standard sequence to win a customer. The source describes that sequence as a playbook. Two of its steps are named explicitly: finding a champion, meaning someone inside the customer organization who has a problem, and running a pilot, which tests a solution on that problem. The source notes that later stages exist as well, but it does not list them, so this article does not invent them.
The important feature of the playbook is that its steps depend on one another, and the first step depends on the customer being willing to share what it needs. Finding a champion requires knowing who inside the organization has a problem. Running a pilot requires knowing what the pilot should test. The playbook therefore assumes that the customer can describe its work.
Why the Playbook Could Not Start
The standard playbook depended on the customer describing its needs, so it could not begin when the intelligence community's work was hidden. The founders' central early challenge was therefore not proving that the technology idea was sound. It was reaching the knowledge needed to build the product in the first place. The problem was upstream of the product itself.
Tracing a Single Missing Piece
The most useful way to understand this story is to follow the playbook step by step and watch what happens when the first prerequisite is absent. Each step in the playbook needs the one before it, so the missing knowledge does not stop only one step. It stops the whole chain, starting at the first point that depends on it.
Following the blockage through the playbook
A vendor wants to win a customer using the standard playbook, but the customer's work is hidden and it will not describe its needs. Trace what happens to each step.
- 1Step 1: Check the first prerequisite
The playbook's first step depends on the customer being willing to share what it needs. Here, the answer is no.
- 2Step 2: Attempt to find a champion
Finding a champion requires knowing who inside the organization has a problem. With needs hidden, the vendor cannot identify that person, so this step cannot succeed.
- 3Step 3: Attempt to define a pilot
Running a pilot requires knowing what the pilot should test. That knowledge comes from the customer's needs, which are unavailable, so this step is also blocked.
- 4Step 4: Reach later stages
Later stages come after the pilot in the sequence. Because the earlier steps cannot be completed, the process never reaches them.
A single missing piece, the customer's willingness to describe its needs, stops every step of the playbook. The blockage cascades from the first prerequisite forward, so the whole sequence has no starting point.
Predicting the Point of Failure
What do you think happens?
If the customer will not describe its needs, which playbook step fails first, and why?
Reveal answer
Finding a champion fails first, because it requires knowing who inside the organization has a problem, and that knowledge depends on the customer describing its needs.
The playbook's first step depends on the customer's willingness to share its needs. Without it, the next step that needs a known problem owner cannot begin, and each later step inherits the blockage.
Using a different hypothetical customer, one whose work is open and who is willing to explain its problem, describe which playbook steps can proceed and which information each step needs before it can start. Then identify the single prerequisite whose absence would block the most steps.
Hints
- Start with the first step and ask what it needs from the customer.
- Remember that each step requires the one before it to be complete.
- The blocking prerequisite is the one upstream of every other step.
Mistakes About the Founding Challenge
Common mistake Assuming the founders' main problem was proving the technology idea
Why it failsThe source states that the founders' central early challenge was reaching the knowledge needed to build the product, not proving the technology idea was sound.
Do this insteadFocus on access to the customer's knowledge as the early bottleneck.
Common mistake Concluding that the standard playbook failed because the product was weak
Why it failsThe playbook could not start because it depended on the customer describing its needs. The obstacle was the missing starting point, not the product's quality.
Do this insteadLocate the blockage at the first prerequisite of the sales sequence.
Common mistake Treating the playbook as a list of independent steps
Why it failsEach step depends on the one before it, so one missing prerequisite affects the whole chain.
Do this insteadRead the playbook as a dependency chain that starts with the customer's willingness to share needs.
Common mistake Memorizing the founders' names as essential knowledge
Why it failsThe source says the names are part of the historical record and that the course does not require memorizing them.
Do this insteadConcentrate on the founding date, the product idea, and the market access problem.
Why Two Jobs Mattered
Key Takeaways
- The company was founded in October 2003 by five co-founders, and its first product was built for the intelligence community.
- The original product aimed to integrate fragmented data and expose relationships through a clean visual interface, partly in response to information-sharing failures linked to the 9/11 attacks.
- The standard enterprise playbook depended on the customer describing its needs, so it could not begin when the intelligence community's work was hidden.
- A single missing prerequisite, the customer's willingness to share needs, blocks every later step because each step depends on the one before it.
- The founders' central early challenge was reaching the knowledge needed to build the product, not proving that the technology idea was sound.