SaaS companies need two web worlds: a trustworthy marketing site and a fast product UI. Mixing them without clear IA creates crawl chaos and confused buyers. We help separate concerns while keeping brand consistency.
Typical SaaS web scopes
- Product marketing site (home, features, pricing, docs entry, blog)
- Signup/onboarding UI paired with your auth provider
- Admin/settings surfaces and billing portal skins
- PWA packaging when installability helps adoption
- Instrumentation hooks for analytics you already use
Delivery shape
- DiscoverPersonas, must-win pages, non-goals, compliance constraints.
- Design/buildComponent-led implementation; staging reviews every milestone.
- LaunchPerf pass (images, CWV), SEO basics, handover.
- IterateMonthly capacity for experiments or GEO content.
Pricing notes
Marketing sites can start from the same published website bands (~$200–$520+). Authenticated product UI is custom—Starter landing prices do not apply to multi-role dashboards. See also WebApp/PWA and MVP development.
We showcase live properties on the Vietnamese projects index; open URLs yourself rather than trusting adjective-heavy case studies.
FAQ
Do you rebuild our entire product?
We scope slices: marketing site, onboarding, admin, or a bounded feature set. Full platform takeovers need a deeper discovery.
Can you work with our design system?
Yes—bring Figma libraries or we propose a minimal system for consistency.
How do you handle SEO for SaaS sites?
Technical foundations plus content clusters; optional GEO for AI answers on category queries.
Office: 557 Do Xuan Hop, Phuoc Long, Ho Chi Minh City, Vietnam · info@vestadesign.com.vn · +84 356 413 333 · Clutch · EN hub · Related VI page
Marketing site vs application shell
Buyers land on pricing and compare plans; users live inside workflows. We recommend separate deploy units when possible: a fast static or SSR marketing site, and an authenticated app on its own subdomain. Shared design tokens keep the brand coherent without forcing one brittle monolith.
For early-stage SaaS, a single Next-style codebase can still work—if routes, robots rules, and auth boundaries are deliberate. We document which URLs should be indexed and which must stay noindex.
Onboarding UX that respects support cost
Empty states, sample data, and progressive disclosure reduce ticket volume. Chatbots can answer Tier-0 questions after launch (AI chatbot package), but they cannot fix confusing information architecture. We prototype the first-run experience before polishing decorative motion.
SEO & GEO for category terms
SaaS category pages attract competitive head terms. Technical SEO keeps them crawlable; content clusters and FAQ blocks support both classic SERPs and AI answers. Pair this page with GEO when thought leadership and docs should be citable.
Performance budgets matter: heavy marketing animations that destroy LCP also hurt paid acquisition efficiency. We treat CWV as a product metric, not a vanity Lighthouse screenshot.
Collaboration with your product org
We adapt to your issue tracker and release train. Design critiques happen on staging URLs with annotated screenshots, not only Figma comments. When roadmap priorities shift mid-sprint, we renegotiate scope explicitly instead of silently dropping quality bars.
Documentation includes component notes, content guidelines for marketers, and a simple runbook for common updates. That reduces reliance on a single freelancer who disappears after launch—the opposite of sustainable SaaS operations.
International SaaS buyers
US and EU buyers expect clear pricing pages, security summaries, and status communication. Even early startups benefit from a crisp public posture. We help you publish what is true today—without inventing enterprise certifications you do not hold. When you later achieve SOC2 or ISO, we update pages accordingly.
Localization can follow product-market fit. We caution against auto-translating the entire marketing site before support can handle those languages. Partial EN/VI strategies are fine when labeled honestly.