PrismaFlux Media runs from Gevgelija, a border town of 15,000 people in the south of North Macedonia. No tech hub, no startup scene, no networking events.
We haven't submitted a job application or sent a cold pitch in over a year.
Every client we've worked with in the past 12 months found us. Here's how we build that.
The Shift: Outbound vs. Inbound
Most developers think about client acquisition as a funnel they push people through — cold emails, Upwork bids, LinkedIn DMs. The conversion rate on that approach is brutal, the clients it attracts are often price-sensitive, and it scales with your time.
Inbound flips it. You create things that exist permanently on the internet and pull the right people toward you. The work compounds. A case study written in January is still finding clients in December.
The geography thing matters here. We can't walk into a Berlin co-working space and meet a CTO. So inbound wasn't a strategy we chose — it was the only one that made sense from where we are.
The Three Assets That Drive Everything
1. A Portfolio That Answers Real Questions
Most portfolios are a gallery. Ours is structured to answer the question a client is actually asking: "Can this studio solve my specific problem?"
Every case study follows the same structure:
- The situation: what the client was dealing with before
- The constraints: budget, timeline, technical debt, team size
- The decisions: what we chose and why (the architecture reasoning)
- The outcome: measurable results, not vague wins
That last point is what most developers skip. "Improved performance" means nothing. "Reduced TTFB from 1.2s to 80ms, which cut bounce rate by 22%" means everything to the person who has the same problem.
2. Technical Writing That Surfaces in Search
We write about problems we've actually solved. Not tutorials for beginners. Not "top 10 React tips." Specific, opinionated content aimed at the decision-makers who hire senior teams.
A post about Next.js architecture tradeoffs gets found by a CTO evaluating options. A post about multi-tenant SaaS patterns gets read by a founder who just hit that scaling wall. Those are the people who have budgets and need real help.
The bar we set for every post: would a senior engineer find this useful, or would they already know it? If they'd already know it, we're writing for the wrong audience.
3. A Real Domain with a Clear Position
"Frontend developer" is not a position. It's a commodity.
"Architecture-first design engineering studio" is a position. It signals what kind of work we take, what kind of clients we want, and what our opinion is about how software should be built.
When someone lands on PrismaFlux Media, they should immediately understand: this is not a generalist shop that will build anything. This is a studio with a point of view. That filter repels bad-fit clients and attracts good ones.
What the Pipeline Actually Looks Like
The sequence, as it usually plays out:
- Someone searches for a specific technical problem
- They find a blog post or case study
- They read it and decide we know what we're talking about
- They check the portfolio
- They reach out via the contact form or book a call
No cold email. No pitch. No chasing.
The time between step 1 and step 5 varies — sometimes hours, sometimes weeks. But we're not involved until step 5. That's the point.
What We'd Do Differently
Start publishing earlier. We spent the first year of the studio almost entirely on outbound. The content we were avoiding felt like extra work on top of real work. In reality, it was the real work — we just couldn't see it yet.
Niche the writing sooner. Our early posts were too broad. The ones that consistently bring inbound are narrow, specific, and opinionated. If you're trying to reach everyone, you reach no one.
Let the portfolio breathe. We used to update it constantly. Now we update it slowly and deliberately. Three strong case studies outperform ten thin ones.
The Gevgelija Part
Here's the honest version: being based in a small city with no tech scene forced us to build something that works without proximity. That constraint turned out to be useful.
We don't network at conferences. We don't get referrals from co-working spaces. Everything we have came from things we made and put on the internet.
If that system works from Gevgelija, it works from anywhere.
Want to see the portfolio that backs this up? Start here or reach out directly if you have a project in mind.