Maxim Morev's Success Story: Innovator Founder Visa

Maxim holds an MBA with Distinction from the University of Westminster and brings deep full-stack engineering expertise alongside hands-on experience leading digital transformation projects across multiple industries. He co-founded Snooze Tech with Mateja, where he architected cloud-ready compliance systems for healthcare providers and orchestrated the delivery of a hotel booking and activity management platform for a public sector client. He also led operational transformation initiatives, digitising legacy workflows, migrating business operations to AWS, and improving process efficiency through modern cloud infrastructure. Earlier, he led operations at Electus d.o.o. and managed a 190,000-member community for Sidus Heroes. Synterios is where his technical background, operational experience, and entrepreneurial ambition converge.

‍

What was the key trigger for applying for a visa?

The trigger was realising that our product had to be built here. Mateja and I had already been running Snooze Tech in the UK, which meant we understood the market, the compliance environment, and the genuine appetite among UK enterprises and public sector institutions for what we were building. The problem our product addresses- fragmented, insecure, compliance-heavy information management – is not unique to the UK, but the UK has a particularly well-developed regulatory and procurement landscape that makes it the right first market. Once the product architecture was clear in my mind and we had the business plan taking shape, staying felt not just desirable but necessary.

‍

Why did this particular visa seem the most suitable?

Because I am a builder, not an employee, my entire career has been about constructing things: systems, platforms, processes, and teams, and then making them work at scale. The Innovator Founder route is designed for people who are starting something with genuine innovation at its core, not just a service-based business. Our platform is technically innovative: the combination of five interoperable enterprise modules with a physical hardware security key, deployable on-premise or hybrid, with offline capability, is genuinely differentiated in the market. The visa matched the ambition.

‍

What doubts or fears did you have before the process began?

My main concern was about how to present a deep technical product to a non-technical audience without either dumbing it down so much that it lost its credibility or going so deep into architecture that it became unreadable. Our platform is genuinely sophisticated - the Data Lake module alone combines real-time event streaming, big-data processing, a fully containerised and orchestrated microservices architecture, an enterprise-grade search and analytics engine, and deep integration with external ERP and CRM systems. Making that compelling and comprehensible to an endorsing body that is assessing hundreds of applications was a real challenge. I was also aware that my profile spans several industries and roles: community management, food operations, software development, and cloud infrastructure, and I was not sure whether that breadth would read as versatile or scattered.

‍

‍

What accomplishments did you consider most relevant?

The digital transformation work I led was probably the most directly relevant. I was not brought in as a developer – I was Head of Supply and Operations, but I identified that the operational problems the company faced were fundamentally technology problems, and I solved them by building custom .NET and web applications, migrating the business to a cloud-based ERP on AWS, and restructuring the supply chain. The result was a 7% reduction in operational costs within six months, an 11% reduction in logistics costs, a 30% reduction in co-packing costs, and a 30% year-on-year increase in sales following the website and rebranding launch I coordinated. That combination of engineering capability and commercial outcome thinking is exactly what Synterios needs.

At Snooze Tech, one of my most significant projects was designing a compliant, cloud-native platform for a Norway-based healthcare provider. Handling healthcare data in Norway meant working within a strict regulatory environment, so security and compliance had to be built into the architecture from the outset. I designed a solution that combined Docker-based infrastructure, secure CI/CD pipelines, and robust data protection practices to ensure the platform was both technically resilient and compliant by design. That experience strengthened my expertise in designing secure, compliance-first systems and directly influenced the architectural principles I later applied to the product, particularly its security-by-design and compliance-by-default approach.

Were there any career milestones that unexpectedly played a big role?

My time managing the Sidus Heroes community, growing it to over 190,000 members, driving 150% engagement growth over nine months, surprised people, including me. It looked like an outlier on a technology-focused CV. But what it actually demonstrated was the ability to operate at scale with a large, diverse user base, analyse behavioural data, and make iterative decisions based on real signals. Those are product management skills. They translate directly to thinking about how our platform's user experience needs to work across different organisations, user roles, and compliance contexts.

How did you structure your profile given the diversity of your experience?

The through line I built around was operational intelligence: the ability to understand how an organisation actually works, identify where information flow breaks down, and design systems that solve those challenges. Whether I was improving warehouse management processes, architecting cloud platforms, or standardising processes at Electus, I was consistently focused on the same fundamental goal: replacing manual, fragmented, and inefficient workflows with systems that are structured, scalable, and observable. The product is the natural extension of that experience. Once I framed it that way, every role connected into a clear and consistent narrative.

‍

How did you prepare?

