replica-launch

1# replica-launch
2 
3Reads `replica/fixes.md` (the angle and the evidence), `replica/brand.md`,
4and `replica/brand.json`. Writes `replica/launch/`: `landing.md`,
5`pricing.md`, `listing.json`, `launch-plan.md`.
6 
7```bash
8python3 listing.py replica/launch/listing.json      # limits, claims, the original's name
9```
10 
11Start from `listing.example.json` in this folder.
12 
13## The rules
14 
15- **No fake proof.** No invented testimonials, user counts, star ratings,
16  press logos or "trusted by" rows. An empty proof section is better than a
17  fake one. Real beta users, with permission, are fine.
18- **No reviewer quotes as testimonials.** The original's reviews are research.
19- **The original's name stays out** of your app name, store listing, keywords
20  and ads. Apple and Google reject it, and it invites a takedown.
21 
22## Step 1: landing page
23 
24`landing.md`, section by section, then build it in the project:
25 
261. **Hero**: the angle as a headline (what you do, for whom), one line under
27   it, one button. Screenshot of the real product.
282. **The problem**: the top two "hate" themes, in plain words. Paraphrase,
29   do not quote reviewers.
303. **How it works**: three steps, from the core flow.
314. **Features**: each tied to a fix from `fixes.md`. Lead with the fixes,
32   not the parity features. Parity is the price of entry.
335. **Pricing**: the table from step 2.
346. **FAQ**: the real objections, including "can I import from {{category}}
35   tools?" if you built an importer.
367. **Final call to action.**
37…