Rebuild your website. Keep editing in WordPress.

The challenge

Happy with WordPress. Frustrated with the website?

Your content is already in WordPress, and your team knows how to use it. But the theme may be hard to change, pages may load slowly, or every new feature may mean another plugin to maintain.

We review the design, content, plugins, and publishing tasks before recommending a rebuild. If smaller fixes would do the job, we'll say so.

What's included

Built for your visitors and the people who update it

Keep your design or start fresh

We build layouts for your services, articles, and other pages. We check them with real content on phones and larger screens, including long headings and pages with lots of images.

Connect your existing content

Your proposal names the posts, pages, fields, and blocks connected to the new layouts. We inventory page-builder content and visitor features such as forms separately. An existing plugin is not automatically a working feature on the new site.

Agree what editors can do

We define the content and layout changes your team needs, including preview and publishing requirements. The agreed tasks become acceptance checks before launch. Scheduling, private content, and unrestricted page building require a feasibility review.

Plan the launch and handover

The scope includes an agreed URL plan, metadata checks, named form destinations, and publishing instructions. We record who owns the hosting, WordPress, code, and ongoing updates, plus any work that needs a separate quote.

Price and scope

A fixed quote for an agreed scope

We review the site before quoting. Your written proposal sets the layouts, content, integrations, editing tasks, revisions, acceptance checks, and launch support included. Hosting, paid tools, and ongoing care are itemized separately. Changes to the agreed scope are quoted before work starts; the delivery window depends on that scope and your team's reviews.

The steps

How the work happens

1. 1

   Show us the current site

   We review what you have and what needs to change. You get the proposed work, price, and timeline in writing before deciding.

2. 2

   Review the first page

   We build a page that covers the main design requirements. You can check its layout on phones and larger screens before we build the rest.

3. 3

   Try it with your content

   Your team previews drafts and publishes changes. We test the remaining layouts, forms, and other features in the proposal.

4. 4

   Launch and hand over

   We set up hosting and check page addresses, search settings, navigation, and key tasks such as submitting a form before launch.

Before we begin

Is this right for your site?

Leaving a page builder? Read the migration guide for Elementor, Beaver Builder, Divi, or WPBakery.

At handover

What you keep

You own the code and content. We give your team instructions for publishing, hosting, and updates, plus the access details another developer would need to take over.

Technical background: Astro documentation: WordPress integration.

Plan the work

Useful before you choose

Plan the rebuild cost

Compare the one-time work and ongoing responsibilities with a cost worksheet.

Prepare your project brief

Describe the content, editing, integrations, and launch checks that a useful quote needs.

Compare WordPress, headless, and static sites

Choose an operating model around the changes your team needs to make.