> ## Content Index
> Fetch the complete content index at: https://koesnadi.com/llms.txt
> Use this file to discover other available public pages before exploring further.

# The Hidden Cost of Saying Yes: Why Focus Means Knowing What Not to Build
- URL: https://koesnadi.com/the-hidden-cost-of-saying-yes-why-focus-means-knowing-what-not-to-build/
- Published: 2026-09-12T02:12:41.000Z
- Updated: 2026-09-12T02:12:41.000Z
- Author: Samuel Koesnadi
- Tags: Business

Steve Jobs famously emphasized that focus is not just about deciding what to do. It is about deciding what **not** to do. Saying no to things you are interested in can be just as important as saying yes to the things that matter.

I want to extend that idea with a more practical reason.

Almost everything you put into the market has some level of value. When you make a quick improvement, you might improve one dimension while accidentally making another worse. You gain something, but you also spend time, attention, and resources that could have been used elsewhere.

I was thinking about this this morning while having a walk, and after watching an Instagram Reels of Tim Cook's interview talking about saying no to things Apple has interest in building.

To write on this journal, I rely on ChatGPT to turn my unorganized thoughts into coherent sentences. Then I thought: wouldn't it be great to have something like that built directly into the CMS? That is my engineer ass talking.

Technically, I could build it. I could connect an AI API, integrate it into the editor, and make the writing workflow smoother.

But then I asked myself a more important question:

**Would building it actually create more value than simply using ChatGPT?**

Given how capable ChatGPT platform is and also it is FREE, building an easy to use plugin on Ghost that utilizes a must-paid API would probably not give me a meaningful advantage. Even if I could make it slightly better or more integrated, I would still be spending time on something that already has a good-enough solution, which is going back and forth between the ChatGPT platform and the editor to write this journal.

If there were a free plugin that I could install in five minutes, I would absolutely try it. (I checked, there isn't)

But building one from scratch?

My time is probably better spent somewhere else.

For me, that means building KIRA, an AI customer service infrastructure, and making it genuinely competitive.

I feel like, this is what saying no really means, and why saying no matters. Commitment is key.

It is not necessarily saying that an idea is bad.

Sometimes, it means recognizing that I do not have the time to do a good idea (and potentially rely on others to build what I might think is a good idea). Doing it so, feels to me even increases my appreciation for others' great works.

In a world where software can be built faster than ever, the competitive advantage may increasingly come from knowing what **not** to build.