We are a product engineering partner for companies whose software carries real consequence — insurance policies, payments, patient records, regulated filings. We take products from first conversation to live service, and we stay to run them.
“It’s not about us. It’s all about you and your users.”
Our flagship is a product we own, operate and are accountable for. Everything we have learned about regulated markets, mobile distribution and applied AI went into it — and comes back out into client work.
Romania’s mandatory motor insurance (RCA), plus travel and home cover, bought in about two minutes on a phone. Built, shipped and operated by us.
Client names are withheld under confidentiality. The domains, the scope and the technology are described exactly as delivered.
A European Commission portal governing distribution of medicinal products across EEA member states. Full-stack architecture and delivery across two generations of the platform — portal framework, business process orchestration, reporting and a rebuilt front end.
Identity provider for the public accounts behind one of the world’s largest sports properties: authentication, profile and consent for a very large consumer base, wired into marketing automation and change-data-capture pipelines.
A B2B platform for checking patient insurance eligibility and submitting claims in the US healthcare market. Service architecture, data model and cloud delivery pipeline built from scratch.
An EU-funded platform giving care professionals a shared workflow across web, iOS and Android — one clinical process, three clients, one set of rules.
Structured capture and review of clinical trial feedback, with enterprise directory integration and the audit trail that regulated research requires.
High-volume ingestion and standardisation of third-party odds feeds, odds-setting algorithms, and big-data processing optimisation — plus game-provider and payment integration on the commercial side of the same business.
Full-stack delivery of a duel-based real-money gaming platform, including the real-time transport that keeps opposing players in the same match state.
Consumer-facing ordering experience and payment integration for a B2C food delivery platform, front end through to the transactional back end.
Alongside BOLO we build and publish our own consumer apps and web products — including yantra.world, a React front end over Spring Boot microservices. They are how we try new stacks at our own expense rather than a client’s.
We are engineers first. We are most useful when we own an outcome end to end, but we are equally happy joining a platform that already exists and needs to become faster, safer or cheaper to run.
Discovery, architecture, delivery and launch as one continuous responsibility — not a relay of handovers.
Consumer apps that survive the review process and keep their rating — shipped to every store that matters in your market.
The systems of record and the services around them: transactional, auditable, and built to be operated by people who were not there when they were written.
Infrastructure that a small team can actually run — automated, observable, and boring in the way production should be.
Machine learning only where it removes real work. In BOLO that meant deleting an entire data-entry step and pricing a policy better.
Test automation is not a phase at the end. Quality is a property of how the code was written, measured continuously.
Legacy systems rarely need replacing wholesale. They need a route out that keeps the business running while it is walked.
Someone has to be there at 02:00. If we built it, that someone can be us.
Most engagements start with a short paid discovery. Two to four weeks, and you walk away owning the architecture and delivery plan either way.
Every project is different. These four things are not.
This underpins everything that follows. We research and learn as much as we can about your organisation, your business goals and your users’ needs — before a line of code exists to defend.
We plan to deliver real value in every iteration, and refine against your business plan until it meets your targets. Good design means keeping the design simple from the start and improving it continuously — not getting it perfect on day one and then freezing it. Code review and refactoring are part of the design process, not a tax on it.
Short, repeated development cycles — typically two weeks — that incrementally build the system. This improves quality and production time for projects of any size, because problems surface while they are still cheap.
Once trust is established we scale with the goals: product-centric teams with deep domain knowledge, extended with business analysts, proxy product owners and architects as the work demands, coordinated through practices like Scrum of Scrums or SAFe.
Not a list of everything we have ever touched. This is the set of tools currently carrying live workloads for us and for our clients.
Clever House Engineering is deliberately compact. There is no bench to fill and no layer between you and the people writing the code. The founder is on every project.
Everyone on a project is a practising engineer with production scars — systems in banking, insurance, healthcare and betting where the failure modes are financial or clinical, not cosmetic.
We run internships and train students inside real projects rather than in a sandbox. It is how the Cluj engineering community stayed good, and it keeps us honest about explaining our own decisions.
We present at local meet-ups and conferences, and we follow the ones we do not speak at. Reading and arguing about what other teams are doing is part of the job description.
Our work has taken us from the Netherlands and the UK to Norway, Japan and the United States — as delivery partners, and as guests of the teams we build for. Distributed collaboration is the default here, not an accommodation.
Before Clever House, and alongside it, our people have built internet banking for a Dutch bank, migrated a major European betting platform off .NET and onto Java, worked on mobile synchronisation infrastructure used by Nokia and AT&T, and delivered healthcare systems for one of the world’s largest industrial groups. That is the experience that arrives with us on day one.
Most begin with a short paid discovery — two to four weeks — that ends in a written architecture and delivery plan you own outright, whether or not you continue with us. It is the cheapest way for both sides to find out whether this is a good fit before anyone commits a year.
Write to us with the problem rather than the specification. We will come back with what we think it actually takes — including if that turns out to be less than you expected, or someone other than us.