No founding legend – just the road these projects actually took.
In the beginning there was no business plan. There was a fridge, and on it, notes. Appointments, shopping lists, who has to be where and when – and every week something fell off, literally and otherwise.
Family organisers exist. None of them matched what such an app should do and, more importantly, should refrain from doing: no location history, no behaviour reports, no advertising, no analytics about children. So it was built from scratch – first for one household, with no intention of turning it into anything.
It got interesting at the forks in the road. The diary in D’App got a PIN that not even parents can reset. The convenient parental master key would have taken an hour to build – and would have cancelled out the entire point. It never came.
Next2Bee posed the same kind of question from the other side. An AI turning an inspection into a diagnosis would have been impressive. It was deliberately not built, because a “probably not that” could keep someone from reporting a notifiable disease. Tools that know what they must not know – that has run through every project since.
One application became several, and several became a shared way of building: our own servers instead of an anonymous cloud, encryption as the foundation rather than an add‑on, parts that travel from one project into the next. At some point it was clear that this was useful to others too – and that MSolutions should be more than a folder full of side projects.
Today the brand is settled, the projects are in beta, and client work is being added. The commercial framework is still being set up. Until it is in place, the imprint would rather show a gap than an entry that is not yet true.
Solutions that connect. Both are meant: systems that work together – and people who can rely on them.
Whatever is not on these pages, we are happy to answer in person.