---
id: "11.2"
title: "Nutrova"
dept: sales-and-partnerships
status: draft
owner: Param
branded: false
last_verified: 2026-10-26
sources:
  - "brew origin/main a559de6: db/partner-copy.js:43, deploy.sh:19-20 and 41, moved.js:5, tools/probe-sources.mjs:12, shelf.js:5 and 15, social-feed.js:295, reader/stages/socials.js:99, docs/audit-2026-10-24-design-partners.md"
  - "brew commits deb7d90, 119dc8a, 41d9c09, 0b356a2"
  - "memory: brew-live-stores, brew-prod-backend, feed-for-all-brands, brew-jam-v2"
---

# Nutrova

## Answer

Nutrova is a design partner with a full read and Plays but no connected accounts, so the next step is getting its team in and its first account connected.

## Today

### Profile

| Fact | Source |
|---|---|
| Slug `nutrova-com`, store nutrova.com | [src: memory brew-live-stores] |
| Sells supplements; the source probe searches for marine collagen | [src: brew/tools/probe-sources.mjs:12] |
| Instagram handle nutrova; its social name can read "Nutrova India" | [src: brew/tools/probe-sources.mjs:12] [src: brew/reader/stages/socials.js:99] |
| A similar name, NutroVally, is never counted as Nutrova on the shelf | [src: brew/shelf.js:5] [src: brew/shelf.js:15] |
| A real design partner prospect; never wiped or reset | [src: memory brew-live-stores] |
| Home is production since 25 Oct | [src: memory brew-prod-backend] [src: brew/deploy.sh:19-20] |

### Connections

- None. On 24 Oct only Arata had any [src: brew/docs/audit-2026-10-24-design-partners.md:3]

### History

| Date | What happened | Source |
|---|---|---|
| 22 Oct | Listening was cut off by a deploy; listening now restarts at the depth it started with | [src: brew/social-feed.js:295] [src: memory feed-for-all-brands] |
| 23 Oct | Studio tested live on Nutrova; a layout fix keeps words off the product | [src: memory brew-jam-v2] [src: brew commit 41d9c09] |
| 24 Oct | Design partner audit: Brand Book, card fit and card audits clean; PDFs download; no sideways scroll on a phone | [src: brew/docs/audit-2026-10-24-design-partners.md] |
| 25 Oct | Copied to production | [src: memory brew-prod-backend] [src: brew/db/partner-copy.js:43] |
| 25 Oct | Its home briefly moved back to staging for a 26 Oct onboarding, then all five went to production | [src: brew commit deb7d90] [src: brew commit 119dc8a] [src: brew/moved.js:5] |
| 25 Oct | The look judge had dropped a Nutrova page mock; mocks are no longer judged as photographs | [src: brew commit 0b356a2] |

### Open issues

- None logged against Nutrova after 25 Oct [src: brew/docs/audit-2026-10-24-design-partners.md]

### Next step

The 26 Oct onboarding named in the commit is the last step on record; whether it happened is not recorded. See Open.

## Tomorrow

| Item | Version | Tag |
|---|---|---|
| Nutrova's team signs in with nutrova.com emails and owns the brand | v1 | New |
| First real account connected, Shopify or Meta, so its Plays are rewritten on its own numbers | v1 | New |
| Health claims on every surface pass the claim check against Nutrova's own studies or Brand Book | v1 | Stays |

## How we do it

1. Before the onboarding call, open Nutrova on production signed in as staff and check the feed, three Play PDFs and one jam.
2. On the call, walk the [onboarding playbook](/sales-and-partnerships/onboarding-playbook).
3. Log the call in the [partner feedback log](/product/partner-feedback-log) the same day.

## Numbers

| Metric | Definition | Where measured | Status |
|---|---|---|---|
| Team members | People from nutrova.com who joined | `private/members.json` | Proposed |
| Connected accounts | Real accounts reading | Connector ledger | Today: 0 |
| First hand off | Date of the first brief shared or sent | Jam records | Proposed |

## Open

1. **Did the 26 Oct onboarding happen, and with whom?** Proposal: add the date, the people and what they said to this page and the feedback log.
2. **Which account does Nutrova connect first?** Proposal: Shopify through its own app, since it needs no platform review and feeds the most Plays.
3. **Who signs off health claims?** Proposal: ask Nutrova for the studies behind its claims and load them into its Brand Book before any Studio make is shared.