about
I'm Gregor, and I'm the person you'd actually be working with.
Not a salesperson who introduces you to someone else. Not an account manager who passes your job to whoever has capacity this month. If you hire me, I'm the one doing the work, and I'm the one you call when something needs changing.
I've been doing the technical side of small businesses for over a decade — booking systems, conversion tracking, websites, and the connections between them.
Most of what breaks isn't complicated. It's just unowned.
When I get called into a business, the problem is rarely something exotic. It's a consent banner someone switched off. A booking flow that crosses a domain and drops the data. A site nobody has been able to change since the person who built it moved on.
Each of those is small. What makes them expensive is that nobody inside the company was in a position to notice. The staff are running the actual service. The online side belongs to no one, so it drifts, and the drift only becomes visible once it's already cost you something.
The technical work is the easy part. Knowing what to look at is the job.
That's the way I think about all of it. Not "here are four services" — more like: your booking, your measurement and your site are one system, and the failures almost always happen at the joins, where each specialist assumed someone else was watching.
The same job, in three different decades.
I won't give you a CV. But the shape of it explains how I work, so it's worth a minute.
I started out making things, not selling them
My first work was in game development — designing how a thing behaves rather than how it's marketed. It set the habit I still have: understand the system underneath before touching the surface.
Seven years standing between business people and developers
Enterprise IT — building and integrating portal systems for large organisations, including a national grid operator and a bank. My job was to sit in the middle: take what the business needed, work out what it meant technically, and make sure what got built was what was actually wanted. I did that for seven years, and it turned out to be the most useful thing I've ever learned.
A decade of doing all of it myself
For the last ten-plus years I've worked with small businesses — building their websites, setting up their booking, fixing their tracking, running their ads. No team to hand things to. Which means when something breaks at three layers down, I'm the one who goes in and fixes it.
The through-line is the same in all three: I've always been the person standing between a technical thing and someone who needs it to work. That's still the job. The systems changed; the skill didn't.
Worth knowing before you get on a call with me.
I'll tell you what you actually need
Clients usually come to me with a solution already picked — "we need a new website", "we need this plugin". Often that's not the problem. I'd rather spend the first conversation working out what's actually wrong than quote you for the thing you happened to name.
I'll explain it in plain language
You shouldn't have to learn what a container or a conversion action is to make a decision about your own business. Explaining technical things to non-technical people isn't a courtesy I add on — it's most of what I actually do.
I'll tell you when something isn't worth the money
Some problems cost more to solve than they cost you to live with. When that's true, I'll say so and show you the numbers, even though the smaller job is the one that pays me less.
I'll tell you what's still not perfect
If a fix gets you to 80% and the last 20% would cost more than it's worth, you'll hear the real number. I'd rather hand over something honest than something that sounds finished.
I don't disappear
I've kept the same clients for over a decade, and I've never walked away from one. The work I do isn't finished when it launches — it's finished when you stop needing it, and that's usually years later.
I'll say when I'm not the right person
I don't do brand identity. I'm not a copywriter. If what you need sits outside what I'm good at, telling you that costs me one job and saves you a bad one.
HRMES is new. What's behind it isn't.
HRMES Commerce is a new company, built on more than twenty years of hands-on technical work — enterprise systems first, then a decade of websites, booking and tracking for small businesses.
So there's no long client list under this name yet, and I'm not going to pretend otherwise. What there is instead: the actual work, described in detail, including the parts that didn't go perfectly. Read a case study and decide for yourself whether the person who wrote it knows what he's doing.
I'd rather show you the work than tell you about the company.
I still build my own things.
Partly because I like it, partly because it's the only honest way to stay current. You can't recommend an approach you've never had to live with.
-
My own sites
I run content sites of my own, which means I'm on the receiving end of my own decisions — the slow platform, the awkward migration, the tracking that seemed fine until it wasn't.
-
Automation, properly
I'm building automated content and data workflows on my own projects before I offer them to anyone. There's a lot of noise about AI right now. I'd rather show you something that runs than sell you a promise.
-
[ Personal detail — your words ]
Something real and non-work: where you live, what you do at weekends, something you're into. Two or three sentences. This is the bit people remember.
-
[ Personal detail — your words ]
A second one, or delete this box and run three across. Keep it plain — no "passionate about", no life philosophy. Just a true thing about you.
start here
Easiest way to find out if I'm useful to you.
Tell me what you've got and what isn't working. If I can help, I'll tell you how and what it costs. If I can't, I'll say that too.