I design and build stable WordPress systems for owner-led businesses that treat their website as operational infrastructure.
I work independently under the studio name devaDesign.
Since 2003, I’ve built 250+ WordPress systems for owner-led businesses across Croatia and wider EU markets.
The focus is structural clarity, controlled complexity, and long-term maintainability. Not speed, experimentation, or disposable builds.
→ Review qualification criteria
Three examples of architectural decisions under real constraints.
This work is for:
This work is not for:
If you recognise yourself more in the second group, this way of working tends to create friction rather than progress.
Work is organised around structure, not urgency.
Decisions are made deliberately. Responsibilities are separated clearly. Changes are evaluated in context, not applied reactively. The goal is coherence over time, as requirements and constraints accumulate.
This approach is typically slower at the start and significantly more resilient later.
Most long-term problems are not caused by missing features or outdated visuals.
They come from early structural decisions: how data is organised, how responsibilities are divided, and how change is introduced.
Over time, those decisions determine whether the site supports growth or resists it.
Treating a website as a one-off project often leads to rebuild cycles and rising technical debt. Treating it as a system allows change without destabilising everything else.
These are not services in isolation. They are recurring contexts where architectural responsibility becomes critical.
Defining the structural foundations that determine how a WordPress system behaves over time.
Building systems shaped around business rules, workflows, and responsibilities rather than generic patterns.
Treating performance as a structural property supported by clarity and controlled complexity.
Reducing accumulated complexity and restoring predictability in existing systems.
This way of working assumes active participation.
It requires clarity about what the website must support, willingness to make decisions early, and an understanding that structure introduces both capability and constraint.
I take responsibility for architecture and system integrity. Business decisions, priorities, and trade-offs remain with the client. This separation is deliberate.
If responsibility is expected to be deferred or avoided, this will not be a good fit.
Limited-scope work is rare and accepted selectively.
It is used for tightly defined interventions, not as a cheaper entry point.
This website is designed to confirm alignment before any conversation.
If this way of working fits how you operate, start with the qualification criteria.