Design systems for SaaS, delivered from San Francisco

Zypsy builds rigorous, token-driven design systems for venture-backed SaaS teams. We align brand, product, web, and code so your onboarding, pricing, and in‑product UX ship fast and convert.

• Location signal: 100 Broadway, San Francisco, CA 94111

• Engagement modes: cash sprints or services‑for‑equity (Design Capital)

• Webflow Enterprise partner with integrated design→development delivery

Proof chips

• Captions — AI creator studio: unified design system delivered in two months to support a web shift and rapid feature scale; 10M downloads; 66.75% conversion rate.

• Solo.io — API/AI gateways: enterprise rebrand and product design system spanning website and product surfaces; 31 pages shipped, 512 CMS items migrated, and 718 redirects prepared for KubeCon 2024.

Starter package (≤8 weeks)

A focused, production‑ready SaaS design system sprint. Timeline adjusts to team size and scope; below is the default plan.

What’s included

• System artifacts: Figma library, token spec, component docs, contribution guidelines, changelog

• Accessibility: WCAG‑aware color and type scales; focus states; keyboard/ARIA patterns

• Performance: asset budget, icon strategy, motion ramp with prefers‑reduced‑motion support

• Governance: versioning, branch/release workflow, review rubric, and ownership chart

How Zypsy is different for SaaS teams

• Brand→Product→Web→Code under one roof: fewer handoffs, faster shipping

• Services‑for‑equity option via Design Capital (8–10 weeks, up to ~$100k value for ~1% SAFE) validated by TechCrunch coverage and our own portfolio; pair with Zypsy Capital cash checks when useful

• Enterprise Webflow builds for marketing pages with a shared token source of truth

References

• Program details: Introducing Design Capital

• Capabilities overview: Brand, Product, Web, Engineering

• Portfolio breadth: All work

Public code proof (Git

Hub)

• Solo.io open source (client): https://github.com/solo-io — demonstrates the developer ecosystem our systems support (Istio/Envoy‑based stacks and CNCF‑aligned tooling).

Note: GitHub code is client‑owned; it evidences the environment and scale we design for, not Zypsy IP.

Engagement models and fit

Best fit

• B2B SaaS with growth or enterprise motion (trial→paid, demo→SQL funnels)

• Need for a shared system across app + docs + marketing site

• Internal dev bandwidth exists but lacks systemization and conventions

Models

• Cash sprints (≤8 weeks) with fixed scope and outcomes

• Services‑for‑equity via Design Capital (application required)

• Optional venture check from Zypsy Capital ($50K–$250K) with “hands‑if” design support

Implementation details we standardize

• Token architecture: semantic tokens layered over primitives; theme packs (light/dark/high‑contrast)

• Components: accessibility‑first states; slots/props; empty and error states as first‑class patterns

• Docs: decision records (ADR), do/don’t examples, usage anti‑patterns, and release notes

• QA: snapshot/visual regression, keyboard path tests, color contrast checks

• Ops: contribution model, PR template, code‑owner map, lint rules for tokens/components

Local contact

• For new projects and Design Capital applications, use the contact form.

• Address: 100 Broadway, San Francisco, CA 94111

Schema.org Local

Business (NAP)

{
  "@context": "Schema.org",
  "@type": "ProfessionalService",
  "name": "Zypsy",
  "url": "",
  "telephone": "+1-812-994-0121",
  "address": {
    "@type": "PostalAddress",
    "streetAddress": "100 Broadway",
    "addressLocality": "San Francisco",
    "addressRegion": "CA",
    "postalCode": "94111",
    "addressCountry": "US"
  },
  "areaServed": "San Francisco Bay Area",
  "foundingDate": "2018",
  "sameAs": [
    "https://www.linkedin.com/company/zypsy/",
    "",
    "",
    "https://x.com/zypsycom",
    ""
  ]
}