Work that held up.

I build things, put them out, and see what actually happens.

When something works or breaks in a way that teaches me something useful, I write about it here. Execution, distribution, and the parts that don’t go the way I expected.

Edgaze shows up only when it matters.

No spam. No schedule. I only send when there is something worth reading.

From newsletters@arjunkuttikkat.com. Hosted on Brevo. Unsubscribe anytime.

The point

Why this exists

Most newsletters are written to keep a cadence going. This one isn’t.

If you get an email from me, it means something actually happened that changed how I’d build or approach something. That’s the only filter.

I’m not trying to sound smart or summarize ideas. I’m writing things I wish I had known a week earlier.

Email on a fixed cadence trains readers to skim. I refuse that trade. If my name hits your inbox, it means I sat down because there was a concrete thread worth pulling, something that changed how I would ship, sell, or scope the next sprint.

Expect validation discipline before code, postmortems when users expose blind spots, and distribution notes grounded in attempts, not theory. When Edgaze matters to the story, it is in. When it does not, it stays out. No standing ovation section.

If you want hype without stakes, unsubscribe. If you want a founder still filing receipts from the arena, stay.

What you'll get

What shows up here

Notes from building and trying to get real usage
Things that worked and why
Things that failed once people actually used them
Gaps between what people say and what they do
Decisions I would redo differently

No templates. No recycled advice. Just what happened and what I took from it.

Sometimes

Validating before building

Sometimes it’s about validating before building.

Sometimes

What breaks when users show up

Sometimes it’s what breaks when users show up.

Sometimes

Distribution that didn’t work at all

Sometimes it’s distribution that didn’t work at all.

Sometimes

Interest didn’t turn into usage

Sometimes it’s where interest didn’t turn into actual usage.

No forced structure

I write what’s worth writing

I don’t force structure. I write what’s worth writing.

I don’t send often.

If there’s nothing useful to say, you won’t hear from me. If that changes, you should unsubscribe.

Arjun

Last step

If this sounds useful, stay.

If not, no hard feelings.

Arjun

No spam. No schedule. I only send when there is something worth reading.