Nutri AI - Meal Scanner

Photograph meals, review editable nutrition estimates and keep a personal food diary.

Freemium mobile app + monthly or annual subscriptionsHealth & Fitness
Visit website
Reported revenue$43MRR · Unspecified $MRR snapshot pulled from the founder's RevenueCat account on July 19, 2026; the article separately labels activity and collected receipts over June 21–July 19.Original disclosure
Business modelFreemium mobile app + monthly or annual subscriptionsHealth & Fitness
Profile depthResearched profileProduct facts and editorial breakdown
Source checkedOct 20, 2026Observation date, not revenue cutoff

Business overview

Public positioning

Photograph meals, review editable nutrition estimates and keep a personal food diary. The July 19, 2026 original article identifies Matheus Mello as solo founder at Quantivo AI and describes his own ten subscription apps. The official NutriAI About page checked October 20 names founder Matheus Mello and describes a small team; exact present employee and contractor counts are unreported. The July solo statement is not projected forward as a current headcount.

How it makes money

App-store subscriptions unlock additional scans, history and AI coach conversations.

Business breakdown

Researched Oct 20, 2026

Source-linked product facts, followed by MRRTrace analysis of the customer problem, workflow, trade-offs and questions to test.

The customer problem

The official store describes photo capture, estimated nutrition and a meal history. Editorial interpretation: the useful customer problem is the effort of maintaining a diary when entering each ingredient feels burdensome. Start with people who recently abandoned a log and reconstruct the point where recording stopped. A fast first scan may create enthusiasm without solving the later task of correcting an ambiguous meal. A small prototype should show what was inferred, let the person change it and make the saved entry easy to find. Interview participants about their recording goal without assuming that they need automated health explanations.

Core workflow

  1. Photograph a meal or scan a packaged-food barcode to create an estimated diary entry.
  2. Inspect and correct the result before saving it, then optionally record a personal check-in.
  3. Reopen meal history or a summary and decide whether the retained record answers the user's original logging goal.

What customers pay for

Editorial analysis: observe completed and corrected diary entries, time spent repairing mistakes and voluntary return after the first week. Keep capture speed separate from the reliability of the saved information. Review a varied set of meals with an appropriate independent reference process before drawing accuracy conclusions. For business validation, ask which part of the history becomes useful enough to renew and measure cancellation alongside repeat use. At this scale, a few individual renewals or refunds can move the reported MRR substantially. App-store charges, model inference, support and acquisition costs would be needed to assess contribution margin; the disclosed snapshot does not supply them. Compare a simple diary prototype with the proposed automated workflow using the same recording task. Observe whether the saved effort survives correction and whether people can retrieve an earlier entry without assistance. These are proposed usability checks, with no claim that the product has passed them or improved any health outcome.

Distribution signals

Observed channels and entry points; their performance is not inferred.

  • Public app stores and an owned product website

    The official site and Google Play listing expose the download path. The original financial account does not report Nutri AI-specific acquisition channels, spending or attribution, so their effectiveness cannot be ranked.

    Evidence

Trade-offs

  • Editorial risk: minimizing entry effort can also hide uncertain ingredient and portion estimates. Make uncertainty and correction visible, and test whether users actually inspect an answer before it enters their history.
  • Editorial risk: richer personal history may improve the perceived usefulness of summaries while increasing the importance of clear data handling. Resolve the conflicting photo-retention descriptions and test export and deletion with disposable records before relying on privacy marketing.

Open questions

  • Which repeated diary task motivates renewal once the novelty of photographing a meal fades?
  • Can a new user identify an uncertain estimate and explain what happens to the associated photograph?

A MRRTrace reading of public product material. Trade-offs and questions are editorial analysis.

Revenue evidence

Founder disclosure
$43MRR · Unspecified $ · MRR snapshot pulled from the founder's RevenueCat account on July 19, 2026; the article separately labels activity and collected receipts over June 21–July 19.
Reporting period
MRR snapshot pulled from the founder's RevenueCat account on July 19, 2026; the article separately labels activity and collected receipts over June 21–July 19.
Figure as of
Jul 19, 2026
Reporting method
Founder disclosure
Source checked
Oct 20, 2026
Source published
Jul 19, 2026

The Nutri AI row reports $43 under an explicitly labeled MRR column and 10 paying subscribers. Only the dollar sign is given, so USD is not inferred. The article's $64 MRR and $87 collected over 28 days describe the ten-app portfolio, not Nutri AI alone. Scope is app-store subscription revenue; fees, taxes, refunds, costs and profit treatment are unspecified. No independent payment audit.

Matheus Mello, original first-person portfolio disclosure on his SoleOS site
This historical disclosure is separate from any current Stripe connection shown on this page. MRRTrace has not audited the business. Revenue is not profit, and historical figures are not current earnings guarantees.

Official site checked October 20, 2026 displays $9.99/month or $39.99/year with a seven-day trial. The dollar currency is not explicitly named; stores display regional prices. Current offers do not establish the July subscription mix.

The source page may change its prices, limits, or offer after the recorded check date.

What founders can learn

Editorial notes

Study whether easier meal capture creates a diary habit that customers keep paying for after the initial scanning novelty.

Before you build something similar

  • The disclosed MRR is a small founder-reported snapshot, not proof of profitability, sustained growth or market size.
  • Portfolio receipts, portfolio MRR and the maker's separate services business are not assigned to this app.
  • The official April 2026 privacy policy says photos are not retained on its servers, while the current data-use page says photos remain in private storage until account deletion. Google Play also declares no data collected. These descriptions require reconciliation; no privacy assurance is inferred.
  • Meal grades, symptom associations and AI advice are advertised product outputs. Accuracy, health effects, data deletion and security were not tested; this profile does not endorse clinical claims.
  • The Google Play package and founder identity distinguish this product from similarly named nutrition apps. Current pricing and features are observed separately from the July financial snapshot.

These are MRRTrace observations, not statements by the founder or proof of a repeatable outcome.

Source material

6 sources
  1. July 19, 2026 original founder RevenueCat portfolio account Public source · Checked Oct 20, 2026
  2. Official product and current pricing Public source · Checked Oct 20, 2026
  3. Official About page naming Matheus Mello Public source · Checked Oct 20, 2026
  4. Google Play exact package, developer and website link Public source · Checked Oct 20, 2026
  5. Official privacy policy dated April 2026 Public source · Checked Oct 20, 2026
  6. Official data-use page with photo-retention description Public source · Checked Oct 20, 2026