How I work

I do not fit your brand
into a template.
I build the site around it.

Off-the-shelf tools always have a ceiling: theme, plugins, panel, workarounds. I first decide what the site needs to say and do, then design and code it exactly for that purpose - no compromises baked into the tool.

Tell me about your project See why not WordPress
I reply within 24 hours on business days.
proces.config
Start
message and decisions, not theme picking
Design
many iterations, one right direction
Code
no plugin or panel ceiling
Outcome
a faster, lighter site that truly feels like yours

This is not a different way to click a site together. It is a different way to think about a site.

Message and direction

First I decide
what the site should say.

Design does not start with a “nice section”. It starts with a decision about how the brand should be perceived: calm, premium, bold, technical, warm, concrete. The words, layout, color, typography, and motion all follow from that.

  1. 01

    I do not start with a template

    I do not browse themes asking which one is closest. I find the right direction first, then build the entire interface around it.

  2. 02

    I make many versions

    I test layouts, rhythms, and first impressions. The right direction sometimes appears at once and sometimes has to be pulled out of chaos - and I find it then too.

  3. 03

    AI widens the field, it does not replace taste

    I use AI to multiply the number of ideas, comparisons, and directions. The decision, selection, taste, and execution stay on my side.

  4. 04

    I do not ship “good enough”

    If something feels like a compromise, I go back to it. The site should have its own character, not be another acceptable template.

Collaboration stages

From idea to launch
- without chaos.

I work in stages, not endless revision rounds. Each phase has a goal and closes specific decisions before we move on.

  1. 01 Faza 1

    Sketch and direction

    Before I write the first line of code, we agree on the foundations: core message, site character, colors, typography, and what goes on each page.

    • Sales analysis - what should convince and what action it should lead to
    • Design analysis - hierarchy, rhythm, first impression
    • Brand feeling consistency - so the whole speaks with one voice
  2. 02 Faza 2

    Build and decisions

    I build what follows from the sketch. I usually start with the hero - to see how the whole presents itself. Once the direction is set, I put up the skeleton and add content and detail.

    • Prototype key sections before expanding the full site
    • Visual and technical decisions in one place - no project drift
    • I code everything myself - changes never hit plugin limits
  3. 03 Faza 3

    Finish and fine-tuning

    When everything is approved, there is room for final touches: copy tweaks, small fixes, technical matters, and SEO. Then the site goes live - ready and polished.

    • Tests across many screen sizes - mobile is the starting point
    • Technical polish: speed, meta, structure for search engines
    • Final iterations until the whole truly clicks
Why not WordPress

The most expensive part of WordPress
is what you cannot simply build.

WordPress looks reasonable while you want things the theme or plugin already expected. The problem starts where the site needs to be exactly yours.

The off-the-shelf tax 80/20 fast start, painful finish

80% comes together quickly. The last 20% can eat the entire project.

At first it feels nice: choose a theme, click sections, install plugins. Then you want to move logic, change form behavior, build an unusual layout, speed the site up, tighten SEO, and keep mobile intact - and suddenly you are not designing a site, you are negotiating with someone else's system. That last 20% can eat 200% of the time.

WordPress

  • The plugin almost does what you want

    And that “almost” becomes workarounds, extra settings, plugin conflicts, or accepting weaker UX.

  • The theme dictates character

    You can change colors and fonts, but underneath stays the same rhythm, the same sections, and the same “WordPress smell”.

  • A panel is not a strategy

    Lots of settings do not mean control. More often they just create more places where layout and consistency can break.

  • Speed fights the baggage

    Themes, builders, and plugins ship code you do not need. Optimization then drops to cleanup after decisions that should not exist.

That is why I code it myself

Custom code does not pretend everything can be clicked. Every feature takes a decision - but there is no ceiling. If something should behave differently, I just build it. Usually faster and more precise than hunting for a plugin that does 70% of what should be 100%.

  • Full control over UX

    Layouts, motion, forms, transitions, and details work as the project needs - not as the theme allows.

  • Less baggage, more speed

    The site loads what it needs. No builder that you use in 8% but ship to the user in 100%.

  • Features without plugin permission

    Integrations, custom sections, tracking, languages, forms, panels - if the project needs it, I build it for the project.

Short version: you are not paying me to click.

You are paying for decisions, design, code, and responsibility for the outcome. Not for searching a panel to find which plugin can do 70% of what should be done in 100%.

Invisible quality

These are not features.
This is the difference between a site and a template.

The most important things are not seen - they are felt. The site opens at once, text reads well, nothing jumps while loading, and mobile does not look like an emergency version. All of it is designed, not accidental.

  • 01 / 04

    Speed built in, not bolted on

    I build the site to be light by nature - not rescued by a tenth cache plugin. Speed is a decision made at the start, not a fix at the end.

    • SSG where the page can be ready immediately
    • dynamic section loading - heavier elements arrive only when needed
    • page prefetching so transitions feel instant
  • 02 / 04

    Images and fonts without accidents

    Media and typography are common reasons sites feel slow. I treat them as part of the project, not an add-on bolted on at the end.

    • images sized for the actual screen and device
    • fonts embedded and loaded stably, with no text jumps
    • zero multi-megabyte assets on phones
  • 03 / 04

    Mobile checked by hand

    Responsive design does not end when elements “fit”. I check rhythm, hierarchy, and reading comfort across real widths.

    • phone as the starting point, not an add-on
    • tests across many widths, not just desktop and mobile
    • sections designed around real user behavior
  • 04 / 04

    Typography like print, not by accident

    I care about copy because it sells. I even apply the old print rule: no orphans or widows. Nobody will name it - but everyone feels that it is professional.

    • line length and paragraph rhythm under control
    • no orphaned single words hanging at line ends
    • clear hierarchy without making everything huge
The technical polish in short

A handful of things that happen under the hood - so the site stays fast, stable, and refined in the details.

  • SSG
  • Dynamic section loading
  • Page prefetch
  • Responsive image sizes
  • Embedded fonts
  • No orphans or widows
  • Tests across many widths
  • Clean, light code

Taking on new projects

Let's talk about your site.

Tell me what you need - or send a loose thought about the problem you want to solve. I will reply with specifics.

Get in touch See my offer
  • I reply within 24 hours on business days.
  • No automatic quotes - I read first, then give a concrete figure.