What is Phokus?

Phokus is an AI driven ecosystem built for sport, turning data into commercial power. It centralises key data sources, unlocking insights that drive smarter decisions and maximize revenue. It enables clubs to understand their customers and fans, allows personalised marketing, increases revenues and strengthens engagement and retention. Simultaneously, it provides essential measurement tools, offering a 360° view of club assets, brand partnerships, and valuations—helping you drive value.

What were the challenges you were facing before Archbee?

We needed a knowledge base that would support our users during onboarding. Initially, we worked closely with customers, but as we began to scale, we required a solution that was easy to set up, allowed for quick article creation, and could be customised to fit our needs. It also had to be scalable and flexible to add new features over time. Plus, cost was always a key consideration.

What made you choose Archbee over the alternatives?

We explored a number of alternatives, some of which were excellent, but we had a few key requirements. While price was a factor, we were willing to pay for value, and Archbee’s startup discount really stood out. It showed an understanding of the challenges founders face and demonstrated a commitment to building lasting relationships through support.

The features were impressive, but as a product-led company, we wanted to test them ourselves—and the sales team was fantastic. The ability to customise, manage internal authentication, and integrate seamlessly was a huge benefit for our engineering team, while the simple, intuitive plugins made content creation effortless for marketing.

All of this gave us confidence that Archbee was the right choice, offering the perfect balance of features, price, and scalability compared to other competitors.

Can you share any business outcomes?

We’ve just launched and are already seeing a reduction in customer support queries. Feedback so far has been overwhelmingly positive, with suggested improvements relating not to the product itself but to how we’ve structured our knowledge base. Fortunately, making these adjustments has been effortless thanks to the documentation, and whenever we’ve needed help, the customer support team has been fantastic.

We’re still in the early stages, but we’re now exploring integrating the knowledge base APIs with our in-app chatbot. We’re excited to test, deploy, and gather feedback as we refine the experience.

‍