Skip to content

A design team.
Not another handoff.

A senior designer in your Slack, reviews every week, and work that ships in your repo, not a Figma file nobody opens.

Agent product design

What the agent did, why, and what needs you.

Plans, approvals and work that runs for hours. We design everything between a person and an agent, from the first setup screen to the moment someone hits stop.

Seen in Arca, Adapt, SideShift, Polar

What’s included

  • Setup and onboarding, including setup by the user's own agent
  • Plans, tasks and handoffs between agents and people
  • Approvals, reviews and trust
  • Activity, status and history for long-running work
  • Chat, and the alternatives to chat
  • Notifications and agents that reach out first

Design systems agents can read

Your coding agent reads your design system now.

Components in React and Figma, plus the rules an agent follows: easing, timing, when to use a drawer instead of a modal. Engineers who can’t design ship pages that look designed.

Seen in Stealth client, Adapt, Arca

What’s included

  • Component libraries in Figma and React
  • Tokens and per-customer theming
  • Interaction and motion rules agents apply on their own
  • Documentation written for people and agents

Agent-ready brand identity

A brand that isn’t another purple gradient.

Naming, logo, type, color, characters and motion. It comes with a brand file Claude and Codex follow, so your next deck is on brand too. About six weeks.

Seen in Jarvie, Lucky Air Balloon

What’s included

  • Naming and positioning
  • Identity, type and color
  • Characters, mascots and motion
  • Brand files for Claude and Codex
  • Small brand tools that export on-brand assets

Taste on top of speed

You shipped it with Cursor. Now make it yours.

It works, and it looks like every other app. We polish one or two screens to 100%, then carry that language through the rest of the product.

Seen in SideShift, Vondy

What’s included

  • Product and UX audits
  • North star screens
  • One coherent structure and navigation
  • A visual language that scales

Research and strategy

Agents do the synthesis. Designers make the calls.

We hand an agent your query logs and interview notes. It writes the hypotheses. A designer checks every one. Then we design from what’s true.

Seen in Polar

What’s included

  • User interviews
  • Usage and query analysis
  • Product audits
  • UX strategy

Websites and launches

A site that explains you in one scroll.

Built in code or Framer, with a layer AI assistants can read. Launch campaigns, motion and launch films too.

Seen in Flip, Jarvie, Assert Labs

What’s included

  • Positioning and sitemaps
  • Marketing sites
  • Launch campaigns and motion
  • Agent-readable sites

AI-native teams, seed to Series B.

Most people call us for one of four reasons. Here they are, with what they said on the first call.

You're building an agent product

Harnesses, AI browsers, copilots, voice agents. Nobody has a playbook for these yet. We’ve designed more than ten since 2025.

Heard on a first call: “No one is bringing that level of craft to AI products.”

Your agent already designed the product

You shipped fast with Claude Code or Lovable. It works. It also looks like every other app. This is the most common reason people call us now.

Heard on a first call: “There's a difference between really clean UI and dummy-proof UX.”

Engineering moves faster than design

Your engineers ship faster than design can keep up. Hiring a senior designer takes months. We start in one to two weeks.

Heard on a first call: “We need someone who can think like a non-technical user.”

You're adding agents to a product people use

Your agent should feel like part of the product, not a chat box bolted to the corner.

Heard on a first call: “People just don't know that it exists.”

Adapt

Paste one prompt into Claude Code and it sets up the whole product

Read the story

First call to first designs in about a week.

We do the homework first. For one website client, the whole site was wireframed before the kickoff call.

  1. Discovery callWalk us through the product and what isn’t working.
  2. Proposal the same dayWhat you need, how we’d work, and when we start.
  3. We do the homeworkWe audit the product before kickoff and show up with quick wins.
  4. KickoffGoals, access, cadence. Your designer joins Slack that day.
  5. First designs in 24 to 48 hoursNot a deck about designs. Designs.

Your design team, not a vendor.

We join your Slack and work your hours. If priorities change on Wednesday, so does our week.

One review

45 minutes. Everyone who decides is in the room.

Two iteration cycles

Explorations early in the week, refinement after the review.

Daily updates

Looms, screenshots and live links in your Slack.

A Monday note

What’s coming this week, and what we need from you.

Every designer here ships in code.

Not a Figma mockup with fake data. A prototype you can click, built in Claude Code. On many projects we push UI straight to your repo, so your engineers stay on the hard problems.

  • Claude Code
  • Codex
  • Cursor
  • Conductor
  • Claude Design
  • Figma
  • Framer
  • Vercel
  • React
  • Next.js
  • Linear
  • Slack
  • Loom
  • Our own harness

Scoped by the work, not the hour.

Every engagement gets a named senior designer and a project manager. Most run three to six months. Many run longer.

Embedded

One senior designer, named in your contract, plus a PM. Where most teams start.

Design department

Three senior designers working in parallel. A design org in two weeks, not a year of hiring.

Async

Senior design over Slack with a few days’ turnaround. For upkeep and small features.

Projects

A brand, a website or a launch. Fixed scope. A brand takes about six weeks.