I don't open Webflow when I receive a Figma design.
Before building, I review the design system: typography, colors, spacing, components, and breakpoints. This defines how the site should be structured, not just how it looks.
Next, I assess feasibility: Webflow limitations, custom functionality, and CMS needs.
I look for gaps early—missing states, unclear mobile behavior, undocumented interactions, and expected CMS content volume. These are easier to solve before building.
My process starts with the design system: style guide, variables, and reusable components. CMS comes before templates. Desktop first, responsive after. Then interactions, custom work, QA, and optimization.
My design background helps. I’m not just building the design—I’m preserving the intent behind it.
Just finished building a Salon Booking Management System!
The goal was simple: make appointment management easier for salon owners and reduce the manual work involved in handling bookings and reminders.
The system connects the complete workflow in one place:
1 Customer makes a booking
2 Booking gets confirmed
3 Owner sees it on the dashboard
4 Upcoming appointments are organized clearly
5 Reminders help the owner stay on top of appointments
One of the key things I focused on was making the experience simple, clean, and easy to understand, while keeping the workflow practical for a real business.
This project helped me think beyond just building screens — and focus more on the actual business problem, user flow, and overall product experience.
Excited to keep improving it and turn it into an even more polished product.