I led the technical architecture sections of the business plan, including the module descriptions, non-functional requirements, system architecture diagrams, deployment models, security design, and integration specifications. This was substantial work, as the plan covered each of the five modules in significant depth, along with the hardware key. I also prepared the technical roadmap and contributed to the pricing model, particularly the licensing structure and the hardware key economics. For my personal narrative, I focused on connecting each stage of my career to a specific technical or architectural capability that directly supports the product and its development.

What was the most difficult part?

Writing the business plan with the level of technical depth it required while keeping it coherent as a business document rather than a technical specification. There is a balance between demonstrating genuine technical sophistication, which strengthens credibility, and making the content accessible and compelling for a non-technical endorsement audience. We had to show that the product is built on a robust technical foundation without making the plan read like internal engineering documentation. Achieving that balance required several rounds of refinement.

What moments pleasantly surprised you?

I was surprised by how much the on-premise and offline deployment capability resonated. I had thought of it primarily as a technical differentiator for government clients with strict data residency requirements. But it turned out to signal something broader: that we had designed the product for real enterprise environments, not just cloud-native scenarios. That showed market understanding, not just technical capability.

‍

What helped you in working with the team?

Tech Nomads helped me understand that the application needed to speak two languages simultaneously: technical enough to demonstrate genuine innovation and accessible enough to be assessed by a non-specialist. They helped me find the right level of abstraction for each section — where to go deep, where to summarise, and where to use plain language to describe something that could easily have become impenetrable jargon.

Where exactly did expert support play a decisive role?

In structuring the innovation argument. It is not enough to have a technically sophisticated product; you have to demonstrate that the innovation is meaningful relative to what already exists in the market. Tech Nomads encouraged us to clearly articulate what makes our solution different, how it addresses challenges that existing alternatives do not, and why those differences matter to customers. That sharper positioning made the innovation claim far more convincing.

Was there anything you definitely could not have done alone?

I could have written the technical documentation. What I could not have done alone was translate it into a visa application that an endorsing body would find compelling. Those are very different writing tasks, and conflating them is a common mistake. The expertise Tech Nomads brought was not just process knowledge but also a genuine understanding of what makes an application persuasive – which is not the same thing as what makes a product impressive.

‍

How did you feel at different stages?

At the start, I felt focused. I had a clear picture of what we were building and why it was the right bet. During the preparation process, that focus became intense — there was a lot of work to do on the business plan, and it had to be right. The technical depth required for each module is not something you can rush. By the time we submitted, I felt confident that we had built the strongest possible case. The wait was harder than I expected. When the decision came through, the feeling was validation, followed immediately by urgency. We had things to build.

What advice would you give to professionals who doubt whether they have enough achievements?

Stop measuring yourself against a CV template and start measuring yourself against outcomes. The question is not what your job title was or which industry you worked in — it is what actually changed because of your work. I reduced costs by specific percentages, grew a community to specific numbers, and architected systems that are running in production today. Those outcomes are concrete and verifiable. If your work has produced real, measurable change, that is an achievement. The task is to document it honestly and connect it to what you are building.

Is there anything you would do differently if you were starting over?

I would invest earlier in documenting the technical decisions I made and the outcomes they produced. Architects and engineers tend to move on to the next problem once something is working. But the evidence of those decisions, why a particular infrastructure choice was made, what problem it solved, and what it cost before and after, becomes valuable later. I had to reconstruct a lot of that from memory. Better documentation habits from the start would have made everything easier.

‍

NEXT STEPS

How have your life and career plans changed since receiving the visa?

The visa gave me the ability to commit fully to recruiting, to clients, and to long-term product decisions. Before, there was always a constraint on how far ahead I could plan. Now, I am not dividing my attention between building the business and managing immigration uncertainty. That clarity of focus is itself a significant change.

What opportunities opened up immediately?

We accelerated conversations with early-adopter clients, particularly in sectors where compliance and data sovereignty are significant concerns: finance, legal, and public sector organisations. The endorsement acts as a quality signal in those conversations. It tells prospective clients that an independent body has examined the business and found it credible. In enterprise sales, credibility is currency.

What are your expectations for this new stage — personally and professionally?

Professionally, I want to get our platform into production environments with real clients who have real compliance challenges, and I want the outcomes to be strong enough to speak for themselves. The product is technically ambitious, and I want to prove that the ambition was justified. Personally, I want to build something that lasts — a platform that institutions in the UK and eventually across Europe rely on for their most sensitive information management needs. That kind of trust is built slowly and lost quickly, and I intend to earn it properly.

‍