Key screens
Homepage, a few app screens, or the main funnel so the team agrees before Webflow or code starts.
Figma
Wireframes and screens before the build.
Simple Figma files for teams that need a clear path before Webflow or code. Wireframes, key screens, clickable flows. Not enterprise design systems.
- Key pages and flows written down first
- A prototype link people can click through
- A file tidy enough for the next build step
What you get
AI can draft screens fast. Someone still has to decide which pages matter, what the user does first, and what the file should look like before build starts. That is the Figma work I take. Scoped screens, not design-system consulting.
Wireframes first
Structure and layout before polish, when the offer or flow is still messy.
Clickable path
A simple prototype link so people walk the main journey instead of reading a deck.
Tidy AI drafts
Busy or inconsistent AI UI cleaned into readable spacing, hierarchy, and copy.
Ready for the next tool
Named frames and a short note on what comes next: Webflow, Cursor, or Lovable.
What I do not take
Complex design systems, advanced variables, and multi-brand libraries. Those need a specialist. I will say so early.
Working together
Brief in. File out.
Screen list
Which pages or flows? We write the list down so the job stays small enough to finish.
References
Brand book, links you like, and who approves. I work from that, not from a blank vibe.
Wireframes
Structure first. You react before we spend time on polish.
UI + prototype link
Simple screens and a clickable path. You share the Figma link for feedback.
Billing
Fixed price for a defined screen list. Hourly for small edits. Monthly retainer for weekly availability. We agree which one before I start.
Related work
No separate Figma gallery yet. These are projects where screens and flows mattered before or beside the build.
