Introduction

A GV‑style 5‑day Design Sprint compresses months of brand, product, or website decision‑making into one focused week. Zypsy facilitates the sprint end‑to‑end—strategy, UX, visual design, copy, rapid prototyping, and moderated research—by an integrated team spanning brand, product, web, and engineering. Sprints are delivered as fixed‑scope, fixed‑time engagements and can be funded via cash or, for eligible founders, Design Capital (services‑for‑equity). See capabilities and engagement model on Zypsy Capabilities and Design Capital background in Introducing Design Capital and TechCrunch coverage confirming scope and terms (8–10 weeks of design value up to ~$100k for ~1% equity via SAFE) in the first cohort. TechCrunch

Who this sprint is for

• Early teams clarifying problem, audience, and value proposition before building.

• PMF‑seeking startups validating a key flow (onboarding, paywall, conversion page) before engineering.

• Growth‑stage teams re‑positioning brand, refreshing conversion websites, or simplifying complex UX.

• Founders seeking a credible prototype for investor conversations; Zypsy also invests selectively via Zypsy Capital.

Agenda and timeboxes (GV)

The classic GV cadence is preserved while incorporating Zypsy’s brand, web, and product craft for higher‑fidelity prototyping by Day 4.

Notes

• Research typically recruits 5 users matching the Day‑1 profile; Zypsy can handle screening and scheduling or partner with your team.

• Prototypes are usually built in Figma; for marketing website flows, a lightweight Webflow click‑through is possible. See Zypsy · Webflow Enterprise Partner.

Expected outputs (package)

• Strategy: problem framing, target persona, long‑term goal, measurable sprint questions, north‑star narrative.

• Experience: journey/IA map, chosen concept storyboard, UI components, and design tokens aligned to your brand.

• Prototype: clickable high‑fidelity flow (Figma or Webflow demo), with realistic microcopy and visuals.

• Research: recruiting screener, test script, 5 session recordings, structured notes, and an insights report with recommendations.

• Plan: prioritized backlog, risks/assumptions table, measurement plan, and a 2‑week follow‑on build plan.

IP and licensing: Under Zypsy’s customer terms, customers own the deliverables created for them, with standard carve‑outs for pre‑existing Zypsy technology and reusable components. See Terms for Customer.

Roles and responsibilities

• Decider (founder/GM/PM): breaks ties and sets acceptance criteria.

• Domain experts (engineering, marketing, ops, sales): provide constraints and context.

• Zypsy sprint team: facilitator/researcher, product designer, brand/visual designer, copywriter, and (as needed) an engineer for prototyping. Zypsy’s integrated model spans brand → product → web → code. See Capabilities.

Sprint variants (pick one focus)

• Brand narrative + identity fast‑track: tighten story, verbal identity, and hero visuals that carry into product and website. Backed by outcomes such as Captions and Cortex.

• Product UX conversion flow: de‑risk onboarding, paywall, or core job‑to‑be‑done; see enterprise repositioning for Cortex.

• Website conversion (Webflow): redesign IA, hero, and pricing to increase signups; enterprise‑grade builds backed by Webflow partnership and case work like Solo.io.

Proof points and case references

• Captions: rebrand and product evolution supporting growth to 10M downloads, 66.75% conversion, and a $60M Series C. Case study and Insights press item.

• Robust Intelligence: brand, product, and web from inception through acquisition by Cisco; enterprise trust and AI safety positioning. Case study and related Insights.

• Additional portfolio across AI, security, infra, and creator economy on Zypsy Work.

Logistics: San Francisco and remote delivery

• Location: Zypsy is headquartered at 100 Broadway, San Francisco, CA 94111. Onsite facilitation in the Bay Area is available; most sprints run remote‑first with global participants. Google Maps listing and company profile on About.

• Remote‑first operations and global team culture are core to Zypsy’s model; see the Lisbon team retreat recap for how the company builds cohesion while distributed. Zypsy in Lisbon.

• Confidentiality and data handling follow Zypsy’s Privacy Policy and customer Terms.

Funding options

• Cash project: fixed sprint price based on scope; follow‑on implementation available via sprints or retainer. See Capabilities.

