Webflow Certified Partner · Taking new projects
Webflow sites that hold up after launch
I'm a Webflow developer for agencies and marketing teams. I build the CMS, custom code and motion behind sites that keep growing after launch, so a new page never has to wait for a developer.
/
/
/
01 · Selected work
Recent builds
A large CMS, custom features, heavy motion, a five-day deadline. Each project below solved a different problem. Hover to play the film, or open the live site.

HurtApp
01
Page system and motion · 2026
+ 30+ pages from one component set
+ 20+ CMS collections that the team can run themselves
+ Motion that guides through the product

Popdock AI
02
CMS and custom code · 2025
+ 20+ linked CMS collections
+ Custom features past Webflow's limits
+ Fast, even with heavy visuals
+ A design system the client's team updates on its own

Holocene
03
CMS and motion · 2025
+ 40+ unique pages on one connected CMS
+ 20+ fast-loading animations
+ Filterable resources library and blog

Leefstijl Lab
04
GSAP and motion · 2025
+ Scroll-driven GSAP storytelling
+ Physics-based falling objects
+ Custom video player with its own controls

Formula Capital
05
Speed and detail · 2025
+ Small site, built to load fast
+ Navigation that condenses on scroll
+ Smooth modals and Lottie motion

Eyawork
06
Fast turnaround · 2026
+ Live in 5 days
+ Fast load times and subtle motion
+ Links that open the right tab

EcoglobalBTD
07
Design and development · 2024
+ Designed and built end to end
+ Smooth scrolling with custom motion and hover effects
+ A polished first impression

Stolla Fit
08
GSAP and motion · 2025
+ Motion-heavy build with GSAP
+ Easy for the team to update
02 · Services
What I build
Eight of 50+ builds. A large CMS, custom features, heavy motion, a five-day deadline. Each one solved a different problem. Hover to play the film, or open the live site.
You have a finished design and need it built without losing anything on the way. I build it in Webflow as drawn, at every breakpoint, and flag anything that won't hold up before I start, not halfway through. You get a site that matches the file and a structure your team can keep extending. No design yet? I can refine what you have myself, and for a full design I bring in a designer I work with. The build stays with me either way.
If every new page needs a developer, the CMS is usually the problem. I plan collections and references around the content you actually publish, so pages fill themselves from what your team enters. I also take over builds where the CMS got hard to manage and restructure it.
Motion should help people understand the product without slowing the page down. I build scroll scenes, physics, Lottie and custom video players with GSAP, and keep them light enough to run smoothly on a phone.
The biggest risk in a move is losing the search traffic you already have. I audit every existing URL, move your content into a CMS built for it, and redirect old pages to new ones, so links keep working and rankings have somewhere to land.
Also
Custom integrations, technical audits, and ongoing work on sites I built or inherited.
Not for me
Ecommerce builds and design-only projects.
03 · Clients
What clients say
04 · Process
How a project runs
You always know what's happening and what comes next. Small sites take about a week, and large CMS builds about a month.
01
Intro call
Thirty minutes. You tell me what you need, and I tell you whether I'm the right person for it. If I'm not, I'll say so.
02
Proposal
A fixed price and a timeline, based on the design and scope. For open-ended work I can bill hourly.
03
Plan
Before I build, we agree on the site structure, the CMS collections and how each part should behave. On a call or in writing, whichever you prefer.
04
Build
I build and keep you posted as pages come together. Quick questions go through Slack. Decisions go by email, so they're easy to find later.
05
Handover and
launch
I move the site to your Webflow account, walk your team through editing it on Zoom and record Loom guides. I stay on until launch and can connect the domain for you.
05 · About
Who you'll work with
I'm Žarko Dimitrić, a Webflow developer based in Serbia. I've worked only in Webflow for more than four years and built over 50 sites, most of them as a development partner for design agencies.
I do all the development myself. When a project also needs design, I bring in designers I've worked with before, but the build stays with me, and so does the conversation.
I build on the Lumos framework and write custom JavaScript when Webflow's native tools run out. The CMS gets planned around the content your team actually publishes, so they can add and edit pages without waiting on anyone.
I'm on CET, but I keep my hours flexible for clients in the US and Australia, including late calls when a project needs them. Most messages get an answer the same day.
06 · FAQs
Questions before we start
Yes, that's most of my work. I go through the file first and flag anything that won't hold up in Webflow before I start, so you don't find out halfway through.
No. I can refine a rough or partial design myself, and for a full design I bring in a designer I've worked with. Development stays with me, and so does the communication.
Usually, yes. I've built sites with 20+ CMS collections and 40+ unique pages. If your content model pushes past what Webflow does well, I'll tell you on the first call.
Yes, when Webflow's native features aren't enough: custom functions, CMS logic, integrations and animation. I keep scripts small and use code only for what Webflow and CSS can't do on their own.
No. Webflow's ecommerce has limits I'd rather not build a store around.
I build in Lumos by default. If your team already works in another system, like Client-First, I can follow it.
Yes, most of my projects are white-label. I work under your agency's name, and I'm happy to sign an NDA.
Yes. I take over sites other developers built, restructure CMS setups that got out of hand, and fix urgent problems, like a form that suddenly stops working.
CET. I work with clients in the US, Europe and Australia and keep my hours flexible, including evening calls.
Projects start at $2,000. Most are fixed price, agreed after the first call once I've seen the design and scope. For open-ended work I can bill hourly.
Small sites take about a week. Large multi-page CMS builds take about a month.
Usually right away. It depends on what I'm working on at the moment, so I'll give you an exact start date on our first call.
Yes, that's what the CMS setup is for. At handover I walk your team through it on Zoom and leave Loom recordings for later.
I stay on through launch, and I'm available afterward for changes, fixes and new pages.
I handle the technical side: a proper heading structure, meta titles, descriptions and alt text your team can edit per page, and URL mapping when you migrate. I don't run SEO strategy or write content.
Not covered here? Ask me directly.
07 · Contact
Let’s build it.
Projects start at $2,000. Pick whichever way suits you. Every one reaches me directly.









