Insights for IT, integration and e-commerce decisions.

This overview collects what we have learned in IT projects. An article is written here when the same question has been on the table in several projects — not when a topic happens to be in fashion. That is why there are five of them and not fifty. Each one answers decisions that fall before the work starts: whether a middleware pays off, which shop system fits the range, what a procurement procedure settles early, what selling direct really brings in, and how visibility shifts when assistants answer instead of result lists. They are written for people who have to decide and have learned to answer for it.

Which article is useful to you depends on where you stand. Facing a procurement procedure: the public administration article, for the four decisions that fall before the start. Connecting two systems and unsure whether a platform justifies the effort: the middleware article — it counts connections, not systems. A shop is due: the comparison, ordered by range, pricing logic and three years of operation. Considering selling direct and unsure what channel conflicts come with it: the D2C article. Staying visible when an AI answer names two or three sources instead of ten links: the SEO article.

The questions in these articles rarely reach the table early. Most of the time they come up for decision once a deadline is pressing — and then there is no time left to settle them properly. What is written here is an attempt to make them answerable beforehand: not with a recommendation, but with the criteria a decision can rest on. Which figures you need for that is stated in each article.

None of these texts replaces a look at your own situation. They describe patterns from projects, not recipes. Whether a pattern fits depends on the systems, data and people you have today. If your question is missing, a conversation is the shorter way than a sixth article.