Tuvi

For product teams

Product teams

One shared document where design happens, gets reviewed and ships: live co-editing, comments in context, branch-based review and a Dev Mode hand-off engineers actually use.

  • Design, review and hand-off in one document
  • Branches make parallel exploration safe
  • Viewers and personal drafts never cost a seat

The hand-off tax most teams still pay

  • Feedback lives in chat threads and meeting notes, detached from the frames it describes — and gets re-litigated every sprint.

  • Parallel explorations mean duplicated files, and nobody is quite sure which copy is the real one.

  • Developers rebuild designs from screenshots and redlines, re-measuring values the file already contains.

  • The design tool is a black box to the rest of the toolchain — nothing to script, nothing your automation or AI agents can read.

What changes in the first sprint

1
shared document from first draft to Ready-for-Dev — no export chains between tools
3
editors collaborate free on the Starter plan; viewers are always free
7
code formats available the moment work moves to engineering
30 days
of version history on the free plan — unlimited on Professional and up

The Tuvi features product teams lean on

One document from idea to Ready-for-Dev

The quiet cost in most product teams is not designing — it is moving design between contexts: exporting for feedback, duplicating for exploration, screenshotting for hand-off. In Tuvi the whole loop stays in one document. Explorations live in branches instead of file copies; critique happens in comments pinned to the exact frame; the chosen direction merges back with a review that shows what changed; finished frames get a Ready-for-Dev annotation that tells engineering, unambiguously, what is stable.

Version history backs the whole process — 30 days on the free plan, unlimited on paid — so bold experiments are cheap and 'we broke the good version' is a restore, not an incident. The document stops being an artifact you protect and becomes a place your team works.

Pricing that follows how teams actually work

Product teams are a few editors surrounded by many readers: PMs checking states, engineers inspecting details, stakeholders reviewing directions. Tuvi bills accordingly — you pay per editor seat, and viewers are free on every plan. Personal drafts are free forever, so individual exploration never touches the team's bill, and yearly billing takes 20% off.

The ramp is honest too: Starter costs nothing for up to 3 editors, 1 project and 10 files — enough for a real pilot, not a crippled demo. Professional at $12 per seat removes the limits and adds Dev Mode, edit-capable share links and unlimited history; Organization adds SAML SSO and org-wide libraries when governance becomes the constraint.

Frequently asked questions

We already have a design tool. What does switching actually cost?

Less than usual, because your existing .fig files open natively — components, overrides, styles and auto-layout stay editable. The pilot is: create a free Starter team, import one real project, run one sprint in it. No converter, no re-drawing, and your original files remain valid throughout.

How do design reviews work in practice?

Comments attach to the canvas right where the issue is, alternatives live in branches instead of duplicate files, and a merge with review reconciles the chosen direction. Frames that pass review get a Ready-for-Dev annotation for engineering.

What do our engineers get out of it?

Dev Mode on paid plans: click any element to read exact spacing, typography and variable values, then copy code in CSS, React, Tailwind, SwiftUI, UIKit, Compose or Android XML. Plus asset export in four formats and MCP access for AI tooling.

How does pricing scale as the team grows?

Per editor seat, per month: Starter is free for up to 3 editors, Professional is $12 per seat with unlimited projects, files and editors, and yearly billing saves 20%. Viewers never count toward seats, so a growing review audience is free.

What happens to our files if we downgrade or leave?

Your designs stay exportable — PNG, JPEG, SVG and PDF, including batch ZIP — through your plan's retention window even after cancelling, and personal drafts remain free forever. We consider an easy exit part of the product.

Related pages

For developers

Developers

For agencies and studios

Agencies & studios

Move one project into Tuvi this sprint

View plans