AI Built the Prototype. We Build the Real Thing

Rebuilding, not wrapping. AI tools hand you a front end that runs, with the copy and images written straight into the code — that is precisely why they are fast. WordPress needs the opposite: content separated from presentation, editable through an interface, and reusable across pages that do not exist yet. We keep the design and behaviour, model the content properly as post types, fields and blocks, and rebuild the front end against that model.

Anything that produces markup or a front-end codebase we can read: Claude, ChatGPT, Cursor, v0, Lovable and Bolt, plus plain HTML and CSS, React and Next.js projects, and repositories on GitHub. A deployed URL, a repository or a folder of files is enough to scope from. If your project is locked inside a hosted builder we cannot export from, tell us early and we will say whether it is workable before you commit anything.

Yes, headless is a legitimate option and sometimes the right one. It suits content-heavy sites where front-end performance is a commercial priority and someone will own a second system long term. It costs you the live preview editors expect, most of the plugin ecosystem, and a second deployment to maintain. For most agency client sites a native build is cheaper to run and easier to hand over, and we will tell you which one your project actually is.

Everything that should change. Repeating elements become real content structures — team members, testimonials, case studies, pricing rows — edited through fields rather than markup. Menus, headers and footers move into the theme's templating so they are changed in one place. Where a section genuinely should not be editable, we lock it deliberately rather than leaving it fragile.

A converter maps markup to markup. It has no opinion about how your client's content should be structured, because it cannot see the pages that will be added later or the fields the marketing team will need. That judgement is the work. Converters also tend to inline styles and place headers and footers outside the theme's global templating — invisible until the first content update, expensive from then on. We use AI heavily inside our own process; we do not hand you its raw output.

Rougher than you think is usually fine. We take the design and the behaviour rather than inheriting the architecture, so messy class names and duplicated components add little cost. What does add cost is missing content, undecided functionality and unscoped integrations. We review the project before quoting and tell you what is unresolved.

Yes, as standard. NDA before the first brief, no contact with your client, and your naming on staging URLs, documentation and repositories. You sell the project, own the relationship and invoice for it. Our name appears on nothing your client sees.

A standard four to five page build typically turns around in 48 to 72 hours once designs and content are with us. Custom post types, integrations, ecommerce or a content migration take longer, and we give you a specific date before starting rather than a range. That figure is build time and assumes a complete brief.