posting build logs in niche communities

Weekly build logs beat product updates for us. Each post had three parts: what shipped, what broke, what I'm trying next

my first paid ad campaign

I spent $800 on Meta ads before anyone had organically converted. Creative looked fine—problem, solution, CTA. Landing p

shipped a landing page in one weekend

My product worked but my homepage was a Notion doc with a signup link. Embarrassing for demos. I blocked a weekend: Satu

got my first 10 beta users without paid ads

I had a working MVP and zero distribution plan. Posting on Twitter felt like shouting into a void, so I picked one subre

my first paid ad campaign

I spent $800 on Meta ads before anyone had organically converted. Creative looked fine—problem, solution, CTA. Landing p

my first paid ad campaign

I spent $800 on Meta ads before anyone had organically converted. Creative looked fine—problem, solution, CTA. Landing p

pricing with one simple annual plan

We had monthly, annual, and a fake "enterprise" tier that confused everyone. Support questions were mostly "which plan d

pricing with one simple annual plan

We had monthly, annual, and a fake "enterprise" tier that confused everyone. Support questions were mostly "which plan d

time-boxing deep work before support

Support and Slack were eating my mornings. I'd plan to code, answer five messages, and lose two hours context-switching.

distribution beats perfect code early on

I refactored the backend for a month while competitors with worse products grew faster. Code quality mattered to me; cus

distribution beats perfect code early on

I refactored the backend for a month while competitors with worse products grew faster. Code quality mattered to me; cus

building features nobody asked for

I spent three weeks on a collaboration mode because a competitor had it. Not one trial user had requested sharing, comme

building features nobody asked for

I spent three weeks on a collaboration mode because a competitor had it. Not one trial user had requested sharing, comme

instrumenting errors before scaling

We scaled traffic before error tracking was solid. Users hit silent failures; we learned from angry emails, not dashboar

using a shutdown ritual to avoid burnout

I used to "quickly check" Slack at midnight and wake up thinking about bugs. Sleep suffered; morning focus disappeared.

using a shutdown ritual to avoid burnout

I used to "quickly check" Slack at midnight and wake up thinking about bugs. Sleep suffered; morning focus disappeared.

pricing clarity matters more than coupons

We ran a 50% launch discount to "reduce friction." Conversion ticked up; annual value dropped; support got harder becaus

pricing clarity matters more than coupons

We ran a 50% launch discount to "reduce friction." Conversion ticked up; annual value dropped; support got harder becaus

building features nobody asked for

I spent three weeks on a collaboration mode because a competitor had it. Not one trial user had requested sharing, comme

choosing boring tech for speed

I almost rebuilt on a trendy stack because Twitter said so. Postgres, a monolith, and hosted auth were "boring" but alre