Price the workflow, not just the page

A client site may use separate products for pages, forms, booking and follow-up. List which products would actually be retired. Keep subscriptions for specialist design, commerce, reporting or integrations that remain necessary in the new budget. The presence of a website builder does not establish that every client workload can move.

The relevant comparison is the full annual cost of delivering the same service. A site-only project and a managed lead-generation service should not share the same cost assumptions. Include rebuild time, content checks, redirects and any period when both systems remain live.

WorkloadDecision to test
Brochure site with occasional enquiriesIs the CRM and automation portion worth paying for?
Landing pages with active follow-upCan a submission reach the correct owner and workflow?
Several managed client sitesCan each client access only the intended workspace?
Complex catalogue or editorial siteCan the proposed setup reproduce the required content and commerce model?

Build one representative page first

Choose a page with the hardest layout, form and reporting requirements, rather than the simplest template. Check it at mobile and desktop widths, with keyboard navigation and a real form validation failure. Confirm required fonts, consent wording, confirmation messages and tracking events.

Then send a clearly labelled test enquiry. Inspect the resulting contact, assignment, booking step and follow-up. Reply or opt out and confirm the next action changes as expected. A successful page render is only one part of the test.

  • Does the lead arrive once, with the correct source and required fields?
  • Does the client receive the intended notification without exposing another client's data?
  • Can the team edit the page without changing a shared template unexpectedly?
  • Can you identify the cost of the follow-up generated by a busy campaign?

Plan the URL move before changing the domain

Create a list of existing URLs, including campaign landing pages and frequently linked assets. Map each URL to its replacement or an intentional retirement. Preserve important page content and metadata, and verify redirects where supported. Keep the old environment available until the migration checks pass.

A platform change does not guarantee search visibility or higher conversion. Compare page performance, form completions and qualified enquiries using the same definitions before and after the move. Keep a rollback owner and a copy of the original content.

Choose a tier and test the workflow

Use the plan finder and pilot worksheet →

Use your current invoice, a realistic usage allowance and the software you will keep. Compare the full first year, including the period when both systems are running.

Open the cost calculator

Sources & editorial basis

We use the vendors’ published plan information linked above. Workload selection, budgeting examples and pilot checklists are our editorial analysis. We have not performed hands-on tests of these products or migration paths.

Read the full methodology and commercial disclosure.