Airbnb's early growth began with showing up for the people using it

There is a point in an early business when the next useful improvement is difficult to see from your desk. You can examine the website, revise the pitch and study the numbers, yet still miss what is happening for the person on the other side.

In Paul Graham's account of early Airbnb, the founders went door to door in New York to recruit users and help existing users improve their listings. He also recalls them taking better photographs of early hosts' apartments. The work brought them close to both the people and the experience they were trying to improve.

The lesson we draw is about the distance between acquiring a user and understanding what makes the product useful to them. Getting closer can reveal where that distance comes from.

An Introduction opens a door, not the whole relationship#

For a founder, a meeting with a relevant person can feel like progress immediately. It is progress when the person has a reason to engage. What happens next still matters.

A customer may understand your proposition and struggle with the first step. They may complete setup and fail to reach the useful result. They may enjoy the demonstration without having a reason to use the product again. Those moments can look similar in a calendar and very different in a business.

This is why the handoff should carry context. What is the person trying to accomplish? What did they agree to discuss? Which conditions were important to them? If you begin the meeting by asking them to repeat everything, you spend attention that could have gone toward understanding the work.

Look for friction the person can show you#

A general question about satisfaction often produces a general answer. A concrete walkthrough of a recent task gives you something more useful.

Ask the person to describe the last time they tried to do the job your product supports. Let them tell you where it began, which decisions they had to make and where they stopped. With their permission, examine only the information necessary to understand the workflow. There is no need to collect a customer's private records just to learn that a handoff is confusing.

If they cannot reach the useful result, find out whether the obstacle is missing functionality, unclear instructions, a change in responsibility or a lack of urgency. A new feature might address the first and do nothing for the others. The distinction gives your team a better next decision.

Choose a commitment that fits the conversation#

A first conversation does not have to end with a purchase. It should end with a next step both people understand. That might be an evaluation with an owner, a follow-up after a particular event or an honest decision that the fit is weak.

Avoid a vague promise to keep in touch when the business needs a clearer answer. Ask what needs to be established, who needs to participate and when it would be useful to revisit the decision. If the person is only offering research feedback, keep the discussion in that scope. If they want to consider buying, make the evaluation and commercial responsibilities clear.

Write down the next step in ordinary language. You should be able to return to the notes a week later and understand what was agreed without guessing from the tone of the meeting.

Getting closer remains useful as the business grows#

You cannot personally attend to every interaction forever. You can preserve what useful early conversations teach you.

Turn repeated confusion into a better explanation. Turn a recurring implementation question into a clearer setup step. Turn a genuine customer result into an evidence-backed story only with the permission and records needed to support it. Keep the unsuccessful evaluations too; they help explain whom the product should not pursue.

Kite creates Introductions with person, company, conversation and qualification context, plus a next step. Your part is to make that next conversation count. The follow-through guide helps you carry the handoff into a useful discussion and keep interest, evaluation and payment distinct.