Follow information through the wedding
I connected guest lists to personal RSVP links and a wedding website. Replies update the planner, where the couple can seat guests, track the budget and follow a checklist and day-of timeline.
Wielki Dzień
One connected product for the couple planning a wedding and the studio helping deliver it.
The problem
Guests, RSVPs, payments and deadlines were spread across different tools. The product also had to reflect Polish wedding details, including different kinds of deposits, while giving the studio a practical process for inquiries and offers.
My part
Solo product and engineering work across the web product, CRM and native apps. The recorded couple and guests are synthetic.
What this shows
I can design around two different users of the same service and connect their workflows without flattening the details of the business.
Where it started
Wielki Dzień connects an inquiry-response engine, a studio CRM and a wedding planner for couples. The response engine imports marketplace inquiries, prepares contextual AI replies and routes them to a person for approval. The two sides share a need for organized information, but use it in very different ways.
See it in action
English AI narration · Subtitles included · Play with sound, or read the transcript.
Read the video transcript
0:00 I built a wedding planning product that brings guests, decisions and deadlines together. This couple is fictional.
0:14 The dashboard makes progress visible: replies, budget, checklist and time left before the wedding.
0:24 Guests stay in groups, with plus-ones, personal reply links and spreadsheet import and export.
0:35 Replies from the wedding website arrive here automatically, including dietary needs and messages.
0:44 The seating plan connects each guest to a table. Couples can rearrange the room and export the result.
1:03 The budget compares planned and paid amounts, with separate handling for different deposit types.
1:14 A reusable checklist turns the wedding date into practical deadlines for each task.
1:24 Each couple also gets a website, with their story, venue, schedule and reply form.
1:41 The product connects planning, websites, the studio's customer management and native mobile apps.
The decisions behind the product
Model the details that matter locally
The budget keeps binding deposits separate from refundable advances. Seating exports to printable plans and place cards, while eight website themes let couples publish their own information.
Support the business behind the experience
The studio CRM handles leads, priced offers and electronic signatures. AI drafts replies to marketplace inquiries, with a person approving each reply before it is sent. Native iOS and Android apps extend the planning flow.
What came out of the work
Replies ready for review in minutes
Across 25 matched production drafts from 18 September to 8 October 2026, the median time from an incoming inquiry to an AI reply draft was 3.96 minutes. Staff approve or edit the reply before sending; 21 AI-prepared replies had been sent.
A connected planning workflow
A guest's answer moves from the wedding website into the planner, with seating, budget and deadlines in the same product. The business side has its own lead and offer workflow.
Measured search reach
Google recorded 4,433 search clicks across April to September 2026. Monthly clicks rose from 222 in April to 940 in September, a 323.4% increase between those months.
- ~4 minto prepare an AI reply for reviewMedian 3.96 min · 25 drafts · 18 Sept - 8 Oct 2026. A person approves sending.
- 21AI-prepared replies approved and sentProduction outbox · 18 Sept - 8 Oct 2026
- 609inquiry conversations available to the response workflowImported message history · July 2024 - 8 Oct 2026
- 8wedding website themesChecked 6 Oct 2026
- 4,433Google search clicks in 6 monthsGoogle Search Console · 1 Apr - 30 Sept 2026
- +323.4%Monthly search click growthSept 2026 vs Apr 2026
Search metrics use the scope shown with each result. Search position is an average across searches.
Traffic over time
Google Search ConsoleGoogle search clicks
+323.4% · Sept vs Apr 2026Domain property: wielkidzien.pl (all subdomains)
- Latest month
- 9401 Sept - 30 Sept 2026
- First month
- 2221 Apr - 30 Apr 2026
Source, methodology and monthly data
Open Google Search Console report · Checked 8 Oct 2026
Domain property: wielkidzien.pl (all subdomains). Provider timezone: America/Los_Angeles.
- Six complete calendar months: 1 April to 30 September 2026. Current is September; comparison baseline is April. Both comparison months have 30 days. This is not a comparison against the preceding six months.
- Final web-search data, all countries and devices, America/Los_Angeles reporting timezone. Search clicks are not website visits or unique visitors.
- Domain properties include all subdomains with property aggregation. Documentation pages retain exact page filters from the preceding evidence collection and measure documentation interest, not adoption.
- Monthly chart values and the six-month total are reconciled with independently queried totals.
- The percentage, where shown, compares September 2026 with April 2026, the last and first complete months of this window.
| Month | Google search clicks |
|---|---|
| 1 Apr - 30 Apr 2026 | 222 |
| 1 May - 31 May 2026 | 643 |
| 1 Jun - 30 Jun 2026 | 581 |
| 1 Jul - 31 Jul 2026 | 886 |
| 1 Aug - 31 Aug 2026 | 1,161 |
| 1 Sept - 30 Sept 2026 | 940 |
PostHog recorded activity488 pageviews in 28 days
wielkidzien.pl and www.wielkidzien.pl only · UTC
Recorded activity is affected by consent, blockers, tracking gaps and internal traffic.
| Metric | 7 Sept - 4 Oct 2026 | 10 Aug - 6 Sept 2026 |
|---|---|---|
| Recorded pageviews | 488 | 781 |
| Recorded sessions | 412 | 668 |
Inside the implementation
Explore the features, architecture and quality checks
What I built
- A guest list with groups, plus-ones, CSV import and export, and a personal RSVP link for every guest
- An RSVP inbox fed by the wedding website: yes, no or maybe, with diet, a message and the date of each answer
- A seating plan: drag a guest onto a table, or click a guest and then a table, drag tables around the room, and export the plan and place cards to PDF
- A budget per category, planned against paid, that keeps a zadatek (a binding deposit, lost if the couple backs out) apart from a zaliczka (a refundable advance)
- A 39-task checklist from a template, each task due a set number of months before the wedding, plus the wedding-day timeline
- A wedding website per couple, built from 15 kinds of sections in one of 8 themes
- An admin CRM: leads in 11 stages, priced offers with a public link, and e-signature through Documenso
- A bridge to the Wesele z klasą marketplace: Claude drafts replies to open inquiries, and each draft waits for a person to approve it in the CRM or Slack
- Native iOS (SwiftUI) and Android (Kotlin, Jetpack Compose) apps with the dashboard, guests, budget and timeline
How it works
- GuestsThe couple adds guests or imports a CSV, and each guest gets a personal RSVP link.
- WebsiteThe wedding website goes live in one of 8 themes, with story, venue, day plan, FAQ and gifts.
- RSVPAnswers with diet and a message land in the panel and update the counts on the dashboard.
- SeatingGuests go to tables on a canvas, and the plan and place cards export to PDF.
- Budget and checklistBudget, checklist and the wedding-day timeline stay in the same panel.
Quality and reliability
- The package that builds priced offers is checked offline, without external services
- Passwords are hashed with Argon2
- AI drafts for marketplace inquiries never go out on their own: each one waits for a person to approve it
Technology
Explore another problem I worked on
- Sztuka HarmoniiConnected four booking platforms into one calendar, with patient booking and practice operations around it.
- EEG biofeedback demoMade recorded EEG signals explorable in the browser, with local file analysis that keeps the recording on the device.
- Vibethon.ioBuilt the submission, demo and weighted-voting flow for an internal hackathon in one calendar day.