SAAS LAUNCH DESIGN BRIEF From DesignPal | https://designpal.io Updated October 14, 2026 Use and adapt this template for your own projects. No attribution required. Copy it into your document or project board. Replace the prompts with answers. Start with one deliverable, then add the next item to the queue. 1. THE FIRST DELIVERABLE What are we making first? Name one item, such as a landing-page hero, a five-slide launch deck or three ad concepts. State what is outside scope. Deliverable: Out of scope: 2. THE PERSON AND THE MOMENT Who will see this? Include their role, company stage, immediate problem and where they will encounter the work. Avoid "everyone who uses software." Audience: Where they will see it: What they already know: 3. THE MESSAGE What should that person understand after one glance? Write one sentence. Then list the evidence you can actually support. Mark unverified claims. Main message: Supporting facts or approved proof: Claims we cannot make: 4. THE NEXT ACTION What should the viewer do next? Choose one primary action, such as requesting a demo, starting a trial or reading a product explanation. Primary action: Destination URL: How we will observe it: 5. CONTENT AND INPUTS Link the approved copy, product screenshots, logo, fonts, brand guidelines and source files. Name the owner of each missing item. Use test data in screenshots; remove private customer information and credentials. Approved copy: Brand and product assets: Missing inputs and owners: 6. FORMAT AND ACCESSIBILITY Give dimensions, placement, device sizes, file formats and handoff needs. Include readable text, color contrast, descriptive image text and any requirements the designer needs to follow. For a website, distinguish design files from development and implementation. Formats and sizes: Devices or placements: Accessibility and other requirements: Handoff files: Design only, development, or both: 7. CREATIVE DIRECTION Share two references and explain one useful quality of each. List what to avoid. References guide the work; they are not instructions to copy. Reference 1 and why: Reference 2 and why: Avoid: 8. TIMING AND CAPACITY Separate the first-draft date from review and launch. Check dependencies and agree what can fit into the available design capacity and budget. First draft: Feedback due: Final handoff: Launch: Budget or available design capacity: Dependencies: 9. ONE FEEDBACK OWNER Name one person who consolidates feedback and one final approver. Agree what counts as ready before design starts. Keep new requests separate. Feedback owner: Final approver: Ready when: 10. FIRST REVIEW Check the work against the audience, message, action and agreed scope. Separate required corrections from new ideas. A useful feedback note says what is unclear, who it affects and what the work needs to achieve. Required corrections: New ideas for a later request: EXAMPLE: A SMALL, FICTIONAL SAAS LAUNCH This is an illustrative brief, not a DesignPal customer project. Deliverable: Desktop and mobile hero design for a product-launch workspace. Audience: Product marketers at growing B2B SaaS companies coordinating an upcoming launch across product, marketing and sales. Message: Give the whole launch team one shared plan. Action: Request a product demo. Inputs: Approved headline, product screenshot, logo and three product facts. Scope: Hero layout and handoff files. Development and the remaining page sections are separate requests. No invented customer logos or results. Ready when: The audience can identify the product, understand the message and find the demo action. Copy and screenshots remain readable on mobile. WHEN YOU NEED ONGOING DESIGN DesignPal offers brand, web and launch design subscriptions from $1,495/month, with 1-3 active requests by plan. Timing depends on the agreed scope. A trial inquiry is reviewed before a needs call, qualification, an agreed brief and a team-issued trial checkout link. Guide: https://designpal.io/blog/design-brief-template-and-examples-write-a-brief-your-designer-will-love Plans: https://designpal.io/pricing