We turn validated ideas into products that actually trade.
Not a prototype. Not a pilot deck. A working system with real customers, billing that reconciles, and someone who answers when it breaks. We are a small Dutch engineering company, and we take on the work only where we can genuinely change how it ends.
The idea was never the hard part.
Most of the companies we work with have already done the difficult thinking. They have a signed pilot, a waiting list, an operator willing to trial, or a workflow their own staff already run in spreadsheets. Demand is not in question.
What stops them is the distance between something that demonstrates and something that operates — and that distance is where most software work quietly ends.
- An agency delivers to the specification and leaves exactly where commercial reality starts: billing, entitlements, support load, uptime, data protection, tax treatment.
- Freelancers solve the pieces, but nobody owns the architecture, so the client carries integration risk they were never equipped to hold.
- A consultancy hands over a strategy. The product is still unbuilt.
- A large integrator quotes a number an SME cannot justify, on a timeline longer than the opportunity.
We hold the whole thing — the engineering and the commercial mechanics.
One team, from the architecture to the day the first invoice is paid. Four things we are genuinely good at.
Product engineering, end to end
Architecture, build, integrations and launch — then we stay through the first months of real use, when everything you did not anticipate shows up.
Commercial mechanics
Billing, entitlements, pricing, settlement, revenue share, reporting. The parts that decide whether a product is a business or a demo.
Telecom value-added services
Years of designing, launching and running subscription services with mobile operators in Africa and the Middle East, billed through the operator relationship.
Connected devices and IoT
Devices, gateways, cellular connectivity and telemetry — and estates of screens and sensors kept running across many sites at once.
Services that bill through a mobile operator are their own discipline.
We have built and run video on demand, music on demand, book and audio services, live sports scores, and safety and emergency alerting — delivered over operator networks in African and Middle Eastern markets, on handsets ranging from 2G feature phones to 4G smartphones.
Writing the software is the small part. The work is in the operator commercial model, revenue-share settlement, the subscription lifecycle and churn, bundling, content licensing, and delivering all of it over networks that will not forgive a heavy design.
Very few engineering teams in Europe have actually run a service on an operator’s network. It is the part of our record that is hardest to copy.
There is a great deal we don’t do.
It is the reason we are good at the rest. We are a small team, and the only way that works is to take on a small number of engagements where our judgement measurably changes how it ends.
So we will tell you early and plainly if this is not one of them — which is a better outcome for you than six months of finding out.
We say yes when
- Demand is already validated
- You hold the domain knowledge and we hold the engineering
- There is a real path to the thing operating commercially
We say no when
- The brief is developers by the hour
- The scope ends at a demonstration
- We would be learning the domain at your expense
Tell us what you are trying to get into the market.
A short description is enough to start. If it is not a fit, we will say so in the first reply and point you somewhere better.
Start a conversation