Product overview · Handbook

Answer

Brew is an AI marketing team for online stores: paste a store link, get this week's marketing ideas already drafted from real evidence, make the good ones and hand them to whoever ships, and in v1 it never posts, spends, sends to customers or measures.

Today

The promise

Inside line: "Your store's marketing team, in one feed." docs/handover/product/00-overview.md:7
The line a founder repeats: paste your store link, get this week's marketing ideas, already drafted, pick the good ones and hand them off brand-directions/BRIEF.md:30
Stage: design partnership, building before launch, with real brands brand-directions/BRIEF.md:32 memory brew-live-stores

The loop

Step	What happens today	Source
Evidence	Brew reads the store, catalog, reviews, ads, search, AI answers, socials and rivals, then keeps reading on a cadence	SCOPE.md:11 docs/brew-loop.md:5
Plays	The evidence becomes written Plays: 65 kinds, each with why, what we found, the plan and what to watch	brand-directions/docs2/data/plays.json
Feed	Plays, ideas, listening, stories and watchers become one ranked feed, most cards with a first draft	SCOPE.md:13
Jam	The team makes the piece with AI and each other, every version kept	SCOPE.md:18
Hand-off	A brief written for whoever ships it, sent from the brand's own email, or a tracked send to our team	SCOPE.md:20 team-brief.js:20
Learnings	What the team tells Brew, drops in or does rewrites the Plays and the feed	brand-directions/docs2/content/pages.mjs:157-165

Size of the product today

Thing	Count	Source
Sources read	68 in the inventory: 60 read today, 7 once an account connects, 1 off	brand-directions/docs2/content/inventory.mjs
Plays	65: 50 core, 13 from listening, 2 automation	brand-directions/docs2/data/plays.json
Card kinds	34	brand-directions/docs2/content/inventory.mjs
Deliverables	40 in ten groups	brand-directions/docs2/data/catalogue.json
Surfaces in the build	309, of which 267 change, 36 go and 6 are new in tomorrow's map	brand-directions/docs2/data/map.json
Workflow templates	20, specified, not built	brand-directions/docs2/content/pages.mjs:338-359

Where it runs

Site	What it is	Source
feed.joinsquareup.com	Production, where the five design partners live since 25 Oct	brew .wt-prod docs/production.md:3 memory brew-prod-backend
brew.joinsquareup.com	Staging, where every change runs first	brew .wt-prod docs/production.md:3
demo.joinsquareup.com	Showcase with a sandbox per visitor and simulated accounts	SCOPE.md:30 DUMMY.md:19

Who uses it

Design partner prospects on production: Arata, Nutrova, Mana, Puma India, Scrubroom memory brew-live-stores
Test brands: Cozy Snugglet and Zenant memory brew-live-stores
Gully Labs was named the first design partner on 17 Oct and is not in the 24 Oct list memory brew-go-live-2026-10-17 memory brew-live-stores

How it is built to behave

AI on production: Plays on gemini-3.1-pro-preview, everything else on gemini-3.5-flash tools/prod-env.sh:9
Finals on production are made on Gemini; Sloosh is off until Param says commit 0fc7cfc
Connected accounts are real and read only on the live sites since 16 Oct SCOPE.md:14
Everything simulated is tagged Dummy in the UI, the code and DUMMY.md DUMMY.md:3-10
Pricing is a proposal only, with no billing code: plan, wallet and a v4 autopilot share brew working tree docs/pricing.md:3 memory brew-pricing-parked

What it does not do in v1

Post, schedule, launch, pause, move budget, write to any account, send marketing email or WhatsApp to customers, measure or grade results SCOPE.md:32-44. The full list is in the v1 PRD.

Tomorrow

Item	Version	Tag	Notes
The story: get found, get chosen, get them back	v1	New	Every pick serves one of the three brand-directions/_shared/product-model.md:24-26
The week as the unit: we read, you pick, you make, someone ships	v1	New	Monday drop of five picks brand-directions/_shared/product-model.md:27-33
Three tabs, Today, Work, Your store, Settings behind your picture	v1	Changes	Six addresses in all brand-directions/_shared/ia.md:52
One Hand it off with four routes	v1	Changes	Me, My team, My agency or freelancer, Our team
Posts and schedules after your yes, and workflows	v2	New	v2 PRD
Measures what went out and grades the Plays	v3	New	v3 PRD
Runs ads inside rules and a budget, with undo	v4	New	v4 PRD
The name Brew	all	Changes	The future name is open; five brand directions audition memory brand-directions-2026-10-25

How we do it

Start every product change from SCOPE.md, SPEC.md and DUMMY.md on origin/main.
Follow the product rules: truth first, read only, one version, every brand.
Write or change a feature's row in the v1 PRD with an acceptance line someone can check.
Ship to staging, check on the five partners, then promote to production with the clean gate.
Log what partners and Param say in the partner feedback log.

Numbers

Metric	Definition	Where measured	Status
Weekly hand-off stores	Stores where anyone on the team hands off at least one pick in a Monday to Sunday week	Brief records today, a decision log tomorrow	Proposed, defined in product metrics
Partners live	Design partner brands whose home is production	`MOVED_TO_PROD` list on staging	5 since 25 Oct memory brew-prod-backend

Open

Is Gully Labs still a design partner? Proposal: treat it as a past prospect and keep the five in brew-live-stores as the list.
India first, or global from day one? The read asks the market and never defaults it CLAUDE.md:31-32; every partner today is Indian. Proposal: India first through the design partnership, with no India-only code.
The product's future name. Proposal: decide it with the brand direction, then rename in one pass.
When does v2 start? Proposal: after the v1 redesign ships to production and two partners hand off weekly for three weeks running.

Source file content/product/product-overview.md · For agents: Markdown · JSON