I designand builddigital products with weight.
Mateja S.04Services
Pick a lane, or stack a few.
Most projects need both design judgment and solid engineering. Start with one service or combine them into a single build.
Request a quoteThis is the visual and structural work: flows, hierarchy, type, and the components a team can reuse. I design for the real device mix, not a single desktop artboard, and I keep the file (or the in-browser system) tidy enough that engineering does not have to guess.
Next.js, APIs, CMS, and the unglamorous parts: auth, forms, performance, and content models. I write for the person who will inherit the repo. If a hybrid with Webflow is smarter, I will say so instead of forcing a custom stack.
Webflow is the right tool for a lot of marketing sites. I use it when speed and client editing matter more than custom application logic. The build still gets a real design pass, CMS collections, and a handoff so you are not locked to me for every heading change.
Most sites do not fail at launch. They drift. I stay on for Core Web Vitals, SEO foundations, A/B-minded tweaks, and the backlog that never makes it into a redesign. This is a retainer or a scoped sprint, not an open-ended promise.
How a quote is shaped
One core flow, a tight page count, no extra experiments.
The version most clients pick: enough craft, enough room to iterate.
Product surfaces, integrations, or a hybrid Webflow plus Next.js stack.
How a project moves
We lock the goal, audience, and constraints before anyone draws a layout or writes a line.
Structure, wireframes, and visual direction, locked in early so the build stays focused.
Clean implementation with responsive polish, performance, and content you can actually edit.
QA, handoff, and go-live support so launch day is boring, in the best way.
After launch we measure, refine, and keep the product sharp as needs evolve.
Brief
Send a short brief and I’ll recommend the leanest path: Webflow, custom Next.js, or a hybrid of both.
Let’s talk