Build simple landing pages

Finished example

The original layout below is for Juniper Bike Care, a fictional repair service. It is a teaching sample, not a real business or a conversion case study.

A delivery package would include the source or agreed editable builder access, a working review link, an approved copy sheet, and a handoff note. The note identifies who owns the domain, who pays ongoing costs and which parts were actually tested.

Fit and tradeoffs

Two delivery routes. On the DIY route you build and test the page yourself, so the tool and testing notes below apply to you. A supported route, where EYF builds an approved page while you handle the buyer, their approved copy, domain and hosting questions, and their sign-off, wouldn’t require coding or design skill. EYF fulfillment is being prepared and isn’t accepting requests or orders, so this method is DIY for now.

This suits someone who enjoys clear writing, layout and checking how a page behaves on different screens. You do not need to appear on camera. You do need to communicate about scope and learn enough about the chosen tool to make a reliable handoff.

Skip it if you want a quick sale without testing or cannot explain recurring hosting costs. A simple page can expand into copywriting, branding, booking, forms, analytics and ongoing maintenance. A beginner offer should explicitly exclude features you cannot support safely.

How it works

These are the DIY steps for building the page yourself. On a future approved EYF route you wouldn’t build it, but you would still agree the scope, collect approved copy, images and permissions, confirm who owns the domain and hosting, and get the named approver’s sign-off. That route isn’t available yet.

1. Learn a small complete page. Build and revise your fictional sample before selling a live site. Understand headings, navigation, responsive layout and basic accessibility.
2. Define a narrow offer. Agree the sections, copy source, revision round, delivery format and ongoing responsibilities. Separate design from hosting and maintenance.
3. Ask about the visitor’s task. The page needs to answer a real question and lead to one appropriate next step. A page cannot fix an offer nobody wants.
4. Find a relevant buyer. Look for a specific gap, such as a service that has no clear explanation online. Ask whether they want to solve it; do not treat a rough website as permission to redesign it.
5. Share a copy outline before polishing. Confirm the service description and any claims. Never add invented reviews, qualifications or urgency to make a layout feel complete.
6. Test and hand over. Check links, narrow screens, keyboard focus and the contact path. Get approval before publishing. Transfer control of production accounts and explain the recurring costs.

Get Customers

A working sample doesn’t guarantee a buyer; finding one is a separate, uncertain step. The routes and messages below are hypothetical EYF examples to test and adapt, not proven scripts or evidence that a business wants a page. Replace every bracket with a true detail.

Choose your delivery route first

DIY: you build the page. Use the fictional service page from the starter task. The Juniper Bike Care outline above is an illustration, not finished work you can show. Check your page at narrow and wide widths, click every link and confirm the headings. Press Tab to move through it and make sure a visible focus outline shows where you are. Keep it labeled fictional. Its contact button is a demo that explains a next step without sending anything; say so when you share it, and never present it as a working inquiry route or a client result. If you can’t yet build a page that works reliably on phones and wide screens, keep practicing before you sell.

EYF fulfillment: being prepared, not available. In a supported route, EYF would build an approved page and you wouldn’t need coding or design skill. Your job would be to understand EYF’s vetted sample (a finished example EYF has checked and labeled honestly), collect approved copy, images and permissions, confirm who owns the domain and hosting, explain what’s excluded and get the named approver’s sign-off. That route would only work with all of these in place:

• an approved EYF page service that is open
• a vetted EYF sample for that service
• confirmed EYF capacity for the job
• a written EYF quote for the agreed scope
• usable copy, images and details the buyer has approved

EYF fulfillment isn’t accepting requests or orders, and no page service, sample or quote has been approved. Don’t offer EYF delivery or accept paid work that depends on it; it isn’t a way around having a sample.

You can still ask owners how customers find their information now, as long as you don’t promise a page. Either route needs the buyer’s approved copy, images and service details. The domain (the web address) and hosting (the service that keeps the page online) should belong to the buyer, who approves any recurring costs.

Shape the offer in the buyer’s words

“One clear page that explains [service], what’s included and how customers take the next step.”

Agree the sections, where the copy comes from, one tested next action, one revision round and the delivery format: source files or agreed builder access (an invitation to edit in the website tool you used), a review link (where they can see the draft before anything goes public), an approved copy sheet (the final page text in one document) and a handoff note. Exclude booking systems, payments, forms that collect personal or sensitive information, ongoing maintenance, hosting or domain setup unless agreed, publishing unless agreed, and any ranking, traffic or sales promise.

Delivery for this offer: DIY, using your own tested practice page. EYF fulfillment is being prepared but isn’t an option you can offer yet.

A gap you notice, such as a service with no clear explanation online, is a reason to ask a question. It isn’t permission to redesign someone’s business; the owner may be happy as things are.

Three routes to a first buyer

A local group that allows offers. Use a Facebook group or Nextdoor only for an area where you actually live or work. Read each group’s current rules first; don’t assume offers are allowed. If they aren’t, ask whoever runs the group or use another route. Where allowed:

“For [actual area] service owners who want a clearer page explaining [service] and its next step, here’s my fictional sample. I’m happy to talk through one-page scope and hosting costs first.”

A warm introduction. Ask a contact whether they know an owner who wants a clearer service or contact page. Give them the fictional sample and a short scope to forward, and let them make the introduction.

“Do you know an owner who wants a clearer service or contact page? Could you forward this fictional sample and short scope if it seems relevant?”

A personal message based on one true observation. Look at one business’s page and note something specific and relevant you couldn’t find. Write to that owner alone, never to a bulk list.

“On [actual page], I couldn’t find [specific information or next step]. How do customers normally get that information? Would a focused page help?”

