Project Wedding, YC Founder Story

Company: Project Wedding (projectwedding.com) Founders: Joe Wong, Margaret Wong & Srini Panguluri YC Batch: Winter 2006 Industry: Consumer Web / Wedding Tech / Marketplace Founded: 2006 | Launched: April 2007 Team Size at Launch: 2, 3 Exit 1: Acquired by eHarmony (~2008) Exit 2: Acquired by WeddingWire (July 2011) Peak Traffic: 1 million+ monthly visitors

---

---

The One-Line Summary

Three founders walked into YC with a web desktop OS nobody wanted, pivoted mid-stride into wedding planning, sold the company twice, and then did it all over again a decade later with Zeus Living. This is a story about the power of the pivot, the courage to abandon your original idea, and what happens when a real couple builds a product for real couples.

---

Lens 1, The Before State

Who Were They Before YC?

Joe Wong, Margaret Wong, and Srini Panguluri were engineers and builders drawn into the earliest wave of web application development in the mid-2000s, a moment when the internet was transitioning from static pages to dynamic applications, and a whole generation of developers believed you could rebuild the desktop computer experience inside a browser.

Joe and Margaret were a couple, a rare dynamic in the startup world, who shared both a personal life and an intellectual obsession with the web. Srini Panguluri had a background that spanned enterprise software (Oracle) and early-stage building, with a deep interest in how consumer products could be designed from first principles. Together, the three had the technical chops to ship quickly and the personal trust that comes from genuinely knowing each other outside of a boardroom.

None of them came in as "wedding industry experts." They were not wedding planners, event coordinators, or even particularly focused on the consumer wedding space before the pivot. They were software builders who happened to be planning a real wedding and discovered firsthand just how broken the process was.

The Personal Pain They Were Living

The founding insight for Project Wedding was not abstract market research. Margaret and Joe were a couple planning their own wedding, and the experience was, in their words and the company's founding description: hard.

Finding reliable wedding vendors in 2006, 2007 meant navigating a patchwork of phone book listings, outdated websites, wedding magazines, and word-of-mouth referrals. There was no centralised review system. No way to compare photographers, florists, or caterers by price, region, or quality. No place for real brides and grooms to share honest experiences. The dominant player, TheKnot.com, had the brand name but the community experience was thin and the vendor discovery was clunky.

The problem was lived, not imagined. And when founders solve a problem they've personally experienced, especially with real stakes attached, the product instincts are sharper than anything a survey could produce.

The Pivot That Most Founders Fear

Here is the part most people don't know: Project Wedding was not the team's first YC company. Joe, Margaret, and Srini had originally entered YC with a product called YouOS, an ambitious attempt to build a full operating system experience inside a web browser. Think: a desktop with folders, apps, and windows, all running in a browser tab, years before Chrome OS or cloud computing became mainstream vocabulary.

YouOS got attention. It was technically impressive. Hacker News noticed it. But it was solving a problem that users weren't willing to pay for or change their behaviour around at that time. The traction just wasn't there.

The pivot from a web OS to a wedding planning site might look, on the surface, like an enormous leap. It was. But the underlying thread was consistent: the team was obsessed with making complex real-world systems simple and accessible through a web interface. Whether it was a desktop environment or a vendor marketplace, the DNA was the same, take something messy and fragmented, and make it elegant.

Key Insight for Aspiring Founders

Your original idea is not sacred. Your team and your problem-solving instincts are. Joe, Margaret, and Srini didn't abandon their YC journey when YouOS stalled, they redirected it. The YC batch gave them the framework, the credibility, and the urgency to find something that worked. The pivot wasn't failure. It was the job.

---

Lens 2, The Idea Origin

How the Idea Was Actually Born

The story on the YC company page is deceptively simple: "In 2007, a couple started Project Wedding to tackle this problem." That couple was Joe and Margaret, and the problem was their own upcoming wedding.

In 2006, 2007, the wedding market was a $70+ billion industry running almost entirely offline. Vendors had no digital reviews. Brides had no peer community online. Planning tools were essentially glorified checklists in wedding magazines. TheKnot existed but felt like a static brochure, not a living community. The analogy the team understood intuitively: Yelp was transforming restaurant discovery through real reviews and community. Wedding vendor discovery needed the same revolution.

The original YouOS codebase, a web application framework they'd spent months building, turned out to be genuinely useful as the technical scaffolding for a new kind of community site. Hacker News commenters even noticed this at launch: "It's the YouOS company. There's YouOS code under this." The technology was repurposed. The mission was redirected.

The First Version Nobody Asked For, Then the One They Did

The early version of Project Wedding launched in April 2007 with vendor listings, customer reviews, wedding photo galleries, forums, and editorial content. It was modestly designed and clearly bootstrapped, but it had something that TheKnot didn't: a real community voice.

Brides-to-be in Northern California began finding it organically. Within weeks of launch, the site was receiving 10,000 page views a day just from that region, before any marketing budget, press coverage, or paid acquisition. The community content was what created the loop: real brides sharing real reviews attracted more brides, who left more reviews, which attracted more vendors.

The Signal That Validated It

Within a year, eHarmony, the online dating company with millions of newlywed users who had literally used eHarmony to find their partners, came calling. The strategic logic was obvious: eHarmony matched couples; Project Wedding helped them get married. The acquisition made eHarmony the owner of the full romantic journey from first date to wedding day.

When a company in an adjacent space decides to buy you rather than build against you, that's the strongest possible signal that your product is real.

The Pattern This Follows

Project Wedding fits the "Yelp for X" idea archetype, taking a trusted, community-review model from one category and applying it to a fragmented, high-emotion, high-spend vertical where users desperately need social proof. The wedding industry was particularly ripe: purchases are large (photographers cost thousands, venues tens of thousands), decisions are made rarely, and bad choices are catastrophic. Exactly the conditions where reviews matter most.

---

Lens 3, The Application Anatomy

The Unusual Context, A Pivot Inside YC

Project Wedding's YC entry is genuinely unusual because it wasn't a fresh application. The founders were already in the YC ecosystem through YouOS (W06). What happened was an in-batch or post-batch pivot, the team realised YouOS wasn't finding the traction that justified continued pursuit and redirected their energy and YC relationship toward a new problem they were living personally.

This is important for aspiring founders: YC is not just funding an idea. It's funding a team's ability to find and execute on the right idea. The Wongs and Srini demonstrated that exact quality, they didn't stubbornly defend a failing product, they course-corrected with speed and conviction.