A project management platform for wedding planners
A web project management and collaboration platform for wedding planners and the clients they work with. Multi-role workflows for scheduling, billing, forms, decision-tracking, and guest and seating management, built as a full-stack MVP.
- Geography
- Seattle, Washington, United States
- Stage
- Early-stage startup
- Team
- 1 senior + 2 mid full-stack engineers, 1 product designer, 1 product owner
The situation
Wedding planning runs on a chaotic mix of email threads, spreadsheets, paper contracts, and improvised tooling. Plannerd, a Seattle-based startup, set out to replace that with a single platform serving wedding planners, the couples they work with, and the vendors involved in every wedding.
The brief was a full project management and collaboration hub: scheduling, billing, form sharing, progress tracking, decision management, guest list and seating, and design inspiration. All of it had to ship as a clean MVP that the founder could put in front of pilot planners and refine from there.
What we built
The engagement was a fixed-scope AI Product Engineering build. Plannerd ran with a senior full-stack engineer, two mid full-stack engineers, a product designer, and a product owner. The build was a conventional SaaS application; the strategy file flags an "AI Wedding Planner" framing the original page used, and that framing is dropped here because the engagement did not ship AI features.
The platform is split into role-based workflows. The planner role manages the engagement (decisions, budget, vendors, design inspiration). The client (couple) role moves through the same surfaces with permissions trimmed to what they need to see and approve. Both roles share guest list and seating management, with conflict detection at the table level.
Tech stack is React with TypeScript on the frontend, Django and PostgreSQL on the backend, AWS for hosting and infrastructure, GitHub Actions for CI. The component architecture was deliberately built for scale: each section (decisions, guests, seating, design, billing) is its own module so the founder can iterate on one surface without touching the others.
The dashboard design and UX work landed as a coherent product rather than a stitched-together prototype, which mattered for the founder's pitch to pilot planners.
Outcome
-
MVP shipped with planner, client, and admin role workflows in production
-
Modular section architecture (decisions, guests, seating, design, billing) iterable independently
Plannerd shipped as a functioning multi-role SaaS MVP with the full feature set the founder briefed. The platform is operational and in use by planners; no quantified user metrics are on file in the workspace source, so Section 5 stays at the engagement-deliverable level rather than padded with claims that are not verified.
Engagement line