Entrepreneurship & Strategy

Say No to the Big, Endless Project: Why iCHEF Turned Down Custom Development

Share this article
LINEFacebook

Robin’s commentary, preceded by excerpts from Rework (source credited in the text)

Storage information

Bookmarks and reading positions are stored in this browser. Manage and back them up in My Reading.

Collected in Robin Shen’s Field Notes · Content type and attribution are shown above

English version published 2026-11-08 with AI assistance. Attribution, source notes, and verification limits are retained in the text. 中文原文

Reading guide

Robin uses iCHEF as an example. In his account, Taiwan’s largest restaurant group offered the company a large sum to build a custom system. The team declined: it would have turned iCHEF into a project-based software shop, with a product tailored to one major customer rather than its many small and midsize customers. It could even have become that customer’s outsourced IT department. Robin cautions against long projects with budgets in the tens of millions of Taiwan dollars. Requirements keep changing, delivery drags on, and the big budget raises expectations. A better approach is to divide a year-plus engagement into several three-month projects with clear requirements and smaller budgets.

Key points

  • Long projects invite scope creep and can become impossible to close out.
  • A product built for one big customer rarely fits the broader small-business market.
  • Break large engagements into three-month projects with clear scope and smaller budgets.
Entrepreneurship & Strategy thematic illustration
Entrepreneurship & Strategy · Thematic illustration · AI generated

Full text — English translation

#HaveTheCourageToSayNoToCustomers #TryingToMeetEveryCustomerRequest #LeavesYouWithAMediocreProduct Source: Jason Fried and David Heinemeier Hansson, Rework, “Say no by default” and “Let your customers outgrow you.” The English passages below are restored from the original: https://cpcglobal.org/publications/Rework.pdf Editorial note: Rework attributes the faster-horse line to Henry Ford; that attribution has not been independently verified here. Say no by default “If I’d listened to customers, I’d have given them a faster horse.” —Henry Ford (as attributed in Rework) It’s so easy to say yes. Yes to another feature, yes to an overly optimistic deadline, yes to a mediocre design. Soon, the stack of things you’ve said yes to grows so tall you can’t even see the things you should really be doing. Start getting into the habit of saying no—even to many of your best ideas. Use the power of no to get your priorities straight. You rarely regret saying no. But you often wind up regretting saying yes. People avoid saying no because confrontation makes them uncomfortable. But the alternative is even worse. You drag things out, make things complicated, and work on ideas you don’t believe in. It’s like a relationship: Breaking one up is hard to do, but staying in it just because you’re too chicken to drop the ax is even worse. Deal with the brief discomfort of confrontation up front and avoid the long-term regret. Don’t believe that “customer is always right” stuff, either. Let’s say you’re a chef. If enough of your customers say your food is too salty or too hot, you change it. But if a few persnickety patrons tell you to add bananas to your lasagna, you’re going to turn them down, and that’s OK. Making a few vocal customers happy isn’t worth it if it ruins the product for everyone else. ING Direct has built the fastest-growing bank in America by saying no. When customers ask for a credit card, the answer is no. When they ask for an online brokerage, the answer is no. When they ask if they can open an account with a million dollars in it, the answer is no (the bank has a strict deposit maximum). ING wants to keep things simple. That’s why the bank offers just a few savings accounts, certificates of deposit, and mutual funds—and that’s it. Don’t be a jerk about saying no, though. Just be honest. If you’re not willing to yield to a customer request, be polite and explain why. People are surprisingly understanding when you take the time to explain your point of view. You may even win them over to your way of thinking. If not, recommend a competitor if you think there’s a better solution out there. It’s better to have people be happy using someone else’s product than disgruntled using yours. Your goal is to make sure your product stays right for you. You’re the one who has to believe in it most. That way, you can say, “I think you’ll love it because I love it.” Let your customers outgrow you Maybe you’ve seen this scenario: There’s a customer that’s paying a company a lot of money. The company tries to please that customer in any way possible. It tweaks and changes the product per this one customer’s requests and starts to alienate its general customer base. Then one day that big customer winds up leaving and the company is left holding the bag—and the bag is a product that’s ideally suited to someone who’s not there anymore. And now it’s a bad fit for everyone else. When you stick with your current customers come hell or high water, you wind up cutting yourself off from new ones. Your product or service becomes so tailored to your current customers that it stops appealing to fresh blood. And that’s how your company starts to die. After our first product had been around for a while, we started getting some heat from folks who had been with us from the beginning. They said they were starting to grow out of the application. Their businesses were changing and they wanted us to change our product to mirror their newfound complexity and requirements. We said no. Here’s why: We’d rather our customers grow out of our products eventually than never be able to grow into them in the first place. Adding power-user features to satisfy some can intimidate those who aren’t on board yet. Scaring away new customers is worse than losing old customers. When you let customers outgrow you, you’ll most likely wind up with a product that’s basic—and that’s fine. Small, simple, basic needs are constant. There’s an endless supply of customers who need exactly that. And there are always more people who are not using your product than people who are. Make sure you make it easy for these people to get on board. That’s where your continued growth potential lies. People and situations change. You can’t be everything to everyone. Companies need to be true to a type of customer more than a specific individual customer with changing needs. #Rework --- Robin: On having the courage to turn customers down. Let me give iCHEF some credit. Back then, Wowprime, Taiwan’s largest restaurant group, wanted to pay iCHEF a large sum to build a custom system. The team ultimately said no. That deal would have turned it into a project-based software company. A product tailored to a big customer generally won’t work for all your small and midsize customers. And in Taiwan, once a large company has paid you, serving it can become especially demanding. You can end up committing your entire team to one customer, unable to close out the project—or effectively becoming its outsourced IT department. By turning down Taiwan’s biggest restaurant customer, iCHEF could develop its product around the needs of the majority of its customers. It could set its own priorities and timeline rather than become a large company’s IT team. That choice still came with the usual early SaaS challenge: losing money while building the business. It could also create differences with shareholders over the company’s direction. None of that is inherently bad. What matters is thinking it through: knowing what you’re doing, what product you want to build, and whom you want to serve. Then get your existing shareholders on board—or find new shareholders who share your vision. There’s nothing wrong with choosing to run a project-based software business, either. It’s a business decision. You might avoid some of the losses and pressure of the early years, and it may fit Taiwan’s software industry better. My advice is not to assume you should take a lengthy project just because the budget runs to tens of millions of Taiwan dollars. Winning a big contract feels great. But the longer it runs, the more time the customer has to come up with new ideas, add requirements, and change old ones. You may never be able to finish. A huge budget also raises expectations. Closing the project out may be anything but easy; signing it could be the start of a nightmare. For a project expected to run more than a year, work with the customer to split it into several smaller engagements. Give each one a clear objective and a short timeline—say, three months—with well-defined requirements and a smaller budget. That resets expectations and reduces the chance of a flood of new requests or changes to the old ones.

These articles are personal notes, book excerpts, and collected reprints. Figures and events reflect the time of the original publication, are not current information, and do not constitute investment advice.

Share this article
LINEFacebook

Comments

What do you think? Share your experience or questions.

Loading comments…

My reading notes

These notes stay in this browser and are not published. Writing a note also saves the article. Back up or move your notes in My Reading.

Manage my bookmarks and notes →

STAY CURIOUS

Save a good question for your next visit.

Save this article, or follow the Facebook page and RSS feed for additions. Historical articles retain their original publication dates.

Browse All articlesSearch articles and full text →