Before You Build
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

Many small teams build technically impressive health, education, or campus tools, then discover that the person who benefits is not the same as the buyer. WePlate gives a concrete example of student-user value failing to convert into university budget demand.

Primary check

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

Checklist

  • Can you name the first buyer segment and the repeated job they need solved?
  • Can you reach that segment without relying on one fragile channel?
  • What evidence would disprove the institutional buyer mismatch risk?
  • 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.

Relevant if

  • You are building a similar mobile app with public-source distribution risk.
  • You need to validate who will repeatedly pay before investing in product polish.

Less relevant if

  • You already control a reliable acquisition channel for the exact buyer segment.
  • The product is an internal tool with no need for public distribution.

Pre-build tests

  • Run a landing-page or concierge test with the narrowest buyer segment before building the full workflow.
  • Ask users to commit to a paid pilot, not only to join a free waitlist.

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.