Landing page design or development: what to buy

Identify what is missing

If you have a developer and need a visual direction, a design engagement may be sufficient. If you already have an approved layout, you may need implementation. If you only have an idea, you may also need structure and copy before either stage can proceed.

Write the current state honestly. “We have a design” is incomplete if it only shows one desktop screen and omits forms, mobile layout, and error states. “We have copy” may mean draft notes that still need editing and approval.

Define a design deliverable

A design brief should specify sections, breakpoints or responsive expectations, component states, source file access, and assets. Ask how the design explains long headings, missing images, navigation, form errors, and confirmation messages.

Decide whether the designer is expected to write copy or use approved text. Placeholder text can make a page look balanced while concealing the actual content problem. Review with representative real content whenever possible.

An illustrative design-only scope might include desktop and mobile layouts, button and form states, and an annotated handover. It would exclude deployment and form-delivery setup.

Define a development deliverable

Development should identify the platform, editable content, interactions, integrations, and deployment responsibility. Explain where the page will live and who controls that environment.

A developer needs to know how the form routes enquiries, whether a booking widget is involved, and what third-party scripts are required. Ask who supplies credentials through secure access and who verifies the resulting workflow.

If a site builder is used, confirm account ownership and plan requirements. If custom code is delivered, agree where the repository or export belongs and how your team will maintain it.

Avoid gaps between two providers

When design and implementation are separate, agree who resolves ambiguous behavior. Ask the designer for reusable assets and implementation notes; ask the developer to flag missing states before proceeding.

Do not assume pixel-identical output across every browser is the only quality measure. Content clarity, responsive behavior, and a functioning user journey also matter. Specify reasonable acceptance conditions instead of relying on visual resemblance alone.

A combined service can simplify coordination, but its offer still needs to identify what is included. Use a tailored offer when the package does not match the required workflow.

Keep conversion claims realistic

A freelancer can improve clarity and implement a page, but cannot guarantee profitable traffic or a particular conversion rate. Results also depend on the offer, audience, campaign, pricing, and follow-up.

If analytics are required, define the event and who checks it. A button click and a successfully delivered enquiry are different signals. Avoid adding scripts merely because a standard package includes them; each should serve a defined purpose.

Review the complete experience

Open the page at phone and desktop sizes, use the keyboard, read the actual text, and complete the main action. W3C’s introductory checks are useful for spotting basic accessibility issues, not certifying the entire page.

Check the published URL, form delivery, metadata, and any agreed tracking. Confirm how to edit the headline without breaking layout. Acceptance should establish that the page performs its intended task and that the business can operate it afterward.