Landing Page Design Services

It turns your approved campaign and offer into a page design your builders can understand and build. Softscotch settles the content order, the words on the page, how it adapts to different screens, form and interaction states, the visual style, reusable page parts, accessibility requirements and the handover details that a polished screenshot usually leaves out. On its own, it doesn't create a working page or guarantee any sales result.

Your proposal can include a signed page brief, agreed page copy, wireframes with real content, the visual style, mobile and form states, reusable page parts, accessibility notes, a prototype review, approved design files and an annotated handover for your builders. It names the exact page and versions, review rounds, who writes the copy, the design tool, included images, who builds the page, outside costs and what's not included.

Not automatically. Design-only work ends with the approved handover package. A review of the test build or the actual build can be added, and our full Landing Pages service can take you from planning all the way to a working, launched page. Work in your CMS or page builder, connecting systems, analytics, hosting, putting the page live and upkeep are separate unless written into your proposal.

Choose Landing Pages when you want Softscotch to take care of a working page through building, connecting systems and launch. Choose Landing Page CRO when you already have a live page and need its data looked at, changes made and results measured. Landing Page Design is the narrower service that runs from brief to handover, though a proposal can combine these services with separate deliverables, fees and owners.

We usually aim to deliver a signed design brief, cost outline and list of dependencies within 3 to 5 business days once we have your campaign, offer, content, brand, platform details and decision makers. It names the included page and versions, the page's job, which wireframe comes first, missing content and images, tool and specialist costs, review dates, who will build the page and what's not included.

You provide or approve the audience, offer, price, who qualifies, product facts, proof, claims, terms, brand materials, the campaign that sends visitors, your platform's current limits, what you assume about forms and your CRM, editable images and files and usage rights. We also need access to the right tools, a contact on the build team, the risk reviewers you appoint and decision makers who can approve content and design within the planned time.

We can include the page copy named in your proposal, such as headings, where proof goes, button text, form labels, help text, error messages and confirmations. Deeper customer research, positioning, building your offer or a larger copywriting program is priced separately. Your team approves product facts, claims, terms, prices and proof.

Yes, wherever approved or realistic content is available. We test agreed long, short, missing, expired and error examples, and provide sample screens plus rules for stacking, wrapping, order, spacing, images and elements that stick to the screen. There's no standard number of screens, and the built page still needs checks at in-between widths, with larger text settings and with text reflowing to fit.

Yes, when a form is included. We can cover labels, instructions, focus, correct and incorrect entries, loading, server failure, duplicates, "are you human" tests, confirmation and recovery. We only use a multi-step form when it makes a genuinely complex set of questions clearer. The working error checks, saving progress, spam protection, data security, creating records in your CRM and sending leads to the right person stay with your builders unless added.

We can write notes on the intended page structure, reading order, keyboard and focus behavior, contrast, labels, errors, tap target sizes, text reflow, animation and alternatives, against the agreed target. A design file, design tool add-on or automated check can't prove WCAG conformance (the main web accessibility standard), certification, legal compliance or how screen readers and other assistive technology will behave, so testing of the built page and by a qualified specialist may still be needed.

When we suggest animation, we state its purpose, what triggers it, how long it lasts, how it can be controlled and its likely cost to page speed, and we provide an approved calmer or still version for non-essential movement, for people who turn animation off on their device. Your builders must build and test this; a design review alone can't confirm it works in every browser or device.

We set out each image or video's purpose, cropping, size, versions for different screens and loading priority, plus font licenses, backup fonts and how to stop the layout jumping. The final file compression, code, delivery, loading of outside scripts and Core Web Vitals (Google's page speed and stability scores) belong to your builders and need testing on the built page and with real visitors.

It contains the approved design version, included editable files, final copy, reusable page parts and their versions, named design settings, rules for screen sizes and interactions, images and license details, requirement notes, links to the build, known limits, build checks and next owners. The exact contents, how long you keep access and any review of the test build are written in your proposal.

We don't assume any particular design tool. Figma can help with comparing versions, notes, images and developer review, but you may need a paid plan or paid seats to use some of these features. Tool seats, premium fonts, stock or custom photos and video, paying research participants, translation, specialist reviews, building, connecting systems, hosting and ongoing optimization are separate unless your proposal lists them.

The built page should keep the approved content order, page parts, states and visual style under the agreed conditions. An exact pixel-for-pixel match on every screen size, browser, font, language, zoom level and personal setting isn't realistic, and isn't always a good thing. Making the page adapt properly to screens, have the right structure and work for everyone can require deliberate differences.

No. A prototype review can reveal unclear content, missing states or places where buyers get stuck, and we can prepare clearly different versions for an approved test. But a design file can't split real traffic fairly, track reliably who saw what and what they did, reach a large enough sample or prove cause and effect, and we don't promise more conversions, leads or revenue.

Your builders build and test the page. When included, we can offer a set period for answering questions, compare an agreed test build with the design, design extra approved versions or look after reusable page parts. Building, putting the page live, analytics, sending leads to your CRM, live monitoring and CRO don't continue automatically after a design-only handover.

We usually aim to deliver the first brief and cost plan within 3 to 5 business days once inputs are ready, realistic wireframes in weeks 1 to 2 and a visual style you can review in weeks 2 to 4. An annotated handover usually follows in weeks 4 to 6, when content, images, platform decisions and approvals are ready. Pricing depends on the included pages and versions, copywriting, forms, reusable page parts, images, review rounds, tool access, specialist input and handover support. These are planning ranges that depend on those inputs, and fees, outside costs, limits and what's not included are written down before work begins.