Zapier's first paying customer began with a problem already in public
Wade Foster found an old integration request, checked whether the need remained and learned that the customer's actual job had changed.
An old request opened a current conversation#
A public signal can tell you which question to ask. It cannot tell you whether the person still has the problem.
In Wade Foster's account of Zapier's first paying customer, he found Andrew Warner's older request for a PayPal–Highrise integration. Warner had already addressed that issue, but needed a different connection: Wufoo to AWeber. Zapier built it, Warner paid $100 for beta access, and the team helped him get it working.
Foster also cautions that the early approach was not a repeatable sales process at that price. This is a specific founder account, not a pricing benchmark or a promise about another business's first sale.
Ask whether the signal still describes the situation#
The first useful move was to check a need rather than insist the old request was current. A job post, forum question, company announcement or public workflow can be a clue. Time and context can change its meaning.
For a technical provider, the observed request may suggest a conversation about how the process now works. For a service business, a new location may prompt a question about service responsibility. For a software founder, an integration request may expose a larger workflow.
Keep three fields in your notes: what was observed, what it might mean, and what a person actually confirmed. That distinction prevents a research clue from quietly becoming a claimed pain point.
Solve the job the person now wants done#
Warner's next need differed from the one that led Foster to him. The wider lesson is to listen after a conversation starts. Your prepared offer may need a different scope, or your business may not be the right provider.
Ask what the person needs to complete, which inputs are available and what would make a solution usable. Do not promise a custom build before checking the work and your capacity. If the request is valuable but uncertain, agree a bounded next decision.
The paid-pilot guide helps translate interest into scope, inputs, delivery and an end decision. It leaves pricing and actual commitments with your business.
Keep the lesson distinct from a scalable motion#
A founder can learn a great deal from an early engagement that is not economical to repeat unchanged. Record the implementation effort, support, revisions and what the customer valued. Then decide which parts can become a repeatable offer.
Do not treat the visibility of an influential customer as a channel you can reliably reproduce. Focus on the work your business controls: finding a relevant question, confirming the current need and delivering what was agreed.
Kite helps you meet qualified people relevant to your objective. Use observed evidence to prepare better questions and required criteria. An Introduction starts a relationship; the sale and the delivery need their own confirmed decisions.
Sources behind this story
Primary accounts and industry guidance inform the facts. The discussion and recommendations are Kite University's editorial analysis.
- How Andrew Warner became Zapier's first paying customer Zapier · Wade Foster · Checked 2026-10-14
Give your business goal
a place to start.
Kite is an introductions platform. It gets you into phone or video meetings with qualified people who have a reason to do business with you.
Your experience should make the next step clearer.