Scalable B2B Kentico solution for Koni

Bits Orchestra helped KONI move off a template-locked website and onto a widget-based Kentico architecture that now powers multiple regional sites.
KONI

Project goals

KONI needed to replace an aging B2B website with a scalable solution. The new platform had to fit into ITT Group's existing technology ecosystem, support day-to-day operations without constant developer involvement, and give customers a more modern, usable experience when researching products online.

Result

KONI ended up with a scalable Kentico platform that improved how the company markets its products and manages daily site operations. The architecture was built to extend beyond the original site, supporting additional B2B properties on the same codebase. Post-launch, page views rose 62% and item views rose 67%.

Key results

  • 62% increase in page views post-launch
  • 67% increase in item views
  • 19.7% rise in event count growth
  • 439.9% uplift in clicks on redesigned navigation and CTAs
  • The architecture was designed to extend to future sites without a new development cycle.

About the client

KONI makes adjustable hydraulic shock absorbers; the company describes itself as the inventor of the world's first adjustable version of the product. KONI is part of ITT Group and operates primarily in the B2B manufacturing and automotive supply space.

Business challenge

KONI's existing website was outdated, inconsistent with its brand, and difficult to scale. As the company's main touchpoint for partners, distributors, and customers, the site's limitations had a direct effect on the business. Four requirements shaped the project:

  • Brand modernization. The old site didn't reflect KONI's current brand or offer a strong user experience.
  • Alignment with ITT Group's stack. KONI is part of ITT Group, which standardizes on Kentico CMS. Staying on that platform kept maintenance and operations simpler across the group.
  • B2B focus. The site is a primary channel for partners and distributors, so changes to it carry direct business consequences.
  • Multi-site scalability. The architecture needed to support additional B2B portals down the line, not just the initial rebuild.

Why Bits Orchestra

KONI needed a partner with real Kentico depth, not just general web development experience. Bits Orchestra is a Bronze Kentico Partner with certified developers and a background in manufacturing, retail, and supply chain projects — sectors where B2B websites tend to carry more architectural complexity than typical marketing sites. That combination, along with a full-cycle delivery approach, matched what KONI was looking for in a long-term technical partner.

B2B website on Kentico — but outgrowing the template-based approach?

We've built B2B platforms for manufacturers where the same codebase needs to serve multiple brands, markets, and user roles — without a new development cycle each time.

Solution

The initial scope was a fairly standard templated Kentico build. Once the design was finalized, it became clear that a template-based approach wouldn't give KONI the operational or design flexibility it needed — content editors would have been dependent on developers for anything outside the existing templates. That gap called for a more deliberate approach to CMS development, one built around reusable components rather than fixed templates.

Bits Orchestra pivoted to a widget-based architecture instead. Widgets let CMS users assemble and update pages without new templates or developer involvement, and the same widget library could be reused across multiple properties. That reusability became the basis for building koni.com and group.koni.com from a shared component set, and later extending the same codebase to a separate B2B platform for the North American market. The redesigned navigation and CTAs that came out of this architecture saw a 439.9% uplift in clicks, and event count grew 19.7% post-launch.

Delivery approach

Development ran iteratively, with client feedback built into the process rather than saved for the end. A B2B marketer from KONI's side was brought in early for user acceptance testing, so usability issues surfaced before launch instead of after. Regular feedback cycles shaped navigation, content structure, and component usability throughout the build, and each feature was tested and validated before the next was added.

Technical implementation

  • Kentico Xperience on .NET Core as the CMS foundation

  • Vue.js integrated with Kentico for a componentized, reusable frontend

  • Server-side rendering (SSR) with Vue.js to improve SEO indexing and page load performance

  • Widget-based content architecture shared across multiple sites

  • ASP.NET MVC and Amazon infrastructure supporting the platform

Before and after

Architecture: Before vs. After

Area

Before

After

General

Single-site, template-based Kentico build

Widget-based Kentico architecture reused across multiple B2B sites

Website

Legacy website, outdated and inconsistent with KONI's brand

Modern site built on koni.com, group.koni.com, and a North American B2B platform, sharing the same widget library

Content flexibility

Template-based structure limited design and operational flexibility

Non-technical staff can update product and marketing content directly

Performance & SEO

Not detailed, but described generally as outdated and limiting B2B engagement

Vue.js with server-side rendering supports faster load times and better SEO indexing

Scalability

No shared architecture across KONI's multiple web properties

Architecture designed to extend to future B2B sites without rebuilding from scratch

Team

Bits Orchestra staffed the project with three specialists: 

  • a Kentico technical consultant who handled architecture design, work planning, and task assignment; 
  • a frontend developer who built the widgets and UI components;
  • a backend developer responsible for feature implementation and backend integration.
On KONI's side, a project manager oversaw the process, shared requirements, gave feedback, and participated in testing throughout the build.

Summary

One Kentico widget architecture, built during this engagement, now runs three separate B2B sites: koni.com, group.koni.com, and a North American platform. None of the later sites required a new development cycle — they were built on the same components as the first. For a company weighing a Kentico rebuild across multiple brands, regions, or business units, that's the practical takeaway: the same widget library extends to a new site without starting over.


Website redesign for Koni Example of Kentico website redeisgn B2B platform for KONI by Bits Orchestra

About the project

Client:

KONI (part of ITT Group)

Project:

Company type:

Enterprise

Country:

USA

Timeline:

Jan. 2023 - Apr. 2024

Solution:

Check other case studies