--- id: "10.7" title: "Launch plan, Seeti" dept: marketing-and-growth status: draft owner: Param branded: true direction: cooker last_verified: 2026-10-26 sources: - "brand-directions/cooker/marketing.html m7, m8" - "brand-directions/book/content/h.js h-6 programme, timeline, launch; h-7 six-weeks" - "brand-directions/docs2/data/dirs.json cooker" - "brew origin/main a559de6: public/app.js:404; build.js:222-226" - "handbook content/product/design-partner-program.md" - "memory: brew-live-stores, brew-go-live-2026-10-17, brew-prod-backend, brew-pricing-parked, brew-shopify-app-review" --- # Launch plan, Seeti ## Answer The launch plan grows from five design partners to reads opened in small batches, with a six week calendar in Seeti's voice beside the partner work; there is no launch date, and no opening happens until partners say it works. ## Today | Fact | Source | |---|---| | Five design partners on production: Arata, Nutrova, Mana, Puma India, Scrubroom | [src: memory brew-live-stores] [src: memory brew-prod-backend] | | Gully Labs was the first design partner on 17 Oct and is not on the 24 Oct list | [src: memory brew-go-live-2026-10-17] | | The landing says design partner preview | [src: brew/public/app.js:404] | | Reads are limited: three new brands a day per person and a daily reading budget | [src: brew/build.js:222-226] | | What partners get, what we ask and how they graduate are not written down | [src: handbook content/product/design-partner-program.md] | | Pricing is parked; the 26 Oct proposal is a plan, a wallet and a share of ad spend at v4, not to be quoted | [src: memory brew-pricing-parked] | | The Shopify app was submitted for review on 21 Oct | [src: memory brew-shopify-app-review] | | No launch date, launch event or waitlist exists | [src: no source found in memory or brew origin/main] | ## Tomorrow ### The design partner programme, as Seeti's book has it | A partner gets | Version | Tag | |---|---|---| | A read of your store from public pages, about 3 to 4 minutes | v1 | New | | Your feed with drafts and a numbered brief to hand off | v1 | New | | A call every week or two with the founders | v1 | New | | A direct line when something feels wrong | v1 | New | | First say on what we build next | v1 | New | | We ask | Version | Tag | |---|---|---| | Open the feed on Mondays for six weeks | v1 | New | | Tell us when an idea is wrong or generic | v1 | New | | Hand off at least one brief and tell us what the shipper said | v1 | New | | Permission to learn from your feed, never to share your data or name | v1 | New | Seeti on the deal: You get the cooking. We get told when it is too salty. The cap, said once and plainly: each read costs real time and money while we build. No countdowns, no fake spots left. Seeti: One pot at a time. That is the cap. ### After a founder asks | When | What happens | Who | |---|---|---| | Same day | A reply by email, from a person, no character | A founder | | Within a few days | The read runs; the link goes out with one finding to look at first | The person who ran it | | Week one | First call, 30 minutes: what you handle, your next big moment, one thing you never post; walk the picks; make one and hand it off | A founder | | Weeks two to five | Monday picks, short calls, notes from the partner | A founder | | Fridays | The weekly founder note; Seeti signs off: Kitchen's clean. See you Monday. | A founder | | Week six | Keep going, and what to change | A founder | Seeti: Six weeks. Every Monday, three whistles. ### Six weeks, one theme a week | Week | Theme | Instagram | LinkedIn | Partner work | |---|---|---|---|---| | 1 | Meet Seeti | Post 1 meet Seeti, post 2 the whistle explained, Sunday stove | Why a cooker | List 40 founders to invite | | 2 | Three whistles | Three whistles candle special, post 4 Undercooked, Sunday stove | What it does not do | 20 invites, 5 calls | | 3 | The read | Post 6 reel one, post 5 whistle rating, Order up | The AI search finding | First reads cooked | | 4 | A festival | Three whistles festival special, reel two Undercooked, Sunday stove | A design partner lesson, no names | Weekly calls running | | 5 | The offer | Post 7 next door's menu, reel three the lid, Order up | The offer | 20 more invites | | 6 | Best of six weeks | Three whistles best of six weeks, post 8 boiled over, Sunday stove | What we learned in six weeks | Review, plan the next six | What we watch each week, inside the team only: read asks, reads run, first hand offs, second Monday opens. ### From partners to launch | Opening | What it needs first | Version | Tag | |---|---|---|---| | Second partner cycle | First cycle notes reviewed; the reveal and the Monday drop shipped | v1 | New | | Open reads in batches | Read cost known and under control; the cap lifted honestly | v1 | New | | Posts with your OK | Posting with approval and undo, tested with partners | v2 | New | | Shows what worked | How it went, per live pick | v3 | New | | Ads inside your rules | Rules and budget limits set by the founder | v4 | New | Each opening gets the same small kit: a reel in Seeti's voice, a founder post, an email to the waitlist and a note to partners first. Never call it open to all before it is. Seeti on the date: Nobody lifts my lid early. Not even for a launch. ## How we do it 1. Reply to every ask the same day, as a person. 2. Run the read only for an email at the brand's own domain; anyone else gets the demo stores. 3. Book the week one call before sending the read link. 4. Log every call and note in the [partner feedback log](/product/partner-feedback-log) the same day. 5. Post the week's calendar row; partner work comes before posts when time is short. 6. Before any opening, check the list in From partners to launch is done. ## Numbers | Metric | Definition | Where measured | Status | |---|---|---|---| | Partners active | Partners with a hand off in the last seven days | Brief status | Proposed | | Week four opens | Partners still opening Today in week four | Visitors log and feed opens | Proposed | | Asks per week | Store links sent to us | The asks list | Proposed | ## Open 1. **What is the launch date?** Proposal: none until every partner hands off weekly for four weeks; then open reads in batches. 2. **What do partners get on paper?** Proposal: free use through the partnership and a loaded wallet, as in [design partner program](/product/design-partner-program). 3. **When does the six week calendar start?** Proposal: the Monday after the direction and name are picked. 4. **Is there a public launch day at all?** Proposal: no single day; each version gets its own small opening. 5. **Who sends the Friday founder note?** Proposal: Param, every Friday from week four.