We launch a feature here on Thursday, and the landing page section for it is the one new users keep bringing up on calls and in replies, more than the hero, more than pricing.
It is a simple block. One sentence: see the change before it ships. One picture of a working copy of your site with the change on it, and two buttons: approve, or send it back.
I think it works because it answers the question people actually have about any tool that writes code for them: what if it gets it wrong? The answer is not trust us , it is look at it first . The other sections explain what it does. This one removes the fear.
Curious what the equivalent section is on your landing page: the one that answers the fear rather than describing the feature. And for those who have run the test, did it convert better than the feature description?
Hi everyone! I'm Filipe, from Portugal. I build Mayora, a shared budget for people who share money with someone: a couple, a household, flatmates. Everyone logs what they pay and sees the same month at the same time, bills only count as spent once they're paid, and bank statements are read on the phone instead of being uploaded. It launches here tomorrow. Happy to talk about shared finances, building solo with Expo and Supabase, or anything else, and I'd love to hear what you're working on.
Hi! I'm Filipe, and tomorrow I'm launching Mayora here, a shared budget for couples and households. I built it because my partner and I kept ending the month with two different ideas of what we had spent. Before the launch I'd love to hear how you do it today: a spreadsheet, a joint account, an app, or nothing at all? And what makes you give up on a budget?
