If you need a campaign-ready URL, do not request “landing page design” and assume development, hosting, form delivery and measurement are automatically included. Specify the outputs, owner of each output and evidence that they work in the environment visitors will use. A design can be excellent while no working enquiry route exists.
Landing Page Design focuses on a clear offer and primary action, with content, evidence, forms, mobile layouts and measurement requirements for implementation. Turning that specification into a published page needs an explicit implementation, access and approval scope unless the agreement already includes it.
Separate four outputs often given one name
The first output is design: layouts, states, approved content and interaction specifications. The second is implementation: a page operating in a browser with the agreed behavior. The third is connection: routing the form to the correct destination and configuring authorized measurement. The fourth is launch: approving the environment, domain, tests and responsibilities before accepting traffic.
These stages do not require four suppliers. One team may deliver them, but separating their outputs prevents acceptance disputes. “The page is delivered” should identify a clear stage rather than describing a design file the buyer believes is a working URL.
Identify implementation inputs early: domain ownership, hosting permissions, the account receiving enquiries, information collected by the form and responsibility for approving relevant content and policies. Some launch blockers are administrative rather than technical. Discovering them on campaign eve does not reduce their impact.
Worked hypothetical: a polished form without a received enquiry
Imagine a business preparing a campaign for an office maintenance service. It receives an interactive prototype moving between the offer and thank-you screens. The campaign owner assumes the page is ready. Review reveals that the form connects to neither an inbox nor a business system, and the preview URL is for design review only.
The team rewrites acceptance around three outcomes: the page loads from the approved domain, a test enquiry can be traced to the agreed destination and the specified measurement event occurs after the defined successful submission. A click on submit is not automatically a received enquiry.
In a later test, the team submits four valid invented enquiries and two incomplete ones. The expected result is four destination records, each created once, while the two incomplete submissions receive actionable correction guidance without creating incomplete records.
These are test quantities, not conversion rates or results from a real campaign.
Design the failure states as well as the success state
Specify empty, invalid, sending, successful, failed and repeated-submission states. What does a visitor see when the destination is unavailable? Where does the operational owner see the problem? A thank-you screen should not appear simply because a button was pressed before the intended outcome is known.
W3C’s form-notification guidance recommends feedback about submission outcomes and understandable error guidance. This supports one part of the experience; it does not certify the entire page’s accessibility. A broader evaluation needs its own suitable scope and evidence when required.
Where it is the selected delivery route, App Development can implement the agreed web functionality. Identify whether the work sits inside an existing website or a standalone page and who handles changes to surrounding systems. A one-page brief should not silently include extra integrations or an entire administration portal.
Measurement is a specification that needs testing
Define each event’s name, meaning, trigger and intended reader. Distinguish page viewing, starting a form, accepted submission, arrival at the destination and commercial qualification. You do not need to measure every stage, but one label should not stand for several different outcomes.
Agree how team tests will be excluded from reports or identified. Name who reviews consent and privacy settings with the appropriate owner. Do not send personal information to an analytics tool merely because adding it is easy. Test within authorized settings and state the evidence limits: one observed event does not establish the accuracy of all campaign reporting.
Paid Campaign Strategy and Management covers the agreed campaign scope, budget controls, quality criteria and tested tracking. Approving a landing page does not itself authorize advertising spend or promise a particular number of leads.
When a campaign manager and implementation supplier are different people, establish one shared event definition before launch. Otherwise both can truthfully report successful delivery while measuring different stages of the journey.
Handover for accepting real traffic
Before launch, Software Quality Assurance should follow the journey from the URL to the final destination on the agreed environments. Acceptance includes approved content, correct links, a functioning form, understandable feedback and measurement matching its definition, with any defect or exception recorded.
Name the launch decision owner, the person authorized to stop intake or amend the page and the person handling enquiries after arrival. Specify support hours, reporting route and the treatment of changes after acceptance.
If an essential approval remains pending, deliver the design or implementation under its actual status. Do not describe it as campaign-ready. A clear partial-delivery statement is more useful than a launch claim that conceals unresolved access or routing.
Ask the person receiving enquiries to submit a test, locate it and explain the next handling step. That closes the gap between a technically responsive button and an operating process the business understands.
Frequently asked questions
Is an interactive design file a published page?
No. It can demonstrate navigation and states without real hosting or form processing. Clarify what the link represents rather than treating visible interaction as proof of implementation.
Who provides the domain and hosting?
The agreement should identify account ownership, configuration responsibility and payment responsibility. Do not assume authority to transfer an existing asset or create a new subscription.
When has the form passed acceptance?
When it produces the agreed outcome, the record is traceable at its destination and failure and duplication behave as specified. A thank-you message alone is not proof of receipt.
Does page readiness mean the campaign can start?
The offer, content, budget, destination and enquiry-handling owner also need approval. Launch combines those decisions; visual quality alone does not make it ready.
Before requesting a quote, say whether you need design only, an implemented page or a tested launch with named responsibilities. That small distinction can prevent a substantial gap on campaign day.
Source
- W3C WAI: User Notification for forms, reviewed 26 October 2026. The enquiry counts are hypothetical.
