Investimental
active since 2022
a regulated fintech ecosystem spanning onboarding, internal operations, investor education, and trading
A partner for companies redesigning, modernizing, and evolving software systems that support core operations.
We help teams clarify what should change, improve software that already matters to the business, and build systems that can be trusted in production, especially where AI, complexity, and continuity have to coexist. Based in Bucharest, Romania, we work with startups, scale-ups, and established companies that need more than implementation capacity. They need a team that brings structure, engineering judgment, and long-term ownership to software operating under production constraints.
We grew around software that had to work beyond the demo
Control F5 was built on a simple belief: software should be useful, reliable, and built with care.
Over time, the work that defined us was not generic product delivery. It was software tied to operational workflows, internal operations, connected systems, and environments where reliability mattered.
That includes regulated fintech ecosystems, internal workflow platforms, customer-facing reservation and self-service products, AI-enabled information systems, and long-running operational services.
As the company evolved, so did our role. We became the kind of partner clients rely on when the challenge is not just building something new, but understanding what should change, how it fits the wider system, and how it can keep working as the business evolves.
That is also how clients describe us: not just as a vendor, but as a team that gets invested, understands the business context, and helps find better solutions.
The kind of work that shaped us
Our positioning was not invented in copywriting. It was earned through the kinds of systems clients trusted us to design, modernize, and evolve over time.
Again and again, that work placed us in environments where software carried core operational weight.
That includes work such as:
- a regulated fintech ecosystem spanning onboarding, internal operations, investor education, and trading
- long-running operational platforms where continuity and responsiveness mattered every day
- internal systems where reporting, permissions, traceability, and workflow control had to be clear and reliable
- customer-facing reservation and self-service platforms where search, transactions, content, and core business systems had to work together
- AI-enabled media and information products where editorial workflows, publishing operations, and multiple applications needed to function as one system
These projects shaped how we think: clarity before execution, system fit before feature count, and thoughtful decisions under production constraints.
What clients usually rely on us for
Clients usually come to us when one or more of these are true:
- the software spans multiple workflows, systems, or user roles
- the platform supports important day-to-day operations
- the existing system has become harder to maintain, extend, or trust
- the team needs both engineering capability and delivery structure
- a modernization effort has to happen without disrupting live operations
- AI is being explored, but it needs to be integrated in a practical, controlled way
- the work needs continuity, not just short-term output
In practice, that has meant long-running collaborations across regulated systems, operational platforms, customer-facing products, and embedded product environments.
UNTRR / e-rovinieta
active since 2017
a high-continuity transactional platform supporting customers, internal teams, and partner workflows
Travel Planner
active since 2019
a reservation platform connecting search, booking flows, content operations, and core travel systems
Informat
active since 2023
an AI-enabled information system combining publishing workflows, editorial tooling, custom APIs, and mobile products
Bit Soft
active since 2020
an embedded engineering collaboration inside a mature hospitality software environment
How we work in practice
We work as a systems and delivery partner, not just an execution layer. Our process is built to help clients move from uncertainty and operational friction to reliable software in production. That may mean clarifying what should change, redesigning workflows, modernizing an important platform, or delivering a new capability inside a larger system. Clients often mention our responsiveness, communication, and ability to stay flexible when requirements evolve.
1
Clarify
We start by understanding the business context, product goals, workflows, user roles, technical constraints, and where the hidden complexity sits. This stage usually includes business analysis, workflow mapping, solution design, technical scoping, and risk framing. It is where we reduce ambiguity early and create a practical path into delivery.
2
Design, build, and test
We move into structured delivery through backlog definition, UX and system design, team formation, estimation, sprint execution, QA, review, and release preparation. We usually work in two-week sprints with regular planning, reviews, demos, and estimation sessions.
3
Support, stabilize, and evolve
Once the system is live, we continue with maintenance, product adjustments, modernization work, feature additions, and ongoing support. We like long-term product environments because they let software improve with the business instead of becoming harder to change over time.
We typically work in two-week sprints and use an Agile approach with close communication, regular review cycles, and a cross-functional team structure.
The people behind delivery
Stefan Iorgulescu
Founder & Managing Partner
Vlad Moise
COO
This matters because software operating under production constraints usually needs coordinated thinking across product, workflows, architecture, engineering, quality, and operations.
- project and delivery management
- business analysis and product thinking
- technical leadership
- software architecture
- frontend and backend engineering
- mobile development
- DevOps
- QA and testing
- UI / UX
The values behind the name
The name Control F5 reflects the principles we want to bring into every collaboration:
Communication
Good delivery depends on clarity, transparency, and frequent alignment. That is why we work with regular planning, review, and feedback loops.
Trust
We aim to be the kind of partner clients can rely on in both routine delivery work and more demanding system decisions. Trust is built through consistency, responsiveness, and ownership over time.
Respect
We value thoughtful collaboration and honest discussion. Good systems are usually shaped by multiple perspectives working well together.
Loyalty
We take long-term partnerships seriously. Many of our most important engagements have grown over years, not months.
Fairness
We believe healthy collaboration is built on pragmatism, accountability, and mutual respect. That includes giving practical advice, presenting alternatives, and not following a request blindly when there is a better solution.
How we think about quality
Quality is not a final checklist for us. It is part of how the work gets done.
We care about:
- architecture and implementation decisions that hold up over time
- standards and best practices that improve maintainability
- testing discipline and release confidence
- balancing modern tools with technical stability
- workflow clarity, not just code output
- decisions that make future change easier, not harder
For us, quality also includes how decisions get made. Clients often value not just implementation, but the way we listen, clarify, propose alternatives, and help shape a better path forward.
We are interested in useful technology, not trend-driven choices. That includes AI.
We believe AI can improve delivery and product experience, but only when it is used inside a process that still protects quality, maintainability, security, and control. We do not treat AI as a substitute for architecture, QA, release responsibility, or engineering judgment.
Flexible ways of working
We usually support clients in one of two ways:
Project Development
We take responsibility for the full path from clarification and solution design to implementation, testing, release, and ongoing support. This works well when clients want one coordinated team that can connect decisions across disciplines and move the system forward end to end.
Embedded Product Support
We provide specific expertise and engineering capacity inside an existing product environment. This works well when clients already have an internal product or engineering function, but need stronger execution capacity, technical depth, or faster progress in key areas. In the best cases, the collaboration feels like adding a capable extension of the internal team.
In both models, the goal is the same: to become a trusted part of how important software gets changed, delivered, and kept reliable over time.
What clients value in working with us
Clients tend to mention the same things repeatedly: responsiveness, reliability, adaptability, technical depth, and the feeling that we care about the outcome, not only the task list.
A few themes appear again and again:
- Partnership, not just execution — clients describe us as an invested partner, not simply a provider of services
- Responsiveness under pressure — in continuity-sensitive environments, clients value the peace of mind that someone capable and accountable is there when it matters
- Adaptability and communication — teams appreciate that we stay responsive to changing needs while keeping communication clear and regular
- Better decisions, not just faster output — founders and product owners often mention that we help challenge assumptions and improve the initial brief
“Not just a service provider, but a trusted partner in our growth.”
“The team was highly responsive … and was flexible to the client's changing needs.”
“They give us the peace of mind that they can solve even the most unpleasant situations at any time.”
That is the kind of trust we want to earn.
We are usually a strong fit for teams that
- are responsible for software tied to specific workflows, operations, or important user journeys
- want more than isolated development capacity
- need clearer planning before significant change or delivery begins
- care about maintainability, quality, and release discipline
- are modernizing systems that cannot afford reckless change
- are exploring AI in a practical, business-relevant way
- value a long-term partner over a short-term vendor relationship
Looking for a partner to help clarify, modernize, or evolve an important system?
Whether you are reshaping an operational platform, improving an existing product, or exploring where AI can create clear value without losing control, we can help you move forward with the right mix of clarity, engineering depth, and delivery discipline.