The team is three people, Param who owns the company and this handbook, Sai and Arvind, and the sources show what each has done but never who owns which area, so this page records only what is known and proposes an ownership split for Param to accept or change.
Today
Who is on the team
Person
What the sources say
Source
Param
Owner. Approves plans, makes product and brand decisions, tests on the live staging site, holds the only admin email on production
Wrote and owns the QA sheet "The Feed QA Master"; the shared docs site is made for Sai; pricing is parked until Param and Sai agree it; left a note on onboarding: no mascot, no founder slide, never "agents"
Wants Built for Shopify later and says 50 installs is easy
memory brew-shopify-app-review
Comments on this handbook know four names: Param, Sai, Arvind and Claude. handbook/comments/server.mjs:15
Staff access in the product is by domain: joinsquareup.com and shopos.ai get full access on production. brew/tools/prod-env.sh:9memory brew-access-rules
Most building is done by Claude sessions that Param directs; see How we work with Claude. memory brew-handbook
What is not known
Titles, who owns sales, design partners, design, QA or engineering, and who decides when Param is away. No source says. memory brew-handbook
Tomorrow
Item
Version
Tag
An owner named for each of the 18 departments
v1
New, see Open
One person who can promote to production besides Param
v2
New
Roles grow with the hiring plan
v2
Changes
How we do it
Every department in this handbook has one owner. The owner field in each document's front matter says who.
Owners keep their documents current and answer questions in Open; Param verifies.
Decisions are written in the decisions log the same day, with who made them.
Numbers
Metric
Definition
Where measured
Departments with an owner
Departments whose documents name someone other than the default
registry.json and front matter, Proposed
Open questions per owner
Unanswered Open items in each owner's documents
Next, Proposed
Open
Who owns what? Proposal, for Param to edit:
Param: company and strategy, product, brand, finance decisions, AI and models, ops and infrastructure, security and legal, this handbook.
Sai: sales and partnerships, customer success and support, design partner relationships, QA rounds through the QA sheet, and the money routines the finance pages propose: the spend ledger, the monthly credit read and the financial model; pricing is agreed by Param and Sai together.
Arvind: integrations and ecosystem, including the Shopify app and Built for Shopify, and marketing and growth.
Everyone: research and insights.
What are the titles? Proposal: none until a fourth person joins; describe people by what they own.
Who decides when Param is away? Proposal: Sai for partners and Arvind for integrations, with no production promotes until Param is back.
