Prompt 654 words Copy
# Design from Reference: Spendesk Use cases
Create an original, high-fidelity visual design inspired by the reference. Prioritize composition, typography, colors, spacing, and component styling over technical implementation.
## Reference
- **Product:** Spendesk
- **Category:** Use Cases
- **Screenshot:** attached to this message (also available at https://media.saasframe.io/o/b89622be01d133bf7d9b.webp)
- **Source:** https://www.spendesk.com/en/use-cases
Analyze the attached screenshot first. If no image is attached, open the screenshot link; if neither is accessible, ask for it rather than guessing.
## Visual Design Context
### Overall aesthetic
- **Character:** Polished use-case overview with soft lavender bands, strong purple actions and friendly illustrated team roles.
### Page composition
- **Canvas:** 1440 × 3126 screenshot pixels; CSS estimates are near screenshot scale, with capture scale unverified.
- **Sequence:** Navigation/lavender hero; six use-case links; six team-role descriptions; lavender testimonial; saturated purple CTA; white footer.
### Information hierarchy
- **Priority:** Centered title and paired demo/trial actions introduce the page. Use cases and team roles form separate three-column, two-row groups.
- **Captured detail:** Duplicate plain labels/chevrons appear beneath the elevated use-case tiles; treat this as a visible rendering artifact, not a recommended design pattern.
### Typography
- **Family:** Neutral rounded sans-serif; exact font is unverified.
- **Scale:** Estimated CSS hero 48px, section titles 32–36px, role headings 18px, body 17–18px and compact tile labels 16px.
### Colors & surfaces
- **Sampled palette:** White #FFFFFF; pale lavender #F7F3FE; deep purple #4C1BAF.
- **Accents:** Purple icons/actions, small pastel role portraits, dark navy text and a mint primary action in the lower purple band.
### Components
- **Use-case tiles:** White shadowed horizontal cards with pale icon squares and small right chevrons; estimated 8px radii.
- **Roles:** Small circular illustrated avatars above heading/description, without enclosing cards.
- **Actions:** Filled/outlined rectangular pair, about 50px CSS high and 6px radii. Footer includes four link groups, legal/language row and chat launcher.
### Visual rhythm
- **Spacing:** Broad 80–112px CSS section padding and generous gutters; centered testimonial supplies a visual pause.
### Responsive
- **Guidance:** Mobile is not shown. Stack tiles/roles, wrap action pairs and omit accidental duplicate labels.
### Adaptation guidance
- **Transfer:** Preserve separate task-based and team-based browsing. Use relevant roles, clean rendering and verified testimonial content.
## Content
**Instructions:**
Generate realistic example content that fits the selected design reference.
Create appropriate headlines, descriptions, labels, buttons, and supporting copy based on the type of interface being designed.
If a product or business description is provided, use it to guide the content.
Otherwise, invent a plausible fictional SaaS product appropriate for the reference.
Keep the content concise, coherent, and visually balanced.
Do not present fictional statistics, customer names, or testimonials as verified facts.
## Design Direction
**Instructions:**
Use the reference screenshot as the main source of visual inspiration rather than a strict layout template.
Preserve its most distinctive design characteristics, such as typography, visual rhythm, color relationships, component treatments, and overall aesthetic.
Feel free to modify section arrangements, proportions, spacing, and individual components to better suit my content.
Introduce original design decisions where they improve usability, composition, or brand consistency.
The result should clearly reflect the reference's visual language without looking like a direct reproduction.
Follow the visual identity of the reference design.
Use its typography, color palette, component styling, and overall aesthetic as the primary design direction.
Do not introduce an unrelated visual identity.
## Output
**Instructions:**
Generate a high-fidelity visual mockup of the requested interface.
Present the design as a polished, realistic website or product UI screenshot.
Prioritize visual composition, typography, spacing, colors, alignment, and component details.
Use the available image-generation or visual-design capabilities.
Do not replace the mockup with source code, a written design specification, or a textual description.
If direct visual generation is unavailable, clearly explain the limitation.
## Constraints
- Use the actual screenshot as the primary visual reference.
- Preserve essential messaging and factual accuracy.
- Prioritize visual quality and consistency.
- Do not invent unsupported product claims.
- Adapt structure and copy length for visual balance. Reference image Attach it to your message: assistants can’t open image links. Open in ChatGPT ↗ Open in Claude ↗
Build it in Lovable ↗ v0 ↗ Figma Make ↗
Opening a tool copies the screenshot so you can paste it with your prompt.