Copywriting Brief Template for a SaaS Landing Page
Use a copywriting brief template and a completed SaaS landing page example to define the audience, inputs, and acceptance criteria.
A useful copywriting brief lets a writer make the same decisions about the page that your team would make. To brief a copywriter for a SaaS landing page, write down the visitor’s question, the answer the page should give, and what the visitor can do next. Attach the sources the writer needs to verify that answer.
Take a shift handoff tool. A support operations manager clicks through from an email about weekend coverage. They want to see how the Monday lead picks up open tickets. The page needs to show what the weekend agent enters and what the Monday lead sees. If that fits their team, the manager can request a demo. That single question gives the writer a goal, a scenario to illustrate, and a reason for the button. The template below turns those decisions into an assignment. The example follows it through to the first draft and review.
How to write the assignment
Write the assignment in sentences you could read aloud to your writer. Name the deliverable, the reader, the question the page should answer, and the next action. If the assignment says “explain the product,” spell out what the reader needs to see before deciding whether to act.
Assignment formula
Write [deliverable] for [reader in a specific situation]. Show [the answer to the reader’s question through a concrete example]. Invite them to [next action].
Completed assignment
Write a landing page for support operations managers arriving from an email about weekend coverage. Use one open ticket to show what the weekend agent enters manually and where the Monday lead sees the owner, due time, and next step. Invite the reader to request a demo.
That gives the writer a scene to build the page around. One filled-in card can show what passes from one shift to the next. The demo and help article give the writer enough detail to describe the handoff accurately. Put those sources in the context section.
Fields to give the writer context
Add these fields below the assignment in your shared document. For an open question, add the person who can answer it and the date you need a decision. The writer can start on the sections with enough evidence while your team resolves outstanding details.
| Field | Fill in |
|---|---|
| Page and campaign context | [Page type, reason for launching, traffic source, campaign and launch date] |
| Audience | [Job title, situation, current workaround, question they need answered before taking the next step] |
| What happens after the click | [Where the main button leads and what happens after submission] |
| Use case | [What prompts the user to open the product, what they do, and what result they see] |
| Inputs | [Link to documentation, demo recording, customer interview notes, and owner for each source] |
| Approved claims | [Capability, conditions or plan requirements, supporting source, and date checked] |
| Constraints | [Confidential information, unverified claims, approved terms, and any limits on section length] |
| Deliverables | [Page sections, file format, required variants, and any form or confirmation copy] |
Start with the visitor’s question, then describe the workflow and find the sources that show it. For the weekend handoff, find a recording that shows both sides. The writer needs to see a weekend agent create a card and a Monday lead open the incoming list. Add the help article for the card fields and make sure the writer can open both sources.
Flag any upcoming features shown in the recording. If the writer sees automatic ticket imports in a test workspace, they might assume the current workflow takes care of that step. The support operations manager could then book a demo expecting less manual work. The example brief below spells out how tickets get into the tool so the writer can set that expectation on the page.
A completed landing page copy brief example
Relay Desk is a fictional SaaS tool for support shift handoffs. The features, source documents, campaign, and workflow in this example are invented. The brief is for a standalone page aimed at US B2B SaaS support teams.
| Field | Completed brief |
|---|---|
| Page and campaign context | Create a landing page for an email about weekend support coverage. In the email, the Monday lead searches a Slack channel to find which tickets are still open and which customers were promised a follow-up. |
| Audience | Support operations managers at US SaaS companies with staggered or weekend coverage. They already have a help desk and use team chat for handoffs. Before booking a demo, they want to know what agents enter manually and where the next shift sees its follow-ups. |
| What happens after the click | “Book a demo” opens a request form. A sales rep emails the visitor to arrange a time after submission. |
| Use case | A Saturday agent is handling a workspace-access ticket. Before signing off, she creates a handoff card, assigns it to the Monday lead, sets a follow-up time, and asks the incoming lead to check with the account admin that the invitation went out. The Monday lead opens the incoming shift list and sees the ticket summary, owner, deadline, and next action. |
| Inputs | The “Weekend Handoff” demo from minute two to minute four shows card creation and the incoming shift list. The “Handoff Card Fields” help article documents manual entry and the available fields. The “Demo Request Follow-Up” sales note explains the form and follow-up. Product owns the demo and help article. Sales owns the follow-up note. |
| Approved claims | Agents can enter an owner, a due time, and a next step when they create a handoff card. The assigned shift can see its cards in the incoming shift list. Use the help article and demo for these claims. Use the sales note for what happens after form submission. |
| Constraints | Agents add tickets to Relay Desk manually. Leave automatic imports out of the copy until product confirms release. Use “handoff card” consistently. Make up the ticket example and keep actual customer names, ticket IDs, and account details out of the page. |
| Deliverables | One shared document with hero copy, a three-step workflow, one filled-in card, three FAQs, a repeated demo button, and a line below the form explaining follow-up. Add a source link or timestamp next to each product claim in the review draft. |
The page could open with “Hand off open tickets to the next shift.” The supporting copy might read, “Add an owner, a due time, and a next step to each handoff card. The incoming team sees its cards in one list.” Then show the weekend ticket in a card so the reader can see the information an agent enters and what the Monday lead has to work with.
Give the card a caption that makes the manual step visible. “Before you sign off, create a handoff card for any ticket that needs a follow-up.” The reader can now see who does the work and when. That answers the question they brought from the campaign.
Suppose someone suggests “Finish every handoff in under five minutes.” Ask what was timed, how many tickets were involved, and whether those conditions match the reader’s use case. The demo supports the workflow shown on the page. To support a claim about elapsed time, the team would need measurements from a defined scenario. Until those are available, the filled-in card gives readers a concrete way to judge the work involved.
Review and deadlines
Fields to fill in
- First draft, consolidated feedback, and final copy [dates].
- Product claims and form copy [reviewers].
- Consolidating feedback and resolving disagreements [owner].
Relay Desk example
Marketing shares the brief and sources on Monday. The writer delivers a first draft Thursday. On Friday, product checks capabilities, sales checks the form copy, and marketing consolidates feedback. The writer delivers clean copy the following Monday.
Acceptance criteria
Open the draft alongside the completed brief and follow the visitor from the hero to the request form. They should recognize the weekend handoff, see what each agent does, and decide whether to book a demo. The team can check each step against the brief.
- The hero identifies the shift handoff problem and describes what happens to open tickets. A support operations manager can recognize the situation without reading the FAQs.
- The example includes an owner, a due time, and a next step. The order of actions matches the demo, and the interface terms match the help article.
- Each capability has a source the product reviewer can open. The workflow states that agents create handoff cards manually.
- Both demo buttons lead to the request form. The form copy says that a rep will email to arrange a time.
- The draft includes every commissioned section, and the example contains only fictional ticket and account information.
If the draft gives equal weight to a demo, a trial, and a sales deck, go back to the assignment. The manager came to see how a weekend handoff works. Once the page answers that question, give them one next step and check that the form delivers what the button promises.
Assign one person to consolidate feedback. If product wants manual entry visible and marketing wants a short hero, the reviewer can put the detail in the workflow block where the reader is deciding how the process will fit into a shift. Record that decision in the review draft so it carries through to design and the final copy.
Fill out the template before assigning your next SaaS landing page. Share it with the writer and the people who will review the draft.
Let’s plan your technical article
Tell us about the product and audience. We’ll help choose a topic, format and outline.
Discuss a project