WedMap
WedMap was a wedding marketplace that tried to help couples find and book venues and service providers online.
View original storyProduct snapshot
What it was
WedMap listed wedding locations and service providers and aimed to let couples find and book wedding services online.
Who it was for
Problem / value
It promised a more digital, centralized way to plan weddings instead of relying on scattered offline information.
Core workflow
Couples would discover wedding locations and vendors, while suppliers would get exposure, leads, or bookings through the marketplace.
Core dependency
A clearly validated paying side, enough high-quality suppliers, and a narrow transaction workflow that could repeat.
Product form
Pricing model
The model changed from listings to lead generation to revenue sharing. The source reports about $2,000 in monthly revenue, but stable pricing details are not disclosed.
Competitors or alternatives
What happened
Summary
WedMap had a fast prototype and some revenue, but failed after the team built too broadly before understanding users, monetization, and marketplace operations.
Outcome
WedMap shut down after nearly three years despite some revenue and marketing activity.
Core risk
A two-sided marketplace can look promising while still lacking a clear paying side, narrow workflow, and cheap path to product-market fit.
Shutdown reason
The founder points to a mix of team limits, lack of market experience, insufficient customer research, weak prioritization, resource pressure, and premature platform complexity.
Demand signal
The team later said they did not speak to enough users or understand what people would really pay for. Some revenue appeared, but the paying workflow was not stable enough to guide the product.
Distribution issue
Growth relied on many channels at once, including social, email, ads, SEO, events, and sales. The founder said the team tried many things but did none of them really well, while sales remained manpower-heavy.
Timeline
- Founded to digitize wedding planning
- Built the first prototype in one month
- Rebuilt toward an Airbnb-style marketplace for venues and vendors
- Changed monetization from listings to lead generation to revenue sharing
- Reached about $2,000 in monthly revenue
- Stopped active work in June 2018 and shut down the company at the end of 2018
Before you build
Why it matters
Marketplaces burn time on both product and distribution. If the team builds the platform before proving the transaction loop, every extra feature adds complexity without clarifying demand.
Primary check
Talk to both sides, prove the paying workflow, and use off-the-shelf tools before building a full marketplace platform.
Checklist
- Who pays first and what proof would make them pay again?
- Can the first workflow run manually for ten transactions?
- Which feature would you delete if the goal is learning, not platform scale?
- Talk to couples and suppliers before defining the feature set
- Run one paid lead or booking workflow manually
- Choose one buyer and one pricing test
- Delay custom platform work until repeat transactions are visible
Relevant if
- You are building a local marketplace or vertical directory
- Your business model could charge either side of the market
- You are tempted to build a custom platform before proving the workflow
Less relevant if
- You already have repeat paid transactions in a narrow workflow
- You are digitizing an internal process with one buyer instead of a two-sided marketplace
Pre-build tests
- Sell a paid venue-lead pilot before building supplier dashboards
- Use a no-code or WordPress marketplace setup to test search and inquiry flow
- Interview recent couples and vendors about where planning breaks and what they already pay for
Transferable lessons
- Interview both sides before deciding features
- Pick one monetization model to test before expanding scope
- Use off-the-shelf tools until repeat transactions justify custom software
- Treat early revenue as a signal to investigate, not proof that the full marketplace works
If you build this today
Start with one wedding workflow, such as venue lead qualification, sell a paid pilot to one side, and run the marketplace with existing tools until repeat bookings prove the model.