Skip to content

SEA Bridge is a SCOPE Trade partner hub in Thailand · Read →

GVP
Reading time

Level-0 Needs: What Does Your Customer Need That They Have Never Said?

Global Venture II: Sprint · Week 2: find the job your customer is trying to get done, and one need they have never said out loud.

Level-0 Needs: What Does Your Customer Need That They Have Never Said?

By Kasper-Tanakrit Sermsuksan · Global Venture II: Sprint · Week 2

You are here: GV2-02 · Week 2 · Global Venture II: Sprint · article 2 of 15 · Weekly form · Next: GV2-03 Who Actually Pays, and What Else Could They Spend It On?

In short: Find the job your customer is trying to get done, and one need they have never said out loud. You leave with 5 logged conversations (of your team's 100) · 3 Jobs-to-Be-Done statements · 1 unsaid need, with the behavior that shows it.

The idea in two minutes

A Level-0 need is the need underneath the request. At SEA Bridge we read it in two parts.

  1. The job. What is the customer trying to get done, before any product exists? People "hire" products to do jobs1.
  2. The unsaid need. What will they need next, before they ask? That is the spirit of omotenashi: "anticipating and addressing needs before they're expressed"2.

You rarely hear Level-0 needs in an interview. You see them. Leonard and Rayport called this empathic design: "learning users' unarticulated needs through a process of keen observation"3.

My advice: ask about the past, watch the present, and never pitch in a discovery conversation.

Real cases

The morning milkshake

A fast-food chain asked customers to describe the ideal milkshake. Sales did not move. A researcher then watched who bought shakes and when: about 40 percent were bought early in the morning by commuters taking them to go4.

The job was a long, boring drive. "They weren't yet hungry, but knew that they'd be hungry by 10 a.m."4 The real competitors were bagels and doughnuts.

Kulina: orders on time, and someone to talk to

At Kulina, my team wanted to build a full restaurant management app for our partner restaurants. The owners needed something simpler. As I wrote in my book: "They needed their orders on time and someone to talk to."5 The app was our idea. The need was theirs.

Lemonilo

Lemonilo kept a job Indonesians already do every day, eating instant noodles, and made it healthier, instead of asking people to adopt a new habit. Read the Lemonilo case this week.

Do this week

  1. Watch before you ask. 30 minutes where your customer does the job. Note workarounds and complaints. Time: 30 min · Proof: Notes or photos
  2. Five conversations, not surveys. "Tell me about the last time you…" Time: 2 hrs · Proof: 5 log entries
  3. Three JTBD statements: When I ___, I want to ___, so I can ___. Each must be easy to prove wrong. Time: 20 min · Proof: 3 statements, each tied to a conversation
  4. The omotenashi test: name one need the customer has never said, and the behavior that shows it. Time: 20 min · Proof: 1 need + 1 observation
  5. Reread your Global Venture I interviews. Quote two questions where you led the answer. Time: 15 min · Proof: 2 quotes

Tools

  • Request → job → unsaid need. Write what they asked for, the job under it, and what they will need next.
  • Past, not future. "Would you buy this?" gets a polite yes; "What did you do last time?" gets a fact6.
  • Do things that don't scale. Paul Graham's advice to recruit users by hand is a discovery tool too7.

Tips and reality check

  • If everyone says "I would use it", you asked about the future. Go back to the past.
  • Note who uses, who pays and who decides. They are often three different people.
  • One clear unsaid need beats ten features.

✦ If you are doing this as part of Global Venture II: Sprint

Conversations count toward your team's 100. Form due Monday 13:00 before Week 3.

Thank-you emails within 24 hours, with kasper@seabridge.space in CC (not BCC). Late work: 80% same day, 50% within 7 days, 30% within 30 days.

Frequently asked questions

What is a Level-0 need?
The need underneath the request. It has two parts: the job the customer is trying to get done before any product exists, and the unsaid need they will have next, before they ask.

How do you find needs customers never say out loud?
Watch more than you ask. Observe customers doing the job, ask about the last time it happened rather than about the future, and never pitch in a discovery conversation.

✦ A Note for Global Venture II Students · Week 2 · Weekly form

This week's focus: FISHE I · Intellectual · Readiness CRL · about 3 hours of field work.

Your readiness move:

  • Dimension: Customer (CRL)
  • Move: 4 → 5, or your level → next
  • KTH CRL 4: "The problem/need and its importance is confirmed from multiple customers or users."8
  • KTH CRL 5: "Customers/users have expressed interest for the product/service and confirmed that it can solve customers’ problems/needs (i.e. initial problem-solution fit)"8
  • One Metric: For example: conversations that confirm the same job
  • Customer Development (Blank): Where you are on the four steps: Customer Discovery → Customer Validation → Customer Creation → Company Building. By the end of this course: Discovery done, Validation started (someone pays or commits)9.
  • I-Corps (NSF): Your log toward the team's 100 conversations. NSF I-Corps teams are expected to conduct "at least 100 interviews with potential customers"10.
  • Disciplined Entrepreneurship (MIT): Which of the six questions this week answers: who is your customer · what can you do for them · how do they acquire your product · how do you make money · how do you design and build it · how do you scale11.

How we measure progress. KTH is one yardstick among several. The KTH lines are quoted in KTH's own words: based on the KTH Innovation Readiness Level™ by KTH Innovation, licensed CC BY-NC-SA 4.0 (kthinnovationreadinesslevel.com).

Keep reading

All articles in Global Venture II: Sprint · 15 articles

Further reading

References

Web pages accessed Nov 2026.

  1. Christensen, C. M., Hall, T., Dillon, K., & Duncan, D. S. (2016, September). Know your customers' "jobs to be done." Harvard Business Review. https://hbr.org/2016/09/know-your-customers-jobs-to-be-done
  2. Sezer, E. (2024, November 26). Omotenashi in practice. GLOBIS Europe. https://globis.eu/omotenashi-in-practice/
  3. Empathic design (on Leonard & Rayport, 1997, Harvard Business Review). Wikipedia. https://en.wikipedia.org/wiki/Empathic_design
  4. Nobel, C. (2011, February 14). Clay Christensen's milkshake marketing. HBS Working Knowledge. https://www.library.hbs.edu/working-knowledge/clay-christensens-milkshake-marketing
  5. Sermsuksan, K.-T. (2023). The Startup Mindset [in Thai], Chapter 8. Wish Publishing. English: the author's own translation, not yet published.
  6. Fitzpatrick, R. (2013). The Mom Test. https://www.momtestbook.com/
  7. Graham, P. (2013, July). Do things that don't scale. https://paulgraham.com/ds.html
  8. KTH Innovation. KTH Innovation Readiness Level™, descriptor scales. Quoted unaltered; licensed CC BY-NC-SA 4.0. https://kthinnovationreadinesslevel.com
  9. Blank, S. Customer development (session slides, ENGINEERING 140A, Management of Technology Ventures). UC San Diego Startup Toolkit (PDF). https://innovation.ucsd.edu/startup/startup-toolkit/Steve-Blank-CustDev.pdf
  10. U.S. National Science Foundation. Information for Accepted National Teams (I-Corps). https://www.nsf.gov/funding/initiatives/i-corps/information-accepted-national-teams
  11. Aulet, B. (2024, April 16). Disciplined entrepreneurship: 6 questions for startup success. MIT Sloan. https://mitsloan.mit.edu/ideas-made-to-matter/disciplined-entrepreneurship-6-questions-startup-success

About the author: Kasper-Tanakrit Sermsuksan is the Founder of SEA Bridge and a Visiting Lecturer in Computer Engineering and Digital Technology at Chulalongkorn University's Faculty of Engineering. Learn more →

Work with us

Want to build on this story?

Tell us what you need: a venture, a market, a partner or an interview. The right person replies.

Tell us what you needPress and interviews →