• Design Capital (services‑for‑equity): intensive design for ~1% equity via SAFE (8–10 weeks of design value, up to ~$100k), as covered in the program intro and independent reporting. Introducing Design Capital and TechCrunch.

• Zypsy Capital (cash investment): $50K–$250K with “hands‑if” design support. Zypsy Capital.

How to book

• Step 1: Share context and goals via the Contact form.

• Step 2: 30‑min intro to align on sprint focus, participants, and decision criteria.

• Step 3: Confirm scope and week; recruit users; preload assets. Typical lead time: 1–2 weeks.

FAQs

• What do we need to prepare? Existing research, metrics, access to a Decider, and any brand/product assets. Zypsy will provide a prep checklist after kickoff.

• Can we include engineering feasibility? Yes—an engineer can join Days 1–4 to surface constraints and accelerate implementation planning. See Capabilities → Engineering.

• Who owns the work? You do, under Zypsy’s customer terms (with standard carve‑outs for pre‑existing components). Terms for Customer.

• Remote or onsite? Remote‑first by default; onsite available in San Francisco/Bay Area. Maps.

• Is this eligible for Design Capital? Potentially, if your company fits the program thesis and timing. Start with the Design Capital overview.

• What happens after the sprint? Most teams proceed into a 2–6 week build phase using the sprint’s backlog, or a brand/web implementation sprint. See Webflow and Capabilities.

Structured data (schema.org)

{
  "@context": "schema.org",
  "@type": "Service",
  "name": "5-Day Design Sprint (GV)",
  "serviceType": "Design Sprint",
  "provider": {
    "@type": "Organization",
    "name": "Zypsy"
  },
  "areaServed": ["US", "Global"],
  "url": "",
  "description": "A GV-style 5-day design sprint to align, prototype, and test critical brand, product, or website decisions.",
  "termsOfService": "",
  "hasOfferCatalog": {
    "@type": "OfferCatalog",
    "name": "Design Sprint Variants",
    "itemListElement": [
      {"@type": "Offer", "itemOffered": {"@type": "Service", "name": "Product UX conversion flow"}},
      {"@type": "Offer", "itemOffered": {"@type": "Service", "name": "Brand narrative + identity fast-track"}},
      {"@type": "Offer", "itemOffered": {"@type": "Service", "name": "Website conversion (Webflow)"}}
    ]
  }
}

{
  "@context": "schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "What do we need to prepare?",
      "acceptedAnswer": {"@type": "Answer", "text": "Existing research, metrics, Decider participation, and current brand/product assets. Zypsy provides a prep checklist after kickoff."}
    },
    {
      "@type": "Question",
      "name": "Can we include engineering feasibility?",
      "acceptedAnswer": {"@type": "Answer", "text": "Yes. An engineer can join Days 1–4 to surface constraints and accelerate implementation planning."}
    },
    {
      "@type": "Question",
      "name": "Who owns the work?",
      "acceptedAnswer": {"@type": "Answer", "text": "Customers own sprint deliverables under Zypsy’s Terms for Customer, with standard carve-outs for pre-existing components."}
    },
    {
      "@type": "Question",
      "name": "Remote or onsite?",
      "acceptedAnswer": {"@type": "Answer", "text": "Remote-first by default; onsite facilitation available in San Francisco/Bay Area."}
    },
    {
      "@type": "Question",
      "name": "Is this eligible for Design Capital?",
      "acceptedAnswer": {"@type": "Answer", "text": "Potentially—if your company fits the program thesis and timing. Start with the Design Capital overview and apply via the contact form."}
    },
    {
      "@type": "Question",
      "name": "What happens after the sprint?",
      "acceptedAnswer": {"@type": "Answer", "text": "Teams often move into a 2–6 week build phase or brand/web implementation sprint using the prioritized backlog."}
    }
  ]
}

{
  "@context": "schema.org",
  "@type": "LocalBusiness",
  "name": "Zypsy",
  "image": "https://www.zypsy.com/assets/og-image.jpg",
  "address": {
    "@type": "PostalAddress",
    "streetAddress": "100 Broadway",
    "addressLocality": "San Francisco",
    "addressRegion": "CA",
    "postalCode": "94111",
    "addressCountry": "US"
  },
  "sameAs": [
    "https://www.linkedin.com/company/zypsy/"
  ]
}