Founder, Line Free India — queue-free booking & token system for salons. First-year BTech CSE student, building in public. I also build SatyamLabs & CodeAtlas.
My first long-form video is live 🎬
I tested 10 FREE AI tools that outperform paid ones — study, voice, design, jobs. No subscriptions, no watermarks.
Watching it? I need honest feedback more than praise 🙏
https://t.co/2rtMUZ5OkN
@openanysi@odd_joel This is the clean split I needed — approval for anything that moves or cancels a booking, and API spend managed on its own. I was bundling them into one guardrail in my head. Thanks, that's going into how I wire it.
@dflow_sh@odd_joel That framing clicked — cap limits damage after, approval stops it before. For salon bookings I'll take approval first: a wrongly cancelled booking costs a customer, not just money. API spend cap comes second. If you could only ship one first on a small app, which would it be?
@gabriel_sstech@Mashruf32 Exactly — every salon I visited still runs on a notebook, and it breaks the moment a walk-in and a booking collide. One view of who's waiting and who's booked is the whole idea behind what I'm building. Thanks for getting it — what would you show first on that screen?
Question for salon owners: would you rather gain 10 new customers a month, or lose zero regulars to long waits? I'm building Line Free India and keep going back and forth on this — new customers feel like growth, but a regular who walks out never comes back. Which would you pick?
@YashHustle_22 Solo, for now. I'm a first-year student building a salon booking app — the niche is mine to learn, and solo means I can change direction in an afternoon. I'd want a co-founder only when the bottleneck is clearly a skill I don't have, not just loneliness.
@NimbicaAI Directories surprised me in the wrong way — views, not bookings. What actually surprised me: one salon owner telling another owner. No SEO, no listing, just a busy Saturday where the queue actually moved. Referrals from users beat every directory I tried.
@Doublerightvc@morgancacm Agree — but how do you actually get those 8 to talk? My salon owners won't take a call, they answer between haircuts on WhatsApp. So I ask one question at a time, in the chat they're already in. Conversations, not surveys.
@morgancacm Honest question on your numbers: 24 users before, 8 now on the waitlist — did the 16 drop off, or were they a different count? My 'users' vs 'waitlist' numbers never match either, and I'm trying to figure out which one to actually trust.
@zakir_digital Filling mine in: For salon owners, who are tired of walk-in queues eating their day, Line Free India gets customers booked in advance without the phone calls and waiting. Does that pass your test, or is 'booked in advance' too vague?
@simplydt@zakir_digital Same friction, different side: my salon customers pay at the counter in cash/UPI, so I skipped invoicing them entirely. The salon pays me monthly, the customer pays the salon as usual. Splitting who pays whom removed the whole invoicing headache.
@zakir_digital My stack is embarrassingly small — one tool per job, and 'talk to salon owners' is the job no tool covers. The moment I added a second analytics tool I stopped looking at either. Which job in your list do founders over-tool first?
@tryorbix I stopped chasing waitlist numbers. What worked for me: posting the actual problem — salon owners losing customers to walk-in queues — and talking to them in person. A waitlist of strangers never booked anything; a few salon owners who'd tried it did.
@ParveshBurnwal Honest question: which of these 50 actually brought you a paying user? I tried a few directories and got views, not bookings. Walking into salons and asking owners to try it beat every list for me. Lists feel like progress, talking doesn't.
@ClaylightAI@steffdoesthings The mum test is real. My first 'users' were friends who'd never book a salon through an app — polite yes, zero repeat use. Now I only count a salon owner who books a real customer through it. That's my 10-people test.
@X4DX54 For my salon booking app I'm going paid subscription — salons pay for reliability, not code. Open source feels generous, but who answers the 9am 'my bookings broke' call? Curious what tipped it for you?
@MaxHirsch13 Agree on the feedback loop, but does it work when your users aren't online-community people? My salon users live on WhatsApp, not Discord — so I'm testing a small WhatsApp group instead. Same idea, different room?
@Kedeodev Users, always. Had this exact one in my booking flow — AI swore the slot logic was right, tests passed, then a walk-in and a booking collided at the same chair. The bug was in my assumption, not the code. The user is the only test that can't lie.
@SuiBuilds C — it's still the one I reach for when I want to actually understand what's happening under the hood. Which pre-2000 language would you still start a new project in today?
@pingvikas Solid method — but step 4 is where most people stall. 'Find what's missing' usually means talking to the users, not the dashboard. I found my gap by standing in salons and watching the queue, not by scrolling MRR lists.
@wangyan_im@cyclopathh1 That's the scary version — the knot becomes load-bearing and nobody dares touch it. I've started writing a one-line 'why this exists' note on every feature I ship, so future-me isn't guessing. Cheap insurance.