... everyone. Raffay here. Building Finly AI: voice/text expense entry, receipt & PDF import, and spending insights that are actually useful instead of another spreadsheet with extra steps. Background's more backend/infra than finance, so the funny part is the AI side was the easy build. The trust and security work that comes with touching people's money data has eaten way more of my time than expected. No big manifesto, just building and trying to get it right before ...

... instrument has to be built before you know what youre looking for. once you know, you scope it without noticing. Comment from Raffay Sajjad(@raffay_sajjad): The email signup one got me. Had a decent list built up before finly's first version even worked properly and read it as validation. Actual activation once people could get in was way lower than the signup number implied. Signups measure curiosity, not whether someone's willing to change what app they open ...

... were building. Comment from Anna Ludwinowski(@anna_ludwinowski): @austinbuhl  Interesting that you land on problem-first for Salestrics but demo-first as a viewer. Do you think there's a difference between what convinces you to look closer versus what you'd actually put in your own launch copy? And on "most startups" - is there a specific kind of team you picture hitting that per-seat pricing wall, or is it genuinely everyone past a certain size? Comment from ... ... Ludwinowski(@anna_ludwinowski): @picspace  "What changed for the user" instead of "what did I build" is exactly the right swap! It's the same trap in enterprise IT and in most launches here, just dressed differently (feature list vs

... concentration Gmail and not only for communication, but also for storing ideas and sending myself email reminders for posts and one I am working on : StartupHQ to organize competitor research, validate ideas, and keep my roadmap focused. Comment from Sumit Singh Chauhan(@sumit_singh_chauhan): My 5: 1. VS