Hi, I'm Eugenia
Part developer. Part business owner. Professional problem-solver.
For more than 20 years, I've worked behind the scenes of online businesses — sometimes building the thing from scratch, sometimes figuring out why it isn't working, and quite often helping someone decide whether they should build it at all.
I've worked directly with business owners, alongside designers and agencies, and as the person developers call when something has gone spectacularly wrong.
And I've learned quite a few things along the way.
The most important things I learned
... are not about technology
Because after you've worked on enough websites, you start seeing some patterns.
People trying to solve a business problem with a technical solution.
Adding more software because the existing setup isn't working quite right.
Rebuilding things because that's easier to sell than figuring out what's actually wrong.
Sometimes technology is the solution. Sometimes it's just a distraction.
That's probably why my clients tend to stick around
I've worked with most of my current clients for more than a decade.
And no, I don't have a magical secret to client retention. 
Mostly because once you've worked together for that long, the relationship inevitably becomes about more than building the technology.
AI can give you an answer to almost any technical question these days. And sometimes it's a pretty good one - when it's not confidently making s...tuff up.
I know, because my clients now email me the suggestions from AI with a comment like:
“ChatGPT says I should check these things. I checked the first 2 but don't know what the rest means, so I'm sending it to you, lol.”
And that's where I think experience still matters.
AI can give you ten possible things to try. I can look at your particular situation and tell you which ones I'd actually bother with - and which ones I'd ignore.
Sometimes knowing what not to do is the most useful part.
And I enjoy those conversations much more than I enjoy installing another plugin.
What I'm doing now
I want spend less time building and more time using the experience I've accumulated over the years to help people make better decisions about their technology.
Sometimes that means a quick second opinion.
Sometimes it means digging into a much bigger problem.
Sometimes it means building the thing once we've worked out what the thing actually is.
And when a project needs custom development that's outside what I want to take on, I have people I trust that I can send it to.
So if you're wondering whether you should...
...rebuild your website.
...change platforms.
...buy that plugin.
...build that online course system.
...or just leave things alone for now and focus on something else -
that's exactly the kind of conversation I'm interested in having.
You don't have to know what you need before you get in touch.