I recently sat down with Waseem Daher, co-founder and CEO of Pilot, a company that specializes in bookkeeping, tax prep, and CFO services for high-growth startups. Before Pilot, he co-founded two other startups with the same group of co-founders, including Ksplice, which was acquired by Oracle in 2011, and Zulip, which was acquired by Dropbox in 2014. As a product leader, I was especially interested in his repeatable frameworks for idea validation and building conviction.
We focused on the earliest days of Pilot. Waseem took me behind the scenes of the ideation stage and walked through how the founding team gained enough conviction to actually start building. He also explained why Pilot landed on its human plus machine model, with a software component in addition to employing full-time accountants and tax preparers to partner with customers. That hybrid approach resonated with me because it aligns technology leverage with trusted, high-touch service where precision and context matter.
From a product discovery perspective, I mapped his approach to a few principles I use with my teams: define the problem boundary tightly, de-risk the riskiest assumptions first, and run short learning loops that translate directly into product decisions. In Pilot’s case, the early tests weren’t about flashy features—they were about proving that a human-plus-software workflow could reliably deliver accuracy, speed, and peace of mind to finance leaders at startups.
We then dug into building Pilot’s ICP and getting the product into the hands of paying customers. Waseem shared practical tips for framing conversations with potential customers to make sure you’re building a must-have product that solves hair-on-fire problems, not a nice-to-have. I’ve found similar tactics effective: insist on clear stakes and urgency, test willingness to pay early, and probe for budget ownership and implementation appetite. When discovery is anchored in real pain and committed timelines, founder-led GTM becomes a force multiplier.
Looking ahead, he outlined how he prioritizes which offerings to add to Pilot’s product suite. I appreciated the disciplined focus on adjacent problems where the core strengths of the human plus machine model create an unfair advantage. This mirrors my own product roadmapping lens: measure outcomes over output, earn the right to expand by nailing the core job-to-be-done, and stage extensions that compound value for the same ideal customer profile (ICP).
If you’re a founder—or aspire to be one—there’s a clear playbook here: validate ideas by stress-testing real urgency, crystallize your ICP early, and use learning-driven iterations to progress toward product-market fit. For product pros, the takeaway is to balance operational excellence with software leverage, and to let customer pain—not feature ambition—set the pace. Pilot’s journey offers crisp, repeatable patterns for zero-to-one execution and beyond.
Inspired by this post on First Round.
Leave a Reply