Only mention what you actually checked. If your sample isn’t ready, ask only the first question and listen. Don’t build a mockup from their logo, photos or text before they agree.

Handling replies

• Interested: “What do people ask before taking the next step with you, what can the page truthfully promise, which copy and images are approved, who reviews it, who’ll update details after handoff and when do you need it?” Also ask whether they already have hosting and a domain.
• Asks the price: “The quote covers one page with [agreed sections], one tested next action, one revision round and [source files or builder access] with a handoff note, delivered [timing] after I have your approved copy and details. Hosting, domain costs, booking and maintenance aren’t included.” Base the fee on your own time estimate, including messages and revisions, not on a rate seen online. Agree a price or deadline only when you know you can build it yourself; EYF delivery can’t be part of a quote until a service is open and has quoted you.
• Wants more customers or search ranking promised: Explain what you test: clarity, links, narrow screens and the contact path. A clear page may remove friction, but you can’t guarantee traffic, ranking or sales; decline if they need that guarantee.
• Already has someone or isn’t interested: Thank them and stop.
• Missing copy or facts, or wants forms, payments or booking: Explain the dependency and ask for approved details. You might narrow to a static page whose next action uses a contact route they already have, or decline. A real form is separate scope covering where data goes, consent and deletion.
• Not now: “Would a check-in be welcome when you’re ready to update the page?” Return only if they agree.

If there’s no reply and a check-in would be welcome on that channel, send one: “Is a clearer page for [service] useful right now? If not, no need to reply.” Then stop.

If nobody replies

Don’t repeat the message. Was the gap you noticed something the owner cares about? Does your sample work on a phone and look relevant to their kind of service? Was the scope clear, including hosting? Is this channel where they’d discuss it?

Change one meaningful thing, such as the type of business, the offer wording, the sample or the route. No quota or deadline applies.

Agree a small paid pilot

Confirm in writing (the scoping guide goes into more detail):

• the page’s purpose, and its one next action with the real destination it should reach, such as their existing phone number or email
• the approved copy and images, with permission to use them
• the sections, and excluded work such as booking, payments, forms and maintenance
• the delivery: source files or agreed builder access, a review link, the approved copy sheet and a handoff note
• who owns the domain and hosting and pays any recurring costs
• whether you’ll publish it: only if that’s included and the buyer approves the final page
• the fee, and how and when you’ll be paid
• a deadline counted from when you receive usable copy and details
• the named person who approves the page
• one included revision round, with feedback collected into one list, and how extra changes would be priced separately
• that the job is finished when that person confirms final acceptance

You and the buyer arrange payment directly; EYF doesn’t invoice or collect it. Anything you might later pay EYF for fulfillment would be a separate purchase. Your fee has to cover your time finding the buyer, messaging, building, testing and revising, plus any payment or tool fees, so no price guarantees a profit. If you later used EYF fulfillment, its separately quoted charge would also change what you keep.

Deliver, revise and get acceptance

Share the review link and copy sheet with the approver. Ask for all their changes in one list and make that included revision. Then rerun your checks: narrow and wide widths, every link, visible keyboard focus and the next action reaching the approved destination. If any part is still demo-only, label it in the handoff note, along with who owns the domain and hosting and what costs recur. The website handoff guide covers the rest of that note.

Then ask the named approver to accept the final page explicitly: “Does this page match what we agreed? If so, please confirm it’s accepted.” Publish only if publishing was agreed and they’ve approved it. Acceptance and payment are separate steps; confirm both.

After acceptance and payment

Once the page is accepted and paid, ask whether you may show it or describe the project accurately. If you share it in a group, follow its rules. Describe what you built and tested; don’t claim bookings or traffic you can’t verify.

If the owner is happy, you can also ask for an introduction. This is optional:

“If you know another owner who wants a clearer page, would you be comfortable forwarding my scope, and a link to your page if you’re happy to share it? Feel free to say no.”

A later real update or another defined page is a new job; maintenance and hosting are agreed separately, never assumed. For your second client, repeat a route that worked or try another suitable channel.

Your next step

Open your practice page, test it at two widths, click every link, tab through it and confirm the demo button is labeled. Write two plain sentences explaining who would own the domain and hosting for a real buyer. Then choose one route and draft one opening using a fact you’ve actually checked.

What buyers need

A plausible buyer needs visitors to understand the offer and know what to do next. Confirm the specific problem with questions: “What do people ask before booking?”, “What can the page truthfully promise?” and “Who will update details after handoff?”

Upwork’s research includes web design, but its marketplace signal is broader than this beginner offer. Webflow’s plan page shows why a free practice environment must be separated from custom-domain hosting. Google’s SEO guidance supports clear useful pages; it does not establish that a newly built page will rank or acquire customers.

Treat pricing, publication and data collection as decisions the buyer approves. For a first project, a clear static service page may be enough. Do not add payments or collect sensitive information just because a tool offers a button.

Common questions

Do I need to code?

You can use a visual builder or learn basic HTML/CSS. You still need to understand the tool’s limitations and be able to test and explain the result. Choose one route for your first sample.

Can the practice page be free?

Yes. Local HTML/CSS needs no paid host, and some builders offer free staging. A real custom domain, production host or advanced feature may require payment. Check the current plan rather than promising free hosting forever.

Who should own the domain and account?

For a buyer’s live website, the buyer should control their domain and production account. Document any access you retain and the maintenance responsibilities before launch.

Can I guarantee more sales or search traffic?

No. A clear page may remove friction, but traffic, the offer and buyer behavior are separate factors. Do not invent a conversion lift or ranking promise.

What should I do about forms?

Keep a practice sample demo-only. For real forms, confirm where data goes, what is collected, access controls, consent and deletion responsibilities. Scope extra work explicitly.