People imagine remote studios operating from Lisbon co-working spaces, Bali beach cafes, or at minimum a city with a subway system.
We run PrismaFlux Media from Gevgelija.
If you've never heard of it, that's the point. It's a town of around 15,000 people in the south of North Macedonia, pressed against the Greek border. There are no tech meetups here. No startup offices. No networking happy hours. The closest thing to a co-working space is a cafe with decent Wi-Fi and an owner who doesn't mind you working there for three hours.
We built a design engineering studio from here. This is what that actually looks like.
The Setup
The studio's office is a room with the hardware and connectivity that the work demands: high-spec machines running Linux and macOS side by side, multiple monitors, and a connection that's faster than most people expect for a town this size. We're not fighting for bandwidth at a co-working space or hoping a cafe router holds up during a client call. Our connection is ours, stable, and fast enough to push large repos, share screens, and run cloud deployments without thinking about it.
That's the only infrastructure the studio actually needs. Everything else is software: Vercel for hosting, Neon for Postgres, GitHub for code, Linear for work. When the job is architecture and implementation, the physical footprint can be remarkably small.
The Time Zone Math
Our clients are in the US, UK, and Western Europe. Gevgelija is UTC+1 in winter, UTC+2 in summer. That puts us 1–2 hours ahead of the UK and 6–9 hours ahead of the US East Coast.
In practice: the day starts at 8 or 9 AM. By the time UK clients are at their desks, two or three hours of focused work are already done. By the time US clients wake up, there's been a full productive morning and the afternoon is open for calls.
This is not a bug. It's one of the better features of the studio's location.
The deep work hours — the ones where you're actually solving hard problems, writing architecture documents, building complex components — happen in the morning before the world needs us. The communication, the reviews, the calls happen in the afternoon when clients are online.
We didn't design this on purpose. It's just how the time zones worked out. But we'd design it this way if we could.
What You Actually Miss
We want to be honest about this because most remote work content is either pure evangelism or pure complaint, and reality is messier.
You miss the incidental conversations. The hallway chat that turns into a product decision. The lunch where someone mentions a problem and you realize you solved it last month. That kind of serendipity doesn't happen when you're working in a room in Gevgelija and your collaborators are in four different time zones.
We've replaced some of it with Slack, with Loom videos, with long async messages that probably contain more thinking than we'd do out loud. It's not the same. Some things are lost.
You miss the immediate feedback loop. In an office, you can spin your chair and ask someone if your approach makes sense. Async has a latency to it. Sometimes you spend three hours going the wrong direction before someone reads your message and points it out.
You miss the social architecture of a workplace. Even if you didn't love your office, it gave you a structure to the day that you didn't have to build yourself. Remote work means building that structure from scratch, every day, indefinitely.
These are real costs. We're not pretending otherwise.
What You Don't Miss
The commute. Obviously. But it's not just the time — it's the mental residue a commute leaves. Getting to the desk takes thirty seconds. You arrive at work already thinking about the problem you were thinking about when you woke up.
The open-plan office. We can focus here. Actually focus. The kind of deep concentration that software architecture requires — holding an entire system in your head, reasoning about edge cases, writing code that needs to be right — that's hard to do in a noisy room. It's much easier in a quiet one.
The performance of being busy. In an office, there's often an implicit expectation to look busy, to be visibly present, to signal effort. Remote work, done right, only cares about output. Did the feature ship? Is the code clean? Does the architecture hold? That's the whole scorecard.
The geography tax. If the studio were in a tech hub city, we'd be paying city prices for everything — rent, food, transport — just to be physically near an industry that we can access entirely online. Gevgelija is cheap. Not "developing world cheap" — it's a normal European town with normal European amenities — but cheap relative to Berlin or Amsterdam or London. A low cost base lets the studio make pricing and hiring decisions from a position of stability rather than pressure.
The Gevgelija Advantage
Here's the thing nobody writes about: being from a small, specific, non-obvious place is actually an asset online.
Everyone in tech is from London or Berlin or San Francisco, or at least a city someone's heard of. When your location is part of your story — a design engineering studio running from a border town in North Macedonia — it's memorable. It's specific. It stands out in a way that "freelance developer based in a major European city" does not.
The geography that looks like a limitation from the outside is part of the identity of the studio. PrismaFlux Media from Gevgelija is more interesting than PrismaFlux Media from Anywhere Generic.
We lean into it. It's on the website. It's part of how we talk about the work. And the clients who find it interesting are almost always the ones we want to work with.
What It Requires
Running a studio from a small city isn't passive. It doesn't just happen because you have laptops and an internet connection. It requires a few things that take real effort to build:
Self-imposed structure. You need working hours that you actually respect, an environment you can focus in, and some separation between work time and not-work time. Without those, remote work becomes either workaholism or drift.
Deliberate communication. When you're not in the room, you have to be a better communicator than you'd need to be in person. More written documentation. More proactive updates. More clarity on scope and expectations before work starts rather than during it. For a studio that ships client work asynchronously, this isn't a soft skill — it's the core skill.
A visible presence online. If clients can't find you — portfolio, GitHub, LinkedIn, published writing — you don't exist. Being remote and being invisible are not the same thing, but they require the same corrective action: show up online, consistently, with work worth looking at.
Tolerance for ambiguity. You will sometimes not know if you're doing it right. The feedback loops are longer. The signals are quieter. You have to be comfortable operating in that uncertainty for stretches of time.
The Honest Summary
Running a studio from Gevgelija isn't a lifestyle choice performed for an audience. It's just where the studio is from and what it does. The town doesn't make it easier or harder to write good TypeScript. The architecture of a well-structured Next.js app doesn't care what's outside the window.
What the location does is keep the costs low, the distractions minimal, and the story specific.
That's enough.
PrismaFlux Media is a design engineering studio building scalable digital products from Gevgelija, North Macedonia. If you have a frontend architecture problem, book a free strategy call.