Design is not the coat of paint at the end. It is the decision about what goes on the screen, in what order, and what happens when the user does the thing you did not plan for — all of which is settled long before anything is made to look good.
6 deliverables
What goes where, and in what order, before a single pixel is drawn.
Clickable versions you can put in front of a real user before anything is built.
The finished interface, with every state the build will need.
Tokens, components and rules, so the twentieth screen still looks like the first.
Logo, palette, type and the basic assets to apply them consistently.
Contrast, focus order, target sizes and semantics checked against WCAG.
Design
We start with the path a person takes to get something done, written out step by step. Half the screens in a typical first draft turn out to be unnecessary once that path is on paper, and the ones that survive get designed properly rather than approximately.
A design that looks right at one width and falls apart at another is not finished. We deliver the states developers actually need — loading, empty, error, long text, the Indian name that is forty characters, the price that runs to seven figures — plus the responsive behaviour between breakpoints. Because we also build, the handover is a conversation rather than a document thrown over a wall.
Readable contrast, tap targets a thumb can hit, visible focus for keyboard users, labels that screen readers announce. None of this costs extra when it is decided at design time, and all of it costs a great deal to retrofit.
Toolkit
Yes. You get the Figma file, the design system and a developer handover pack, and your own team or another vendor can build from it.
Frequently. It usually starts with an audit of the current interface against the tasks people are actually trying to finish, which is what tells you whether the problem is the visual design or the flow underneath it.
A focused marketing site is one to two weeks. A product interface with a dozen or more screens is three to six weeks, depending on how many rounds of feedback it goes through.
Yes — the Figma file is shared with your account and it is yours, including components and tokens.
Whatever exists: current screens, competitor examples you like, your brand assets, and most valuably half an hour with somebody who does the job the software is for.
Next step
A short call, a written scope and a fixed price — no obligation, and the scope is yours either way.