WhoBuilt

Startup Technology

Oct 10, 2018· 1 h 0 min· 121K views·Watch on YouTube

Speakers

Jared Friedman of Y Combinator moderates a Startup School panel with technical founders from PlanGrid, Segment, ObEN Reality, and Second Measure on building products, engineering teams, and startup technology.

The companies and their technology

Ralph Gootee describes PlanGrid’s blueprint collaboration tools and its AWS-based stack, which spans Python, Go, mobile apps, web, and Windows. Calvin French-Owen explains how Segment routes customer data through hundreds of tools using AWS, ECS, Kafka, and Go. Diana Hu discusses ObEN Reality’s augmented reality backend and C++ code, while Lillian describes Second Measure’s credit card data analysis platform and its data science and engineering teams.

Finding a first product

Gootee’s first blueprint viewer took a month to build after he discovered that large PDF files overwhelmed early iPads. Segment’s founders tried a lecture tool and a user analytics product before testing a shared data API; a landing page collected about 500 emails, and they built a hosted version in a week. Hu’s team spent time making augmented reality algorithms run well on phones, then found interest from game developers. Second Measure used quick user testing to learn that customers needed guided insights rather than an unrestricted data exploration tool.

Balancing speed with engineering practices

The panel says early teams often prioritize shipping and learning, while adding tests, CI, and security as users, systems, and teams grow. Segment described moving from hackathon-style development to stronger testing and data handling, especially after signing enterprise customers paying more than six figures annually. Gootee says PlanGrid treated security and scalability as essential from the start because construction projects depend on the software, including projects with hundreds of thousands of blueprints.

Adapting process and setting expectations

Panelists favor adjusting workflows to the team’s size instead of following a methodology rigidly. They discuss daily stand-ups, weekly planning, documentation, time-boxing, one-to-ones, and OKRs as tools teams can adopt when useful. For deadlines, they recommend communicating uncertainty, accounting for release constraints, and gathering independent estimates from team members.

Hiring, outsourcing, and learning from users

The founders caution that outsourcing core technology can also outsource early product learning, though contractors may help with well-defined work or trial hiring. They describe different choices on remote work, shaped by company needs, communication, and documentation. In the audience discussion, panelists advise showing products to users early and often, and one suggests building disposable prototypes before committing to a first version.

Takeaways

  • Test the hardest product assumption with a small prototype before building a full system.
  • Use the technology your team knows when speed and learning matter most.
  • Add engineering process as system complexity, team size, and customer reliance increase.
  • Treat security and reliability according to the real cost of failure for your customers.
  • Keep core product learning close to the company, and make user feedback part of development.

Mentioned in this talk

Search inside this talk

What was claimed 22

Show all 22 facts

Related talks