How do you know when to use a no-code tool instead of coding?

I have been building no-code tools for the past 4 years (like www.notionapps.com, an app builder for Notion databases)

And every time someone asks me "Should I code my app or use no-code tools?", I do not give a direct answer.

I usually reply with more questions, and they find the answer themselves. Here are some of those questions.

--
Question 1:
What are you building? What is the first version?

More the clarity you have here, the easier it is to make the decision. Coding or no coding, there is always a learning curve and your goal is to optimize.
--
Question 2:
Is learning how to code the main motivating factor? Or usage?

Coding is a life skill that gives a peculiar confidence that you can disrupt the world. You do not always have to “ship fast”, prioritize what you want.
--
Question 3:
Even if you can code, do you have the resources to maintain it?

IMO, the toughest part is to maintain what you deploy. Be it feature requests, bugs, logs, or analytics, there are many ancillary pieces to keep in mind.
--
Question 4:
Are you sure the first version is an app and not a landing page?

Quite often, a simple landing page to collect emails might (in)validate your idea. Also building simple is the best way to get used to no-code.
--
Question 5:
Are you prototyping a new idea or is this an internal app?

Internal apps have different requirements like how to integrate with your systems, how to automate and save time, how to securely store data etc.
--
Question 6:
Are you aware of the limitations of using a no-code tool?

Your app will be limited by the building blocks provided by the tool. Also, you have to rely on the provider for support.
--
Question 7:
Have you tried Airtable, Notion, or Coda?

Since these are not app builders but supercharged spreadsheets and docs, it is easier to get started. Also, just these tools could be your solution.
--
Question 8:
Are you looking for a no-code tool or a low-code tool?

Simply put, no-code tools are designed for business users and low-code tools are for developers and IT teams to build faster. Choose accordingly.
--
Question 9:
Is this a stop-gap solution?

Every no-code tool gives the illusion that it is scalable. Analyze the tool's limitations alongside your expected usage to know if it is a stop-gap.
--
Question 10:
Is there a popular “platform” in your domain that will help you get started?

Sometimes your solution does not need reinventing. For example, if your core idea is an e-commerce brand, start with Shopify or its alternatives.
--
Question 11:
Do you want to build it yourself or hire an expert to save time?

A good no-code expert is not just a technician but also has domain/process expertise. If you are hiring, make sure the offerings are not limited to a tool.
--

What other questions do you pose when evaluating no-code tools?