Joyce Doan / Work / Skalaview Website
AI Marketing Platform · UI/UX Designer

Skalaview Website

Designed the website and brand identity for Skalaview — an AI-powered digital marketing and e-commerce platform serving retail, healthcare, and real estate businesses across Vietnam and Singapore.

UI/UX Designer BRANDINGWEB DESIGNWEBFLOWFIGMA
Website
skalaview.com ↗
Focus
Brand Identity · Web Design · IA
Scope
Full Website · Bilingual (EN/VI)
Platform
Webflow
Markets
Vietnam · Singapore
Year
2025
01 — Context

The Challenge

Skalaview is a digital marketing and e-commerce company that uses generative AI to help brands grow their online presence, automate sales processes, and engage customers more effectively. Their platform combines AI Assistants, AI Performance Marketing, and AI Insights into a single offering — serving businesses across retail, healthcare, and real estate in Vietnam and Singapore.

The challenge was translating a technically sophisticated AI platform into a website that business owners could immediately understand and trust. The risk on both sides was real: too much technical language and you lose the SME decision-maker; too much marketing language and you lose credibility with the tech-evaluating buyer.

My Role

I was part of the in-house design team at Skalaview, working alongside marketing, development, and the founding team. My work covered the full design surface: brand identity, UI design, design system setup, and Webflow execution — including the bilingual (English and Vietnamese) site experience.

02 — Discovery

Research & Key Insights

AI product marketing operates differently from standard SaaS. Four patterns shaped the design direction.

01

SMEs need outcomes, not features

Small and medium business owners don't evaluate AI capabilities — they evaluate whether the product will help them sell more, save time, or find customers. Feature-first copy loses them immediately.

02

Trust is built through specificity

Vague AI claims ("cutting-edge," "revolutionary") are everywhere and signal nothing. Concrete use cases — inventory automation, appointment scheduling, customer support — are what make the platform feel real and applicable.

03

Bilingual isn't just translation

Vietnamese and English audiences have different expectations around formality, hierarchy, and trust signals. The bilingual site needed to feel native in both — not just a direct word swap between versions.

04

Partnership framing over vendor framing

Skalaview's positioning is explicitly about partnership — "more than choosing a service provider." The visual and content system had to reinforce that tone consistently, not undercut it with transactional UI patterns.

03 — Design

Key Design Decisions

Decision 01

Lead with outcomes, not AI terminology

The hero and service sections were framed around what the business gains — improved visibility, streamlined sales, better customer engagement — rather than the underlying AI technology. "Customized marketing solutions" and "streamlining sales processes" land faster for an SME owner than any model name or technical spec.

Decision 02

Modular design system for bilingual content

A modular component system was critical for the bilingual build — Vietnamese text is typically shorter in character count but denser in meaning, while English can run longer in UI-sensitive spots. Every component was designed to absorb both language variants without breaking layout or hierarchy.

Decision 03

Industry verticals as navigation anchors

Rather than organizing by product alone, the site uses industry context (retail, healthcare, real estate) to help prospects self-identify. A healthcare business evaluating AI assistants needs to see their own use case — appointment scheduling, patient queries — not a generic feature list.

Decision 04

Clear visual hierarchy for data-driven content

Skalaview's platform generates insights and analytics — the website needed to reflect that capability through confident, structured layout. Dense information was organized through clear typographic hierarchy, section rhythm, and whitespace so data-heavy sections felt structured rather than overwhelming.

04 — Architecture

Site Architecture

The navigation was structured around the four core product areas, with About and Partnerships completing the trust layer for prospects doing due diligence.

Site Map
Home — brand entry and platform overview
AI Assistants — automation across verticals
AI Performance Marketing — campaign optimization
AI Insights — analytics and recommendations
Partnerships — co-growth and integration partners
About Us — mission, team, and culture
Audience Journeys
SME Decision-Maker
Home AI Marketing Contact
Operations / E-commerce
Home AI Assistants Contact
Partner / Investor
About Partnerships Contact
05 — Foundation

Design System

A modular component library was built to support the bilingual site, content scalability across product pages, and consistent handoff to the development team for Webflow implementation.

Figma File Structure
Pages
📄Cover
📄Brand Identity
📄Design System
📄Wireframes
📄Desktop — Final
📄Mobile — Final
📄Handoff & Specs
Components Built
Navigation bar + language switcher Service pillar cards Industry vertical sections Team member cards Buttons + CTAs (all states) Footer + contact forms
Foundations
Typography hierarchy Color palette + brand tokens Spacing scale Responsive grid system
Component States
Default Hover Active Disabled Error & Success
06 — Outcome

Result

Skalaview launched with a bilingual website that communicates a technically sophisticated AI platform in terms that SME decision-makers can immediately evaluate and act on. The modular system supports ongoing content expansion across product pages, industry verticals, and both language variants without requiring design rework.

The partnership framing — reinforced through tone, layout, and the About and Partnerships pages — gave the brand a distinctive position in a market where AI vendors typically lead with technology rather than relationship.

Reflection

The bilingual requirement was the most technically demanding part of the project — not the translation itself, but ensuring every component held together in both languages without layout drift. Building the modular system before touching any page-level design was the right call. Without that foundation, the bilingual build would have been unmanageable. If I were doing this again, I'd involve the Vietnamese copywriter earlier in the process so language constraints informed component sizing from the start, rather than being handled as an adaptation step.

← Previous Marketing Center Next → Reserve Manager
Get in touch

Have a problem worth designing?

Let's talk