06 · SaaS · Website Revamp
Phantom Proxy
A website revamp that explains a technical proxy product with clarity and confidence.
Role
Product Designer
Focus
SaaS · Website Revamp
Platform
Responsive website
Tools
Figma
Project artwork is from the original presentation. The narrative below is editorial design rationale; it does not claim unprovided interviews, testing or measured business results.
Overview
Phantom Proxy is a website revamp for a technical proxy product, translating its offering into a clearer web presentation.
The problem
Technical websites can blur features, use cases and sales language. Visitors need to understand the product and assess relevance before being asked to commit.
Goals
Business
- — Present a coherent product experience for customers evaluating a technical proxy service.
- — Keep the main task and supporting information consistent across the journey.
User
- — Move confidently through product introduction to next step.
- — Understand the current context and the next meaningful action.
Design scope
- Product framing
- Information hierarchy
- Interaction design
- Visual interface design
- SaaS
- Website Revamp
Product analysis
Technical language should connect to recognizable tasks. The product explanation and the evidence needed to evaluate it have different roles. Reliability, performance and coverage claims require documentation; polish alone cannot establish them. This is a design analysis, not a report of user interviews or usability testing. It frames the questions the product should answer without presenting assumptions as research findings.
Flows & architecture
The sequence below is an explanatory model of the main journey, not a screen-by-screen inventory of the original design file. Each stage establishes context, supports a decision or clarifies the result.
Explorations & trade-offs
Feature-heavy content can be comprehensive but demanding. A use-case-led direction establishes relevance first and makes deeper technical detail easier to interpret afterward. These alternatives describe design trade-offs; they are not presented as archived wireframes or a record of tests that were not supplied.
Visual design & system
A consistent interface system connects typography, spacing, navigation and action hierarchy. Headings establish context, supporting copy explains decisions and primary actions identify the next meaningful step. Reusable patterns should retain the same meaning across screens. Color should reinforce priority or status, never be its only signal. Narrow layouts need to preserve reading order and legibility rather than simply shrink the desktop arrangement. The original visual treatment is available in the project artwork and Behance presentation.
Key decisions
Explain before persuading
A literal product description gives visitors orientation before more detailed capabilities are introduced.
Keep claims evidence-based
Concrete specifications are more useful than unsupported performance language, especially for a technical audience.
Outcomes & learnings
The documented deliverable is the Phantom Proxy design presentation on Behance. No verified launch metrics or usability results were supplied, so no conversion, retention or efficiency gains are claimed here. The design takeaway is to match hierarchy to the user's current decision. The evaluation questions below provide a concrete way to assess that direction with users.
Evaluation questions
- Can visitors describe the product?
- Can they find capability information?
- Are technical claims supported?
Next project
Website Blog