Before You Build
English
English中文日本語
Mobile AppShut Down

WePlate

WePlate targeted university food and dining workflows, but the founder reported contacting close to 100 universities with no buying interest and no revenue. The product needed institutional demand validation before product buildout.

View original story

Product snapshot

What it was

WePlate was a nutrition app and B2B SaaS attempt that recommended cafeteria meals and portion sizes for students, then tried to sell menu analytics to college dining teams.

Who it was for

college studentscollege dining teamscampus dietitiansuniversity food-service administrators

Problem / value

Make healthy cafeteria eating more specific for students while giving campus dining teams menu-nutrition analytics.

Core workflow

Students received meal and portion recommendations, while dining teams could analyze cafeteria menus and nutrition gaps.

Core dependency

The product needed universities or dining teams to care enough about the analytics workflow to buy.

Product form

mobile appB2B SaaSanalytics tool

Pricing model

No public pricing data found; founder interview says the team offered to work with colleges for free during sales attempts.

Competitors or alternatives

MyFitnessPalNoommainstream diet appscampus dining softwaremanual nutrition analysis

What happened

Summary

WePlate recommended specific cafeteria meal items and portion sizes for users' dietary needs.

Outcome

The team built useful technology and an MVP, but public founder evidence says the intended institutional buyers did not show willingness to buy, even after broad university outreach.

Core risk

Institutional Buyer Mismatch

Timeline

  • Founder started WePlate in December 2021.
  • Founder reported building an MVP and beta-testing it at a college cafeteria.
  • Founder shut the venture down after eight months.

Before you build

Why it matters

WePlate targeted university food and dining workflows, but the founder reported contacting close to 100 universities with no buying interest and no revenue. The pre-build question is whether college students, college dining teams, and campus dietitians have enough urgency, budget, and repeat behavior to support this workflow through a channel you can keep reaching.

Primary check

Secure institutional buyer commitment before investing in analytics for a campus nutrition workflow students may use but schools must fund.

Checklist

  • Who owns the budget for this problem?
  • What repeated event triggers the buyer to use this every week or month?
  • Which channel reliably reaches college students, college dining teams, and campus dietitians without a one-off launch spike?
  • What evidence would show Institutional Buyer Mismatch before you build more?
  • Define which segment among college students, college dining teams, and campus dietitians pays first and why the problem is urgent now.
  • Prove the workflow happens often enough to justify buying.
  • Test one acquisition channel for college students, college dining teams, and campus dietitians before relying on launch traffic.
  • Write down why a buyer would switch from MyFitnessPal, Noom, and mainstream diet apps.

Relevant if

  • You are building a mobile app for college students, college dining teams, and campus dietitians.
  • The product promise is specific: Make healthy cafeteria eating more specific for students while giving campus dining teams menu-nutrition analytics.
  • You have interest, signups, usage, or founder confidence but have not proven paid repeat use.
  • Buyers can already use MyFitnessPal, Noom, and mainstream diet apps or avoid switching altogether.

Less relevant if

  • You already have paying college students, college dining teams, and campus dietitians who repeatedly use the workflow and renew or expand usage.
  • The product is an internal tool with a mandated user base and no external go-to-market risk.

Pre-build tests

  • Run the workflow manually for a small group of college students, college dining teams, and campus dietitians.
  • Ask one buyer to pay, renew, or sign a dated pilot before building the next version.
  • Test one non-launch acquisition channel and count qualified conversations, not page views.
  • Put the offer next to MyFitnessPal, Noom, and mainstream diet apps and ask what would make the buyer switch now.

Transferable lessons

  • Validate the budget holder, not only the end user's need.
  • For institutional SaaS, test procurement and willingness to pay before building a complex MVP.
  • A real problem can still be a weak business if it does not increase the buyer's bottom line.
  • Niche positioning may matter more than broad usefulness when students or consumers have low urgency.