# Custom builds
Source: https://docs.luriart.com/optimize/custom-builds
Plain text: https://docs.luriart.com/optimize/custom-builds.txt

For launches and new offers where your current page shape is the ceiling, our team builds a page with you and hands it to Luria as a new starting point.

Most of the time Luria works from the page you already have, improving the pieces that matter. Sometimes the page itself is the ceiling. A new offer that does not fit the old layout. A launch that deserves more than a headline swap. A campaign with an audience your current page was never written for.

That is what custom builds are for. Our team builds a page with you, one to one, and hands it to Luria as a new starting point rather than a variant of the old one.

## When a custom build makes sense
* **A launch.** New product, new line, new category. The story is different enough that you want a page built around it.
* **A new offer.** A bundle, a subscription, a high-ticket tier. The pricing and the promise need their own shape.
* **A campaign with its own audience.** You are about to put real spend behind a message, and the landing page should be built for that message from the first line.
* **You have hit a plateau.** Luria has converged, the numbers are steady, and the remaining upside is in a different page, not a better version of this one.

If you are not sure, ask. Sometimes what feels like a ceiling is a training gap, and a session in [Brand Brain](/train/brand-brain) fixes it for free.

## What we need from you
The build is collaborative. We bring the conversion craft and what Luria has learned about your buyers; you bring the things only you know.

| We ask for    | Why                                                                                                                                       |
| ------------- | ----------------------------------------------------------------------------------------------------------------------------------------- |
| The offer     | Exactly what is being sold, at what price, with what terms. Bundles, guarantees, shipping, anything that shapes the promise               |
| The audience  | Who this page is for, where they are coming from, what they already know. Cold ad traffic and a warm email list get different pages       |
| Assets        | Product photos, lifestyle imagery, video, reviews, press, founder story, anything you want on the page. We do not generate product photos |
| Constraints   | Your do-not-say list, legal or compliance limits, brand rules, anything off the table                                                     |
| A launch date | So we work backward from it                                                                                                               |

Share these in the dashboard's custom build request form, or over email.

## How it works
1. **Kickoff.** A short call to walk through the offer, the audience, and the assets. We confirm what the page needs to do and which goal it is optimizing toward. See [Goals](/train/goals).
2. **Build.** We draft the page and share a preview link. You review, we revise. Most builds take one or two rounds.
3. **Approval.** You sign off on the final page. Nothing goes live without that, same as any change that touches price or claims. See [Approvals](/dashboard/approvals).
4. **Handoff to Luria.** The page enters testing as a new starting point.

Rough turnaround from kickoff to live is one to two weeks, depending on asset readiness and revision rounds.  Launch deadlines are workable; tell us the date early.

## How the custom page enters testing
A custom build does not start cold. Everything Luria has already learned about your buyers carries over:

* **Your Brand Brain.** Voice, rules, do-not-say list, seasonal patterns. All of it applies to the new page from the first visitor.
* **What has worked.** If Luria has found that your Meta traffic responds to proof-first layouts or that short CTAs beat long ones, the new page starts from there instead of rediscovering it.
* **Your traffic streams.** Per-source and ad-level optimization pick up immediately. See [Traffic sources](/optimize/traffic-sources).

From there, Luria treats the custom page the way it treats any page: the same approval ladder, the same logged and reversible changes, the same stage progression. You will see it in [Reading results](/dashboard/reading-results) alongside everything else, with its own baseline so you can compare it to what it replaced.

**Note:**
  If you want the custom page to run against your existing page rather than replace it, say so at kickoff. Luria can split traffic between them and let the numbers decide.

## What a custom build is not
* It is not a redesign of your whole site. One page, built for one job.
* It is not theme or template work. We build the page inside Luria; your theme code and site builder are untouched, same as always.
* It is not a one-time deliverable that then sits still. The point of handing it to Luria is that it keeps improving after launch.

## Get started
Email [support@luriart.com](mailto:support@luriart.com)  with a line about the launch or offer, or book a call from your dashboard under **Help > Book a call**.  Custom builds are part of the high-touch tier; if you are not on it, we will tell you what it costs before anything starts.

## Next steps
  * [Brand Brain](/train/brand-brain)
  * [Approvals](/dashboard/approvals)
  * [Reading results](/dashboard/reading-results)
  * [Contact support](/troubleshooting/contact-support)