I overengineered wedding invitations so badly that users can now code their own invite sites and host them on my platform
So about 8 months ago I started building iwed.ai, what I thought was a simple tool - make pretty wedding invitation websites in 60 seconds, no design skills needed.
Fast forward to today, and uh... things got a little out of hand.
Since I posted about it 4 months ago on this subreddit, we have already 10x'd our numbers π - thousands of users on the platform now, collectively managing lacs of guests and crores in wedding budgets. Some of the invite websites have hit 2,000+ impressions and 1,000+ unique guests viewing them π€―. 60+ new accounts signing up every day π. Dozens of paid users already, and honestly, what they are paying for surprised me.
- Host more variations of wedding invite websites
- Custom Artwork and Logo for their wedding website
- AI photo generation, where couples upload their pics and get pre-wedding style photoshoots in 40+ themes
- Snaps, which is basically a private Instagram for your wedding guests to access and share event photos and videos in full resolution.
But here is where the overengineering kicks in...
The original idea was simple: Create a wedding invite website - type a prompt, get a wedding invite.
But then users wanted more control. So we kept adding.
- more templates
- custom sections
- background music
- photo gallery
- password protection
- and so on
https://i.redd.it/86mjaodvrlch1.gif
But the requests wouldn't stop!
Can I have a different background color? Can I add 2 timelines? Can I customise how the RSVP form looks like? Can you do something like this invite website? I made something on Claude, can you host it?
Who would have thought, user's always want more! π€·ββοΈ
I did what any 'vela' person would do, I overengineered the solution. I built a mini-lovable, but it felt incomplete so I made it available through MCP!
https://i.redd.it/x5oykej9nlch1.gif
Now? You can design a full prompt-based custom wedding website (think mini-lovable, replit, base44)
AND if you are a technically inclined user, you can literally build your own wedding invite site using Claude or Cursor (we added MCP support), hit one button, and host it on iWed.
https://i.redd.it/77l7ud8oolch1.gif
Password protection, impression tracking, RSVP management, guest list management - all of it just works.
So now we are this weird hybrid: a prompt-to-site tool for non-technical users AND a hosting layer for people who want to code their own stuff. The MCP integration means dev-savvy couples can build their dream invite in their editor of choice and deploy with a click.
Honestly not sure if this is genius or symptom of scope creep, but the numbers are going up and I look forward to seeing how couples adopt these new customisation tools. Happy to answer questions about the stack, the MCP integration, or how we're handling the "platform vs. builder" duality.
Posted Jul 11, 2026, 1:33 PM UTC