Landing page proposals: copy + design split without two vague paragraphs

Landing page jobs sound simple until you open the thread. The client wants something that “converts,” looks modern, loads fast, and matches the brand. They may not know whether they need a copywriter, a designer, a developer, or one person who does all three. Your proposal should make that split obvious without dumping two vague paragraphs that could apply to any website on earth.

This guide is for freelancers who sell landing pages (or pieces of them): designers, copywriters, developers, and generalists who bundle work. The goal is a proposal structure clients can skim in thirty seconds and still understand deliverables, dependencies, and revision boundaries.

Why vague landing page proposals lose

Clients hiring for a single page are usually in a hurry. They skim for:

• Do you understand the offer (not just “a nice page”)?
• What exactly will I receive (files, sections, copy, mobile layout)?
• What do you need from me before you can start?
• Who owns copy versus layout versus implementation?

When you write “I will design a beautiful high-converting landing page” twice in different words, you trigger the same filter as generic agency spam. The fix is not more adjectives. It is a clear split between copy, design, and build, plus honest assumptions about what the client already has.

If your openings still sound interchangeable, compare them to the patterns in freelance proposal opening lines and the failure modes in why clients ignore your proposals.

The three lanes: copy, design, build

Think of a landing page as three lanes that can be done by one freelancer or three specialists.

Copy lane: headline, subhead, offer, proof, objections, CTA text, form microcopy, SEO title and meta if included.

Design lane: layout, visual hierarchy, spacing, typography, color, imagery direction, mobile composition, handoff files (Figma, etc.).

Build lane: responsive implementation, performance basics, form integration, analytics hooks, CMS or static deploy, QA on real devices.

Your proposal should state which lanes you cover and which lanes depend on the client or a partner. That single move prevents the classic dispute: “I thought copy was included.”

Open with outcome, then show the split

First paragraph: mirror their business outcome in one or two sentences.

Second block: your lane split in plain bullets or short paragraphs.

Example shape (adjust to your role):

You need a landing page that explains [offer] and drives [action]. I would handle [your lanes]. Copy would be [client-provided / collaborative / fully written by me]. Design would cover [specific deliverables]. Build would include [stack and launch support].

If you only do design, say that upfront. If you only write copy, say you deliver a wireframe-ready doc or section map. Clients respect boundaries more than surprise invoices.

Proposal template: copywriter-led

Use this when you write words and someone else designs or builds.

Hi [Name],

I can help with the copy for your landing page aimed at [audience] so the page clearly explains [offer] and pushes visitors toward [CTA].

What I deliver

• One primary page outline (hero, problem, solution, proof, FAQ if needed, final CTA)
• Headline and subhead options (2-3 directions)
• Section drafts ready for design handoff
• CTA and form microcopy
• One revision round on structure, one on polish (or define your rounds clearly)

What I need from you

• Offer details, pricing model, and objections you hear from leads
• Any existing brand voice notes or pages you like
• Access to current analytics or sales notes if you have them

What I do not include

• Visual design, Figma files, or development (happy to collaborate with your designer or dev)

Suggested sequence

1. Short call or async brief to confirm angle
2. Outline approval
3. Full copy draft
4. Revision and handoff

If design and build are open, I can recommend sequencing so copy approval happens before pixels get locked.

Proposal template: designer-led

Use this when you deliver visual design and optionally guide copy structure but do not write final marketing copy.

Hi [Name],

I can design a focused landing page for [product/service] that makes the offer scannable on mobile and desktop.

What I deliver

• Wireframe or lo-fi structure for key sections
• High-fidelity design for one primary page (desktop + mobile)
• Design system basics for the page (type, color, spacing, components used on-page)
• Export-ready handoff for development (Figma with specs, assets noted)

Copy assumptions

• Option A: You provide final copy before visual design
• Option B: I place placeholder copy and you replace before build
• Option C: I include light headline support, full copywriting quoted separately

What I need from you

• Brand assets (logo, fonts, colors) or examples you want to stay close to
• Proof elements you can share (logos, quotes, metrics you are allowed to publish)
• Decision-maker for approvals

Build

• Development is out of scope unless we add it as a second milestone. I can hand off to your dev or recommend one.

This version prevents the client from assuming you will rewrite their entire pitch deck.

Proposal template: developer-led full page

Use when you implement in Webflow, WordPress, Next.js, etc., and may depend on external copy and design.

