Comdesk Refresh: Three brands become one platform
Three brands, three websites, three growing content libraries. Not because anything had gone wrong, but because each of them was a success in its own right.
When Comdesk, CallOne and Inopla merged, three providers became one brand. A matching website was the logical next step: a platform that shows the product off clearly, stays easy to manage, and can scale with the business. It has been live since the end of October 2025.
We’ll walk you through how we tackled the moving parts, from setup to content migration to custom modules, and why we put our effort into the setup and the CI/CD pipeline so early on.
The starting point: a strong product, a fresh look
Comdesk is listed as “Top Rated” and a “Leader” in the VoIP software category on OMR Reviews, with more than 100 reviews and a 4.7-star rating. The product is ready, and it has plenty to offer: cloud telephony that grows with the team, a rethought contact center with ACD, native telephony built into Microsoft Teams, and AI-powered automation for call routing, callback logic and follow-ups.
Once the three brands merged, the obvious question came up: how do we bring the whole range under one roof without losing what made each of the individual sites strong? That was exactly our job.
Setting up on the client’s infrastructure: sooner rather than later
The new platform runs entirely on Comdesk’s infrastructure, inside a Kubernetes environment with its own CI/CD. That’s good for operations and security, but it also means setup, build processes and release cycles come with their own quirks. So we decided early on to get the technical foundation in place first, including setup, the CI/CD pipeline and the staging environment, before we built a single page.
It paid off. With the foundation ready early, we could test and validate the new site structure step by step, right in the target environment, instead of running into surprises at launch. At the same time, the client team could work alongside us and give feedback early. That left us enough room to fold in special modules like KPI components or overlays without friction.
The design came from the client. We brought it to life with a custom WordPress theme and several custom plugins, so the editorial team wouldn’t be stuck with off-the-shelf tools but could work with modules built around the brand identity and the product’s actual use cases.
The client owned the design; we were the partner who made it work
The design for the new platform came from the client, specifically from a new design team that had just joined the project. Rather than having the finished result tossed over the fence to us, we were involved from the very start.
We gave feedback early on: where certain implementation decisions would get expensive, where patterns from the WordPress Block Editor would pay off, and where the editorial team might later trip over a particular design choice. And we shared what to watch out for on the web, the kind of thing that isn’t always on the radar in other design disciplines: variable content lengths, responsive behavior, the performance cost of large images, and consistency across many different page types.
The result: the design wasn’t simply “translated.” It was created with a clear sense of how it would be built and maintained down the line. That made things easier for the design team, gave us a straightforward path to implementation, and ultimately left Comdesk with a website that holds together both visually and technically.
Type
Website
Customer
Comdesk
Services
Design Consulting, Front-End Development, WordPress
Period
2025–2026
Modules that the editorial team actually uses
A website for a product with more than 200 features needs content that’s quick to create and easy to find. So we built a handful of templates for different content types, from product pages to use cases to guides, so the editorial team never has to start a page from scratch and can lean on consistent building blocks instead.
The FAQ and how-to sections come with filters, so visitors can jump straight to a topic instead of scrolling through page after page. Forms are wired directly into the CRM, which means inquiries land exactly where they need to be handled. And for data protection, we integrated Usercentrics for consent management, set up for the German audience and the requirements that come with being a provider in the communications sector.
It sounds obvious, and it should. In practice, though, these are exactly the things that cause trouble later if you don’t think them through early.
Content & SEO: audit first, then migrate
The content work ran in parallel with the technical build. Three existing websites meant a lot of content: some of it strong, some outdated, some simply redundant. A one-to-one migration would have been the path of least resistance, but it would have wasted what we’re good at.
So we started with a content audit: What actually gets read? What matters for SEO? What can be consolidated? What’s worth restructuring? We paid particular attention to the Call-One blog, which was already well established and had to keep its visibility through the move. We also rethought the structure of the blog and FAQ, so the three former websites would turn into one manageable information architecture.
The upshot: the new platform isn’t just “new,” it’s discoverable, consistent and easy to maintain.
What matters in the end: hand-offs, not surprises
In a project that spans the client’s infrastructure, multiple brands and three content sources, success doesn’t come from any one clever module. It comes from the hand-off points in between. From day one, we made sure the setup, deployment and migration workflows lined up, instead of slamming together just before go-live.
The platform has been live since the end of October 2025. It’s not just a consolidated website but a foundation the marketing and product teams can keep building on together. The next phase, a smooth self-service onboarding flow, is already in planning.
Do you also have a project that suits us?
Contact us! We are always interested in new challenges.