Website Strategy & Wireframing
Before anything gets designed, I map what has to be on the page and in what order. Most sites fail right here: sections exist because other sites have them.
Most business websites look fine and do nothing. Visitors land, scroll, leave — no call, no order, no email. I build the other kind: a site that gives someone a reason to act before they close the tab.
No drag-and-drop templates. No recycled designs. Just a site built around how your customers actually decide to buy.
Each one started with something specific going wrong: a product that was impossible to show online, a brand with no personality, a page nobody had a reason to trust. Here's what I did about it.
A woodworking studio was selling handcrafted 3D wooden maps with no proper way to show them online. Flat photos killed the product — the depth and the grain are the entire reason someone buys one.
I built the site around the photography — large, uninterrupted images with the personalization options sitting right next to them instead of three clicks away. Browsing and ordering became one motion.
Gym sites all blur into each other — loud colors, a "join now" button, nothing that tells you what training there actually feels like. Atlas had to read as disciplined rather than hyped.
A black-and-red build with one route through it: see the programs, meet the coaches, claim a free first session. The offer repeats at the end of every section, so there's never a point where someone is interested and has nothing to click.
Supplement sites land in one of two ditches: sterile pharmacy or shouty diet ad. Neither gives anyone a reason to believe what's in the bottle.
I rebuilt the page around what's in the product: ingredients and sourcing up front, claims trimmed to what could be backed up, wellness filler cut entirely. Trust came from specifics rather than adjectives.
A wellness brand that had to feel energetic without tipping into unserious. In health, the line between memorable and untrustworthy is thinner than it looks.
I pushed a saturated color system as far as it would go, then pulled it back until the page still read as credible — color carrying the personality, strict typographic hierarchy carrying the authority.
Most projects run through all four stages. Some only need one — that's fine too.
Before anything gets designed, I map what has to be on the page and in what order. Most sites fail right here: sections exist because other sites have them.
Every screen gets one job and one obvious next step. Looking sharp is the baseline — the layout's real work is making the next click feel like the natural thing to do.
I build in Webflow by hand — clean structure, compressed assets, tested on real phones rather than a browser window dragged narrow.
Launch day is when the useful data starts. I stay on for speed checks, content updates and search fixes, once there's real traffic telling us what to change.
I'm a Webflow developer in Belgrade. I don't do "digital experiences" — I build websites that bring in calls, orders and clients. Every project starts with the same question: what has to happen on this page for someone to act? Everything after that is in service of the answer.
Before Webflow I studied Computer Science at Računarski fakultet in Belgrade and graduated with a 9.3 GPA. That order matters: I approach a website the way I was trained to approach a system — decide the structure first, keep it consistent, and make sure it still makes sense to whoever opens it six months later.
A new site, a redesign, or a page that should be converting and isn't — send me the details and you'll get back a straight read on how I'd approach it and roughly what it takes. No pitch deck.
Every inquiry gets a real reply — usually within 24 hours.