What you should get when you pay for a landing page

When you pay for a landing page, four things are the minimum: a live page, the design source file, and the copy in a document you can edit. The fourth is admin access to the hosting and the page builder, under your own account. If any of those four still sit inside someone else's account after the invoice is paid, you rented a page rather than bought one. This is the full handover list to agree before work starts.

The handover list when you pay for a landing page

Ask for all seven of these. A live URL on your domain. The Figma file or equivalent transferred into your account, rather than shared with view access. The built project itself, so a Framer or Webflow project moved to your workspace, or a repository you can open. Copy in a document you can edit without asking permission. Exported assets, meaning images, icons and logo files at the sizes actually used on the page. Font files with the licence in your name. And a short written note of what was built where, so the next person does not start from zero.

Ownership has to be written down

Paying an invoice does not move a Figma file into your account on its own. Figma treats whoever created a file as its owner until someone explicitly transfers ownership, and freelancers do close accounts and disappear. The standard professional term reads like this: you own the final deliverables on full payment, while the designer keeps unused concepts and their own internal tools. Put that in the agreement, and do the transfer before the final payment clears rather than after. If a designer refuses to hand over files you have paid for, no platform support team can sort it out for you. It becomes a contract dispute, and the leverage you had was the last invoice you already settled.

Every account in your name

The domain registrar, the DNS, the hosting or site builder, the analytics property, the form tool, the email platform. Create all of it under your company email, and add the designer as a collaborator you can remove in one click. This is the most common way small businesses get stuck. The page works perfectly, then the person who owns the account stops replying, and nobody can change anything on the page.

The parts nobody lists until they are missing

Where does the form actually send, and who gets the notification? Is analytics installed and firing, and does a submission count as a conversion rather than a page view? Is there a thank you page for the ad platforms to track? Do the meta title and description read properly in search results? Is there a social preview image, so the link does not look broken when someone pastes it into Slack? Is the favicon yours? Is the page indexed or blocked, and was that on purpose? Each one takes ten minutes during the build and a week to find afterwards.

What not to demand

Skip the rejected concepts and iterations. Designers keep those, and that is normal practice. Skip unlimited post-launch edits bundled in free forever, because that is a support contract and it should be priced as one. Skip the source code for internal tools and components they built once and reuse across every client. Asking for these tends to raise your quote, or quietly lose you the good candidates. Ask for the things you need to run and change your own page, and stop there.

Put it in one paragraph before the deposit

You do not need a fifteen page contract. One paragraph carries most of the weight. List the deliverables by name. Say that ownership of the final deliverables transfers to you on full payment. Add that every platform account is created under your email. Define what counts as one revision round, and what a further round costs. Set a handover date. Send it with the deposit request. A professional signs it within the hour, and anyone who stalls on this paragraph has told you something valuable for free.