WhoBuilt

Office Hours with Kevin & Qasar

Jul 31, 2014· 42 min· 16K views·Watch on YouTube

Speakers

Y Combinator partners Kevin Hale, a product and design specialist, and Qasar Younis discuss YC office hours and advise three startups during a public session.

How YC office hours work

Qasar describes four types: group, individual, investor, and company office hours. Individual meetings are usually tactical, drawing on context built over time rather than functioning as pitches. Kevin advises founders to know their numbers, bring a specific problem, and show progress from previous feedback.

Zifi tests demand for culture-focused hiring

Zifi profiles high-growth small and medium-sized companies to help them attract junior talent by showing their workplaces and employees. The founders had 12 companies listed, no placements yet, and had been working on the business for about six months. Kevin and Qasar urge them to learn what students actually value, focus on quality applicants, and test whether company culture drives demand before scaling supply.

VY connects retail foot traffic to action

VY uses Wi-Fi sensors, people counters, and 3D cameras to track how shoppers move through stores. It had four paying pilot customers across one or two locations each, and had generated about six figures in pilot revenue. Kevin cautions that long sales cycles and data without clear actions could undermine the business; he recommends agreeing on measurable outcomes and building features that help retailers improve them.

Screenpush improves its message and onboarding

Screenpush is a screenshot collaboration tool for digital design teams. Kevin says its site takes too long to explain what the product does, and walks through signup and setup problems, including unclear fields, confusing login, and an app that gives little feedback. He recommends describing the product plainly and having people unfamiliar with it regularly try the site and onboarding.

Takeaways

  • Know retention and other key numbers before asking an adviser to diagnose a problem.
  • Bring a specific question to office hours and report what changed after earlier feedback.
  • Test whether the customer side of a marketplace has real demand before adding more suppliers.
  • For long enterprise pilots, agree on success measures and actions that would justify a rollout.
  • Ask people unfamiliar with your product to test its explanation, signup, and first use.

Mentioned in this talk

Search inside this talk

What was claimed 17

Show all 17 facts

Related talks