Upverter, YC Founder Story

Company: Upverter Founders: Zak Homuth (CEO), Stephen Hamer (CTO), Michael Woodworth YC Batch: Winter 2011 (W11) Industry: Hardware / Developer Tools / EDA (Electronic Design Automation) Founded: 2010 | Public Launch: 2011 | Acquired: Altium, August 2017 Headquarters: Toronto, Ontario, Canada Outcome: Acquired by Altium, entire founding team joined

---

---

The One-Line Summary

Three engineers from Waterloo looked at a $4 billion EDA software industry that hadn't changed meaningfully in 30 years, asked why hardware design still felt like the 1990s, and built the "GitHub for hardware", then had to pivot their entire business model three years before anyone would pay them for it.

---

Lens 1, The Before State

Who Were They Before YC?

Zak Homuth grew up in Canada and studied Computer Engineering at the University of Waterloo, one of Canada's most respected technical programs and a factory for engineers who end up at the biggest technology companies in the world. He never finished the degree. He dropped out not once but twice, a fact he wore as a badge, not a wound.

Before founding Upverter, Zak had already stacked a resume that looked more senior than most people have at 40: Lead Developer at IBM Deutschland in Germany, Software R&D Team Lead at Infosys Technologies, and Hardware/Firmware Engineer at Sandvine, a telecom infrastructure company. He had also founded a consulting business providing software and hardware services, and an electronics manufacturing service, running both as CEO before pivoting into Upverter.

His co-founders, Stephen Hamer and Michael Woodworth, had a similar arc. All three met in 2004 while studying at the University of Waterloo. They were not first-time students wandering into a startup, they were practicing engineers who had spent years inside the very tools they were about to disrupt.

The Personal Pain They Were Living

The frustration that became Upverter didn't arrive from a blog post or a market research report. It was accumulated scar tissue from years of working as hardware engineers.

Here's what hardware design actually looked like before Upverter: you paid $10,000, $100,000 per seat for software like Altium Designer or Cadence. That software ran only on Windows, only on your local machine, saved files locally, and was completely isolated from anyone else on your team. If you wanted to collaborate on a circuit board design, you emailed files. If you made a mistake in version 3 and needed to go back to version 1, you hoped you'd saved a copy somewhere. If you wanted to reuse a component from a past project, you either rebuilt it from scratch or dug through folders of archived files.

The process of designing a printed circuit board, the physical foundation of nearly every electronic device on earth, still felt like it was running on the logic of the early 1990s. No collaboration. No versioning. No cloud. No sharing.

For Zak and his co-founders, who had lived inside this world professionally, the broken nature of it was not an observation. It was a daily aggravation. The tools that should have been accelerating innovation were, in Zak's words, making the EDA industry "hostile to innovation."

Why They Almost Didn't Look Like "YC Founders"

Upverter came from Canada, not California. The founding team was building for a niche audience, hardware engineers, that most Silicon Valley investors didn't understand. The market was dominated by incumbents that had existed for decades with entrenched enterprise clients and pricing power that seemed immovable.

They were also building something that required genuine domain expertise to even evaluate. You couldn't quickly demo Upverter to a generalist investor and expect them to understand why it mattered. The pain was invisible unless you had spent time trying to design a PCB with legacy tools.

In many ways, this was the opposite of a "hot" YC pitch: no consumer app, no network effects, no viral loop, and a market nobody in Sand Hill Road spent their weekends thinking about.

Key Insight for Aspiring Founders

The most defensible startups often come from industries that outsiders have written off as "solved." Hardware EDA was a $4 billion market that hadn't innovated in 30 years, exactly because everyone assumed the incumbents had locked it up. The founders who had lived inside those locked-up industries are the ones with the real map.

---

Lens 2, The Idea Origin

How the Idea Was Actually Born

By 2008, two years before Upverter was founded, Zak, Stephen, and Michael had already identified the core problem. They had been working as hardware engineers and kept running into the same wall: EDA tools were isolated, expensive, and built for a world where engineers worked alone and didn't share their work.

They had been watching what GitHub did for software developers: making code shareable, versionable, and collaborative. And the question that haunted them was obvious once you saw it from their vantage point, why doesn't hardware have this?

The gap between the software world and the hardware world was enormous. A software developer could write code on any machine, push it to GitHub, have a teammate review it in minutes, roll back to any previous version, and build on top of open-source libraries created by strangers around the world. A hardware engineer doing equivalent work had none of that. The tools were locked to a single machine. The files were private by default. The components had to be drawn by hand from datasheets. There was no common library of reusable parts. Nothing was collaborative. Nothing was in the cloud.

In 2010, they decided to stop complaining and start building. The vision was clear: bring everything that made software development modern and collaborative, cloud, versioning, real-time collaboration, open libraries, sharing, to the world of hardware design.

The First Version

The first version of Upverter was described, correctly, as "GitHub for hardware." It was a browser-based schematic editor, you could open your designs in a web browser instead of installing software, collaborate in real time with teammates, fork designs the way you'd fork a repository, and share your work publicly with a URL.

The technical bets they made were ahead of their time: HTML5 for a browser-native design tool, GitHub-inspired versioning, open-source-first philosophy. They were essentially asking: what if designing a circuit board felt like writing code with a team?

Early coverage called it "the Google Docs of hardware design." That phrase did more to communicate the product than any pitch deck could.

The Signal That Validated It

When they launched the beta and presented at DEMO Fall 2011, one of Silicon Valley's oldest product showcases, the response from the hardware and maker community was immediate. Engineers who had been tolerating the status quo for years finally had a word for what they'd been missing.

The open hardware movement, which was gaining momentum through projects like Arduino and efforts like Facebook's Open Compute Project, needed exactly what Upverter was building. Zak noted that Facebook's hardware team had publicly said that the tools for open-source hardware design "aren't there yet", and that most contributions to their open hardware projects had to come from large companies because individual engineers couldn't afford the required software. Upverter was the direct answer to that problem.

The Pattern This Follows

Upverter fits what you might call the "GitHub moment" idea archetype: take a workflow that works brilliantly in one domain (software development) and port the core insight, collaboration, versioning, openness, to an adjacent domain that is still operating as if it's 1995. This pattern has generated some of the most durable B2B companies: Figma did it for design, Notion did it for documents, Upverter tried to do it for hardware.

---

Lens 3, The Application Anatomy

What Made Their Application Work

Upverter applied to YC W11 with a clean, technically credible pitch that connected a massive underserved market to a clearly understood analogy: