Hey you 👋

Sorry for skipping the last two times, I have been busy with travelling and a lot of back and forth, so I couldn’t keep up with the new editions. I didn’t want to rush or sound vague in my newsletters, so I decided not to share anything until I’m really prepared.

So here’s a small update: From now, I’ll be sending my editions biweekly to make sure I share useful stuff while not feeling burnout. Because sharing weekly editions has become a little overhwhlemed since deadlines stare at me.

So welcome back after almost two weeks. I saw you are loving my last editions, and happy to see they were so helpful.

Well, I recently also collaborated with Insideletter on a guest post — How I grew my newsletter. The goal of this blog was to share my personal strategies and how I’m growing my newsletter.

It also includes tips on what to do and what not to. So if you are someone struggling with newsletter growth or planning to start one, check it out. Maybe it could be of some help. Also, you can reach out to me regarding the same— I’ll try my best to share whatever I have learnt and am still doing along the way.

Okay, let’s jump to the topic for which you’re here. Maybe it could sound like a ranting but a reality of the market where writing is overlooked and underpaid.

I’ve been saying no more than yes lately….

Not intentionally. It just started happening.

Over the past few months, I have had a lot of conversations—through outreach and some inbound as well. On the surface, everything looked promising. People wanted high-quality SaaS content, someone who understands the product, and someone who can go beyond surface-level writing.

But as those conversations moved forward, something felt off.

The expectations were clear. The budgets weren’t.

And that made me realize something.

Most people don’t actually see what goes into good SaaS writing.

From the outside, it looks simple. Write a blog, add some keywords, and publish it.

But the real work starts before that.

  • Understanding the product.

  • Figuring out what the user is actually looking for.

  • Going beyond obvious research.

  • Turning all of that into something clear, useful, and actually worth reading.

That takes time. And more than anything, it takes thinking.

For a while, I still said yes. I thought maybe this is just how it works.

But over time, it became clear that not every opportunity makes sense and might leave you burned out.

So I started saying no more often, not to avoid work, but to make space for better work.

Most people think they need more opportunities, but more often, they need better ones.

I’m starting to see the difference now.

Do you find it harder to say yes or to say no? Let me know if you want tips to say no, hahaha. I’m pro now.

Btw, I’m still stuck with my research for my substack vs beehiv comparison blog because I’m collecting different perspectives to shape the piece better.

Alongside, I’m also working on my travel blog for my recent trip. Will share about it here in the next edition, maybe. So stay tuned.

And and and I'm also working on something more exciting, will share about it on LinkedIn soon. Something personal that was on my bucket list for longggg.

If you’re new to this newsletter or reading this edition for the first time, then take a look at these previous editions; you may find them helpful.

Also Check:

Okay, so that’s it for today. Hope you have an amazing weekend.

See you next time 👋

~ Divya ✍️

Keep reading