Snapshots

No partner has said yes in writing, so no stories yet

Waiting on you
  • Nothing of a partner's appears without a written yes for each use.
  • v1 measures nothing, so no partner result exists to tell.
  • Our only partner figures are read findings, which describe a store, not a result.
  • Four story types grow with versions; a template and the ask are ready.
  • Ask only after a partner's second Monday of hand offs, in a personal email.
12 of 32AI answers named one partner
Your call

Which partner do we ask first, and is it Arata?

Product marketing · 15.10

Customer stories and proof

Needs youLast checked Mon Oct 26Owner Param

Answer

The partner results we may share, each with written permission; today there are none, because no partner has given permission and v1 measures no results, so this page holds the rules, the ask and the template until Param gets the first yes.

Today

Fact Source
Five design partner prospects use production: Arata, Nutrova, Mana, Puma India and Scrubroom memory brew-live-stores
No partner has given written permission to be named, quoted or shown in our marketing; none is recorded in any source memory brew-live-stores
Arata agreed on 15 Oct that its team notes stay public on the demo site; that is not permission for a story memory brew-audit-2026-10-15
Gully Labs was named the first design partner on 17 Oct and is missing from the 24 Oct list memory brew-go-live-2026-10-17 memory brew-live-stores
v1 measures nothing, so no partner result exists to tell brew/SCOPE.md:39
The only partner figures we hold are read findings, such as one partner named in 12 of 32 AI answers; they describe the store, not a result of using Brew brew/docs/handover/product/08-demo-guide.md:14-16
Proof we may use is what a founder can see in their own read; never a lift, a logo or a quote we did not get in writing brand-directions/book/content/b.js b-7 proof-rules
Sample reviews in our other products are fixtures and never shown as real memory harry-reviews-fictional

Tomorrow

Item Version Tag
A written yes from each partner before any name, logo, quote or screen of theirs appears v1 New
Story type one: a finding from their read, with their yes, such as what their reviews say that their pages never do v1 New
Story type two: how their week changed, in their words, with their yes v1 New
Story type three: what a post that went out after their yes did v2 New
Story type four: a measured result tied to the Play that made it v3 New
Never an invented customer, quote or result v1 to v4 Stays

How we do it

  1. Ask a partner only after their second Monday of hand offs, never in the first call.
  2. Ask in writing for one thing at a time: the name, a quote, a screen, a finding. Keep the reply.
  3. Write the story with the template below and send it back for their yes on the exact words.
  4. Store the yes beside the story, with the date and the person who gave it.
  5. If a partner leaves, take their story down the same week.
Store: <name, only with written yes>
Who said it: <person and role>
Their Monday before: <their words>
What the read found: <one finding, with its source>
What they made and handed off: <one piece>
What they say now: <their words>
Permission: <date, person, what they agreed to>

Numbers

Metric Definition Where measured Status
Stories with permission Stories with a written yes on file This page Proposed, zero today
Partners asked Partners asked for a story Pipeline Proposed

Open

  1. Which partner do we ask first? Proposal: Arata, since it is furthest along and has real accounts connected, after its next weekly hand off.
  2. What is the first story, before results exist? Proposal: a finding from their read, with their yes, told as what we found, never as a result.
  3. Who asks? Proposal: Param, in a personal email, never a form.
  4. Is Gully Labs still a partner we may ask? Proposal: treat it as a past prospect and do not ask until Param confirms.
Sources
  • brew origin/main a559de6: SCOPE.md:39; docs/handover/product/08-demo-guide.md:14-16
  • brand-directions/book/content/b.js b-7 proof-rules; h.js h-2 proof
  • memory: brew-live-stores, brew-audit-2026-10-15, brew-go-live-2026-10-17, harry-reviews-fictional

Source file content/product-marketing/customer-stories-and-proof.md · For agents: Markdown · JSON