Design Sprint · $6,000 · flat, design only, about 5 business days
The screens, designed, in a week
You have a developer, or a team, and what you are missing is the design. Up to about fifteen screens for a website, a web app, or a mobile app: flows agreed on Monday, the hardest screen first, a full set in Figma with tokens and specs by Friday. No code, no handoff gap, one senior.
Or book a 20-minute call first. No pitch, just fit.
01
Designed by someone who ships code
Every screen comes with the states a developer will ask about: empty, loading, error, edge. Nothing is drawn that cannot be built as drawn.
02
Hardest screen first
Monday goes to the screen that decides the product, not the login page. If the core flow works by Wednesday, the rest of the set follows fast.
03
Tokens and specs, not just frames
Color, type, spacing, and component tokens in Figma, ready to lift into code. Your developer gets a system, not a picture of one.
Receipts
Screens that shipped as drawn.
Design and build by the same hand, which is why the build matches the file.
What ships
A complete set, ready to build.
Up to about fifteen screens is the honest capacity of a senior week. A bigger product runs as two sprints, agreed up front.
Design
- Flows first. The paths a user takes to value, agreed on Monday before any screen.
- Copy direction. Headlines, labels, and microcopy written into the screens, never lorem ipsum.
- Up to ~15 screens. Desktop and mobile for a site; the core flows for a web or mobile app.
- Every state. Empty, loading, error, success, and the edge cases a developer will ask about.
- Screencast reviews. Wednesday and Friday, recorded, so review takes minutes.
Handoff
- Figma file. Organized by flow, with components, not loose frames.
- Design tokens. Color, type, spacing, radius, ready to lift into code.
- Specs and notes. Interaction notes where the frame cannot say it.
- A build path. If you want it coded, the Product Sprint or Cadence picks up the file without a handoff.
Pricing
Two ways to buy it.
Design Sprint
$6,000
Flat. Design only, up to about fifteen screens, about five business days.
- Flows agreed on day one
- Up to ~15 screens, every state designed
- Figma file with components and tokens
- Two recorded reviews and revisions inside the week
- Specs and interaction notes for your developer
Want it built too?
$9,000
The Product Sprint: design and working code in about five business days, deployed.
- One to two core flows, up to 10 screens
- Custom design plus production code
- Deployed, source handed off
- Cadence available after, one feature cycle a month
How it runs
Five business days, flows to handoff.
01
Mon
Flows and the hardest screen
Kickoff in writing or on a call. The flows are agreed and the screen that decides the product gets designed first.
02
Wed
First review
The core flow, every state, with a screencast. You comment in Figma; I revise the same day.
03
Fri
Full set and handoff
The complete set, components, tokens, and specs. A second screencast walks your developer through it.
Fit check
Built for some, not everyone.
This is for you if
- A team with engineering capacity and no senior designer
- A founder who needs screens to hand a contractor or an agency, buildable as drawn
- A redesign of something live that nobody has had time to think through
Not built for
- A product with no developer lined up. The Product Sprint designs and builds it
- A hundred-screen enterprise console in a week. That is a sequence of sprints
- Brand work. Start with Startup Branding
Designed to be built
Artyom Sklyarov
I have spent twenty years on both sides of the handoff, and most design that dies, dies there. Designing with the build in my hands means every frame you get has been checked against what a developer will actually do with it.
If you do decide you want it built, the same person picks up the file on Monday.
Start your design sprint
Tell me what needs designing. I'll personally review it and reach out within 24 hours.
Step 1 of 3
About you
The fine print
Questions, answered.
A complete, buildable set of screens in Figma with tokens and specs, and no code. It is for teams that have a developer and are missing the design. If you want it built, the Product Sprint or Cadence picks up the file without a handoff.
$6,000 flat for about five business days and up to about fifteen screens. A bigger product is two sprints, agreed and priced before the first one starts.
Because that is what a senior designer can do properly in a week, every state included. A number higher than that on a five-day quote means states are being skipped, and your developer finds out later.
Any of the three. A marketing site is usually five to eight pages, desktop and mobile. A web or mobile app is the core flows. The brief asks which, and the flows are agreed on Monday.
A Figma file organized by flow with components, design tokens for color, type, spacing, and radius, interaction notes where a frame cannot say it, and a recorded walkthrough. Everything needed to build without guessing.
As many as fit in the week. Wednesday's review is where most changes happen; Friday's is confirmation. Revisions on the chosen direction, not a restart on a new one.
Yes, as an add-on: the token set, the component library in Figma and in code, and the documentation, From $12,000, two to three weeks, usually after a Design Sprint or inside a Design Partner month. The sprint's tokens are the seed; the system is the full tree.
01 / 07
What exactly is design only?
A complete, buildable set of screens in Figma with tokens and specs, and no code. It is for teams that have a developer and are missing the design. If you want it built, the Product Sprint or Cadence picks up the file without a handoff.
Ready? Start a Design Sprint. Flows agreed on Monday, the file in your developer's hands on Friday.