Lumière Wedding Planner
Consumer and pro product, built in-house. Solo end to end: strategy, product design, build, content and growth.
Weddings are planned across spreadsheets, inboxes, and group chats, and every participant needs a different view of the same day. Lumière Wedding Planner was built as a role-aware shared workspace rather than another checklist app.
- Solo
- Strategy through launch, one owner
- 4 roles
- Couples, planners, venues, vendors
- Live
- Market-ready with acquisition running
The situation
Wedding planning runs on spreadsheets, email threads, group chats, and disconnected tools. Couples, planners, venues, and vendors each need a different slice of the same information, and no one is looking at the same version of the truth.
The strategic decision
Bet on role awareness instead of features. One source of truth with permissions per participant, so a couple, a planner, a venue, and a vendor all work from the same plan while seeing only what belongs to them. Not a couples-only checklist product.
What was built
- Shared timelines and calendars across every participant
- Guest list and seating management
- Budget and payment tracking
- Vendor coordination, document storage, and tasks
- Controlled sharing with role-based permissions
- The full brand, website, content strategy, and go-to-market foundation
Outcome
A live, market-ready product with positioning, pricing, website, content strategy, and acquisition channels in place. The strategy and the shipped product came from the same hands.
Proof
The product itself: its workflows, its interface, and the complete path from a market problem to a launched platform.
More work
Agricultural biologicals
Bio Ag Management
One position the sales team, the agronomists, and the site now share.
Hospitality software
Hostly Reviews
An evening a week of replies down to roughly ten minutes a day, nothing auto-posted.
B2B product, built in-house
Lumière HQ
A portfolio structure that supports new products without rebuilding the brand.
Execution
See the rest of the work.
The same standard runs through every build: strategy set and executed by the person who wrote it, with nothing lost between the plan and the launch.