Services · 4 ways to work together
What you can buy, and what it costs.
Take any of it as Figma, as code, or both. Industry is not the constraint: if people use it to do their job and it has more than ten screens, I have designed something shaped like it.
| Offer | Price | Time | Delivered as | Pick this if |
|---|---|---|---|---|
| Product surface auditStart here | $80 | 5 working days | A written document and a Figma mock | A screen is quietly costing you |
| Redesign, built | from $200 | 3 to 4 weeks | Figma, code, or both. Your call | One surface stopped making sense |
| Design system build | from $500 | 4 to 6 weeks | A Figma library, a code library, or both | Three engineers, three different buttons |
| Monthly design partner | $300 / month | Ongoing | Figma or code, whichever the month needs | You need design every month |
If you are not sure
Start with the audit. Five days and a fixed fee tells you how I think before you commit to anything larger.
Fixed scope, fixed price, quoted before anything starts. These rates go up as the studio's calendar fills. Prices in USD. Indian teams are invoiced in INR at a local rate, just ask.
015 working days$80
Product surface audit
Find out which parts of one screen are losing you users, what each fix is worth, and what it takes to ship it.
Delivered as. A written document and a Figma mock
Book the auditWhat you get
- A written audit document, roughly 11 pages, in your product's own context
- Every finding scored by impact and by how much engineering effort it needs
- A redesign mock of the worst offender, built in your brand
Everything else included, and what I need from you
- A quick-wins list your developer can start on the same day
- A 45-minute walkthrough call once you have read it
From you. A link to the live surface, or a staging login · One sentence on what the screen is supposed to achieve · Nothing else. No kickoff process, no brief to write.
Proof
Dave Bissell got four findings on a Sunday and had three of them live by Tuesday.
Read the case study023 to 4 weeksfrom $200
Redesign, built
One surface rebuilt so people can finish the job inside it, handed over in whatever form your team will actually use.
Delivered as. Figma, code, or both. Your call
Talk about thisWhat you get
- A short research pass: your data, your support tickets, your users where they exist
- Flows and states, including the empty, loading and error cases most redesigns skip
- A working front end your engineers can run, read and extend, or just the Figma if your team would rather build it
Everything else included, and what I need from you
- The Figma file, matching what was built rather than drifting from it
- A walkthrough with your engineering team at handover
From you. One person who can make decisions, available for a weekly call · Read access to the codebase, or a clear description of the stack · Whatever research you already have, however rough
Proof
Bullpen went from 22 setup clicks to 3, and tested at 85 SUS with 15 reps before launch.
Read the case study034 to 6 weeksfrom $500
Design system build
Stop three engineers building three different buttons. One system everyone builds from, in Figma, in code, or both.
Delivered as. A Figma library, a code library, or both
Talk about thisWhat you get
- A three-tier token system: primitives, semantics, components
- A component library with every state built, including the ones nobody remembers to draw, in Figma or in code
- Storybook, if you take the code version, so your engineers can see what exists before rebuilding it
Everything else included, and what I need from you
- A Figma library bound to the same tokens, so design and build stay in step
- WCAG-AA contrast and focus states checked as part of the build
From you. An engineer who can answer questions about your stack, a few hours a week · Your existing components, however inconsistent they are · A decision on which product surface adopts it first
Proof
Nova is 47 components on a three-tier token system, mapped 1:1 from Figma to CSS in two weeks.
Read the case study04Ongoing$300 / month
Monthly design partner
Design that keeps pace with your release cycle, for teams that need it every month and cannot hire for it yet.
Delivered as. Figma or code, whichever the month needs
Talk about thisWhat you get
- Roughly one week of my time each month, spent on whatever is most urgent
- A standing weekly call, plus async review on your own tools
- Design shipped to the same standard as a fixed project, as Figma or as code
Everything else included, and what I need from you
- First call on my calendar when something breaks
From you. A rough sense of the month's priorities, reviewed at the start of each month · Someone who can unblock decisions inside a day
Proof
Sage AI is what continuous work looks like: three real-time jobs folded into one dialer over a year.
Read the case studyBefore you write · 8 questions
The things people ask on the first call.
Answered here so the call can be about your product instead.
- Do you replace our engineers, or work with them?
Work with them. I build the front-end of the thing I designed, so your engineers get something running they can read and extend.
They still own the architecture, the data layer, and the decision about what ships. What changes is that the design arrives already resolved, so the ambiguity gets settled by me rather than in their sprint.
- Do I get Figma or code? And do you push to our repo?
Whichever you need, and both is common. If your team is going to build it, you get a Figma library with tokens, components and every state drawn. If you would rather skip the translation step, you get a running React front end with the same system underneath, plus the Figma file that matches it rather than drifting from it.
On the code: usually I work in a separate repository and hand it over, because most teams would rather review a whole thing than a stream of commits from an outsider. If you would rather I worked in a branch on your repo, that works too. Either way you decide before we start.
- We already have a Figma file. Does that help?
It helps. It tells me what you have already decided and what you have already argued about, which saves a week.
I will tell you honestly if the file is worth building on or worth restarting. That answer arrives in the first week, before you have spent much.
- Do you do research, or only the visual work?
Both, sized to the engagement. On an audit the research is your product, your support tickets and heuristic review, because five days does not buy participant recruitment.
On a longer project I test with real users where they exist. Bullpen was tested with 15 active sales reps before launch and scored 85 on SUS. I will say plainly when a claim is untested rather than dress up an opinion as a finding.
- You are in India. How do the hours work?
I am on IST, which overlaps European mornings and US evenings comfortably.
In practice we book one call a week at a time that suits you, and everything else runs async. Both of my recent client engagements ran entirely across timezones.
- What happens when we need changes after handover?
Small corrections in the two weeks after handover are part of the price. If something I built is wrong, I fix it.
New scope after that is either a small fixed quote or a month on retainer, whichever is cheaper for you.
- What do you not do?
Logos, brand identity, illustration, marketing sites and pitch decks. I know good people for the first three.
I also do not take on work where the design has already been decided and the job is to draw it. That work is real, and I am the wrong person for it.
- How do we start?
Book a 30-minute call. You describe what is broken, I tell you whether I am the right person, and if I am you get a scope and a price within two days.
If you would rather test the water first, buy the audit. It is five days and a fixed fee, and it tells you how I think before you commit to anything larger.
Still not sure? Send me one screen.