Post your build ideas
LocalASO Track App Store keyword ranks in every countryFind your vibe. Find you job which is just for you and your dataDealtab Brand Deal Tracker That Does The Work For YouIs Major Cooked? Free AI risk score + roast for your college majorWiral.Social LinkedIn, Scheduler, Scheduling Tool, Ghostwriter
Solo Era solo activities, solo maxxing, sidequests, challengeCadentiq daily routine, wellbeing, self care, healthy habitsTexeva Your businessKeepsake Project Management, Freelancers, DesignersOrvyx AI You create
← All ideas
Ppeekly_appEvents·

GoFundMe, but for weddings

Talk to peekly_app@peekly_app

Reach out if you want to build it, build it together, or just ask what they had in mind.

A couple sets up a page for the wedding, and guests contribute to specific things rather than handing over an envelope. The photographer, the flowers, a night of the honeymoon. Everyone sees what's covered and what still isn't. Wedding registries already exist and they are stuck in a world where couples needed a toaster. Most people getting married now have a flat full of things and would rather have help with the €18,000 the day actually costs. Asking for money directly feels crass; asking someone to cover the cake does not. The hard part is entirely social, not technical. There is a line between "help us celebrate" and "pay for our party", and it moves by culture, family and generation. The framing of every screen decides which side you land on. Second: guests must be able to give without an account, in thirty seconds, from a link in a WhatsApp group. The moment grandmother has to register, it fails. And the fees are visible in a way they aren't elsewhere. Taking 5% of a wedding gift feels different from taking 5% of a subscription — probably needs to be the guest's choice to cover it, stated plainly.

Generated build prompt

Your starting point. Copy it and start building.

Opens in your chosen app. Desktop app or sign-in may be required.

View full prompt
Build goFundMe, but for weddings.

Context: A couple sets up a page for the wedding, and guests contribute to specific
things rather than handing over an envelope. The photographer, the flowers, a
night of the honeymoon. Everyone sees what's covered and what still isn't.

Wedding registries already exist and they are stuck in a world where couples
needed a toaster. Most people getting married now have a flat full of things
and would rather have help with the €18,000 the day actually costs. Asking for
money directly feels crass; asking someone to cover the cake does not.

The hard part is entirely social, not technical. There is a line between "help
us celebrate" and "pay for our party", and it moves by culture, family and
generation. The framing of every screen decides which side you land on.

Second: guests must be able to give without an account, in thirty seconds, from
a link in a WhatsApp group. The moment grandmother has to register, it fails.

And the fees are visible in a way they aren't elsewhere. Taking 5% of a wedding
gift feels different from taking 5% of a subscription — probably needs to be
the guest's choice to cover it, stated plainly.

Requirements:
- Ship the smallest version that delivers the core value above, nothing more.
- Pick a stack you can deploy in a day, and state the choice before writing code.
- Handle the empty state, the error state and the offline case explicitly.
- Pricing to build toward: Free to set up, small percentage on contributions with an option for the guest
to cover it. Charging the couple upfront kills it — nobody pays to ask for
help.

Start by listing the screens, then build them one at a time.