Duplicator forks a product's working marketing and rebuilds it under a new profile — a different audience, language layer, or culture — so the same offer can be tested through a different pattern. It does not write product code or invent features; it re-adapts the marketing that already ships.
When to Use
- You have a product with real traction and want to test a second audience (engineers → lawyers, pros → students, one country → another).
- You already have brand traffic and want to check whether a re-storied version converts better.
- You want to enter a new market or culture without rebuilding your main site.
- You suspect a "second marketing profile" exists that you haven't used yet.
Don't use for: writing product code, or inventing capabilities the product doesn't have.
Prerequisites
- A product with an existing site, content, or channels (the marketing to fork).
- Website module: access to scan the current site, plus a domain or subdomain to host the forked page.
- Social module: API keys for whichever parallel channels you want (Facebook, Dev.to, Substack, GitHub, etc.).
How to Run
Describe the product and the target profile (audience, language layer, or culture). Duplicator studies the existing marketing, picks the matching language layer, and generates the forked copy. Full setup and install instructions live in the README.
Procedure
- Capture the source — scan the current site and content to learn what the marketing actually says, and to whom.
- Define the target profile — the audience, language layer, or culture to fork toward (e.g. "lawyers", "esports", "India").
- Pick the language layer — professional slang, everyday, dead-simple, or culture-specific lore.
- Rebuild — regenerate the page and copy under the new profile, keeping the offer intact.
- Ship to a parallel surface — a new domain or subdomain for the website module, or API-key channels for the social module.
- Test — run the forked version on traffic you already have and compare conversion against the original.
- Verify — confirm the fork is live and log the result.
Pitfalls
- Fork the marketing, not the product — never invent capabilities the product lacks.
- Keep the offer identical; only the pattern changes. A changed offer ruins the test.
- Respect what the source actually says — don't over-claim an angle the data doesn't support.
- API keys are secrets; never commit them.
Verification
- The forked copy keeps the same offer while changing audience, language, or culture.
- The forked page is live and reachable.
- The test compares the fork against the original and logs the delta.