How it works

One request, start to finish

1. 01

   Your designer reads it

   Through the client portal. You write the requirement, it enters your queue, and it moves into a slot when one is free. Standard requirements target 48 hours from submission to a reviewed deliverable.

   You set the order of your own queue. Whatever you put next is what moves into the slot when one frees up, so priorities are yours to change at any time.

2. 02

   Drafts in 48 hours

   AI does the drafting, inside your design system, and a senior designer reviews and signs every deliverable. That split is what buys the speed: more on-system variations and early inconsistency checks, without AI having the final say.

   48 hours is the target for a standard requirement, from submission to a reviewed, on-system deliverable in code and Figma. Larger requests are scoped upfront.

3. 03

   Signed personally

   The same named senior designer, on every deliverable. Nothing reaches you without that review. AI never signs off on its own output.

   Unlimited revisions, for as long as the request holds its slot. If a deliverable is not right, you say what is off and it goes straight back into the same slot for another pass at no extra cost, rather than becoming a new request. The slot only frees up when you are happy, so the real limit is your own throughput, not a revision count.

4. 04

   Shipped on-system

   In the client portal, plus your own Figma file and your own code. Every deliverable arrives on-system in both, so there is no separate handoff step to translate a mockup into components.

   There is no separate handoff step. Work arrives as a pull request on your own repo alongside the updated Figma file, so your engineers review design work the same way they review any other change. Wraith's GitHub app can also run an automated design-token check on your pull requests, flagging hardcoded values that should reference a real token; it is informational and never blocks a merge.

FAQ

Who actually does the work?

Enzo E, the studio's founder, is your designer and does final review on everything. AI accelerates the draft: faster turnaround, more on-system variations, early inconsistency checks. It never has the final say.

What's in scope?

Design-system maintenance and extension: components, tokens, patterns, and the documentation around them. Net-new product strategy or research is out of scope, and your designer will say so plainly if a request needs it.

How long until my first deliverable?

You get portal access the day you subscribe and can submit your first request immediately. Before the 48 hour target applies, your designer needs access to your Figma file and your repo so deliverables land on-system rather than as flat mockups, which usually takes the first few days. After that, every standard requirement runs on the normal 48 hour target.

How much of my time does this take, and when are you available?

It is async by default. Requests, questions, revisions and deliverables all live in the client portal, and you get a reply within one business day, so there are no standing meetings to attend. Your designer works US Eastern hours, and keeping the loop written rather than scheduled is part of what protects the 48 hour target.

Do I get code or just Figma files?

Both. A standard deliverable is reviewed and on-system in code and in Figma, not a flat mockup you have to rebuild.

What tech stack and token format do you deliver in?

Yours. Components come back in the framework your codebase already uses, and tokens come back in the format your system already speaks, read from your real Figma variables rather than a parallel set invented on the side. React and TypeScript with CSS custom properties is the common case, but the deliverable conforms to your repo's conventions and your existing token names, not ours.

What happens if a request is bigger than a standard requirement?

It gets scoped upfront instead of being promised in 48 hours. The 48 hour target covers a standard requirement; anything larger is agreed on before work starts, so you always know what is coming and when.

Also worth comparing

• Wraith vs DesignjoyTwo one-designer subscriptions at a similar price, with different scope and a different delivery format.
• Wraith vs SupersideAn enterprise creative subscription with a $15,000 monthly minimum, against a $3,995 design-system subscription.
• Wraith vs hiring a founding designerWhat a US founding designer actually costs, and the specific work a subscription does and does not replace.
• What is an AI design service with human sign-off?The four things that have to be true, and how the category differs from a design subscription and from DIY AI tools.