Elementor Rebuild Process & Design Constraints

Overview

When Asymmetric offers a complimentary Elementor rebuild as part of a website project, the scope of that rebuild is limited to building existing designs — not creating new ones. This distinction is critical to communicate clearly to clients upfront, as it is a common source of scope confusion.

The Elementor rebuild is positioned as a convenience upgrade: it simplifies future client edits (drag-and-drop) and accelerates the development process. It does not include design work.

What the Complimentary Rebuild Covers

• Installing Elementor on the existing WordPress site
• Rebuilding pages that already have a defined design or template into Elementor
• Making minor adjustments during the build process

What It Does Not Cover

• Designing new page layouts for pages that lack an existing template
• Pulling in the design team for custom design hours
• Redesigning or significantly altering existing page structures

"The build portion is, yes [complimentary]. But designing some of the pages we don't have designed for, I think is outside of it."
— Sebastian Gant, ^[1] scope call

Handling Pages Without Existing Designs

When a client needs pages that have no existing template or design, there are two paths forward:

Option 1: Paid Design Service

AAG's design team creates the layouts for an additional fee. This should be quoted separately and added to the project scope via a written proposal or contract amendment.

Option 2: Client-Provided Layouts

The client provides a simple design layout for the developer to build from. This does not need to be a polished mockup — acceptable inputs include:
- Hand-drawn sketches indicating content blocks and rough placement
- AI-generated mockups or wireframes
- Simple diagrams showing "text here, image here" structure

AAG can recommend tools to help clients produce these layouts with minimal effort. The developer builds to whatever layout reference is provided.

Developer vs. Design Team

These are separate functions with separate resource pools:

Pulling the design team into a build-only project consumes hours not budgeted for the engagement. This should be treated as a scope addition requiring explicit approval and pricing.

Recommendations for Project Setup

• Audit pages before the rebuild begins. Identify which pages have existing designs/templates and which do not. Flag gaps early.
• Communicate the distinction in writing. Clients often assume "rebuild" includes redesign. A written proposal or contract should explicitly state that design work is out of scope unless separately purchased.
• Provide client layout guidance proactively. If clients will be providing their own layouts, send tool recommendations (AI mockup tools, simple wireframe apps) before the build starts — don't wait until it becomes a blocker.
• Don't start the build on pages without a design reference. Building without direction leads to rework. Resolve design gaps before the developer touches those pages.

Related Patterns

• ^[2]
• ^[3]
• ^[4]

Observed In

• ^[5] — Scope conflict surfaced mid-project when client assumed the Elementor rebuild included design work for pages that lacked templates. Resolution required internal escalation and a written proposal.