Hi [Name],

I can build and launch a single landing page on [stack] that matches your approved design and loads cleanly on mobile.

What I deliver

• Responsive implementation from approved Figma (or similar)
• Form hookup to [tool]
• Basic on-page SEO structure (titles, headings, alt text if copy provides labels)
• Staging link for review, then production deploy
• Short handoff notes for edits you can make later

Dependencies

• Final copy and approved design before build starts (or I can quote a discovery milestone if those are missing)
• Hosting and domain access, or I can set up [specific host] if you prefer

Performance and scope

• Included: one page, agreed sections, up to [X] revision rounds on implementation details
• Not included: copywriting, brand design, custom illustration, complex animations, multi-language, ongoing A/B tests unless added

First milestone option

If copy or design is not ready, I suggest a paid setup milestone: confirm section list, stack, integrations, and timeline before full build.

That pattern pairs well with milestones when the client never mentioned them.

Proposal template: bundled copy + design + build

If you truly do all three, say so with sequenced deliverables, not one blob paragraph.

Phase 1: Message and section map (copy strategy) Phase 2: Visual design on approved copy Phase 3: Build, QA, launch Revisions: [define per phase]

Bundled work wins when you show the client they will not get stuck in endless redesign because copy changed after build. Each phase has an approval gate.

How to write the split without sounding bureaucratic

Clients do not want a legal contract in the first message. They want confidence. Keep the split short:

• Three to six bullets per lane
• One line on what you need from them
• One line on what is out of scope
• One suggested next step

Avoid repeating “high quality” and “professional.” Replace with specifics: number of sections, revision rounds, tools, and what “done” looks like (live URL, Figma link, Google Doc, etc.).

Revision and approval language that saves arguments

Landing pages fail on fuzzy approvals. State:

• How many revision rounds are included (not “unlimited tweaks”)
• Whether a round is copy, design, or build (do not mix all three in one endless loop)
• What starts a new paid phase (new offer, new audience, extra sections)

Example:

Included: two rounds of design feedback on the approved copy. Copy changes after design approval may require a small add-on or a new phase so layout stays stable.

Pricing posture when the post is vague

Many landing page posts say “need a page” with no assets. Do not fake a fixed price on unknown copy and unknown integrations.

Options:

• Quote Phase 1 only (discovery + section map + estimate for the rest)
• Give a range with clear drivers: number of sections, custom illustrations, copy included or not, form complexity
• Ask three questions that unlock a number: approved copy yes/no, design exists yes/no, integrations list

For broader pricing habits, see fixed-price project proposal pricing.

Mistakes that make you look like every other applicant

• Two paragraphs that both say “conversion-focused” with no deliverable list
• Promising results (“3x conversions”) with no baseline and no access to analytics
• Hiding that copy is missing when you are a designer (leads to rushed lorem ipsum launches)
• Hiding that design is missing when you are a developer (leads to build churn)
• One flat fee with no definition of extra sections, languages, or forms
• Attaching ten portfolio links with no tie to this offer

Use reference past work without dumping ten links when you show proof.

FAQ-style questions clients ask

Can you do it in 48 hours? Answer with what shrinks: pre-written copy, simple layout, no custom illustrations, client available for fast approvals. See 48-hour deadline proposals if you bid rush work.

We only have a rough idea. Propose a short discovery milestone. Show judgment in short job post proposals style: infer, assume, ask three sharp questions.

We have a designer already. Shrink your proposal to copy-only or build-only. Praise that structure; it reduces risk for everyone.

Checklist before you send

• First lines mention their offer and CTA, not your career story
• Copy, design, and build lanes are labeled (even if one person does all)
• Client inputs are listed (assets, access, approvals)
• Out of scope is explicit (SEO campaign, ads, multi-page site, unlimited revisions)
• Next step is one action (approve milestone, answer three bullets, share Figma)
• At least one proof point tied to a similar page or industry

Run the same pass with the proposal checklist before you hit submit.

Closing thought

Landing page proposals win when the client can forward your message to a cofounder and say, “This person knows what we are buying.” The copy plus design split is not paperwork. It is how you prove you have shipped pages before and you will not blur lanes until the week before launch.

If you want a faster first draft you still edit by hand, use Lervos to generate structure from the job post, then tighten the lane split and scope lines yourself. The judgment stays yours; the blank page does not.