innoframe

Two things, and they belong together. We find the process inside a company that quietly eats hours every week – something recorded by hand, typed up twice, passed between three people – and we automate that one. Not the company. That one process.

And we build the websites: designed, implemented, and looked after afterwards.

The technical side, and the standard we build to. Out of the first big client project came something worth more than the site itself: a documented design system, extracted and generalised, now the starting point for every new project.

Its rules are deliberately narrow. Zero border radius. Flat – no gradients, no glass, no shadows. One signal accent, capped at roughly five percent of the surface, never as text on white. A single easing curve for every motion, and a static fallback wherever someone has asked their system for reduced motion.

Narrow rules are what let a small team move fast without drifting into the look that free templates produce. This site does not use that system, on purpose: it is what innoframe delivers to clients, and a personal site that looks like your own boilerplate proves the wrong thing.

Because it is the product, not the packaging. The automation we build is language work: reading what a company already writes down, understanding it, and turning it into a structured result nobody has to retype.

And there is a second front. When a customer asks ChatGPT or Perplexity who does this work in their region, someone gets named – usually not the company that never thought about it. That is a measurable gap, not a trend, and it is a different discipline from classic search.