How to Choose a Lighthouse Customer
Not every customer deserves the same investment. A lighthouse customer makes the next deployment easier to win.
FDE capacity is limited. The first customer should have a specific, important pain, a real business owner, and the willingness to bring real data into the work.
After reading, you should be able to answer:
- Why the lighthouse customer matters, and how to pick one that illuminates the whole map
- Why the first customer often decides whether this playbook can be copied at all
- How to tell a lighthouse from a black hole that swallows the team
Selection criteria
The lighthouse customer has three traits: the pain is concrete and material, the business owner and decision path are present, and the team will validate with its own data. Once the result exists, the customer can speak for you more credibly than a sales deck.
Watch for demand hoppers
A demand hopper asks for every use case across the company in the first meeting, has no business owner, and wants proof without providing real data. When procurement or IT is the only sponsor, the project may have no one who benefits enough to change the workflow.
The leverage effect
The lighthouse is valuable because it can be reused. One reference workflow helps set expectations, shortens later sales cycles, and gives the organization evidence for expansion. That is the rhythm of the Palantir-style playbook: do a single-digit set of lighthouse customers thoroughly, then use the usage data they produce to knock on bigger doors a16z-palantirization. Start with a customer whose success can illuminate the next path, not one whose scope can consume the whole team.
The price deserves stating too. Lighthouse customers are demanding, long, and thin on margin, and almost everything you earn on the first one is the repeatability rather than the contract itself. A customer that is expensive and never turns into a reference is not a lighthouse — it is just another delivery.