Modular Web Infrastructure

Real demand, poorly surfaced

Restoration and service demand existed, but it was poorly surfaced through the existing commerce properties - shops are built to sell products, not to make a service discoverable. The fix was not a better shop page; it was dedicated niche web infrastructure built for that specific intent.

Build once, deploy per niche

The current reusable architecture consists of 21 components. It powers three properties:

• zimmerbrunnen-service.at
• jardin-fontaine.com
• wandbrunnen.at

Two of the properties achieve approximately 90+ Lighthouse scores - a useful quality signal, but not the primary KPI. The primary KPI is whether the service gets found.

Discoverability became enquiries

The result was a measurable increase in restoration enquiries and work in the subsequent period. The system worked because it matched the infrastructure to the intent: a person searching for restoration does not want a product catalog.

The broader pattern - digital problems usually being systems problems rather than page problems - is explored in Most digital problems are systems problems.