# Converting — Product Brief

> Working brief for the prototype space. Confirmed facts are marked as such;
> inferences and unknowns are flagged **TBD** / _(inferred)_ for EC to correct.

## What it is
- **Converting** — a Little Rocket Ltd. product. **TBD:** one-line value proposition.
- _(Inferred)_ Likely a Shopify-facing conversion product: the org also has
  `converting-shopify-app` (a Shopify App) alongside this `converting-web` site repo.
  Confirm the exact scope — e.g. conversion-rate optimization / checkout / merchandising.

## Who it's for
- **TBD.** Primary user (e.g. Shopify merchants / store operators) and the job they hire
  Converting to do.

## Surfaces
| Surface | Repo | Notes |
|---|---|---|
| Marketing site | `converting-web` (this repo) | `converting.now` — currently a placeholder. |
| Prototype gallery | `converting-web` @ `prototype` branch | `prototype.converting.now` — this scaffold. |
| Shopify app | `converting-shopify-app` | _(inferred)_ the product surface. Confirm. |

## What we're proving here
The prototype space is for showing off what's being built — brand explorations, web/landing
mocks, and product UI prototypes — before they're production. Seed sections: Design System,
Product, Web, Marketing Site, Docs, Archive.

## Brand personality
- **TBD.** See `brand/BRAND-BRIEF.md` (greenfield).

## Open questions for EC
1. One-line description of Converting and its primary user.
2. Is the Shopify app the main surface, or is there more (web app, embed, API)?
3. Any existing brand direction (colour / type / mark), or fully greenfield?
4. Vocabulary to lock for `_vocab/` (product-specific terms).