;
};
The guides in [Use Cases](/use-cases/introduction) each cover one page format. This page covers workflows: the end-to-end patterns brands run in Replo week after week, who runs each one, and what you can have working by the end of your first session.
Every workflow starts with a prompt you can copy into chat. Replace the bracketed parts with your own product, URL, or offer.
## Launch a paid-social funnel
Who runs it: a brand buying Meta or TikTok traffic (a bedding brand running ads into an advertorial, a supplement brand sending clicks to a listicle) that wants a dedicated page per ad angle instead of sending everyone to a product page.
Before you begin: connect a subdomain of your domain ([Custom Domains](/custom-domains)) and add the same pixels you use on your main store in **Scripts & Pixels** ([Integrations](/integrations/introduction)). [Why Publish to a Subdomain](/why-subdomains) explains how tracking and attribution carry through to checkout.
Paste the ad creative into chat so the page matches the promise that earned the click:
```text theme={null}
Here's the ad we're running [attach the ad image]. Build an advertorial
landing page for @[product] that matches its offer and headline. Problem
first, then the product, then reviews, then a buy section.
```
If you run Google Ads, you can skip the pasting: connect it in the [Integrations app](/apps/integrations) and Replo reads your live campaigns directly in chat.
```text theme={null}
Look at my active Google Ads campaigns and build a landing page matched
to the messaging of my highest-spend ad group.
```
Ask Replo to compare the pixels on the page against your main store and flag anything that would break attribution. See [the full pre-launch tracking checklist](/why-subdomains#before-you-drive-paid-traffic).
UTMs and click IDs on your ad URLs are forwarded through to checkout automatically.
The quick win: an ad-matched advertorial, live on your own domain, with tracking verified, in one session. For the format itself, see [Build an Advertorial](/use-cases/advertorials) and [Build a Listicle](/use-cases/listicle).
## Recreate your store's slide-out cart
Who runs it: a brand moving campaign traffic onto Replo pages that doesn't want to lose the cart experience its theme took months to tune (free-shipping progress bar, upsells, gift-with-purchase messaging).
Before you begin: connect Shopify ([Selling with Shopify](/commerce/shopify)). The cart drawer on a Replo page is Replo's own UI (which is why it needs recreating), but underneath, every add to cart writes to a real Shopify cart, so anything added on a Replo page lands in your normal checkout with your discount codes and cart-recovery emails intact.
```text theme={null}
Recreate the slide-out cart from [yourbrand.com], including the
free-shipping progress bar, the upsell section, and the promotional
messaging. Match the styling exactly.
```
Replo reads your live site and rebuilds the cart's design and offer logic on your Replo pages. If your cart is more complex, here's where the lines are:
* **Rebuilds cleanly**: the design and messaging, free-shipping progress bars, upsell sections, and gift-with-purchase promos. These are rebuilt as Replo's own logic on top of the real Shopify cart, so discount codes, subscriptions and selling plans, and line item properties all keep working.
* **Doesn't carry over as-is**: cart apps installed as Shopify theme embeds (UpCart and similar) only run inside a theme, so their widgets can't render on a Replo page. Replo rebuilds the same behavior natively instead. Some apps also have a direct integration: connect Rebuy in the [Integrations app](/apps/integrations), for example, and its product recommendations can power the upsells in your rebuilt cart.
* **Not sure which bucket you're in?** Ask before you commit:
```text theme={null}
Here's my current cart [screenshot or yourbrand.com]. Tell me what you can
recreate exactly, what you'd rebuild differently, and anything that won't
carry over.
```
The quick win: a cart your customers can't tell apart from the one on your store, so campaign pages stop feeling like a separate site.
## Give every email and SMS campaign its own page
Who runs it: a lifecycle marketer sending Klaviyo campaigns who is tired of pointing every send at the same collection page.
Before you begin: connect Klaviyo ([Klaviyo](/integrations/klaviyo)) so signup forms on your pages submit straight to your lists.
```text theme={null}
Build a landing page for our [spring restock] email campaign. Lead with
the same offer as the email ([20% off bundles]), feature @[product], and
end with an email signup form that adds new subscribers to my Klaviyo list.
```
The page matches the email that sent the visitor, and the signup form captures the people who arrived from a forward or a shared link. The quick win: your next campaign gets a destination built for it, not a generic page. Launching something new instead? Start with [Waitlist & Launch Pages](/use-cases/waitlist-preorders).
## Run a seasonal promo without touching your store
Who runs it: a brand running BFCM, a holiday drop, or a flash sale that wants the promo live fast and gone cleanly afterward, with zero risk to the theme.
Because Replo pages publish to your subdomain, nothing you build or unpublish can affect your store's theme or navigation. That makes aggressive, short-lived offers safe to ship.
```text theme={null}
Build a Black Friday page for @[collection]: a countdown to the end of
the sale, the discounted bundles up top, and urgency messaging throughout.
We'll turn it on Friday morning and off Monday night.
```
When the promo ends, unpublish the page or ask Replo to restore the evergreen version ([Version History](/features/version-history) keeps every edit reversible).
This is also where promo pages start compounding: once a layout converts, it becomes your template for every moment on the calendar. Duplicate the Black Friday page that worked, swap the offer, the countdown, and the imagery, and it's your Christmas page; then New Year's, then Valentine's Day. Each rerun takes minutes instead of a build cycle, so you can spend the saved time testing offers and creative, and your conversion rate improves promo over promo instead of starting from scratch each time.
The quick win: a promo page built and scheduled in a session, with a clean way back. Prompts for specific formats are in [Build a BFCM Campaign](/use-cases/bfcm) and [Build a Holiday Promotion Page](/use-cases/holiday-promotion).
## Start from a screenshot or a page you admire
Who runs it: anyone with a reference and no time to describe it: a founder who saw a competitor's funnel, a marketer with a Figma mock, a team with a page that already converts on another tool.
The prompt that gets the best results names the reference, what to keep, and what to make yours:
```text theme={null}
Build this page for my brand: [URL]. Keep the layout, section order, and
overall flow, but use @[product], my brand kit, and rewrite the copy for
[your offer].
```
Or paste a screenshot and scope it down:
```text theme={null}
Rebuild the hero and the comparison table from this screenshot for
@[product], in our brand colors.
```
Replo recreates the structure and adapts it to your brand kit and products; "keep the layout, change the brand" beats "copy this exactly," because an exact copy still carries the other brand's voice and offer. Cropped, focused screenshots give the most accurate results; the details are in [Generating Pages With Replo](/features/building-pages-ai). The quick win: the page you wished you had, rebuilt as your own, in minutes instead of a design cycle.
## Put reporting and upkeep on a schedule
Who runs it: a founder or marketer who wants the routine checks (traffic, broken links, stale content) to happen without them.
Before you begin: this is the workflow where connections pay off most. Connect [Slack](/integrations/slack) and reports land in the channel where your team already works instead of waiting in Replo. Connect [GA4](/integrations/ga4) or [Triple Whale](/integrations/triplewhale) and Replo can cross-reference its numbers against yours in the same report.
A [task](/apps/tasks) is a prompt with a schedule attached, so anything you'd ask Replo once, you can ask it weekly:
```text theme={null}
Every Monday at 9am, summarize last week's traffic, revenue, and
best-converting pages, flag anything that dropped, and post the report
to our #marketing channel in Slack.
```
```text theme={null}
Every Friday, check my published pages for broken links, outdated
promo dates, and slow images, and report what you find.
```
Each run is a normal Replo session you can open and read, and a run can end in an action, not just a summary: post to Slack, or put a review meeting on the calendar with the [Google Calendar](/apps/integrations) connection when a number needs a human decision.
The quick win: your first Monday report arrives without you asking twice. [Sell at Scale](/use-cases/sell-at-scale) shows the full growth loop this plugs into.
## Run Replo from the tools you already use
Who runs it: a team that lives in Slack, Claude, or ChatGPT and doesn't want "check on the site" to mean opening another app.
Replo doesn't have to be a place you go. Two connections turn it into something you reach from wherever you already work:
* **Slack.** Connect [Slack](/integrations/slack) and @mention the Replo bot in any channel it's been added to. It runs a full Replo session right in the thread (edit the site, pull analytics, manage products, publish) and posts the result back, so a teammate can ship a copy change from the channel where the request came in.
* **Claude and ChatGPT.** Install the [Replo connector](/mcp/use-with-claude-and-chatgpt) and the AI you already use gets access to your Replo account: list and update your sites, manage products and scheduled tasks, query your analytics, and kick off full build sessions. If your briefs, research, and brand docs live in a Claude or ChatGPT workspace, draft there with all that context, then have it hand the finished brief straight to Replo to build.
```text theme={null}
@Replo update the hero headline on /black-friday to "48 hours only" and republish.
```
The quick win: the gap between "someone should do this" and "done" stops involving a login. For the full connector reference, see the [MCP overview](/mcp/overview).
## Test offers by splitting your ad traffic
Who runs it: a brand with real ad spend that wants to know whether the bundle or the subscription offer wins, without adding a testing tool.
The split happens in your ad platform: point two ads (or two ad sets) at two published pages. Replo's job is building the variants and keeping the test honest.
```text theme={null}
Duplicate our [bundle] landing page and change only the offer: the
variant should lead with [3 months free on the subscription] instead of
[15% off the bundle]. Keep everything else identical.
```
Then ask Replo to design and call the test. Replo's A/B testing [skill](/apps/skills) works out sample size and duration from your real traffic, and tells you when a result is trustworthy versus noise:
```text theme={null}
We're splitting ad traffic between /bundle and /bundle-subscription.
Our baseline conversion rate is [2.4%] on [1,200] visits a day. How long
do we run this, and what difference is big enough to call?
```
The quick win: a one-variable test designed correctly on day one, so you don't burn two weeks of spend on a result you can't trust.
## Next steps
Prompts for each page format these workflows use.
How tracking, ads, and checkout keep working.
Schedule the recurring parts of any workflow.