Bharat in BetaRunning your wedding
Source
- The Ken (opens in a new tab)The Great Rewiring / Sixteen OpeningsOpenings released: 31 Aug 2026
The idea
Families chase vendor discovery, quotations, commitments and delivery while managing preferences, budgets and post-event administration. Source-proposed direction: Coordinate selected vendor workflows, milestone-based payments and physical logistics.
Why this is interesting
- A wedding is a temporary organization with many vendors, decision-makers, payments and physical dependencies but no shared operating system.
- Families repeatedly reconstruct vendor status from messages, calls and spreadsheets, especially when responsibilities shift.
- The market is large, but a useful first product needs a narrow workflow where coordination failure is both common and costly.
Possible starting points
Vendor commitment tracker
Keep quotations, decisions, contracts, deposits and delivery milestones in one family workspace.
Wedding-day operations
Coordinate arrivals, physical items, responsible family members and last-minute changes.
Milestone payment workflow
Tie vendor payments to agreed deliverables and documented approvals.
Questions to answer
- Which vendor category creates the most repeated coordination failures?
- Who becomes the active operator: the couple, a family member, a planner or the venue?
- Can the product stay useful across the planning lifecycle without demanding constant data entry?