Day 17 of building Layzer in public.
Day job + family. No code shipped.
Consistency doesn't mean output every day. Some days are just about staying in the game.
Still in.
#buildinpublic#indiehackers
@radley0x For me: build fast, for myself first. The "user" is me until the product clicks. Then start talking to others. Did that with Layzer β now Day 16 in public and learning the hard way that "useful to me" isn't enough on its own. Curious what others do.
The gifs I've been posting on here? Sometimes Cap. Sometimes a janky tool I built to screen record in the background β instead of doing it manually every time.
@pierreeliottlal "Talk to customers daily" is the hardest bit early on. Sent 17 emails to dormant signups this week β one good reply beats 30 cold signups.
Curious how you'd run #1 for consumer-leaning AI products where the value's hard to feel until you've used it.
@thenowhereway Saving this one. 16 days into building in public β 32 signups, poor retention, zero real distribution strategy. Curious what the founders who got past this stage learned
@akothari@NotionHQ@ivan Building on .ai myself and reading this with quiet envy π The Grateful Dead concert angle is genuinely brilliant. Congrats on landing it
@jackfriks@marclou Solo founder energy reading this π Building https://t.co/vHhLM0PNiw alone, twin dad. Some days I'd trade a kidney for a cofounder.